Tim Slattery said:
This is my office machine, and it's *very* locked-down. We don't seem
to have gadgets. Or maybe they're hidden someplace I haven't looked
yet.
There is no clock.exe file in Windows XP. That app came from somewhere
else, like you downloaded it. Doesn't it's Help -> About menu say who
wrote it (so you could see if they have updates)?
If your workstation is locked down, why are you allowed to install or
copy software on it that is not on an authorized list?
Do any of the other apps for their window also try to stay "always on
top"? You could have apps battling for the z-axis position.
http://en.wikipedia.org/wiki/Z-order
I believe z-order is an attribute of a window object. So it's possible
on app could still change the z-order of a window for a different app.
Your clock app might not even be using z-order but a much clumsier
method of polling its focus attribute: if the window isn't focused then
make it so. That is, the app keeps trying to steal back focus.
For Windows XP (using TweakUI XP to create a registry entry), you could
configure Windows NOT to allow focus stealing. It would modify:
Registry key: HKEY_CURRENT_USER\Control Panel\Desktop
Data item: ForegroundLockTimeout
Alas, every Windows version after XP ignores that registry entry so
focus stealing has been a long time complaint with Windows 7. MS devs
claimed that Win7 was not supposed to allow processes to steal focus
(and modified the flashing button behavior in the Windows taskbar) so
they removed support for this registry entry and assume it is always 0
(zero). By the way, zero was the value back in WinXP that *did* allow
processes to steal focus. Well, turns out they did NOT fix apps from
stealing focus.
Microsoft doesn't want to rely solely on a blinking button in the
Windows taskbar to notify users that a process wants its window to have
foreground focus. The example they provide is anti-virus software. Say
you start a copy operation for a couple dozen files. The AV scanner
finds one that is infected. It opens an alert window to tell you about
the infected file. If the AV's alert window couldn't rise its z-axis to
the top for you to see it, you would see the copy operation hang and not
know why. The AV's alert window would be behind Windows Explorer that
was doing the copy but is now hung because the AV scanner is pending
that file's copy operation waiting for you to make a choice (Ignore,
Delete, Quarantine). So "always on top" isn't an absolute window
positioning method.
I've heard of (but not used) a few utilities that attempt to alter focus
stealing and might work with your unidentified clock program. They are:
PowerMenu:
http://www.abstractpath.com/powermenu/
Window On Top:
http://www.skybn.com/
Deskpins:
http://www.snapfiles.com/get/deskpins.html
Personally I'd check if the author of the unidentified clock program to
see if they have an update that uses a different "always on top" method.