How do I run chkdsk in XP
 

If I use the start\run command when it ends the result is shown only for a flash, haven't got time to read it!! then if I type in command and try to run in dos shell all I get is "Access Denied" error, the command I am executing is simply "chkdsk c:", I don't want to use the /f switch as it is only a check, also when rebooting with the /f switch the results are there again only for a second so, you don't get to read the damned results again,:doh: must be a conspiracy!!:yep:

according to his link http://forums.techarena.in/windows-xp-support/42429.htm

A lot of stuff in there (mostly "information") but no "winlogon"!:hmmm:

What is happening is running NDD is reporting "Security Descriptors" error message but after scheduling a repair when rebooting goes through the test but NDD still shows the same error, it is possibly a fault with NDD but it's been OK for years!:hmmm:

Is that Norton Disk Doctor, by any chance?

maybe try another disk utility?

http://service1.symantec.com/support...520?Open&src=w

http://www.tomshardware.co.uk/forum/...ty-descriptors

google search shows enough links for "NDD Security Descriptors" to raise a question over exactly what ndd is looking at and how it's interpreting it - could be it fixes errors and finds new ones or it's getting confused :-?

Event Logs
Chkdsk will log error messages in the Event Viewer - System Log.
Chkdsk /f removes ACLs that are no longer used and reports this in the Event Viewer - Application Log.

dunno if that's any help finding the logs - I'd go by date and time; and if there are none listed, er, then there aren't any?.

Look for winlogon in the SOURCE column of the application event viewer. (you probably have already lol)

http://ss64.com/nt/chkdsk.html
might shed some light?

I believe that is supposed to happen, command line applications close as soon as the execution stops

are you sure you have admin privileges?

I found the Winlogon file, I was looking on the left for this title but it was one of the Information files with the sub heading of Winlogon!:doh:
This is what is reported:

Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.

390708800 KB total disk space.
155199884 KB in 197450 files.
75604 KB in 16398 indexes.
0 KB in bad sectors.
293052 KB in use by the system.
65536 KB occupied by the log file.
235140260 KB available on disk.

4096 bytes in each allocation unit.
97677200 total allocation units on disk.
58785065 allocation units available on disk.

A Previous scan:

Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.

390708800 KB total disk space.
154497064 KB in 197850 files.
75540 KB in 16374 indexes.
0 KB in bad sectors.
293048 KB in use by the system.
65536 KB occupied by the log file.
235843148 KB available on disk.

4096 bytes in each allocation unit.
97677200 total allocation units on disk.
58960787 allocation units available on disk.

The three cleaning up lines are obviously the fault that is not being cleaned up, anyone know how to fix these?:hmmm:

Forget it, it's too big a job and the problem is no big deal according to many forums, basically it's an XP 32bit problem with handling files when you have over 4 billion of them!!:yep:
Just for fun I downloaded a trial run of a disk utility package including a registry cleaner, every time I try these I get huge problems and end up having to re-ghost to an older system, this one found 1,520 errors, now who out there would recommend pressing the clean button?:hmmm::D

hehe, it's a right pain in the arse ain't it?

Most of the time I don't bother with any 'maintenance' on my computer (other than av scanning). Errors get fixed when I perform a format and reinstall every year or two.
Occasionally I get lost in the depths of windows on some quest for better optimisation or error fixing, with all the internet's collected experience at my fingertips. The most usual outcome is a sense of having spent a lot of time for an unclear result. :DL