B
Barry Watzman
I'm helping a friend who is not local, so I'm doing this by "remote
control", using "remote assistance" whenever possible.
When the friend runs CHKDSK under windows (XP Home), it reports "Errors
Found, cannot repair in read-only mode, run CHKDSK/F to fix" (not the
exact words, but close enough).
I understand that, so we run CHKDSK/F, and it "schedules" CHKDSK to run
at the next restart of the computer, we restart, and CHKDSK runs before
Windows starts, when it has exclusive use of the drive.
The problem is, it apparently is not fixing the problem, because no
matter how many times we do this, CHKDSK under Windows still reports
"Errors Found, run CHKDSK/F to repair".
When CHKDSK does run as the comptuer is starting, the messages that it
prints go by so fast that they can't be read.
Further, while CHKDSK is indicating errors, we have no indication of
what the errors are (the computer itself seems to be running ok).
The Computer is a brand new Dell 8300 with an 80 gig drive, originally
as a single partition, we ran Partition Magic to divide it into two
partitions of about 40 gigs each, but PM didn't finish because it found
problems (error 1555) which is what started this whole thing. It left
with the one partition cut down to the desired size, but the 2nd drive
(partition) not created, rather the 2nd half of the disk was simply
unallocated space (from which the 2nd drive was subsequently created
with a 2nd execution of partition magic).
During the first run of CHKDSK/F, CHKDSK did find and fix some problems
with a few specific files. It referred to these by number, not by name.
However, this has not recurred subsequently, there is no indication of
errors when CHKDSK runs before Windows starts, but the messages at the
end of Chkdsk go by so fast that we can't read them.
Does CHKDSK (run either under windows or during startup) save a log file
from which we could get more detail about the nature of the problems? I
was under the impression that it does, but I can't find it.
Thanks for any help.
control", using "remote assistance" whenever possible.
When the friend runs CHKDSK under windows (XP Home), it reports "Errors
Found, cannot repair in read-only mode, run CHKDSK/F to fix" (not the
exact words, but close enough).
I understand that, so we run CHKDSK/F, and it "schedules" CHKDSK to run
at the next restart of the computer, we restart, and CHKDSK runs before
Windows starts, when it has exclusive use of the drive.
The problem is, it apparently is not fixing the problem, because no
matter how many times we do this, CHKDSK under Windows still reports
"Errors Found, run CHKDSK/F to repair".
When CHKDSK does run as the comptuer is starting, the messages that it
prints go by so fast that they can't be read.
Further, while CHKDSK is indicating errors, we have no indication of
what the errors are (the computer itself seems to be running ok).
The Computer is a brand new Dell 8300 with an 80 gig drive, originally
as a single partition, we ran Partition Magic to divide it into two
partitions of about 40 gigs each, but PM didn't finish because it found
problems (error 1555) which is what started this whole thing. It left
with the one partition cut down to the desired size, but the 2nd drive
(partition) not created, rather the 2nd half of the disk was simply
unallocated space (from which the 2nd drive was subsequently created
with a 2nd execution of partition magic).
During the first run of CHKDSK/F, CHKDSK did find and fix some problems
with a few specific files. It referred to these by number, not by name.
However, this has not recurred subsequently, there is no indication of
errors when CHKDSK runs before Windows starts, but the messages at the
end of Chkdsk go by so fast that we can't read them.
Does CHKDSK (run either under windows or during startup) save a log file
from which we could get more detail about the nature of the problems? I
was under the impression that it does, but I can't find it.
Thanks for any help.