SCSI parameters to disk device mapping problem

NTDEV
1

Hopefully, I’m just having a bad day, but I seem to have hit a brick wall.

The SCSI device map in the registry tells me all the ports, buses, target
Ids and luns that are operational on a system. I can even derive this
information myself by calling IOCTL_SCSI_GET_INQUIRY_DATA on each valid
SCSI port.

My problem is with the higher level disk device object such as
\Device\Harddisk3. Given this device name, can anyone tell me how I derive
it’s SCSI nomenclature. Either to get from \Device\Harddisk3 to a device
name I can call IOCTL_SCSI_GET_ADDRESS on, or directly acquire the Port,
Bus, Target and Lun ID’s.

Thanks,

Mark.

2

\device\harddisk3 should simply be a directory with devices in it.

From a win32 app you’d open \.\PhysicalDrive and send
IOCTL_SCSI_GET_ADDRESS to that. From kernel mode you could open
??\PhysicalDrive to do the same.

what are you trying to do?

-p

-----Original Message-----
From: Mark S. Edwards [mailto:xxxxx@muttsnuts.com]
Sent: Wednesday, September 18, 2002 9:30 AM
To: NT Developers Interest List
Subject: [ntdev] SCSI parameters to disk device mapping problem

Hopefully, I’m just having a bad day, but I seem to have hit a brick
wall.

The SCSI device map in the registry tells me all the ports, buses,
target
Ids and luns that are operational on a system. I can even derive this
information myself by calling IOCTL_SCSI_GET_INQUIRY_DATA on each valid
SCSI port.

My problem is with the higher level disk device object such as
\Device\Harddisk3. Given this device name, can anyone tell me how I
derive
it’s SCSI nomenclature. Either to get from \Device\Harddisk3 to a
device
name I can call IOCTL_SCSI_GET_ADDRESS on, or directly acquire the Port,

Bus, Target and Lun ID’s.

Thanks,

Mark.

—
You are currently subscribed to ntdev as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%