FltMgr and FileDisk, ImDisk, etc. drive letters?

Has anyone been able to get the drive letter or GUID (actually
better) in a mini-filter for these volume-in-a-file products?
All I can get is \Device\ImDisk0, can’t get the drive letter via
Rtlxxx, AND I can’t even get the GUID name (???).


Kind regards, Dejan (MSN support: xxxxx@alfasp.com)
http://www.alfasp.com
File system audit, security and encryption kits.

Dejan Maksimovic wrote:

Has anyone been able to get the drive letter or GUID (actually
better) in a mini-filter for these volume-in-a-file products?
All I can get is \Device\ImDisk0, can’t get the drive letter via
Rtlxxx, AND I can’t even get the GUID name (???).

If you can’t retrieve this information then the product is probably not
fully integrated into the PnP and Mnt mgr interfaces. The likely
implementation used is they create a symlink for the drive letter,
by-passing all of the assignment stuff.

Pete


Kind regards, Dejan (MSN support: xxxxx@alfasp.com)
http://www.alfasp.com
File system audit, security and encryption kits.


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


Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295

That’s exactly what they do, but the question is - how do I work around it?

Peter Scott wrote:

Dejan Maksimovic wrote:
> Has anyone been able to get the drive letter or GUID (actually
> better) in a mini-filter for these volume-in-a-file products?
> All I can get is \Device\ImDisk0, can’t get the drive letter via
> Rtlxxx, AND I can’t even get the GUID name (???).
>

If you can’t retrieve this information then the product is probably not
fully integrated into the PnP and Mnt mgr interfaces. The likely
implementation used is they create a symlink for the drive letter,
by-passing all of the assignment stuff.


Kind regards, Dejan (MSN support: xxxxx@alfasp.com)
http://www.alfasp.com
File system audit, security and encryption kits.

There’s not much you can do if all they’re doing is creating a symbolic link
to their device object. I suppose you could always query the A:-Z: symbolic
links until you found a match (there’s a timing problem with that approach,
but I’m not sure what else you could do).

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Dejan Maksimovic” wrote in message news:xxxxx@ntfsd…
>
> That’s exactly what they do, but the question is - how do I work around
> it?
>
> Peter Scott wrote:
>
>> Dejan Maksimovic wrote:
>> > Has anyone been able to get the drive letter or GUID (actually
>> > better) in a mini-filter for these volume-in-a-file products?
>> > All I can get is \Device\ImDisk0, can’t get the drive letter via
>> > Rtlxxx, AND I can’t even get the GUID name (???).
>> >
>>
>> If you can’t retrieve this information then the product is probably not
>> fully integrated into the PnP and Mnt mgr interfaces. The likely
>> implementation used is they create a symlink for the drive letter,
>> by-passing all of the assignment stuff.
>
> –
> Kind regards, Dejan (MSN support: xxxxx@alfasp.com)
> http://www.alfasp.com
> File system audit, security and encryption kits.
>
>
>