Is there a method, preferably from an application, to take a drive letter
and determine which miniport driver (i.e. iscsiprt.sys) is being used? I
would like to be able to determine if a device is iSCSI or not. If there is
no such scheme to identify the miniport, can anyone suggest an alternative
method? My driver can access the device stack from the kernel, though a
user-space implementation is much preferred. In either case, any
suggestions?
Many thanks,
Steve Soltis
Use IOCTL_STORAGE_QUERY_PROPERTY to get the device descriptor. This
includes a BusType field that should indicate what the underlying bus is
(iSCSI is one option).
Now whether any third-party iSCSI miniport sets the registry keys to
configure this I don’t know. But it’s probably your best bet.
-p
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Steve Soltis
Sent: Wednesday, June 23, 2004 7:53 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Determine if device is iSCSI or not
Is there a method, preferably from an application, to take a drive
letter and determine which miniport driver (i.e. iscsiprt.sys) is being
used? I would like to be able to determine if a device is iSCSI or not.
If there is no such scheme to identify the miniport, can anyone suggest
an alternative method? My driver can access the device stack from the
kernel, though a user-space implementation is much preferred. In either
case, any suggestions?
Many thanks,
Steve Soltis
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Steve,
the answer is quite simple – NO WAY. Even if you’ll use MS API to deal
with iscsiprt.sys
you’ll end with supporting MS as single iSCSI initiator vendor. And
there are others (Cisco,
IBM, Rocket Division Software etc).
If MS would create kind of “standard IOCTL set for iSCSI drivers” we
would be happy to
follow it! But such a standard does not exist…
Regards,
Anton A. Kolomyeytsev
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Steve Soltis
Sent: Wednesday, June 23, 2004 5:53 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Determine if device is iSCSI or not
Is there a method, preferably from an application, to take a drive
letter and determine which miniport driver (i.e. iscsiprt.sys) is being
used? I would like to be able to determine if a device is iSCSI or not.
If there is no such scheme to identify the miniport, can anyone suggest
an alternative method? My driver can access the device stack from the
kernel, though a user-space implementation is much preferred. In either
case, any suggestions?
Many thanks,
Steve Soltis
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@cooldev.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
>Use IOCTL_STORAGE_QUERY_PROPERTY to get the device descriptor. This
includes a BusType field that should indicate what the underlying bus is
(iSCSI is one option).
In the Windows 2003 DDK (both winioctl.h and ntddstor.h), there is this:
typedef enum _STORAGE_BUS_TYPE {
BusTypeUnknown = 0x00,
BusTypeScsi,
BusTypeAtapi,
BusTypeAta,
BusType1394,
BusTypeSsa,
BusTypeFibre,
BusTypeUsb,
BusTypeRAID,
BusTypeMaxReserved = 0x7F
} STORAGE_BUS_TYPE, *PSTORAGE_BUS_TYPE;
I believe the iSCSI entry immediately follows BusTypeRAID (i.e. value of 9)
but it is not defined in the headers I have. Where can I find the latest
STORAGE_BUS_TYPE definition?
Mike
Make the most of your family vacation with tips from the MSN Family Travel
Guide! http://dollar.msn.com
Not all miniports manage to indicate their bus type as anything other than
BusTypeScsi.
=====================
Mark Roddy
-----Original Message-----
From: Mike Berhan [mailto:xxxxx@hotmail.com]
Sent: Wednesday, June 23, 2004 12:38 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Determine if device is iSCSI or not
Use IOCTL_STORAGE_QUERY_PROPERTY to get the device descriptor. This
includes a BusType field that should indicate what the underlying bus
is (iSCSI is one option).
In the Windows 2003 DDK (both winioctl.h and ntddstor.h), there is this:
typedef enum _STORAGE_BUS_TYPE {
BusTypeUnknown = 0x00,
BusTypeScsi,
BusTypeAtapi,
BusTypeAta,
BusType1394,
BusTypeSsa,
BusTypeFibre,
BusTypeUsb,
BusTypeRAID,
BusTypeMaxReserved = 0x7F
} STORAGE_BUS_TYPE, *PSTORAGE_BUS_TYPE;
I believe the iSCSI entry immediately follows BusTypeRAID (i.e. value of 9)
but it is not defined in the headers I have. Where can I find the latest
STORAGE_BUS_TYPE definition?
Mike
Make the most of your family vacation with tips from the MSN Family Travel
Guide! http://dollar.msn.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
>Not all miniports manage to indicate their bus type as anything other than
BusTypeScsi.
That’s fine for me. I can handle it either way. I have seen the value 9
returned with iSCSI (Microsoft iSCSI Initiator), so my assumption has always
been that STORAGE_BUS_TYPE has been expanded to define additional bus
architectures. However, I can’t find any such official definition. I’m
curious if anything has been defined beyond 9, and if 9 is indeed the
official value for iSCSI.
Mike
MSN Toolbar provides one-click access to Hotmail from any Web page – FREE
download! http://toolbar.msn.click-url.com/go/onm00200413ave/direct/01/
I’m told 9 is indeed the official value for BusTypeiScsi and that it should be in the server SP1 DDK (whenever that becomes available).
So 9 is your friend.
-p
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mike Berhan
Sent: Wednesday, June 23, 2004 10:26 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Determine if device is iSCSI or not
Not all miniports manage to indicate their bus type as anything other
than BusTypeScsi.
That’s fine for me. I can handle it either way. I have seen the value 9 returned with iSCSI (Microsoft iSCSI Initiator), so my assumption has always been that STORAGE_BUS_TYPE has been expanded to define additional bus architectures. However, I can’t find any such official definition. I’m curious if anything has been defined beyond 9, and if 9 is indeed the official value for iSCSI.
Mike
MSN Toolbar provides one-click access to Hotmail from any Web page ? FREE
download! http://toolbar.msn.click-url.com/go/onm00200413ave/direct/01/
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Mike, Jeffrey Goldner in September of 2003 mentioned that 9 is iScsi in a
message on the ntdev newsgroup. Looks like you are still working in the
storage area.
“Mike Berhan” wrote in message news:xxxxx@ntdev…
> >Not all miniports manage to indicate their bus type as anything other
than
> >BusTypeScsi.
>
> That’s fine for me. I can handle it either way. I have seen the value 9
> returned with iSCSI (Microsoft iSCSI Initiator), so my assumption has
always
> been that STORAGE_BUS_TYPE has been expanded to define additional bus
> architectures. However, I can’t find any such official definition. I’m
> curious if anything has been defined beyond 9, and if 9 is indeed the
> official value for iSCSI.
>
> Mike
>
> _________________________________________________________________
> MSN Toolbar provides one-click access to Hotmail from any Web page - FREE
> download! http://toolbar.msn.click-url.com/go/onm00200413ave/direct/01/
>
>
“Steve Soltis” wrote in message
news:xxxxx@ntdev…
>
> Is there a method, preferably from an application, to take a drive
letter
> and determine which miniport driver (i.e. iscsiprt.sys) is being
used? I
> would like to be able to determine if a device is iSCSI or not. If
there is
> no such scheme to identify the miniport, can anyone suggest an
alternative
> method? My driver can access the device stack from the kernel,
though a
> user-space implementation is much preferred. In either case, any
> suggestions?
If you can send SCSI commands to it, why not ask the device?
Do an INQUIRY for Vital Product Data page 83h, and look for an
Identification descriptor with an ASSOCIATION set to 1 and a
PIV field set to 1. The PROTOCOL IDENTIFIER field then tells
you the protocol used on the port through which you’re talking;
if its value is 5 then you’re talking iSCSI.
Any indication that vendors support this (PIV) yet? I haven’t seen it
but I’m willing to look since this seems generally useful.
For iSCSI we also look for the version descriptor 0960h in the standard
INQUIRY data. You run the risk for each of these methods failing when a
“transparent” bridge does not update the inquiry data.
We use the BusType enumerations, which as Peter said, is up to the
vendor to set in the registry (see devcon presentation on port driver
parameters). Storport defaults to BusTypeFibre, Scsiport defaults to
BusTypeScsi, etc. For devices that use these port drivers and implement
some other transport (i.e., iSCSI or RAID), it’s entirely up to the
vendor to set this correctly (one line in the INF should do it).
Also, for the record, BusTypeIscsi really is officially 9. (Cisco is
welcome to set it for their miniport.) SAS and Sata follow but I’m not
sure which is 10 and which is 11 - I’ll get back to you. SP1 headers are
being updated and the change propagated to other components such as VDS
and VSS.
Jeff Goldner
-----Original Message-----
From: J. J. Farrell [mailto:xxxxx@bcs.org.uk]
Sent: Wednesday, June 23, 2004 4:48 PM
Subject: Re: Determine if device is iSCSI or not
“Steve Soltis” wrote in message
news:xxxxx@ntdev…
>
> Is there a method, preferably from an application, to take a drive
letter
> and determine which miniport driver (i.e. iscsiprt.sys) is being
used? I
> would like to be able to determine if a device is iSCSI or not. If
there is
> no such scheme to identify the miniport, can anyone suggest an
alternative
> method? My driver can access the device stack from the kernel,
though a
> user-space implementation is much preferred. In either case, any
> suggestions?
If you can send SCSI commands to it, why not ask the device?
Do an INQUIRY for Vital Product Data page 83h, and look for an
Identification descriptor with an ASSOCIATION set to 1 and a
PIV field set to 1. The PROTOCOL IDENTIFIER field then tells
you the protocol used on the port through which you’re talking;
if its value is 5 then you’re talking iSCSI.
This is up to iSCSI target what will you get in such a case. If you’re
dealing with not virtualized storage
but with real hard disk mapped AS IS (iSCSI target does NOT alter any
SCSI traffic between CDB
requestor and device SCSI firmware) described method would not work.
Regards,
Anton A. Kolomyeytsev
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of J. J. Farrell
Sent: Thursday, June 24, 2004 2:48 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Determine if device is iSCSI or not
“Steve Soltis” wrote in message
news:xxxxx@ntdev…
>
> Is there a method, preferably from an application, to take a drive
letter
> and determine which miniport driver (i.e. iscsiprt.sys) is being
used? I
> would like to be able to determine if a device is iSCSI or not. If
there is
> no such scheme to identify the miniport, can anyone suggest an
alternative
> method? My driver can access the device stack from the kernel,
though a
> user-space implementation is much preferred. In either case, any
> suggestions?
If you can send SCSI commands to it, why not ask the device?
Do an INQUIRY for Vital Product Data page 83h, and look for an
Identification descriptor with an ASSOCIATION set to 1 and a PIV field
set to 1. The PROTOCOL IDENTIFIER field then tells you the protocol used
on the port through which you’re talking; if its value is 5 then you’re
talking iSCSI.
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@cooldev.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
My answer was incomplete, hence misleading - apologies.
“Jeffrey Goldner” wrote in message
news:xxxxx@ntdev…
> Any indication that vendors support this (PIV) yet? I haven’t
> seen it but I’m willing to look since this seems generally useful.
I’ve no idea. VPD 83h is now compulsory, I think a port
descriptor is becoming compulsory, but PIV remains optional.
It should be easy enough to implement in most cases, so I
hope it will be implemented increasingly.
If the checks I recommended show true, then the device is
being accessed over iSCSI. If they don’t show true, it
may or may not be being accessed over iSCSI (if there’s a
valid entry indicating a different transport, that shows
it is not using iSCSI - in other cases, this method doesn’t
tell you anything). I focussed on the second question
“determine if a device is iSCSI or not” - this method
provides a partial answer to that. Even if the device
itself can be seen to be being accessed over iSCSI, it
doesn’t necessarily answer the first question “determine
which miniport driver (i.e. iscsiprt.sys) is being used”
- if bridges are involved, the port at the device could
be iSCSI but the port at the host could be anything.
> For iSCSI we also look for the version descriptor 0960h in the
> standard INQUIRY data.
I believe, strictly speaking, that tells you that the
device can be accessed over iSCSI but it doesn’t tell
you that you are currently accessing it over iSCSI. The
target box could support several transport protocols,
and all could be listed here. In practical terms at the
moment, this isn’t much of an issue.
> You run the risk for each of these methods failing when a
> “transparent” bridge does not update the inquiry data.
Yes, I’d missed that - it popped into my head as I woke
up this morning. Are you telepathic by any chance?
> We use the BusType enumerations, which as Peter said, is up to
> the vendor to set in the registry (see devcon presentation on
> port driver parameters). Storport defaults to BusTypeFibre,
> Scsiport defaults to BusTypeScsi, etc. For devices that use
> these port drivers and implement some other transport (i.e.,
> iSCSI or RAID), it’s entirely up to the vendor to set this
> correctly (one line in the INF should do it).
>
> Also, for the record, BusTypeIscsi really is officially 9.
> (Cisco is welcome to set it for their miniport.) SAS and
> Sata follow but I’m not sure which is 10 and which is 11
> - I’ll get back to you. SP1 headers are being updated and
> the change propagated to other components such as VDS and VSS.
If the question is really “what transport protocol is the
miniport using” then this is clearly the right approach,
once everyone falls in line.
The described method may tell you nothing, or it may tell you the
protocol being used on the port connected to the device. If the
device is a “real hard disk” with an iSCSI interface (is anyone
manufacturing such a beast yet?) it will tell you either nothing
or that the port on the disk talks iSCSI. If some sort of transport
bridge along the path decides to change the content of these fields,
it could tell you anything.
“Anton A. Kolomyeytsev (CoolDev.Com)” wrote in
message news:xxxxx@ntdev…
> This is up to iSCSI target what will you get in such a case. If
you’re
> dealing with not virtualized storage
> but with real hard disk mapped AS IS (iSCSI target does NOT alter
any
> SCSI traffic between CDB
> requestor and device SCSI firmware) described method would not
work.
>
> Regards,
> Anton A. Kolomyeytsev
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of J. J.
Farrell
> Sent: Thursday, June 24, 2004 2:48 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Determine if device is iSCSI or not
>
>
>
> “Steve Soltis” wrote in message
> news:xxxxx@ntdev…
> >
> > Is there a method, preferably from an application, to take a
drive
> letter
> > and determine which miniport driver (i.e. iscsiprt.sys) is being
> used? I
> > would like to be able to determine if a device is iSCSI or not.
If
> there is
> > no such scheme to identify the miniport, can anyone suggest an
> alternative
> > method? My driver can access the device stack from the kernel,
> though a
> > user-space implementation is much preferred. In either case, any
> > suggestions?
>
> If you can send SCSI commands to it, why not ask the device?
> Do an INQUIRY for Vital Product Data page 83h, and look for an
> Identification descriptor with an ASSOCIATION set to 1 and a PIV
field
> set to 1. The PROTOCOL IDENTIFIER field then tells you the protocol
used
> on the port through which you’re talking; if its value is 5 then
you’re
> talking iSCSI.
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@cooldev.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com
>
>
Hi,
hard disks with iSCSI interface? Any iSCSI target w/o virtualization
enabled would do this.
StarWind f.e ))
Back to the “iSCSI or not iSCSI – the question is”. There are too many
"if"s in described
solution to make it working ))
Regards,
Anton A. Kolomyeytsev
RocketDivision.Com – Toolkits for Network and Storage Kernel Software
Developers
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of J. J. Farrell
Sent: Friday, June 25, 2004 1:36 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Determine if device is iSCSI or not
The described method may tell you nothing, or it may tell you the
protocol being used on the port connected to the device. If the device
is a “real hard disk” with an iSCSI interface (is anyone manufacturing
such a beast yet?) it will tell you either nothing or that the port on
the disk talks iSCSI. If some sort of transport bridge along the path
decides to change the content of these fields, it could tell you
anything.
“Anton A. Kolomyeytsev (CoolDev.Com)” wrote in
message news:xxxxx@ntdev…
> This is up to iSCSI target what will you get in such a case. If
you’re
> dealing with not virtualized storage
> but with real hard disk mapped AS IS (iSCSI target does NOT alter
any
> SCSI traffic between CDB
> requestor and device SCSI firmware) described method would not
work.
>
> Regards,
> Anton A. Kolomyeytsev
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of J. J.
Farrell
> Sent: Thursday, June 24, 2004 2:48 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Determine if device is iSCSI or not
>
>
>
> “Steve Soltis” wrote in message
> news:xxxxx@ntdev…
> >
> > Is there a method, preferably from an application, to take a
drive
> letter
> > and determine which miniport driver (i.e. iscsiprt.sys) is being
> used? I
> > would like to be able to determine if a device is iSCSI or not.
If
> there is
> > no such scheme to identify the miniport, can anyone suggest an
> alternative
> > method? My driver can access the device stack from the kernel,
> though a
> > user-space implementation is much preferred. In either case, any
> > suggestions?
>
> If you can send SCSI commands to it, why not ask the device? Do an
> INQUIRY for Vital Product Data page 83h, and look for an
> Identification descriptor with an ASSOCIATION set to 1 and a PIV
field
> set to 1. The PROTOCOL IDENTIFIER field then tells you the protocol
used
> on the port through which you’re talking; if its value is 5 then
you’re
> talking iSCSI.
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@cooldev.com To
> unsubscribe send a blank email to
xxxxx@lists.osr.com
>
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@cooldev.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
>From: “Jeffrey Goldner”
>Also, for the record, BusTypeIscsi really is officially 9. (Cisco is
>welcome to set it for their miniport.) SAS and Sata follow but I’m not
>sure which is 10 and which is 11 - I’ll get back to you. SP1 headers are
>being updated and the change propagated to other components such as VDS
>and VSS.
I didn’t see a followup on this so I wanted to check back in. I understand
9 is officially BusTypeIscsi. Just wondering if 10 and 11 are the official
values for SAS and SATA (respectively)? I do understand that this return
value cannot always be trusted. Thanks.
Mike
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it’s FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Yes, that’s the correct order.
BusTypeSas 0x0a
BusTypeSata 0x0b
-----Original Message-----
From: Mike Berhan [mailto:xxxxx@hotmail.com]
Sent: Tuesday, July 13, 2004 4:29 PM
Subject: RE:Determine if device is iSCSI or not
From: “Jeffrey Goldner”
>Also, for the record, BusTypeIscsi really is officially 9. (Cisco is
>welcome to set it for their miniport.) SAS and Sata follow but I’m not
>sure which is 10 and which is 11 - I’ll get back to you. SP1 headers
are
>being updated and the change propagated to other components such as VDS
>and VSS.
I didn’t see a followup on this so I wanted to check back in. I
understand
9 is officially BusTypeIscsi. Just wondering if 10 and 11 are the
official
values for SAS and SATA (respectively)? I do understand that this
return
value cannot always be trusted. Thanks.
Mike
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it’s
FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Jeff,
Curious as to where you got that definition. I see:
BusTypeRAID,
BusTypeMaxReserved = 0x7F
These are the final two bus enumeration types, RAID enumerated as 8, in the
latest Windows DDK, or at least the defintions found in build 1184. So where
did you get a BusTypeIscsi enumerated as 9?
Hmmm … maybe I should ask when the DDK will reflect the latest
enumerations?
–
Gary G. Little
Seagate Technologies, LLC
“Mike Berhan” wrote in message news:xxxxx@ntdev…
> >From: “Jeffrey Goldner”
> >Also, for the record, BusTypeIscsi really is officially 9. (Cisco is
> >welcome to set it for their miniport.) SAS and Sata follow but I’m not
> >sure which is 10 and which is 11 - I’ll get back to you. SP1 headers are
> >being updated and the change propagated to other components such as VDS
> >and VSS.
>
> I didn’t see a followup on this so I wanted to check back in. I
understand
> 9 is officially BusTypeIscsi. Just wondering if 10 and 11 are the
official
> values for SAS and SATA (respectively)? I do understand that this return
> value cannot always be trusted. Thanks.
>
> Mike
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it’s FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
Maybe you should 
Real Soon Now. Keep checking the available downloads. I’ll try to get
you a build number as well since that’s likely to save you some time.
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
Sent: Wednesday, July 14, 2004 11:31 AM
Subject: Re: RE:Determine if device is iSCSI or not
Jeff,
Curious as to where you got that definition. I see:
BusTypeRAID,
BusTypeMaxReserved = 0x7F
These are the final two bus enumeration types, RAID enumerated as 8, in
the
latest Windows DDK, or at least the defintions found in build 1184. So
where
did you get a BusTypeIscsi enumerated as 9?
Hmmm … maybe I should ask when the DDK will reflect the latest
enumerations?
–
Gary G. Little
Seagate Technologies, LLC
“Mike Berhan” wrote in message
news:xxxxx@ntdev…
> >From: “Jeffrey Goldner”
> >Also, for the record, BusTypeIscsi really is officially 9. (Cisco is
> >welcome to set it for their miniport.) SAS and Sata follow but I’m
not
> >sure which is 10 and which is 11 - I’ll get back to you. SP1 headers
are
> >being updated and the change propagated to other components such as
VDS
> >and VSS.
>
> I didn’t see a followup on this so I wanted to check back in. I
understand
> 9 is officially BusTypeIscsi. Just wondering if 10 and 11 are the
official
> values for SAS and SATA (respectively)? I do understand that this
return
> value cannot always be trusted. Thanks.
>
> Mike
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it’s
FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
Build 1219 definitely has the updates, 1210 does not.
-----Original Message-----
From: Jeffrey Goldner
Sent: Wednesday, July 14, 2004 10:14 PM
To: Windows System Software Devs Interest List
Subject: RE: RE:Determine if device is iSCSI or not
Maybe you should
Real Soon Now. Keep checking the available downloads. I’ll try to get
you a build number as well since that’s likely to save you some time.
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
Sent: Wednesday, July 14, 2004 11:31 AM
Subject: Re: RE:Determine if device is iSCSI or not
Jeff,
Curious as to where you got that definition. I see:
BusTypeRAID,
BusTypeMaxReserved = 0x7F
These are the final two bus enumeration types, RAID enumerated as 8, in
the
latest Windows DDK, or at least the defintions found in build 1184. So
where
did you get a BusTypeIscsi enumerated as 9?
Hmmm … maybe I should ask when the DDK will reflect the latest
enumerations?
–
Gary G. Little
Seagate Technologies, LLC
“Mike Berhan” wrote in message
news:xxxxx@ntdev…
> >From: “Jeffrey Goldner”
> >Also, for the record, BusTypeIscsi really is officially 9. (Cisco is
> >welcome to set it for their miniport.) SAS and Sata follow but I’m
not
> >sure which is 10 and which is 11 - I’ll get back to you. SP1 headers
are
> >being updated and the change propagated to other components such as
VDS
> >and VSS.
>
> I didn’t see a followup on this so I wanted to check back in. I
understand
> 9 is officially BusTypeIscsi. Just wondering if 10 and 11 are the
official
> values for SAS and SATA (respectively)? I do understand that this
return
> value cannot always be trusted. Thanks.
>
> Mike
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it’s
FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
Build 1219 definitely has the updates (and it should be part of a few
before that since the change went in on 6/25), 1210 does not.
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
Sent: Wednesday, July 14, 2004 11:31 AM
Subject: Re: RE:Determine if device is iSCSI or not
Jeff,
Curious as to where you got that definition. I see:
BusTypeRAID,
BusTypeMaxReserved = 0x7F
These are the final two bus enumeration types, RAID enumerated as 8, in
the
latest Windows DDK, or at least the defintions found in build 1184. So
where
did you get a BusTypeIscsi enumerated as 9?
Hmmm … maybe I should ask when the DDK will reflect the latest
enumerations?
–
Gary G. Little
Seagate Technologies, LLC
“Mike Berhan” wrote in message
news:xxxxx@ntdev…
> >From: “Jeffrey Goldner”
> >Also, for the record, BusTypeIscsi really is officially 9. (Cisco is
> >welcome to set it for their miniport.) SAS and Sata follow but I’m
not
> >sure which is 10 and which is 11 - I’ll get back to you. SP1 headers
are
> >being updated and the change propagated to other components such as
VDS
> >and VSS.
>
> I didn’t see a followup on this so I wanted to check back in. I
understand
> 9 is officially BusTypeIscsi. Just wondering if 10 and 11 are the
official
> values for SAS and SATA (respectively)? I do understand that this
return
> value cannot always be trusted. Thanks.
>
> Mike
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it’s
FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>