Hans L wrote:

> Hans L wrote:
>
> > Hello:
> >
> > I know, I am weird. I want newly opened applications to steal
> > focus. I know I am weird, because tons of articles on the web is
> > about how not to steal focus, no articles on the opposite. It seems
> > to be a cardinal sin to steal focus. Worse than gluttony, equal to
> > pride.
> >
> > Now, having confessed, I expect you to do the same. You are
> > stealing my 0x000000000(0) (in ForegroundLockTimeout) and replacing
> > it with a value that makes my apps not steal focus.
> >
> > First, I thought it was Tweak IU, but I uninstalled it, and my
> > ForegroundLockTimeout value still changes.
> >
> > Admit it, it is you :-)
> >
> > Okay, maybe it is not you, but would you have any idea what in my XP
> > Home Dell Dim XPS T700 (yeah, it is a little old) does change the
> > value of ForegroundLockTimeout?
> >
> > Regards,
> >
> > Hans L



David & Mungo:

I set HKEY_CURRENT_USER\Control Panel\Desktop\ForegroundLockTimeout to
0x000000000(0).

I set RegMon to log startup changes to the registry.

I got this (and only this) from the log file:


96988: winlogon.exe:748 QueryValue HKU\.Default\Control
Panel\Desktop\ForegroundLockTimeout SUCCESS 0x30D40


I cannot interpret this other than to say that 0x30D40 is the hex
default value for Foreground LockTimeout (200000 ms). However, my
value after startup was (and is always) 0x00002710(10000).

Is it winlogon.exe that sets this value at startup? 96988 is the line
number in the RegMon log file. But what is 748 and QueryValue?

And, more importantly, what can I do about this?

Regards,

Hans L



--