Maybe I am the only one with this, then I know it is on my pc…
Most of the times when I try to exit or exit/save WD, the program is closing but the process keeps running.
This is very inconvenient when you installing an update.
Peter
try using task manager to kill the process (right mouse click on the task bar to bring that up or go ctrl alt del)
has this got worse lately?
That is what I do to kill the process. :?
But I wasn’t sure if it will damage WD or any setting.
(Maybe you remeber that my WD was doing strange things so I had to make a clean install.)
This is not getting worse latley.
I don’t have it with all the time.
Peter
Been happening here about 50% of the time. Usually after I get errors in the programerror log…
FWIW, I just recently started having this happen to me on a semi-regular basis. Using task manager to kill off the process here.
I think it happens about 75% of the time over here.
And it is not recent when this started for me.
Can’t even remember when…
i think i might have fixed this
uploading 10.20o now
I just did a test (as I too have had the stuck process with the exiting of WD)
and it looks to be fixed 8)
10.20o
ready soon :o
Just tried ‘o’ version and no change, still hangs and even takes about a minute to do the Save/Exit process, then when it does exit, it is still processing.
After running it for about 10 minutes, I finally gave up on this version. CPU was 100% for 80% of the time running. You couldn’t get around in WD at all. Finally gave up on my test system. Even shuting down, WD it remained in the job stream and had to force it out fo the process. In my opinion-not a good version at this point.
I’m definitely not loading to my live system. 
i cant think of anything that would cause the high cpu useage
and this morning no reports of it
maybe just a one off…or something else…anything under view, program error log?
its running here OK
Nothing in the error log.
still no other reports like what you are seeing losmon
I can conform that WD did exactly this on exit with version 10.20o (about 10 minutes ago). I’ve noticed this happens fairly frequently when I try to exit WD, there is no message in the error log when this happens.
However it is only mildly inconvenient as I always keep task manager running and can see when it hit’s 100% and can easily kill the process. I just assumed it was a glitch in my computer and so far I’ve always restarted with no problems.
WDv10.20o
I have not seen this problem.
Win 2000 Pro Service Pack 4, Celeron 900, 768MB RAM
Is the Real time Client raw FTP running? Or WD Watchdog? I terminate the Real time Client raw FTP and WD Watchdog before I exit WD.
I have everything running, realtimeclient, WD Watchdog and MYSQL update
Normally I close WD first then Watchdog, then MYSQL, then realtimeclient. I’ll try closing them in the sequence you suggest and see if it fixes the problem. Again it’s only a minor annoyance as it only happens when I come to close everything down and is easily rectified.
it might be if a the direct web cam capture is used…
i myself have trouble with wd closing too
not sure why,.,…it steps all the way through to the compiler to the close command…and if after that that it has trouble…
Not sure if it helps or not, but I do not use the direct web cam capture and have the problem about half the time. I just kill the process and everything is fine. I have never just let it run and see if it eventually ended, but I will do that next time. The last version I exited out of was M, but I have not exited out of O yet.
On my test system, when WD is running, no FTP, no Cameras, I’m using the realtime client to communicates to my llive system. When at 100% you can’t do anything inside of WD until the lull that happens for about 10 seconds, then it climbs back up there at stays approximately 45 seconds.
I can bring WD up, wait 30 seconds, then using the Save/Exit and it clears just fine. Beyond a minute of being alive, then I have to use Task Manager to kill the process. after waiting a good minute or two waiting for it to shutdown. Then I go in and kill the process.
can you try a re install on the test system…
something might have got corrupted
Will do…
I’m willing to try anything at this point.