SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 25 | January | 2004 ]

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


Date: Sun, 25 Jan 2004 20:18:27 PST8
From: waynec@linkline.com
Reply-To: scoug-help@scoug.com
To: "Scoug Help Group OS/2" <scoug-help@scoug.com >
Subject: SCOUG-Help: SYS1377... formerly utility dskts hanging

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, thanks for the help. I don't know how the diskettes got so screwed
up, I can only imagine I copied the wrong diskette over the right one at
some point.
Diskettes are now working (although I haven't checked all devices), and my
next task is to add fat32 capability to them.

But I still have a problem running chkdsk against one of the partitions,
from either the diskettes or the normal hard disk boot.

chkdsk F: /f and chkdsk F: both return a SYS1377 error saying chkdsk cannot
write to the partition root.

That partition is a 1.5 gb fat16 partition and I am able to access the files
on it; it is possible that WinXP wrote one or more files to this partition
in the past few months, if that might be a cause.

Anyone know a solution easier than copying off all the folders & files and
reformatting the partition?

Thanks,
Wayne

****************************************************************************
**********

n <20040120074020.61682.qmail@joan.linkline.com>, on 01/20/04
at 07:40 AM, waynec@linkline.com said:

OK. It's pretty obvious why the utility diskettes don't work. You are
are not loading the drivers required by your hardware.

>Diskette config.sys (which resides on DISK1,

This is correct. That's where the kernel expects to find it.

>while the hangup is on
>DISK2):

What else did you expect? The hang is occuring when the kernel is
attempting to active the protected mode drivers. It needs to load them
all first.

>basedev=ibm1s506.add /v

You are using danis506 on you standard setup. Fix this here.

>libpath=.;\;\os2\dll;\os2\install;d:\os2;d:\os2\dll;e:\os2;e:\os2\dll;f:\os2
> ;f:\os2\dll;g:\os2;g:\os2\dll;

This is pretty screwy. I recommend you get rid of all the odd references
to drives other than the boot diskette.

>rem basedev=danis506.add /v

You need to use the Dani driver since it is the driver that works.

>basedev=ibm2flpy.add
>basedev=ibm2adsk.add
>basedev=ibm2scsi.add
>basedev=ibmint13.i13

You can rem these out. You don't need them.

>basedev=os2dasd.dmd

You need to use Dani's driver since it is the driver that works.

>rem basedev=danidasd.dmd

>rem basedev=jjscdrom.dmd

You need to use JJ's driver since it is the driver that works.

>basedev=aha164x.add

I can't imagine why you left this enabled.

>basedev=aic7870.add

Do you really need this?

>basedev=chincds1.flt

I can't imagine why you left this enabled.

>basedev=ibmidecd.flt

You don't need this. You are using JJ's driver.

>basedev=sony535.add

You don't need this.

>basedev=sbcd2.add

You don't need this.

>device=\os2cdrom.dmd

You need to use JJs driver, just like your standard system.

>Out of curiousity, what does the "\" (backslash) in front of some of the
>drivers mean?

It means the same thing is does in any pathname. It says look in the root
directory. Since the path does not contain an explict drive letter, the
current drive will be used.

If recommend you update the diskette config.sys and suggested, keeping an
eye out for any similar errors I might have missed. The the resulting
config.sys still does not work, send me a copy of what you end up with.

BTW for the future attach the files the the email rather than pasting in
the text. It makes it easier to work with the files.

Regards,
Steven

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

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 [ 25 | January | 2004 ]



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.