siliconman01, that makes sense that both processes are in memory at the time. WW.EXE is waiting for DL.EXE to complete. When you kill the DL.EXE process, it does not have the chance to tell WW.EXE that it completed, so WW.EXE keeps waiting for that message. The desktop magnet feature is fairly new, so there could be an issue there somewhere. I’ll dig around some and see what I can find.
I’ve often wondered why “Only attempt to download data when an Internet connection is found” is even an option. It would seem to me that ww.exe/dl.exe should never try to download data if there is no Internet connection found. That should be the default action. JMO
Perhaps ww.exe needs a message timer that fires off if it does not receive the message from dl.exe within a specified time frame. Then ww.exe would not “hang” indefinitely with high CPU cycles. One time period for cable\dsl and a longer one for dial-up.
It doesn’t… on most computers. That setting is quite old, and is really of no use for most people.
That’s kind of what happens now, but the timer is in DL.EXE. I suppose it’s possible that DL.EXE fails to successfully launch sometimes. If that is happening, WW.EXE might be hanging at that point.
Here’s a new Weather Watcher Live build that includes some more error handling around the download processess. You can install this build over top of your existing Weather Watcher Live installation.
Okay, I admit I’m an idiot!!! You know what my problem was?— I had turned off the “User Account Control” in Vista a few weeks ago. I did not realize that programs and settings I had made BEFORE disabling it would be affected. Once I turned it back on, I lost any changes I had made since! I told you I thought it was ME instead of WWL!!! ](*,)