Win2K cannot chkdsk one partition

[deep-in-the-forest]

Running multisystem. One system is Win2K. In Win2K partition "D" which is boot partition for Win2K and is NTFS, the system will not run chkdsk in command line window and says that partition is locked. If you try to tell the system under My Computer that you want the partition checked upon next bootup, it will not do it but proceeds to boot as normally. IT WILL do a check on any other partition upon bootup or from the command window on any other partition. In Win2K two partitions are NTFS and one is FAT32.

Both other systems work fine. Win2K works fine. Drive "D" is always accessible for writing or reading or installing anything. But, it doesn't like to be chkdsk'ed. It's hiding something from me, right? I hate partitions that hide things from me.

[bluesclues123]

1. Have you tried this method?
Open "my computer"
right click the partition you want to check
left click "tools"
left click "error checking" button
Left click both boxes
Confirm that you want the test to run upon reboot.
Backup all of your important data.
Reboot.

2. When did the problem begin? OR When were you last able to successfully run error checking?

3. Run defrag. Be sure to turn off your screen saver before running defrag. Is defrag able to access / defrag all files? Check the report.

BC123

[glc]

Try booting with the Win2K CD, log into the repair console, and running chkdsk x: /p from there. (x = drive letter)

[deep-in-the-forest]

Hi;

Well, I have tried doing a chkdsk by going into My Computer, tools, etc., but only have checked the files box not the other. I'll try that. I have not tried to defrag.

First...this is triple boot machine, control of booting is Xandros and under the latter I can get to Win2K and DOS. I have thought of using the Win2K CD for repair, but are you saying that I should change BIOS and boot from Win2K CD under this triple boot condition to get to the repair console? (I have a backup drive so I am not afraid to screw up the operating drive....I can merely clone the backup back to the operating drive and start over.)

When was the last time this machine could chkdsk D:? Well, it seems to me that when I ran chkdsk for the past two months it probably never was able to although I wasn't paying much attention while it was running....using /f I assumed that whatever it corrected was OK and I went on my merry way. Same mental stance on machine checking from bootup if a minor crash or I selected randomly to do it upon bootup. Is it possible that it is doing it but not telling me? Also, it WILL do a chkdsk in read-only mode..but when /f is placed in command that is when it comes back and says that D: is locked, would I like to check it upon bootup? I say yes, but it doesn't show it being done. As said in my initial post, you can access D: any other way, Windows Explorer, write to any file, etc.....load new apps, etc.

I'll run defrag and look at the report to see what, if anything, is happening (or not).

Thank you

DITF