M$ XP CHKDSK

[Sam]

I have two serial drives, 120GB each, Drives C and D. Two DVD drives, E and
F, and an external USB 120 GB drive G. Running M$ XP Pro on a new Dell XPS.

I opened up Windows Explorer, right clicked on drive C, Properties, asked to
check the drive for errors. A message came up that said the drive was busy,
do I want to schedule a Chkdsk for the next startup. Yes. The identical
situation for D Drive. I did NOT do the same for the external G Drive.

I shut down and rebooted. Chkdsk ran on Drive D taking forever. The Chkdsk
ran of Drive C taking forever. Then Chkdsk ran on Drive D AGAIN, taling
forever. Then Chkdsk ran on Drive C, this time only a minute or so saying
that Drive C was clean. THEN, without my requesting it, CHKDSK ran on the
external DRIVE G, this time taking forever and ever! Then the computer
booted about 4 hours later.

Why would Ckdsk run twice on the same drives and why would it run on the
external when it was not requested? Yeah, I know I can turn off the
External drive before booting to prevent access, but how should I run a
chkdsk on the drives I want ONLY? And ONLY ONCE!

M$ FOREVER!!!!!

Sam

 

[Carey Frisch [MVP]]

There is no such O/S callled "M$ XP Pro". Please rephrase
your inquiry with correct terminology and grammer.

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

--------------------------------------------------------------------------------------------------


|I have two serial drives, 120GB each, Drives C and D. Two DVD drives, E and
| F, and an external USB 120 GB drive G. Running M$ XP Pro on a new Dell XPS.
|
| I opened up Windows Explorer, right clicked on drive C, Properties, asked to
| check the drive for errors. A message came up that said the drive was busy,
| do I want to schedule a Chkdsk for the next startup. Yes. The identical
| situation for D Drive. I did NOT do the same for the external G Drive.
|
| I shut down and rebooted. Chkdsk ran on Drive D taking forever. The Chkdsk
| ran of Drive C taking forever. Then Chkdsk ran on Drive D AGAIN, taling
| forever. Then Chkdsk ran on Drive C, this time only a minute or so saying
| that Drive C was clean. THEN, without my requesting it, CHKDSK ran on the
| external DRIVE G, this time taking forever and ever! Then the computer
| booted about 4 hours later.
|
| Why would Ckdsk run twice on the same drives and why would it run on the
| external when it was not requested? Yeah, I know I can turn off the
| External drive before booting to prevent access, but how should I run a
| chkdsk on the drives I want ONLY? And ONLY ONCE!
|
| M$ FOREVER!!!!!
|
| Sam

 

[Sam]

MICROSOFT WINDOWS XP PRO. I believe everyone understood that.

Sam

 

[MGGP]

Go get him Carey, bite him, boy !

I agree, let's try to keep this on a professional level
and dispense with the casual jargon like M$. This is not
grade-school, it's business. (BTW it's GRAMMAR)

 

[Tom]

There is no such O/S callled "M$ XP Pro". Please rephrase
your inquiry with correct terminology and grammer.

--

Sheesh Carey, chill out, it is only a word, and not some blasphemy against
your beliefs!!!

If you're going to be this demanding, then I suggest you at least offer the
help in light of your poor spelling! (grammer is spelled GRAMMAR!!)

 

[Tom]

I have two serial drives, 120GB each, Drives C and D. Two DVD drives, E and
F, and an external USB 120 GB drive G. Running M$ XP Pro on a new Dell XPS.

I opened up Windows Explorer, right clicked on drive C, Properties, asked to
check the drive for errors. A message came up that said the drive was busy,
do I want to schedule a Chkdsk for the next startup. Yes. The identical
situation for D Drive. I did NOT do the same for the external G Drive.

I shut down and rebooted. Chkdsk ran on Drive D taking forever. The Chkdsk
ran of Drive C taking forever. Then Chkdsk ran on Drive D AGAIN, taling
forever. Then Chkdsk ran on Drive C, this time only a minute or so saying
that Drive C was clean. THEN, without my requesting it, CHKDSK ran on the
external DRIVE G, this time taking forever and ever! Then the computer
booted about 4 hours later.

Why would Ckdsk run twice on the same drives and why would it run on the
external when it was not requested? Yeah, I know I can turn off the
External drive before booting to prevent access, but how should I run a
chkdsk on the drives I want ONLY? And ONLY ONCE!

Does it still run when you reboot, on the internal drives? You should also
be sure you disconnect the external drive when you do this procedure.

 

[hermes]

Before the MVP (M$ Victim Poster) Hermes responded, Tom typed:

Sheesh Carey, chill out, it is only a word, and not some blasphemy
against your beliefs!!!

Unless Carey is like all of the other Micro$heep and can't think for
himself, can only follow the herd and $shepard, M$!

If you're going to be this demanding, then I suggest you at least
offer the help in light of your poor spelling! (grammer is spelled
GRAMMAR!!)

--
hermes
DRM sux! Treacherous Computing kills our virtual civil liberties!
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams.

Yesterday it worked.
Today it is not working.
Windows is like that.

 

[Sam]

Tom,

Not sure I understand your question. I will definitely disable the external
drive the next time it runs, but I don't know why it ran a chkdsk on the
external in the first place. For instance, if I ran format Drive C, I would
not expect the computer to format Drive G!

As for the tirade from Carey, it is probably the Microsoft mantra that has
permeated the company since they graduated from DOS and Windows 3.0, i.e.,
if you don't know the answer you bluster and show arrogance. Sorry for this
last comment, but if the MVP's are supposed to be here to help, that's what
they should do. If they object to the language, they could provide the help
AND REQUEST one refrain from using whatever terminology that turns them
green.

Anyway, thanks Tom, I'll do a little experimenting when I can spare the down
time on the computer for running chkdsk. This next time, I'll ask for only
a check of only one drive and see what happens.

Sam

 

[Tom]

Tom,

Not sure I understand your question. I will definitely disable the external
drive the next time it runs, but I don't know why it ran a chkdsk on the
external in the first place. For instance, if I ran format Drive C, I would
not expect the computer to format Drive G!

As for the tirade from Carey, it is probably the Microsoft mantra that has
permeated the company since they graduated from DOS and Windows 3.0, i.e.,
if you don't know the answer you bluster and show arrogance. Sorry for this
last comment, but if the MVP's are supposed to be here to help, that's what
they should do. If they object to the language, they could provide the help
AND REQUEST one refrain from using whatever terminology that turns them
green.

Anyway, thanks Tom, I'll do a little experimenting when I can spare the down
time on the computer for running chkdsk. This next time, I'll ask for only
a check of only one drive and see what happens.

Sam

You're welcome Sam,

And post back with any results, positive or negative, as someone here will
definitely come along and give good advice .

 

[FRG]

Heres one more for the block file POOF!

Before the MVP (M$ Victim Poster) Hermes responded, Tom typed:

Unless Carey is like all of the other Micro$heep and can't think for
himself, can only follow the herd and $shepard, M$!


--
hermes
DRM sux! Treacherous Computing kills our virtual civil liberties!
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams.

Yesterday it worked.
Today it is not working.
Windows is like that.