JSI Tip 0638 - How do I interpret \Device\Hardisk#\Partition#?
August 7, 1998
If you receive a message that includes this type of disk identifier, you need to edit the registry. The process is different for SCSI versus IDE drives.
IDE
HKEY_LOCAL_MACHINEHardwareDevicemapAtdisk
Controller0 look at the controller address and interrupt. disk0 look at identifier string for manufacturer and model# disk1 look at identifier string for manufacturer and model# Controller1 look at the controller address and interrupt. disk0 look at identifier string for manufacturer and model# disk1 look at identifier string for manufacturer and model#
SCSI
HKEY_LOCAL_MACHINEHardwareDevicemapScsi
Scsiport0 look at driver, Interrupt, and IOAddress Scisbus0 Targetid0 Logical Unit Id 0 look at identifier and type. Targetid1 Logical Unit Id 0 look at identifier and type. Targetid4 Logical Unit Id 0 look at identifier and type. Scsibus1 Targetid0 Logical Unit Id 0 look at identifier and type. Targetid1 Logical Unit Id 0 look at identifier and type. Targetid2 Logical Unit Id 0 Scsiport1 look at driver, Interrupt and I/O Address. Scsibus0 Targetid0 Logical Unit Id 0 look at identifier and type.
Using the identifier and type values, determine which entries are disks and which are CD-ROMS, Tapes, Scanners, etc. In each value name of Type, a type REG_SZ value, the entry DiskPeripheral equates to a Disk # in Disk Administrator and to a deviceharddisk#, where # starts at 0.
To find deviceharddisk3, find the 4th DiskPeripheral. Note that SCSIPORT is a SCSI controller, SCSIBUS is a channel (some controllers have dual channels), and TARGETID is the SCSI ID (0 -6 with 7 being the controller). If you are not sure which SCSIPORT represents which SCSI controller, look at the driver, I/O Address, and Interrupt of the SCSIPORT entry and match it with the hardware configuration set on the controller. For IDE Devices, the drives are in master/slave configuration order on each controller.
Partition# starts at 1.
About the Author
You May Also Like