Didactylos...



I sure would not get my points if people of similar minds as yours, with all due respect, would be the judge.

While other folks in this thread responded with looking at the situation and putting in some ideas that may help correct (or otherwise understand) the problem, your posts stands out by its looking at the other direction and is held firmly there by your continuing belief that the situation is, as the first sentence in your original post response may have aptly put it -- "unfortunate".

If only we don't throw in the towel so easily, or so readily.

Flange...


Thanks for responding.

Yep, I think that was it: essentially a hardware-induced issue. I shall post some details as soon as I get this verified.


andzgrid

Victors…

Recalling the situation to the best of my memory and after some deliberation, I can now say with a reasonable degree of certainty, that the problem was brought about by a transient RAM memory error. This in turn was brought about by water condensing near and around the areas of the motherboard with temperatures higher than the ambient temperature. The greater the temperature difference, the more the extent of the condensation; that means the processor and the memory chip modules—two of the devices that generate the highest temperature amongst all other devices in the motherboard.

I rule out the CPU as one of the items affected in light of the following: 1) The WinXPP operating system was still functioning; all the normal routines (mouse movement, response to click, and/or type, launch and close of apps, etc) were still there. 2) The processor has a heatsink that also serves to trap the condensation that otherwise would have gone to the exterior CPU chip metal housing.

That the RAM modules were possibly affected can be seen from the following: 1) The text editor app I was using displayed a non-blank text file as blank. 2) Unlike the setup for the processor, the setup for the RAM modules I am using is barren, thermally speaking; it does not have a fan-heatsink combination.

That the issue was a transient one is supported by the fact that after some hours and after reinserting the RAM modules, the machine was back to normal operations with none of the earlier symptoms since. The damage done, if any, turned out to be non-permanent and fully reversible.

Except for the UDMonitor software, which brings me to my next point—the UDMonitor-created backup.

The text file earlier mentioned was intact; it was as if nothing happened. All the apps and other data files remained intact as if nothing happened, all except for the data files under UDMonitor.

I recall using the restore (from the UDMonitor-created backup) function when the WU was aborted, but nothing was restored. I had three (3) UDMonitor-created backup copies but each one failed to restore the WU.

I have no idea how many people using the UDMonitor can vouch to that UDMonitor backup failing to restore a backup copy of the WU in case of a WU abortion.

A backup would have saved what would otherwise be an aborted WU.

So, where does that leave us? I say: a working backup solution. I'll take this to the author of the UDMonitor software.

For now, I thank everyone for their time and patience. We do it all to help find a cure for diseases and together, we shall win!

andzgrid