SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Tue, 2 Oct 2001 09:15:26 PDT
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: CHKDSK.SYS ?

=====================================================
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.
=====================================================

In <3BB9A7C8.6B12@peterskye.com>, on 10/02/01
at 04:41 AM, Peter Skye said:

>Well that's pretty dumb. It should be in the _online_ documentation, not
>in the _offline_ documentation. :)

Well, if it makes you feel better, you could submit a documentation defect
report against the MCP. You can't submit one against Warp4 because it's
out of service. Of course, unless Kim sells lots and lots of eCS, the
chances of any of the existing OS/2 documentation ever being updated is
pretty small. I'll let you do the math to quantify pretty small. :-)

>You mean they don't work together? They aren't a system?

Sure they do. One part is the front-end. The other is the worker code.

>PMCHKDSK.EXE, and which one is most similar to CHKDSK.SYS. I know that

Neither is similar. Chkdsk.sys does no disk checking. All is does is
allocate memory. Without looking at the code, I expect it would do a
VMAlloc and leave the address somewhere where chkdsk32.dll can get at it.

>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?

Just use chkdsk.com or pmchkdsk.exe. I know that chkdsk32.exe is a
front-end, but I don't know what it does. I do know it does not produce
the usual chkdsk output, when run.

>A reboot with an HPFS "dirty bit" set on leads to a bootup message to run
>CHKDSK /F, not CHKDSK32.

As it should.

>CHKDSK.DLL apparently is used by CHKDSK.SYS and CHKDSK32.EXE since the

No for chkdsk.sys. Probably not for chkdsk32.exe.

>dll's at boot time but "chkdsk.dll" is embedded in the CHKDSK.SYS code).

They can't. Think back to your device driver article. The reference to
chkdsk.dll is probably noise.

>CHKDSK.DLL. But you mentioned that CHKDSK32.EXE is an interface to

I did, but I didn't say what type of interface.

>CHKDSK (apparently CHKDSK.COM). CHKDSK.COM has an embedded reference to
>CHKDSK.EXE but there's no such file on my hard drive.

More noise.

If you really want to analyze this kind of thing and get useful results
you need to use:

lxlite /c:exemap
exehdr -v

for static analysis. For dynamic analysis, you need to use the OS/2 trace
facility as a start. These will provide more accurate answers a lot more
of your questions.

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.29d #10183 Warp4/FP11.5
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
Posts containing emotional outbursts rarely receive replies from me.
----------------------------------------------------------------

=====================================================

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".

=====================================================

Return to [ 02 | October | 2001 ]

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.