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 [ 15 | April | 2008 ]

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


Date: Tue, 15 Apr 2008 09:08:33 -0700
From: Ray Davison <raydav@charter.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: eCS 2.0 Didn't Last Long.


1
This is a multi-part message in MIME format.

Content Type: text/plain

Content-Transfer-Encoding: 7bit

Colin Campbell wrote:
> After I posted that I had successfully installed eCS 2.0, I immediately
> started getting
> "OS/2 is unable to operate your hard drive." messages.
>
> I booted once with Alt+F2, and the last driver loaded before the message
> was issued was OS2LVM.DMD.
>
> Each time I boot eCS 1.2, CHKDSK runs against the G: drive and
> pronounces it fine.
>
> What do I do to determine what the problem is, and correct it?

Attached are two files. Put ALTF2ON.$$$ in X:\OS2\BOOT. That will
cause boot to always have Alt F2 on. This will cause all driver loads
to echo.

Put DELAY.SYS IN X:\OS2

Put the following as the top line in CONFIG.SYS.
DEVICE=X:\OS2\DELAY.SYS /K 10 BASEDEVS LOADED
This will then be the first thing to load after BASEDEVS, and it will
stop the boot process for ten seconds.

When I get "unable to operate" it is always drive letter confusion.
BASEDEVS don't care about drive letters; they always come from the boot
partition. All other drivers can be loaded from anywhere, so drive
letters are important.

The above gives you a break point in the boot process. That is, the
BASEDEVS have all loaded. If all is well the next thing to load is
PAUSE. It helps you narrow the search.

Ray


Content Type: text/plain

name="ALTF2ON.$$$"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="ALTF2ON.$$$"

RTpcT1MyXEJPT1RcYWx0ZjJvbi4kJCQ=


Content Type: application/octet-stream

Unknown header: name="delay.sys" :
Unknown header: filename="delay.sys" :
File attachment: unknown


Content Type: text/plain

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

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
"postmaster@scoug.com".

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


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

Return to [ 15 | April | 2008 ]



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.