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

>> Next Message >>


Date: Tue, 5 Mar 2002 09:37:48 PST7
From: Steve Carter <scarter@vcnet.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.
=====================================================

+++++++++++
On 3/03/02, Peter Skye wrote, in part:
>
>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?

This was the method for booting from SCSI when DOS was king.
Nowadays, all modern MBs allow you to choose/specify the boot order.

>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?

NO and NO. The purpose of a SCSI BIOS is to boot a SCSI drive.
The OS loads drivers for other SCSI devices, and usually replacement drivers
for the bootable SCSI HDs . The boot driver for the HD _IS_ the SCSI BIOS,
just like the boot driver for an IDE drive is the MB BIOS.

>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?

The DOS boot order, which I believe is carried over into OS/2, is primary
partitions first, extended next, and the lowest (drive 80 Hex) drive first.
The SCSI BIOS and the BIOS boot order selection determines which physical
drive is initialized first, SCSI, IDE, etc., SCSI ID 0 before SCSI ID1
(unless changed in the SCSI BIOS setup).

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

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

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


>> Next Message >>

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