how to decode such device path?

NTDEV
1

Hello

How can I decode/extract information from this device path returned by
SetupDiXXXX() ?

From enuming DISKs:
\?\usbstor#disk&ven_sigmatel&prod_mscn&rev_0001#012345678901&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

From enuming VOLUMEs:
\?\storage#removablemedia#7&1d086a37&0&rm#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

I notice this “{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}” GUID in common, what
does it stand for?

Are the preceding pathes in a standard format?

Regards,
Elias

2

The guids are not the same.

Each of these guids is defined in ntddstor.h and they are device interface
guids. One is for disk interfaces the other for volume interfaces.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of lallous
Sent: Monday, September 27, 2004 4:24 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] how to decode such device path?

Hello

How can I decode/extract information from this device path returned by
SetupDiXXXX() ?

From enuming DISKs:
\?\usbstor#disk&ven_sigmatel&prod_mscn&rev_0001#012345678901&
0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

From enuming VOLUMEs:
\?\storage#removablemedia#7&1d086a37&0&rm#{53f5630d-b6bf-11d0
-94f2-00a0c91efb8b}

I notice this “{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}” GUID
in common, what does it stand for?

Are the preceding pathes in a standard format?

Regards,
Elias

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
xxxxx@lists.osr.com

3

Thanks for the info.

But how are these pathes encoded? what do they reveal? Is their encoding
standard? so that whenever I get such a path, I can decode in the same
manner?

–
Elias
“Mark Roddy” wrote in message news:xxxxx@ntdev…
> The guids are not the same.
>
> Each of these guids is defined in ntddstor.h and they are device interface
> guids. One is for disk interfaces the other for volume interfaces.
>
>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of lallous
>> Sent: Monday, September 27, 2004 4:24 AM
>> To: Windows System Software Devs Interest List
>> Subject: [ntdev] how to decode such device path?
>>
>> Hello
>>
>> How can I decode/extract information from this device path returned by
>> SetupDiXXXX() ?
>>
>> From enuming DISKs:
>> \?\usbstor#disk&ven_sigmatel&prod_mscn&rev_0001#012345678901&
>> 0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
>>
>> From enuming VOLUMEs:
>> \?\storage#removablemedia#7&1d086a37&0&rm#{53f5630d-b6bf-11d0
>> -94f2-00a0c91efb8b}
>>
>> I notice this “{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}” GUID
>> in common, what does it stand for?
>>
>> Are the preceding pathes in a standard format?
>>
>> Regards,
>> Elias

4

That is the sort of open-ended question that requires the obligatory
response: what are you trying to do?

AFAIC the device path is just that: a device path. You can use documented
interfaces to obtain information from the drivers and OS components managing
that path.

=====================
Mark Roddy

-----Original Message-----
From: lallous [mailto:xxxxx@lgwm.org]
Sent: Monday, September 27, 2004 8:01 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] how to decode such device path?

Thanks for the info.

But how are these pathes encoded? what do they reveal? Is their encoding
standard? so that whenever I get such a path, I can decode in the same
manner?

–
Elias
“Mark Roddy” wrote in message news:xxxxx@ntdev…
> The guids are not the same.
>
> Each of these guids is defined in ntddstor.h and they are device
> interface guids. One is for disk interfaces the other for volume
interfaces.
>
>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of lallous
>> Sent: Monday, September 27, 2004 4:24 AM
>> To: Windows System Software Devs Interest List
>> Subject: [ntdev] how to decode such device path?
>>
>> Hello
>>
>> How can I decode/extract information from this device path returned
>> by
>> SetupDiXXXX() ?
>>
>> From enuming DISKs:
>> \?\usbstor#disk&ven_sigmatel&prod_mscn&rev_0001#012345678901&
>> 0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
>>
>> From enuming VOLUMEs:
>> \?\storage#removablemedia#7&1d086a37&0&rm#{53f5630d-b6bf-11d0
>> -94f2-00a0c91efb8b}
>>
>> I notice this “{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}” GUID in
>> common, what does it stand for?
>>
>> Are the preceding pathes in a standard format?
>>
>> Regards,
>> Elias

—
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