Printable View
I have a Compaq Presario, with 1 gig of RAM, and recently I try to run chkdsk with both options chosen. Usually it runs the next time I boot up, but the recently it starts but say it can't access C drive directly. I downloaded and ran the quick and the extended test with Data Lifeguard Diagnostics for Windows and it said everything passed. So I don't really think I have a problem with the disk.
I would sure appreciate some help on this. Thanks!
What's the exact error message...
Well..it starts to go into chkdsk, then it stops and says something along the lines of, "unable to access 'C' directly". I can't remember exactly, but that's close, and then it goes on to the logon screen.Quote:
Originally Posted by Ya_know
Just a heads up, if you have less than 10% free hardrive space you can run into a number of errors running scandisk or Defragmenter. The fix is removing stuff from your hardrive. This may not be your situation but I thought I would point it out.
Thank you!! That is a good thing to know for the future, I wasnt aware of that fact. I have 120gig hard drive, with 96.2 gigs still free, so probably not the problem....I hope!! https://forums.windrivers.com/images.../2005/03/1.gif Thanks for the info!Quote:
Originally Posted by Richard1
Try running chkdsk from the Recovery Console.
type chkdsk c: /p
for a full surface scan.
I haven't tried from the recovery console, but I have done it through the 'run' command. It ran in a dos window, but I don't think it repairs errors that way...or does it?Quote:
Originally Posted by techs
Are you checking the box that asks if you want to fix errors automatically? If so, then Checkdisk cannot run until you reboot the computer. You can run Checkdisk in windows, but remove the check mark.
Yeah, I usually want it to run next time I reboot, but when I do reboot, it starts but then quits and goes to the logon screen. It didn't used to do this, it has been a recent development.Quote:
Originally Posted by cgonzo