[Videography1]

A month ago I had to restore my system using msconfig. Ever since then
I get a chkdsk on my D: drive (a second hard drive installed in the
Universal Drive Bay on my notebook) before Windows startup. I have
tried other hard drives in the Universal Drive Bay but the chkdsk
persists, so I don't believe it is drive sensitive. The chkdsk command
has been somehow imbedded into my startup sequence. How can I stop it?

One problem is that I can't defrag the D: drives with a chkdsk /f
ALWAYS SCHEDULED :(
bob

[Andrew E.]

Try run,type:cmd In cmd type:CHKntfs /XD:
D: being the drive you dont want checked...

"Videography1" wrote:

> A month ago I had to restore my system using msconfig. Ever since then
> I get a chkdsk on my D: drive (a second hard drive installed in the
> Universal Drive Bay on my notebook) before Windows startup. I have
> tried other hard drives in the Universal Drive Bay but the chkdsk
> persists, so I don't believe it is drive sensitive. The chkdsk command
> has been somehow imbedded into my startup sequence. How can I stop it?
>
> One problem is that I can't defrag the D: drives with a chkdsk /f
> ALWAYS SCHEDULED :(
> bob
>
>

[Serge Melkonians]

Bob,
This article on Microsoft's knowledge base might help
http://support.microsoft.com/default.aspx?scid=kb;en-us;831426

"Videography1" <bob@videographyblog.com> wrote in message
news:1118785708.289547.71810@g43g2000cwa.googlegroups.com...
>A month ago I had to restore my system using msconfig. Ever since then
> I get a chkdsk on my D: drive (a second hard drive installed in the
> Universal Drive Bay on my notebook) before Windows startup. I have
> tried other hard drives in the Universal Drive Bay but the chkdsk
> persists, so I don't believe it is drive sensitive. The chkdsk command
> has been somehow imbedded into my startup sequence. How can I stop it?
>
> One problem is that I can't defrag the D: drives with a chkdsk /f
> ALWAYS SCHEDULED :(
> bob
>