Query disk device ARC name

NTDEV
1

I have a boot start disk class filter. Is there a way for me to query or build the ARC name either during Add Device or Start Device for each disk as it is found?

2

I think that, during AddDevice/MN_START phase of the boot driver, the \ArcName directory is not built yet.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com

http://www.storagecraft.com

wrote in message news:xxxxx@ntdev…
>I have a boot start disk class filter. Is there a way for me to query or build the ARC name either during Add Device or Start Device for each disk as it is found?
>

3

Well, I’m trying to compare it to the \SystemRoot symlink, which returns as the ARC name of the system disk at that phase of the boot process. If I query the PDO name of each disk, I get \Device\000000## which I can’t correlate to the ARC name given to me for the system disk. Is there anything else I can do here?

4

IoGetBootDiskInformation is a solution. Can be called very early.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntdev…
> Well, I’m trying to compare it to the \SystemRoot symlink, which returns as the ARC name of the system disk at that phase of the boot process. If I query the PDO name of each disk, I get \Device\000000## which I can’t correlate to the ARC name given to me for the system disk. Is there anything else I can do here?
>

5

I’ve seen that call, but I don’t want to rely solely on disk signature. Unfortunetly in my apication, there could be a conflict if there is a cloned disk with the same signature that would invalidate the proper operation of my driver, and though it is unlikely it has happened. Hence I am trying to find a way to identify the system disk based on it’s physical path.

6

>operation of my driver, and though it is unlikely it has happened. Hence I am trying to find a way to

identify the system disk based on it’s physical path.

Impossible.

Disk signature is the only way by which the ARC disk name is corellated to Windows device object name.

This is what OS does itself to set \SystemRoot symlink.

If there is a duplicate MBR signature on a boot disk - then I expect Windows to fail boot or to actually use \Windows directory from wrong hard disk (I once saw such a scenario).

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com