Z
zeke7
All I get is a blinking cursor. Here's what happened:
Just finished a fresh single-partition NTFS-format and Windows 2000 SP4
install on a Maxtor 80gb IDE drive, fully Windows-Updated it, and loaded up a
suite of programs. During the numerous reboots required, it always booted
fine and everything was running smoothly.
From the C: drive Properties/Tools menu in Explorer, ran Error checking
(with no switches); it reported no problems. Then ran Defragment in analyze
mode. It reported bad fragmentation, so I booted into Safe Mode (for access
to as much of the disk as possible), deleted as many temp files as I could
find (Temp Internet files, \Docs & Settings\Administrator\Local
settings\Temp, \WINNT\Temp), and ran Defragment.
It defragged fine, very clean-looking result, then ran Error checking again
with no switches, it reported no problems. Next step was to create a
Emergency Repair Disk, but unfortunately I rebooted first.
Now the disk won't boot: I get a blinking cursor in the upper-left corner,
which quickly drops down to a second line, and remains blinking; no progress
from there.
My inclination is to run the Recovery Console from the boot disks, and my
question is which command should I run from there: Fixboot or FixMBR?
I don't want to make unnecessary changes to either one. MS-KB and elsewhere
seem to indicate that FixMBR is more for virus damage to the MBR.
I can run the drive as a slave from another disk (with the same OS install):
Error checking still reports no problems, Defrag analyze mode reports the
same clean result, all files (including the C:\root) look intact and read
fine from Explorer, and an Avira virus scan detects nothing.
Just finished a fresh single-partition NTFS-format and Windows 2000 SP4
install on a Maxtor 80gb IDE drive, fully Windows-Updated it, and loaded up a
suite of programs. During the numerous reboots required, it always booted
fine and everything was running smoothly.
From the C: drive Properties/Tools menu in Explorer, ran Error checking
(with no switches); it reported no problems. Then ran Defragment in analyze
mode. It reported bad fragmentation, so I booted into Safe Mode (for access
to as much of the disk as possible), deleted as many temp files as I could
find (Temp Internet files, \Docs & Settings\Administrator\Local
settings\Temp, \WINNT\Temp), and ran Defragment.
It defragged fine, very clean-looking result, then ran Error checking again
with no switches, it reported no problems. Next step was to create a
Emergency Repair Disk, but unfortunately I rebooted first.
Now the disk won't boot: I get a blinking cursor in the upper-left corner,
which quickly drops down to a second line, and remains blinking; no progress
from there.
My inclination is to run the Recovery Console from the boot disks, and my
question is which command should I run from there: Fixboot or FixMBR?
I don't want to make unnecessary changes to either one. MS-KB and elsewhere
seem to indicate that FixMBR is more for virus damage to the MBR.
I can run the drive as a slave from another disk (with the same OS install):
Error checking still reports no problems, Defrag analyze mode reports the
same clean result, all files (including the C:\root) look intact and read
fine from Explorer, and an Avira virus scan detects nothing.
