SCOUG-HELP Mailing List Archives

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

Date:	Sun, 26 Jan 2003 15:10:45 PST8
From:	Michael Rakijas <mrakijas@oco.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help <scoug-help@scoug.com >
Subject:	SCOUG-Help: CHKDSK/SYS3175

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

** Reply to message from "Steven Levine" on Sat, 25 Jan
2003 10:08:51 PST8

> In <3E32B7A5.A55DB15B@attglobal.net>, on 01/25/03
> at 08:53 AM, Harry Chris Motin said:
>
>
> I recall these from the last thread.
>
> Chkdsk shouldn't trap, but since you are running Warp4, you are running an
> older version of chkdsk and newer versions might avoid the trap.
>
> Here's a couple of things you can try none of which is sure to work.
>
> If you have eCS, try the version of chkdsk*/uhpfs.dll on the CD. The is
> effectively MCP1 level code. MCP2 and FP3 have further updates. FP3 is
> available from the eCS website.
>
> You might try installing the chkdsk.sys driver, although I don't think it
> will solve your problem.

I would recommend this, actually, anyway since you have a large D:\ drive. I
boot to a 6 GB drive (Master, IDE) formatted HPFS C:\. I have a 32 GB (Slave,
IDE) formatted HPFS D:\ that would not go through a chkdsk if it wound up dirty
after an abnormal shutdown. Even with 256 MB of main memory, chkdsk would
complain of not enough memory. By installing the chkdsk.sys driver, you allow
the system to use virtual memory to perform chkdsk. My chkdsks now work every
time. Check the FP15 read me for the details but on my system, I have a
BASEDEV=CHKDSK.SYS statement near the end of my CONFIG.SYS file and a
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 don't think it's too
big of a problem. My guess is that it errors out if it has to there in the IFS
install (which can only use physical memory) but when it's run later, it can use
virtual as well. Again, check the FP15 readme for details. Good luck.

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

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

Return to [ 26 | January | 2003 ]

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.