SCOUG-HELP Mailing List Archives
Return to [ 02 |
October |
2001 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Steven Levine wrote:
>
Thanks for the quick response, Steven.
> >-- Where is the documentation on CHKDSK.SYS?
> Where most new features are documented. In the FP readme.
Well that's pretty dumb. It should be in the _online_ documentation,
not in the _offline_ documentation. :)
Some interesting info in the FP readme.1st file. Now I know how to read
the CHKDSK log file. The readme.1st file also answers my preallocation
and reboot questions -- and thanks for the info you gave.
> >-- What is CHKDSK32?
> Which one? One is a DLL. The other is a 32-bit interface to chkdsk.
You mean they don't work together? They aren't a system?
> >-- Is PMCHKDSK a front end for CHKDSK, or is it something else?
> It's a GUI version of chkdsk.com or chkdsk32.exe.
> All the worker code is in chkdsk32.dll.
Okay, thanks.
Now I have to figure out when to use CHKDSK.COM vs. CHKDSK32.EXE vs.
PMCHKDSK.EXE, and which one is most similar to CHKDSK.SYS. I know that
CHKDSK.SYS goes in the CONFIG.SYS file for bootup autochecking of large
HPFS partitions. But how do you decide which of CHKDSK.COM,
CHKDSK32.EXE and PMCHKDSK.EXE to run?
I can't figure out the file dependencies:
CHKDSK.COM (apparently standalone)
CHKDSK.SYS (references non-existant CHKDSK.DLL)
CHKDSK32.EXE (no embedded reference to CHKDSK32.DLL)
PMCHKDSK.EXE (no embedded reference to CHKDSK32.DLL)
CHKDSK32.DLL
PMCHKDSK.DLL
A reboot with an HPFS "dirty bit" set on leads to a bootup message to
run CHKDSK /F, not CHKDSK32.
CHKDSK.DLL apparently is used by CHKDSK.SYS and CHKDSK32.EXE since the
latter two have small file sizes (I didn't know that drivers could load
dll's at boot time but "chkdsk.dll" is embedded in the CHKDSK.SYS
code). CHKDSK.COM has a bigger file size so it apparently doesn't use
CHKDSK.DLL. But you mentioned that CHKDSK32.EXE is an interface to
CHKDSK (apparently CHKDSK.COM). CHKDSK.COM has an embedded reference to
CHKDSK.EXE but there's no such file on my hard drive.
- Peter
=====================================================
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 [ 02 |
October |
2001 ]
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.
|