Problems with Win2k Pro Scandisk.

[elfnumber1]

As the title states, I am having problems with the scandisk utility running ALMOST everytime I boot the computer up. This is the scenario:

Shut down my computer properly, then I turn it on after a few minutes. It always finds some errors and truncates unnecessary files or whatever it does. Anyhow, I suspect that it's the shut down process that is the problem. Could it be that during the shut down process, the HDD shuts down before Windows saves all that it saves when it shuts down?

Some help please! Thanks.

elfnumber1

 

[Ausm]

Try defragging your Hard drive


Ausm

 

[elfnumber1]

That does not help. Defragging is done approx once a week, if not more. Solution to problem is still out there. Anyone help on this one?

 

[Snapster]

Make sure your cables are correctly plugged in and you're not draining too much power away from the hd. I sometimes had a similar problem because I was splitting the hd power lead, worked fine once I gave it a dedicated lead.

 

[elfnumber1]

Welps, by dedicated lead you mean having the HDD and only the HDD connected to the PSU via the cords. I have it connected this way: HDD and floppy. I will try it on single...

elf

thanks

 

[IceCreamMan]

Call me confused, but since when does scandisk run on Win2k?

 

[elfnumber1]

Sir, if you shut down your computer improperly, you will notice an automatic scandisk run on your HDD. This is true for WinXP as well.

elf

ps: i tried running the HDD on a dedicated power cable, still does it. runs scandisk everytime i shut down and boot up again. i'm thinking it could be a bios setting or an OS setting. help!

 

[azkiwi]

maybe something in startup is causing the problem - seems more likely than shutdown. A corrupt system file, a virus...

 

[Epyon9283]

I had that problem too... The only way I could fix it was by reinstalling win2k. It was so annoying nothing I did had any effect on it. It was shutting down correctly, the hard drive was fine, and there was more than enough power.

 

[elfnumber1]

Yeah it could be that problem, but I don't remember the win2k msconfig prompt so I can't see what's starting up. And I'm sure a format and reinstall of win2k would do the trick, but I have files that need backing up. Anyhow, guess noone really knows without having the system in front of them...

elf