Too Many Win32 Handles
TaskInfo (alternative to Microsoft's inept Task Manager) shows the following while I'm 1G of the way to a 40G restore. This condition also appeared during backup, going maybe 5 times over the warning threshold; but now it's over 100 times, and still rising steadily. Looks ominous.
This could be an aspect of this machine being XP which I continue to hang on to on one machine because I like being productive, though I understand that the world is not on my side, thank you #%$^&*&* Microsoft you @$$#01=S. Acronis needs to be aware that XP users still exist (many millions still, I have read) so they should duly test the effect on XP machines if they're going to claim to be compatible with XP. I would imagine that only the most superficial XP testing is being done nowadays for most mainstream software vendors; hopefully Acronis does better. (I'm suspicious; one of my apps stopped working on XP approximately the day that I installed TI 2016 and ran its first backup. That's why I'm doing the restore anyway, on the very faint hope that something happened *after* the TI installation to wreck the app. However it's highly likely that the TI 2016 installation on XP killed it.)
Hey I like this preview interface! I can copy and paste from it!
Looking at the restore I have files like
SESSIO~1.JTR
The restoration changed that name to
SESSIO~1.JTR~KRKKUAM5
IT did that on a lot of files in the first directory I checked. Disturbingly, it didn't *add* the alternately named file; it *replaced* the filename with the extra ~KRKKUAM5.
I don't want to be a baby but I can't believe that critical protection software would do anything like that.
Maybe I was over alarmed about this maybe being about XP, sorry to spout off, but whatever this is, OMG.
Another new odd filename:
6,164 qmgr0.dat~MKRMDDVE was restored, but
4,232 qmgr0.dat is still there. This looks like a case where there was a conflict so a new file (restored from backup) was created. Is that how it's supposed to work?
After a couple of hours checking: if the specified directories that I commanded to restore were restored alphabetically, then it appears that the renaming damage is limited to \documents and settings, if that means anything to anyone. Actually, it seems to have crashed within that tree.