Hi,
I have a *cough* SCSI port driver. (Not a mini port.) I’m trying to figure
out how to make the text setup portion of Win2k install my driver so that
the user can boot off of my device. This currently does not work.
Unfortunately the Win2k installation gives me no more detail than “We
couldn’t find a disk.”
Any tips on how to figure out where it is choking?
Thanks!
Thomas Swanson
Senior Software Engineer
XIOtech Corporation
A Seagate Company
Eden Prairie, MN
Office: 952-983-2445
xxxxx@xiotech.com
www.xiotech.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Win2K setup is going to load the standard SCSIPORT.SYS, and only really gives you
options to load SCSI miniports. You could either create a specialized install
path with a replacement SCSIPORT.SYS file, or if your scsiport driver can co-exist
with MS’s you could craft your version to “fake out” scsiport to think that you
are a miniport driver so that it will load you. Your error msg “we couldn’t find
a disk” is rather confusing (I’m pretty sure that there is no error msg with this
exact text 
In what context is the error msg displayed – is it indicating it
can’t load your driver because the driver diskette is missing, or is it indicating
that it can’t find any disks attached to your device ?
Regards,
Paul Bunn, UltraBac.com, 425-644-6000
Microsoft MVP - WindowsNT/2000
http://www.ultrabac.com
-----Original Message-----
From: Swanson, Tom [mailto:xxxxx@XIOtech.com]
Sent: Thursday, January 25, 2001 7:54 AM
To: NT Developers Interest List
Subject: [ntdev] boot driver and debugging txtsetup.oem
Hi,
I have a *cough* SCSI port driver. (Not a mini port.) I’m trying to figure
out how to make the text setup portion of Win2k install my driver so that
the user can boot off of my device. This currently does not work.
Unfortunately the Win2k installation gives me no more detail than “We
couldn’t find a disk.”
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hi,
It is now working. It could not locate a disk attached to my device.
This is interesting tho. The issue was that a test engineer was saturating
the SAN I was trying to attach to. This was causing long delays in reading
from the disks on the SAN. This was apparently too long for the install
process. The thing of it is that this is not too long for win2k because
once I had loaded the driver I could absolutely wax the SAN and Win2k just
loads fine. I can even boot with the SAN totally pegged and win2k doesn’t
care. It gets slow but it works.
Very strange.
Thanks for your help! (Thanks to Mark, too.)
Tom Swanson
XIOtech Corporation
-----Original Message-----
From: Paul Bunn [mailto:xxxxx@UltraBac.com]
Sent: Friday, January 26, 2001 12:41 PM
To: NT Developers Interest List
Subject: [ntdev] RE: boot driver and debugging txtsetup.oem
Win2K setup is going to load the standard SCSIPORT.SYS, and
only really gives you
options to load SCSI miniports. You could either create a
specialized install
path with a replacement SCSIPORT.SYS file, or if your
scsiport driver can co-exist
with MS’s you could craft your version to “fake out” scsiport
to think that you
are a miniport driver so that it will load you. Your error
msg “we couldn’t find
a disk” is rather confusing (I’m pretty sure that there is no
error msg with this
exact text In what context is the error msg displayed
– is it indicating it
can’t load your driver because the driver diskette is
missing, or is it indicating
that it can’t find any disks attached to your device ?
Regards,
Paul Bunn, UltraBac.com, 425-644-6000
Microsoft MVP - WindowsNT/2000
http://www.ultrabac.com
-----Original Message-----
From: Swanson, Tom [mailto:xxxxx@XIOtech.com]
Sent: Thursday, January 25, 2001 7:54 AM
To: NT Developers Interest List
Subject: [ntdev] boot driver and debugging txtsetup.oem
Hi,
I have a *cough* SCSI port driver. (Not a mini port.) I’m
trying to figure
out how to make the text setup portion of Win2k install my
driver so that
the user can boot off of my device. This currently does not work.
Unfortunately the Win2k installation gives me no more detail than “We
couldn’t find a disk.”
You are currently subscribed to ntdev as: xxxxx@xiotech.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Device enumeration uses different timeout values compared to read/write operations
once the device objects have been created.
NT doesn’t like other OS’s to play with its disks
Regards,
Paul Bunn, UltraBac.com, 425-644-6000
Microsoft MVP - WindowsNT/2000
http://www.ultrabac.com
-----Original Message-----
From: Swanson, Tom [mailto:xxxxx@XIOtech.com]
Sent: Friday, January 26, 2001 11:23 AM
To: NT Developers Interest List
Subject: [ntdev] RE: boot driver and debugging txtsetup.oem
Hi,
It is now working. It could not locate a disk attached to my device.
This is interesting tho. The issue was that a test engineer was saturating
the SAN I was trying to attach to. This was causing long delays in reading
from the disks on the SAN. This was apparently too long for the install
process. The thing of it is that this is not too long for win2k because
once I had loaded the driver I could absolutely wax the SAN and Win2k just
loads fine. I can even boot with the SAN totally pegged and win2k doesn’t
care. It gets slow but it works.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com