From: eBoy on
HI,

How I get the symbolic name from a device name by WDF macro or APIs ?

My client driver can get a device Name form bus driver, but I don't
know how to get
the symbolic name by WDF.

Thank you.
From: Roberto Agostino on
I am not sure to have understood your request, but...

the function QueryDosDevice can retrieve the ntdevicename from a
dosdevicename, or the full list of all ntdevicenames. So if you have a
dosdevice name you can get the ntdevicename directly, otherwise, you can
obtain the full list and scan it, until you find the searched one ntdevice.

To create and remove symbolic links you can use the function:
DefineDosDevice.

I hope to be useful.

Roberto


"eBoy" <minkids(a)ms46.url.com.tw> ha scritto nel messaggio
news:7e64e48e-66ad-48b3-94cd-f19a10519d5c(a)a39g2000prb.googlegroups.com...
> HI,
>
> How I get the symbolic name from a device name by WDF macro or APIs ?
>
> My client driver can get a device Name form bus driver, but I don't
> know how to get
> the symbolic name by WDF.
>
> Thank you.


From: Don Burn on
Why do you think you need this? The device name is something you can
use in the kernel, but the symbolic name if it is present is there so
that the it can be used by the user space. So why would one driver care
if another created a symbolic link or what its name was?


Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr



> -----Original Message-----
> From: eBoy [mailto:minkids(a)ms46.url.com.tw]
> Posted At: Sunday, June 13, 2010 5:03 AM
> Posted To: microsoft.public.development.device.drivers
> Conversation: WDF to get the symbolic Name
> Subject: WDF to get the symbolic Name
>
> HI,
>
> How I get the symbolic name from a device name by WDF macro or APIs ?
>
> My client driver can get a device Name form bus driver, but I don't
know how
> to get the symbolic name by WDF.
>
> Thank you.
>
>
> __________ Information from ESET Smart Security, version of virus
signature
> database 5192 (20100612) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>