wentreefgirl
October 9th, 2007, 01:14 PM
Its windows 2000 pro.
MaDef
October 9th, 2007, 03:01 PM
Without more information it's hard to say, but my first guess is, your checking the drive that contains your windows install. chkdsk with the /f switch cannot lock the drive because windows is using it.
make sure you have admin rights
click start and in the run box type "cmd" (without quotes).
In the command window type "chkdsk X: /f" the X being the drive you want checked, if you don't specify the drive, chkdsk will check the current drive.
If chkdsk cant lock the drive it will ask if you want to run it at next boot, select yes and reboot, chkdsk should then run just before windows loads.
wentreefgirl
October 9th, 2007, 09:55 PM
I was able to do chkdsk. It suggested at the end of the check that it found errors and suggested i do chkdsk f to fix the errors. but when i did that it cant do this procedure. Not the real error but when it seemed to say. If it did chkdsk without hesitation. Then why not chkdsk f. Its the work computer and I also think its infected and posted somewhere here my hijack this report but got no hits on that.
MaDef
October 9th, 2007, 11:20 PM
When using chkdsk /f, if the drive cannot be locked you should recive the following output on the screen:
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\>chkdsk /f
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) You can then hit the Y key and chkdsk /f will run the next time you boot up.
If you don't get the above, then what is the exat error. copy it down word for word if possible and post it back here.