How do I convert this physical string into logical string?

Hi.

I got my directory path by ObQueryNameString.
But the path is not logical.. like this:

>@??\Device\HarddiskVolume1\MyDir

Originally, the path is C:\MyDir.

Could I convert the string into "C:\MyDir"?

Read about the Mount Manager.

"keandi" <> wrote in message
news: oups.com...
> Hi.
>
> I got my directory path by ObQueryNameString.
> But the path is not logical.. like this:
>
>>@??\Device\HarddiskVolume1\MyDir
>
> Originally, the path is C:\MyDir.
>
> Could I convert the string into "C:\MyDir"?
>

>@??\Device\HarddiskVolume1\MyDir

> Could I convert the string into "C:\MyDir"?

Of course - this is what IoVolumeDeviceToDosName() and
RtlVolumeDeviceToDosName() are for.

Please check the NG thoroughly - as far as I remember, couple of
months ago I explained how to do things like that on some thread.....


Anton Bassov

keandi wrote:
> Hi.
>
> I got my directory path by ObQueryNameString.
> But the path is not logical.. like this:
>
> >@??\Device\HarddiskVolume1\MyDir
>
> Originally, the path is C:\MyDir.
>
> Could I convert the string into "C:\MyDir"?

> Of course - this is what IoVolumeDeviceToDosName() and
> RtlVolumeDeviceToDosName() are for.

I would suggest the OP to rethink the design to never ever use drive letters in
the kernel part, and use the volume GUIDs or even mountdev IDs instead.

The user part will do the necessary conversions from the UI-level drive letters
to the IDs, and then the user/kernel interface speaks in terms of IDs only.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

Sorry for my ignorance but...

why using drive letters in the kernel is a no-no?

Have a nice day
GV

"Maxim S. Shatskih" <> wrote in message
news:O0h4rEF$...
>> Of course - this is what IoVolumeDeviceToDosName() and
>> RtlVolumeDeviceToDosName() are for.
>
> I would suggest the OP to rethink the design to never ever use drive
> letters in
> the kernel part, and use the volume GUIDs or even mountdev IDs instead.
>
> The user part will do the necessary conversions from the UI-level drive
> letters
> to the IDs, and then the user/kernel interface speaks in terms of IDs
> only.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
>
> http://www.storagecraft.com
>

> why using drive letters in the kernel is a no-no?

It is just more complex I think, and does not handle the directory mount
points.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation

http://www.storagecraft.com

Maxim,

> I would suggest the OP to rethink the design to never ever use drive letters in
> the kernel part, and use the volume GUIDs or even mountdev IDs instead.

Well, probably the OP does not use it extensively, so that, for a quick
and simple solution
IoVolumeDeviceToDosName() should work just fine....

Anton Bassov

Maxim S. Shatskih wrote:
> > Of course - this is what IoVolumeDeviceToDosName() and
> > RtlVolumeDeviceToDosName() are for.
>
> I would suggest the OP to rethink the design to never ever use drive letters in
> the kernel part, and use the volume GUIDs or even mountdev IDs instead.
>
> The user part will do the necessary conversions from the UI-level drive letters
> to the IDs, and then the user/kernel interface speaks in terms of IDs only.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
>
> http://www.storagecraft.com