More…
A few interesting points/questions:
-
Why did MS implement SBP2 as a SCSI port driver and not a miniport?
Unless there are some unforeseen issues, you would have expected them to
use a miniport. SPB2 must call the 1394 bus driver and the OHCI (or
whatever standard is in use) driver. Since this can cause a problem in a
miniport; synchronization and performance, I suspect they chose to write
a SCSI port driver.
-
Why is Microsoft implementing their iSCSI driver as a SCSI port driver
and not a SCSI miniport driver? Again, I suspect they are aware of the
issues, like we are, that prevent you from developing a robust and
working miniport driver that must rely on calling into other device
driver.
Would you say that there is the possibility that Microsoft knows
something that you do not?
Food for thought…
Jamey
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gera Kazakov
Sent: Tuesday, December 11, 2001 6:53 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Regarding Pseudo SCSI Miniport driver
Rahul,
To solve similar problem in my port (not miniport) driver I used:
- To detect a New SCSI Host Bus Adapter which may come up upon user’s
request.
-
Issue IOCTL_DISK_FIND_NEW_DEVICES to Device\Harddisk0\Partition0. The
Disk class rescans all Device\ScsiportX devices, claim all new disk
devices and create new Device\HarddiskX\PartitionX devices
-
scan MACHINE\SYSTEM\DISK\Information key and
assign drive letters to all new partitions
- To Remove a SCSI HBA upon user’s request.
Any clues ??
I have no working solution for this yet. An idea is:
first, your app must unmount the partition, and delete
the drive letter. Then you probably need call your driver
(say, through custom IOCTL) to tell it to delete
device associated data, disconnect from server etc.
Then you probably need to destroy Device\HarddiskX
somehow.
regards,
Gera.
PS, regarding TDI calls from miniport - it, of course, works. No hacks
needed. The potential problem is WHQL as miniports are not supposed to
call anything but ScsiPortXXX.
TIA
Rahul Gupta
-----Original Message-----
From: Jamey Kirby [mailto:xxxxx@storagecraft.com]
Sent: Tuesday, December 11, 2001 12:44 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Regarding Pseudo SCSI Miniport driver
No, it is not supported. You are not able to call TDI or NDIS from a
SCSI miniport. There are some hacks to work around it, but they are
hacks and will fail under stress.
Jamey
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Rahul Gupta
Sent: Monday, December 10, 2001 10:46 PM
To: NT Developers Interest List
Subject: [ntdev] Regarding Pseudo SCSI Miniport driver
Hi All,
I am developing a Pseudo SCSI miniport driver for iSCSI on Windows
NT4.0. iSCSI requirements need :-
- To detect a New SCSI Host Bus Adapter which may come up upon user’s
request.
- To Remove a SCSI HBA upon user’s request.
I want to know how I can achieve this in my SCSI miniport driver. If
it has to be Pnp driver then how to develop a Pnp Scsi miniport driver
on Windows NT 4.0.
TIA
Rahul Gupta
You are currently subscribed to ntdev as: xxxxx@storagecraft.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@dcmtech.co.in To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@setengineering.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@storagecraft.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
