Outlook 2003 and Registry

[Sümer Yamaner]

Hi,
Outlook 2003 keeps changing the registry key
HKCU\ControlPanel\Desktop\ForegroundLockTimeout to 0x12fb84. After I
manually reset this value to 0 and restart Outlook, the key is being changed
to 0x12fb84 again. How can I prevent this behaviour?
Thanks.

Sumer Yamaner

 

[Milly Staples [MVP - Outlook]]

How do you know Outlook is doing this?

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Sümer Yamaner asked:

| Hi,
| Outlook 2003 keeps changing the registry key
| HKCU\ControlPanel\Desktop\ForegroundLockTimeout to 0x12fb84. After I
| manually reset this value to 0 and restart Outlook, the key is being
| changed to 0x12fb84 again. How can I prevent this behaviour?
| Thanks.
|
| Sumer Yamaner

 

[Sümer Yamaner]

It is interesting...
During the last few weeks I have asked some questions in these newsgroups
and all I got was "how do you know this, why do you want to change this, why
are you bothering about this, etc."
Regarding your question:
There are some ways to do this. You can make a list of the suspected
programs and check the registry before and after the launch of these
programs one after another.
I am SURE that Outlook 2003 is responsible.
I manually reset the registry value. Wait a couple of minutes and check that
it is set to "0". Then I launch Outlook 2003 and recheck the registry value
to see that it has been changed.
So... I think this is an adequate explanation. Now, if you have a suggestion
I would be glad to hear about it.
Thanks.

"Milly Staples [MVP - Outlook]"

 

[Milly Staples [MVP - Outlook]]

You know, when you come to strangers, state something as fact, and the
stranger (me) asks to know how you know this (as would any other reasonable
person) and gets an answer such as yours, my immediate response is, go
figure it out for yourself.

If you can't be bothered to answer a civil question with a civil response, I
can't be bothered to volunteer my time to research an answer for you.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Sümer Yamaner asked:

| It is interesting...
| During the last few weeks I have asked some questions in these
| newsgroups and all I got was "how do you know this, why do you want
| to change this, why are you bothering about this, etc."
| Regarding your question:
| There are some ways to do this. You can make a list of the suspected
| programs and check the registry before and after the launch of these
| programs one after another.
| I am SURE that Outlook 2003 is responsible.
| I manually reset the registry value. Wait a couple of minutes and
| check that it is set to "0". Then I launch Outlook 2003 and recheck
| the registry value to see that it has been changed.
| So... I think this is an adequate explanation. Now, if you have a
| suggestion I would be glad to hear about it.
| Thanks.
|
| "Milly Staples [MVP - Outlook]"
| || How do you know Outlook is doing this?
||
|| --
|| Milly Staples [MVP - Outlook]
||
|| Post all replies to the group to keep the discussion intact. All
|| unsolicited mail sent to my personal account will be deleted without
|| reading.
||
|| After furious head scratching, Sümer Yamaner asked:
||
||| Hi,
||| Outlook 2003 keeps changing the registry key
||| HKCU\ControlPanel\Desktop\ForegroundLockTimeout to 0x12fb84. After I
||| manually reset this value to 0 and restart Outlook, the key is being
||| changed to 0x12fb84 again. How can I prevent this behaviour?
||| Thanks.
|||
||| Sumer Yamaner

 

[neo [mvp outlook]]

Do you have any other programs installed that might be responsible for this
behavior? The reason that I ask is that I can't duplicate. Also Microsoft
has it published that the default value for this setting is 200000 (or
0x30d40).

By the way, rather than start Outlook and look. I've found that the
freeware tool of Regmon (http://www.sysinternals.com/Utilities/Regmon.html)
is much better to zero in on what might be accessing/changing registry
values.

/neo

PS - don't forget to look at addins to Outlook.

 

[Sümer Yamaner]

Thank you very much for your suggestions. I have already checked the addins
to Outlook and there are no strange ones. I am downloading the application
now and will try it.
Thanks again.

 

[Sümer Yamaner]

My best wishes and thanks for your help...
I think it is obvious who is not able to answer a "civil question" here...

"Milly Staples [MVP - Outlook]"

 

[Sümer Yamaner]

Oh my god... There is an unbelievable registry traffic here ) I am trying
not to lose my focus... It will be hard but I will find the source.
Thank you very much again...