Replacing dialer.exe

[Dave]

Hi!

About 5 years ago, with assistance from some people on this group, I
wrote a custom dialer.exe to replace the built-in one in XP. It's
been working fine for many years, but recently we've noticed that XP
will replace my custom dialer with the built-in dialer.exe. This is
only happening on certain user machines, I think it's because they are
service packed to a higher level than other machines that aren't
having this issue. Basically, it looks like XP thinks that dialer.exe
is a critical system executable, and it wants to restore it if it is
changed. Even worse is that if I delete all instances of dialer.exe
from a computer, XP will still restore the references to it in the
registry so that TAPI calls give an error that it can't find
dialer.exe (my program has a different file name).

So, can anyone tell me how to fix this? I just want to "tell" XP to
leave the dialer alone.

Thanks in advance.

- Dave

[Jack]

lineSetPriority does not work for you?

"Dave" <d...@eliassen.com> wrote in message
news:f44d23d4-8945-4c71...@r9g2000yqa.googlegroups.com...

[Matthias Moetje [MVP]]

Dave,

dialer.exe is indeed a protected system file and should not
be replaced.

Instead you should modify the following registry key to point
at your dialer:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Telephony\HandoffPriorities.RequestMakeCall

Best regards,

Matthias Moetje
-------------------------------------
TAPI WIKI: http://www.tapi.info
-------------------------------------
TERASENS GmbH
Augustenstra�e 24
80333 Munich, GERMANY
-------------------------------------
e-mail: moetje at terasens dot com
www: www.terasens.com
-------------------------------------

"Dave" <d...@eliassen.com> wrote in message
news:f44d23d4-8945-4c71...@r9g2000yqa.googlegroups.com...

[Dave]

Thanks. Sorry - I wasn't clear. I didn't replace the dialer.exe, I
wrote a new dialer program. My program is called "EGIDialer.exe", and
resides in the system32 directory. I did exactly as you said -
modifying that key in the registry. The problem is that XP is
changing that key back to point to the old dialer.exe. It seems to do
it at bootup. If I change the key to point to egidialer.exe, it will
work for a day but then will be pointing back to dialer.exe the next
day. Again, this has been working fine for years, and this issue just
started happening and only on certain new machines that I think are at
a more recent patch level. The other strange thing is that I deleted
the Windows dialer.exe, just to see what happened. I deleted it from
system32 and from the folder where the protected files are stored.
After doing that, Windows still changed the registry back to point to
the old dialer, even though the executable was gone.

So it seems like a recent patch in Windows is causing this. Any ideas
how to fix?

- Dave

On Sep 11, 10:15 am, "Matthias Moetje [MVP]"

<moetje@terasens_nospam_.de> wrote:
> Dave,
>
> dialer.exe is indeed a protected system file and should not
> be replaced.
>
> Instead you should modify the following registry key to point
> at your dialer:
>

> HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Telephony\Hando­ffPriorities.RequestMakeCall

>
> Best regards,
>
> Matthias Moetje
> -------------------------------------
> TAPI WIKI:http://www.tapi.info
> -------------------------------------
> TERASENS GmbH

> Augustenstraße 24

> 80333 Munich, GERMANY
> -------------------------------------
> e-mail: moetje at terasens dot com
> www:  www.terasens.com
> -------------------------------------
>
> "Dave" <d...@eliassen.com> wrote in message
>
> news:f44d23d4-8945-4c71...@r9g2000yqa.googlegroups.com...
>
>
>
> > Hi!
>
> > About 5 years ago, with assistance from some people on this group, I
> > wrote a custom dialer.exe to replace the built-in one in XP.  It's
> > been working fine for many years, but recently we've noticed that XP
> > will replace my custom dialer with the built-in dialer.exe.  This is
> > only happening on certain user machines, I think it's because they are
> > service packed to a higher level than other machines that aren't
> > having this issue.  Basically, it looks like XP thinks that dialer.exe
> > is a critical system executable, and it wants to restore it if it is
> > changed.  Even worse is that if I delete all instances of dialer.exe
> > from a computer, XP will still restore the references to it in the
> > registry so that TAPI calls give an error that it can't find
> > dialer.exe (my program has a different file name).
>
> > So, can anyone tell me how to fix this?  I just want to "tell" XP to
> > leave the dialer alone.
>
> > Thanks in advance.
>

> > - Dave- Hide quoted text -
>
> - Show quoted text -

[Matthias Moetje [MVP]]

Dave,

I don't believe that MS has introduced such a functionality
in a patch, that wouldn't really make much sense.

If you say that this value is overwritten during Windows
start (or probably rather "user logon") I would consider
these two possible reasons:

- Group policy: Group policy settings are applied during
logon and this setting might be defined via group policy

- Autostart programs: You can use autoruns.exe to disable
all programs which are run at startup to see if it is one of
these programs that changes the key

Best regards,

Matthias Moetje
-------------------------------------
TAPI WIKI: http://www.tapi.info
-------------------------------------
TERASENS GmbH

Augustenstra�e 24

80333 Munich, GERMANY
-------------------------------------
e-mail: moetje at terasens dot com
www: www.terasens.com
-------------------------------------

"Dave" <d...@eliassen.com> wrote in message

news:a3ba2a97-723f-40ef...@z30g2000yqz.googlegroups.com...

>> Augustenstra�e 24