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 [ 01 | September | 2003 ]

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


Date: Mon, 1 Sep 2003 18:42:06 PDT7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: JFS

=====================================================
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 <200309011654.h81GsWJk009401@smtp.ucsd.edu>, on 09/01/03
at 09:53 AM, sshapiro@ucsd.edu (Sandy Shapiro) said:

>>>What happened:
>Right after loading the symbios driver, I get the error message: OS/2 is
>unable to operate your hard disk, etc.

OK. That makes sense. The message your are getting from the SymBIOS
driver actually happens long after the driver loads. This has to do with
the gory internal details of how drivers boot. The reason OS/2 can't
operate the drive is because the LVM component can't find a drive to
operate. That's why I told you to verify that the LVM data was set up
correctly.

>I notice in Goran's instructions that os2dasd.dmd should be in the
>\os2\boot directory. In my system it is in the \os2 directory. Could that
>be the problem?

No. Just make sure you only have one copy that can be found. When
loading BASEDEVs, the kernel looks in \OS2\BOOT \OS2 and \. With Warp4
and eCS it's best to have them all in \OS2\BOOT. It's just easier to
manage.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.37 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.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".

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


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

Return to [ 01 | September | 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.