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 [ 03 | March | 2002 ]

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


Date: Sun, 3 Mar 2002 12:12:35 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: boot scsi cd

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

Steve Carter wrote:
>
> >My SCSI adapter card has no BIOS. The
> >motherboard is quite new and the [MB]
> >BIOS supports SCSI boot selection.
>
> All it does is suppress normal booting from an
> IDE HD if a SCSI Host Adapter (HA) and SCSI
> boot drive are present. The HA must still have
> a SCSI BIOS to boot ANYTHING on the SCSI bus.

1) I've heard that you can force a motherboard to suppress its IDE boot
if you tell it there aren't any IDE drives. The SCSI BIOS then boots
(or "allows the motherboard to boot"?) from the SCSI drive (which one if
there are several?) and the OS/2 drivers then "find" the IDE drives when
they are loaded by the CONFIG.SYS file. Is this true?

2) Are there SCSI HA BIOS that _don't_ allow booting to a SCSI device?
When buying a SCSI HA which has a BIOS, do you have to *verify* that it
allows you to boot through it?

3) What is the impact of the driver order in the CONFIG.SYS file? Does
it just affect the drive letter assignments or is there something else
to consider?

-- I think I once had to tell the drivers to initialize one drive at a
time to get a certain drive letter assignment (such as C: IDE, D: SCSI,
E: IDE, F: IDE) but it's been a while and I don't remember what the
driver parameters were.

-- Nor do I remember if I could initialize certain partitions
individually or if I had to initialize an entire physical drive with
each CONFIG.SYS driver line.

- Peter

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

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 [ 03 | March | 2002 ]



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.