R
Ron Miller
Scenario:
1 -- Ran Bootviz on my XPSP2 machine; didn't work; said it couldn't
find the .BIN file that should have been generated.
2 -- Started getting warnings that I had no more room on C:
3 -- TreeSize utility led me to a newly created trace-log file under
System32\Log files\WMI. It was TWO GB in size. The file by the same
name that it replaced had been a mere 20 Kb.
4 -- Couldn't delete the 2Gb file 'cause it was "in use." I couldn't
see an active app or process that might be using it.
5 -- Tried to Restart, but nothing happened after POST. I got no
error message, just a blinking cursor
6 -- Because my XP C: drive is FAT32, I booted from a WinME-DOS boot
floppy. I could get a C: prompt, but the DIR command returned the old
Abort-Retry-Fail message as though the drive had no file structure to
read.
7 -- Booted to Linux on another partition. The Linux file manager
could see the C drive but showed only one directory on it other than
System Volume Information, and it was not the Windows directory. It
was obvious that a catastrophic failure had occurred.
8 -- Used Acronis True Image 8 to restore the drive from yesterday's
backup, and all's well (there was no data stored on the C: drive).
Questions:
1 -- Didn't Bootviz kill my computer?
2 -- If so, how would creating a file that took up all the space on
the drive render it unbootable and mostly destroy its file structure?
Ron
Ron
1 -- Ran Bootviz on my XPSP2 machine; didn't work; said it couldn't
find the .BIN file that should have been generated.
2 -- Started getting warnings that I had no more room on C:
3 -- TreeSize utility led me to a newly created trace-log file under
System32\Log files\WMI. It was TWO GB in size. The file by the same
name that it replaced had been a mere 20 Kb.
4 -- Couldn't delete the 2Gb file 'cause it was "in use." I couldn't
see an active app or process that might be using it.
5 -- Tried to Restart, but nothing happened after POST. I got no
error message, just a blinking cursor
6 -- Because my XP C: drive is FAT32, I booted from a WinME-DOS boot
floppy. I could get a C: prompt, but the DIR command returned the old
Abort-Retry-Fail message as though the drive had no file structure to
read.
7 -- Booted to Linux on another partition. The Linux file manager
could see the C drive but showed only one directory on it other than
System Volume Information, and it was not the Windows directory. It
was obvious that a catastrophic failure had occurred.
8 -- Used Acronis True Image 8 to restore the drive from yesterday's
backup, and all's well (there was no data stored on the C: drive).
Questions:
1 -- Didn't Bootviz kill my computer?
2 -- If so, how would creating a file that took up all the space on
the drive render it unbootable and mostly destroy its file structure?
Ron
Ron