Re: Service Enum params

From: Hablu (anonymous_at_discussions.microsoft.com)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 14:26:09 -0700

> particularly since you're naming your device with a number.

I need to clarify a bit. The virtual bus driver is root enumerated so the PDO naming is done by the root bus driver. So, that name comes from OS's own driver. I have watched the value after disable\enable and found the value same, but I don't know how long it'll be same specially with service packs and future NT versions.

Thanks,
Hablu

     ----- Peter Wieland [MSFT] wrote: -----
     
     that depends entirely on your driver, but the answer is likely to be "no" -
     particularly since you're naming your device with a number.
     
     A device interface registered by the driver will have a constant name (some
     long blob of gook with a GUID in it) iff the device retains the same PNP ID
     every time it's started. You should probably go with that instead of
     physical object name.
     
     -p
     
     --
     This posting is provided "AS IS" with no warranties, and confers no rights.
     "Hablu" <anonymous@discussions.microsoft.com> wrote in message
     news:25EF4EBA-4E08-4DA0-8E8E-C272CBF27125@microsoft.com...
>I was looking for a consistent indexing scheme for PDO's ID generation.
>When the application tries to install another instance of bus driver, it
>does not know whether the already installed bus driver is disabled or
>uninstalled since root bus driver has that info. NextInstance seemed to be
>very handy since it reflects the number of units installed for a bus
>driver.
>> Anyway, I have got it managed by some other ways.
>> I got one more question:
>> Will DevicePropertyPhysicalDeviceObjectName returned by PDO be same if the
> device is disabled then some other device installation activities are done
> and enabled again?
> Say DevicePropertyPhysicalDeviceObjectName returns \Device\00000007
> will it be same always after disable\enable?
>> Thanks,
> Hablu
>> ----- Doron Holan [MS] wrote: -----
>> No, you can't. what are you trying to use this key for?
>>

Relevant Pages

  • Re: toaster sample in Vista
    ... you don't need to install busenum to install a toaster. ... you can create a root enumerated device with devcon, devcon install inf hwid (the bus driver you are trying to install is root enumerated also;)). ...
    (microsoft.public.development.device.drivers)
  • Re: toaster sample in Vista
    ... want to do the same thing in Vista, and the toaster model seems to fit. ... devcon install inf hwid (the bus driver ... I was able to get the bus driver installed,> however ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS WDM driver installation for multi-port NIC
    ... driver at the same time--the ndiswdm driver was acting as a filter, ... each driver is acting as its own function driver. ... Define a new setup class for your bus driver and install ...
    (microsoft.public.development.device.drivers)
  • Re: Service Enum params
    ... A device interface registered by the driver will have a constant name (some ... "Hablu" wrote in message ... >When the application tries to install another instance of bus driver, ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS WDM driver installation for multi-port NIC
    ... My suggestion would be to keep the bus driver separate from the ndis-wdm driver. ... install the ndis-wdm driver as a function driver for the ports that you enumerate and not use that as an upper filter of bus driver for one of the ports. ... Install the ndisedge as a function driver for the child devices you enumerate. ...
    (microsoft.public.development.device.drivers)