M
Michael Grigoni
Greetings:
We're wrestling with a Compaq Deskpro EN that has no bios support for
boot order including scsi. We need the option to boot NT or Win2k from
either the IDE drive or the drive on scsi id 0 and to have access to
all drives from either OS (they're all NTFS).
For our first attempt we have the scsi controller bios enabled; on
powerup the drive on id 0 is assigned drive letter 'd:' and of course
the ide drive is drive 'c:' We put the win2k ntldr on the IDE drive and
made boot.ini:
multi(0)rdisk(0)disk(0)partition(1)/WINNT="NT4 on IDE 0"
multi(1)rdisk(0)disk(0)partition(1)/WINNT'"Win2k Server on SCSI 0"
Boot fails on selecting SCSI 0: "Windows 2000 could not start because of
a computer disk hardware configuration problem. Could not read from the
selected boot disk."
Do we need to disable the scsi bios and use a scsi driver and change the
second 'multi' line to 'scsi'? Or is this a drive letter issue in the
Win2k configuration which can't be practically solved?
Searching the archives reveals other's with similar circumstances and
no posted solutions.
All replies much appreciated
Michael Grigoni
Cybertheque Museum
We're wrestling with a Compaq Deskpro EN that has no bios support for
boot order including scsi. We need the option to boot NT or Win2k from
either the IDE drive or the drive on scsi id 0 and to have access to
all drives from either OS (they're all NTFS).
For our first attempt we have the scsi controller bios enabled; on
powerup the drive on id 0 is assigned drive letter 'd:' and of course
the ide drive is drive 'c:' We put the win2k ntldr on the IDE drive and
made boot.ini:
multi(0)rdisk(0)disk(0)partition(1)/WINNT="NT4 on IDE 0"
multi(1)rdisk(0)disk(0)partition(1)/WINNT'"Win2k Server on SCSI 0"
Boot fails on selecting SCSI 0: "Windows 2000 could not start because of
a computer disk hardware configuration problem. Could not read from the
selected boot disk."
Do we need to disable the scsi bios and use a scsi driver and change the
second 'multi' line to 'scsi'? Or is this a drive letter issue in the
Win2k configuration which can't be practically solved?
Searching the archives reveals other's with similar circumstances and
no posted solutions.
All replies much appreciated
Michael Grigoni
Cybertheque Museum