"WMS Idle not responding."
Some observations:
Upon System "Shutdown", warning that WMS Idle is not responding, i.e. remains active.
Does this occur because MSOutlook, or another program that invoked WMS Idle, has left a live thread or socket descriptor unterminated ????
If so, can this dangling software be tracked down ??
It should be possible -- though I don't know the procedure to do that kind of analysis.
Actually, that was easy to do on UNIXs.
MSWindows op sys design is apparently still pretty sloppy -- like its predecessor MS/DOS.
Maybe VISTA is better, although I haven't gotten that impression.
MicroSoft, where is your pride???
Or is that as ephemeral as your claimed quality -- belied by the CAVEAT EMPTOR "Buyer Beware" poliicies (as implied by the EULA/Licenses -- whereby only the buyer accepts responsibility for effects of MSWindows operating system faults).
Some apparent solutions have been found by users (above comments),
but the implications are draconian.
One user found that de-registering NERO seemed to stop the appearance of the WMS Idle errors,
at least temporarily.
But that means the user cannot burn CDs and DVDs.
What are you going to do about backups ?? !!
Consider also:
For all, or at least most, of the reported dangling WMS Idle faults (mostly upon System Shutdown processing), they started occuring some time after a new Windows XP installation.
For my Windows XP Pro, it was several weeks after installation.
Since I was using Windows Outlook regularly in the meantime,
it appears that the fault is an artifact generated somehow (by unknown process),
that thereafter survives re-booting.
Any more ideas, anyone ??
Robby Bloom
Last edited by robbybloom; 14th Apr 2008 at 11:45 AM..
|