Setting/Changing the device name in Device Manager

Hi,

How do I change the display name in Device Manager?

eg. serial ports show up as "Communications Port (COM1)" etc.

I have similar multiple devices which I'd like to name as "MyDev0"
"MyDev1" etc... (currently they show as the common name from the INF file)

Can this be done programmatically from the driver, or is there special INF
black magic required?

TIA
Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, <http://www.vl.com.au>
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266

you can write a coinstaller which changes the friendly name at install time

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Mark McDougall" <> wrote in message
news:O84#...
> Hi,
>
> How do I change the display name in Device Manager?
>
> eg. serial ports show up as "Communications Port (COM1)" etc.
>
> I have similar multiple devices which I'd like to name as "MyDev0"
> "MyDev1" etc... (currently they show as the common name from the INF file)
>
> Can this be done programmatically from the driver, or is there special INF
> black magic required?
>
> TIA
> Regards,
>
> --
> Mark McDougall, Engineer
> Virtual Logic Pty Ltd, <http://www.vl.com.au>
> 21-25 King St, Rockdale, 2216
> Ph: +612-9599-3255 Fax: +612-9599-3266

Doron Holan [MSFT] wrote:

> you can write a coinstaller which changes the friendly name at install time

OK, thanks! I'll look into it.

Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, <http://www.vl.com.au>
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266

Arghh...

I can set a "port number" in the PDO device extension when the bus driver
enumerates my child devices. This would, for example, correspond to the
UINumber in the registry. The coinstaller would pick up the UINumber so it
can set the friendly name - eg. MyDev0, MyDev1...

During AddDevice() in my child device driver, I need to assign the
symbolic name - eg. MYDEV0, MYDEV1... This, however, needs the same "port
number" or UINumber that was assigned during enumeration - but how do I
access this from the DeviceAdd()?

TIA!
Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, <http://www.vl.com.au>
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266

I should add that I'm writing a KMDF driver...

Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, <http://www.vl.com.au>
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266

"Mark McDougall" <> wrote in message
news:#...
............
> During AddDevice() in my child device driver, I need to assign the
> symbolic name - eg. MYDEV0, MYDEV1... This, however, needs the same "port
> number" or UINumber that was assigned during enumeration - but how do I
> access this from the DeviceAdd()?

You need to decide how you determine which device is which "port number" -
such as by PCI device & function, by i/o address, etc.
The driver may see the devices in any (read: random) order.
Also, decide what to do if some devices won't show up (holes in numbering?).

-- pa

Pavel A. wrote:

> You need to decide how you determine which device is which "port number" -

Got it sorted now.

The bus driver assigns the UINumber during enumeration which is stored in
the caps (and hence hardware registry).

The child driver then picks up the UINumber device property
(WdfDeviceQueryProperty) in AddDevice() and uses that to create the
symbolic link. Likewise, when it calls QueryInterface to get the physical
resources from the bus driver, it also reads the port number (again) from
the interface.

Hence the port number in the PDO matches the symbolic name of the FDO. Now
I just need to add the co-installer to change the friendly name in device
manager to also show the port number and everything will be consistent.

The enumeration is static. No missing ports. Closed system.

Thanks all!
Regards,

--
Mark McDougall, Engineer
Virtual Logic Pty Ltd, <http://www.vl.com.au>
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266