PawPrint.net Forum

I have had several instances where I have installed Worldtime (various releases) on Windows XP Machines.  Sometimes as a New Build, sometimes as a requested install.  Immediately after the installation, the START, RUN feature of Windows ceased to work.  However, WinKey,R does work.  Removing Worldtime solves the problem. Not having Worldtime Autostart means that Start,run works till it is started.  The problem is reproduced on each of these machines EVERY time WT is installed and starts.  Other machines with XP work fine.


Thoughts?

Chris.

I just ran into the same problem. I have been using WT v5.5.2.748 with XP for years with no problems. I recently enabled the "Titlebar Clock" feature of WT. As soon as I did, the "Run.." & "Search" apps on the "XP" style start menu stopped working. Even more bizarre, if I switch to the "Windows Classic" style of start menu, "Run.." & "Search" work correctly. Once I disabled the "Titlebar Clock" feature and rebooted the system, the "Run.." & "Search" apps started working again on the "XP" style start menu! So I can still use WT...I just can´t use the "Titlebar Clock" feature.

I wondered what was causing it... It is a frustrating experience trying to search the net for problems with "Start | Run", as you get Waaaaaay too many false hits.

After reading your post, I promptly uninstalled WorldTime, cycled my login and Yahtzee! Problem solved.

My WorldTime version: 5.5
OS: XP-Pro (SP2)

I initially noticed the behavior back when I installed XP-Pro (SP1). I have no idea how or why WorldTime would moof the "Run Dialog", but as you say, Winkey-R still worked. I tried rooting through the registry to see what key was altered during the WorldTime install to "turn off" the "Start | Run" dialog. It reeks of a security setting that can be used to lock-down the feature. Pure guess is that when they were developing the install "script", they locked the Start-Run feature (perhaps) to prevent anything else from running & conflicting during the install -AND- they forgot to un-lock it after the install.

It´s not a "show-stopper" of a problem, but it is quite the nuisance. It should be an easy fix before the next compile.

-=JD=-