To be more precise, use ??\ instead of \?\ while passing to
FltGetVolumeFromName
Regards,
Ayush Gupta
AI Consulting
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ayush Gupta
Sent: Friday, January 29, 2010 8:59 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] FltGetVolumeFromName returns
STATUS_OBJECT_PATH_NOT_FOUND
Use ?? (double) instead of ? (single) while passing it to
FltGetVolumeFromName.
Regards,
Ayush Gupta
AI Consulting
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@ocarinanetworks.com
Sent: Friday, January 29, 2010 8:07 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] FltGetVolumeFromName returns STATUS_OBJECT_PATH_NOT_FOUND
I have a userland app that passes the following path, retrieved from
GetVolumeNameForVolumeMountPointW() to my driver. FltGetVolumeFromName()
always returns STATUS_OBJECT_PATH_NOT_FOUND.
The path is: \?\Volume{3c48940c-d420-11de-a5d7-806e6f6e6963}\
Note: I have tried with and without the trailing slash.
Question: Why would this happen? Does FltGetVolumeFromName() support the
guidnames? If not, how can I convert the guidname to a name in the
\Device\Volume format.
Thanks,
Rob
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer