on Sun, 26 Jan
2003 21:54:22 PST8
> >CALL=C:\OS2\CHKDSK.COM D: /C statement right after my DPATH statement.
> >I'm not sure but I though I was supposed to remove D: from the autocheck
> >list of the HPFS IFS statement but it is in my current CONFIG.SYS so I
>
> The call to chkdsk is a no-op if you have D: in the autocheck list. One
> benefit of using the call rather the autocheck is faster chkdsk's because
> the kernel is fully up and running when the call's execute. It's a good
> way to clean drives that are not referenced during boot. It also avoids
> the reboot forced by chkdsk.sys.
Are you sure about this. When I reboot after a dirty shutdown (as far as
driver D: is concerned), I don't get a chkdsk on D: until the call statement. I
know because chkdsk D: would fail otherwise. Also, because of the call, I see
the output text and only real activity after a dirty shutdown.
> I'm pretty sure that chkdsk.sys is only used for autochecking drives
> specified in the ifs statement. I know cfgdat.inf says otherwise, but
> that does not jive with what I know.
Hmm. Doesn't sound quite right but I defer to more knowledgeable sources.
> Steven
-Rocky
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 01 |
February |
2003 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.