C:\WINDOWS\system32>fsutil dirty query c:
Volume - c: is NOT Dirty
So, see a couple of other things I am gonna try.
Look, I read Keith's reply in there that consisted of "downloading a 3rd party proggy and then upgrading all the security updates"
Sorry, when I scanned through that, I saw red: First off, XP can be fixed even if you are getting the BSOD, and you don;t really need extra stuff to do it. Second, downloading the security updates is NOT a solution, most of that stuff is for M$'s benefit, not ours. Look, didn't XP run GREAT right outta the box? Then use it that way... The only security things I download are the things that have to do with bonafide threats, like the Blaster worm, and other things that abuse the PC via common services. M$ ships XP so that when it is installed it is expected that the person will go right on the net. But that ought not to be so, it ought to be sold chiefly as an OS, secondly as an internet appliance.
So, I, and my clients, we have certain computers that we use to do work on- this is where I come in, I save the work, I backup the databases, I keep the LANs in line, I kick the routers arses until it works right.
When I set up a client, I keep them protected 17,000 ways from Sunday...
Ah, well that's a rant... Look I've never encountered this before, anyone know what is basically going on... If I have to use a 3rd party tool to fix it, so be it. All mindsoft does is clean up the temp folders and registry.
Allrighty... Thanx in advance if anyone knows why this is happening. If I have to, I'll post a log of the the myriad things I removed from this here PC.
i'm having the same problem chkdsk /f will not run. cannot de frag
don't have zonealarm or spyware doc installed
start - run 'cmd' - the box flashes up then disappears
am i retarded? or is it my machine?
It's yer machine... I've seen that happen, you probably have some spyware running that is telling CMD to shut off.
Type start>run>msconfig and tell us what is starting when the computer starts?
Also, right click on My Computer and pull up MANAGE. Go to "Event Viewer" and then "System" and look for red X's - the error that dropped the CMD window ought to show.
Which reminds me, whenever DEFRAG fails to run on this PC, this is what the event viewer shows:
Event Type: Error
Event Source: PctSpk
Event Category: None
Event ID: 0
Time: 12:13:37 PM
The description for Event ID ( 0 ) in Source ( PctSpk ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: PctSpk error: 1063, StartServiceCtrlDispatcher failed..
"pctspk" has something to do with the PCTel Modem and the PC Speaker. I think, the speaker was trying to "BEEP" and failed.