SCOUG-HELP Mailing List Archives
Return to [ 26 |
January |
2003 ]
<< 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:
> You can modify the diskettes to allocate a swap file. To do this, modify > the MEMMAN setting in config.sys and add a SWAPPATH statement.
>
> You might find a MEMMAN setting that provides more address space to chkdsk. Perhaps:
>
> MEMMAN=NOSWAP,PROTECT
BOY! That Steven Levine, he sure knows his stuff!! I added a swapper
directory on F:\ and modified the MEMMAN line to be identical to my boot
CONFIG.SYS. As a result, the CONFIG.SYS on the bootable floppies now has
the following 2 lines:
MEMMAN=SWAP,PROTECT
SWAPPATH=F:\SWAPPER 20480 20480
I never knew that the CHKDSK program used the SWAPPER directory to help
it work with large partitions. Now, when I boot, using floppies, I can
quickly CHKDSK all of the drives except F:. Each CHKDSK takes only about
1 minute to complete (F:\ is locked, because of the callout to the
SWAPPER directory). And now, on the system CONFIG.SYS file with the
AUTOCHECK parameters modified to autocheck C:\, only, my system bootup
only takes 3 minutes!!
Svobi wrote:
> are you running a 16-bit or the newer 32-bit CHKDSK ?
> What are you CHKDSK files ?
> 2002/02/14 09:42:00 70720 C:\OS2\CHKDSK.COM
> 2001/10/02 18:32:00 147268 C:\OS2\DLL\CHKDSK32.DLL
> 2001/10/02 18:21:00 795 C:\OS2\BOOT\CHKDSK.SYS
> 2001/10/02 18:21:00 6417 C:\OS2\CHKDSK32.EXE
My CHKDSK system is as follows:
11/15/00 7:33p 70720 ----- C:\OS2\CHKDSK.COM
10/06/00 1:52p 6417 ----- C:\OS2\CHKDSK32.EXE
10/06/00 1:52p 795 ----- C:\OS2\BOOT\CHKDSK.SYS
10/06/00 2:03p 139227 ----- C:\OS2\DLL\CHKDSK32.DLL
On comparison to yours, my CHKDSK32.DLL file could be an older version,
compared to yours. You cannot tell by the dates, because, I believe, the
dates are when the files were installed on your computer. I'll have to
follow up on verifying the version/levels of the CHKDSK files and
updating them, if possible.
Both Steven and Svobi had some comments about using a BootOS2
maintenance partition. I'll have to read and understand both of your
conversations on this subject. I may eventually want to go that way.
Another consideration is to make a bootable CD. Now that I have RSJ, I
can go that way, too.
Once again, thanks for your help it correcting my CHKDSK problem!
HCM
_____________________________________________________________________________________________________
Steven Levine wrote:
>
> =====================================================
> 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 <3E32B7A5.A55DB15B@attglobal.net>, on 01/25/03
> at 08:53 AM, Harry Chris Motin said:
>
> >Thanks for your reply. Yes, I am very certain that my boot diskettes are
> >the same level as my OS. I spent a lot of time, a couple of years ago,
>
> I figured they were. You tend to be thourough.
>
> >I'm thinking that the problem may have to do with the amount of memory I
> >have, versus the size of the partition that you are trying to CHKDSK. Let
> >me give you some statistics on my system:
>
> 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.
>
> You can modify the diskettes to allocate a swap file. To do this, modify
> the MEMMAN setting in config.sys and add a SWAPPATH statement.
>
> You might find a MEMMAN setting that provides more address space to
> chkdsk. Perhaps:
>
> MEMMAN=NOSWAP,PROTECT
>
> >I am aware that running CHKDSK from a fully up system is a little
> >different than from floppies. The process is different (as evidenced by
>
> It's not chkdsk that's different. It's that the kernel options are setup
> differently.
>
> >CHKDSK on a partition, while fully up and running, could be dangerous for
> >the files on that partition.
>
> It should not be. If the partition is in use, it will be locked and
> chkdsk will not be able to make any changes.
>
> Steven
>
> --
> ---------------------------------------------------------------------
> "Steven Levine" MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4
> www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
> ---------------------------------------------------------------------
>
> =====================================================
>
> 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".
>
> =====================================================
=====================================================
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 [ 26 |
January |
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.
|