symbolic names for multiple instances of devices - microsoft.public.development.device.drivers

Hi, I've got a bus driver that (statically) enumerates a number of child devices (PDOs) for which I have a corresponding driver. FWIW this is a *closed* system and devices don't go away. I want to create ordered Symbolic names for each device - ie. MyDev0, MyDev1, ... etc, specifically so an application can open them unambiguously using CreateFile("MyDev0")... (ie I need to absolutely know which is 0, which is 1) etc... Right now in AddDevice() I'm calling: WdfDeviceInitAssignName("\\Device\\MyDev%d") WdfDeviceCreate() WdfDeviceCreateSymbolicLink("\\DosDevices\\MyDev%d") However, I need the device *number* to insert into the assigned name and subsequently the symbolic link. How can I get this - especially *before* I call WdfDeviceCreate() ??? Can I create the SymbolicLink in EvtPrepareHw()? If so, I still have the problem with the assigned name, since I read that you can't call CreateSymbolicLink() if you don't call InitAssignName() - although it does appear to work for me?!? Or is there a better way? 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

RtlUnicodeStringPrintf will format the string for you ala printf style formatting. you can create a symbolic link name to an unnamed FDO if you want, KMDF will just create the symlink to the PDO name for you. remember that the number or even the name itself on the FDO has no relationship with the symlink name, your dev name could be \Device\FooBar999 and the symlink could be \DosDevices\BarFoo100. d -- This posting is provided "AS IS" with no warranties, and confers no rights. "Mark McDougall" <markm@vl.com.au> wrote in message news:#0GT#683KHA.1624@TK2MSFTNGP06.phx.gbl... > Hi, > > I've got a bus driver that (statically) enumerates a number of child > devices (PDOs) for which I have a corresponding driver. FWIW this is a > *closed* system and devices don't go away. > > I want to create ordered Symbolic names for each device - ie. MyDev0, > MyDev1, ... etc, specifically so an application can open them > unambiguously using CreateFile("MyDev0")... (ie I need to absolutely know > which is 0, which is 1) etc... > > Right now in AddDevice() I'm calling: > > WdfDeviceInitAssignName("\\Device\\MyDev%d") > WdfDeviceCreate() > WdfDeviceCreateSymbolicLink("\\DosDevices\\MyDev%d") > > However, I need the device *number* to insert into the assigned name and > subsequently the symbolic link. How can I get this - especially *before* I > call WdfDeviceCreate() ??? > > Can I create the SymbolicLink in EvtPrepareHw()? If so, I still have the > problem with the assigned name, since I read that you can't call > CreateSymbolicLink() if you don't call InitAssignName() - although it does > appear to work for me?!? > > Or is there a better way? > > 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

> However, I need the device *number* to insert into the assigned name = and > subsequently the symbolic link Use the global counter and ++ it on each creation. But it is much better to use device interfaces instead. --=20 Maxim S. Shatskih Windows DDK MVP maxim@storagecraft.com http://www.storagecraft.com

"Maxim S. Shatskih" <maxim@storagecraft.com.no.spam> wrote in message news:eA9COU$3KHA.5588@TK2MSFTNGP06.phx.gbl... >> However, I need the device *number* to insert into the assigned name and >> subsequently the symbolic link > > Use the global counter and ++ it on each creation. > > But it is much better to use device interfaces instead. Maybe, combination of both: Device interface to detect all the devices, then query some property (stored in the registry, or call the driver) to get the numbers assigned to devices. -- pa > -- > Maxim S. Shatskih > Windows DDK MVP > maxim@storagecraft.com > http://www.storagecraft.com >

Maxim S. Shatskih wrote: > Use the global counter and ++ it on each creation. I have subsequently discovered that this is how the serial driver does it. In this case, IIUC there's no guaranteed correlation between the first PDO enumerated and the first AddDevice() call - ie. a PDO enumerated as MyPdo2 could conceivably get its AddDevice() called first, and the Assigned/Symbolic name could be "MyDev0" - right? FTR I think I can live with this anyway, since I can store the port number (global counter) in the FDO device extension in AddDevice() and then assign the physical resources in EvtPrepareHw() based on this port number. > But it is much better to use device interfaces instead. Ugghh!! No thanks. These are actually custom communications ports and they will never need to do detection. It's a closed system and each port has a predetermined connection to the outside world. 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 <markm@vl.com.au> wrote: > >> But it is much better to use device interfaces instead. > >Ugghh!! No thanks. These are actually custom communications ports and they >will never need to do detection. It's a closed system and each port has a >predetermined connection to the outside world. Your response indicates that you do not know what device interfaces are. -- Tim Roberts, timr@probo.com Providenza & Boekelheide, Inc.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <blockquote cite="mid:%230GT%23683KHA.1624@TK2MSFTNGP06.phx.gbl" type="cite"> Or is there a better way? </blockquote> Yes.  Device interfaces.  You register the interface for each device, and there's already a library of <code>SetupDiXXX()</code> functions that allow application-mode code to enumerate all devices exporting that interface.  All that your application-mode code needs to know is the GUID used by your kernel-mode code to register the interface for each device.  Device interface names are stable across reboots (as long as the hardware doesn't physically move around, of course); don't require bodges in your driver such as incrementing global counters to generate names and handling name collisions; don't require special knowledge in application-mode code of idiosyncratic naming schemes used by kernel-mode code; and incorporate bus addresses in <a href="http://msdn.microsoft.com/en-us/library/ff547656%28VS.85%29.aspx">instance IDs</a>, retrievable in application-mode code via <code><a href="http://msdn.microsoft.com/en-us/library/ff551106%28VS.85%29.aspx">SetupDiGetDeviceInstanceID()</a></code>.  Don't reinvent this wheel. </body> </html>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <blockquote cite="mid:FBD08674-6453-40F3-80EC-204918E9D0B8@microsoft.com" type="cite"> <blockquote type="cite"> But it is much better to use device interfaces instead. </blockquote> Maybe, combination of both: Device interface to detect all the devices, then query some property (stored in the registry, or call the driver) to get the numbers assigned to devices. </blockquote> There's no need for the global counter for the latter.  M. MacDougall wants to be able to find the specific bus address of the device.  <a href="http://msdn.microsoft.com/en-us/library/ff547656%28VS.85%29.aspx">Instance IDs</a> already incorporate that, and they are retrievable by application-mode code via <code><a href="http://msdn.microsoft.com/en-us/library/ff551106%28VS.85%29.aspx">SetupDiGetDeviceInstanceID()</a></code>.  Since it's xyr own bus driver, xe has full control over the instance IDs in the first place, too. </body> </html>

> In this case, IIUC there's no guaranteed correlation between the first = PDO > enumerated=20 Enumeration order of the PDOs is not defined at all. > FTR I think I can live with this anyway, since I can store the port = number > (global counter) in the FDO device extension in AddDevice() and then > assign the physical resources in EvtPrepareHw() based on this port = number. Correct. --=20 Maxim S. Shatskih Windows DDK MVP maxim@storagecraft.com http://www.storagecraft.com

I don't know if I quite understand your need, but maybe you can preallocate your own array of device structure areas in the nonpaged pool, have an atomic counter that increments for every device you create, and store a pointer to its Device Object in the corresponding slot. When the Open request comes your driver gets control anyway, and from there you can quickly figure out which device you're talking about. In other words, devices are primarily identified by your own structure, not by the Device Object - you just use the Device Object to keep Windows quiet. Instead of embedding your device-unique storage in the Device Object as a device extension, you just maintain your own array of device structures, and do not include a device extension in your device object. I use a variation of this technique in my driver, and I have successfully run production volume through up to 6-board configurations. I do not like device interfaces - correct me if I'm wrong - because they require a nonstandard API in the user side. Hope this helps, Alberto. On Apr 19, 8:35=A0pm, Mark McDougall <ma...@vl.com.au> wrote: > Maxim S. Shatskih wrote: > > Use the global counter and ++ it on each creation. > > I have subsequently discovered that this is how the serial driver does it= .. > In this case, IIUC there's no guaranteed correlation between the first PD= O > enumerated and the first AddDevice() call - ie. a PDO enumerated as MyPdo= 2 > could conceivably get its AddDevice() called first, and the > Assigned/Symbolic name could be "MyDev0" - right? > > FTR I think I can live with this anyway, since I can store the port numbe= r > (global counter) in the FDO device extension in AddDevice() and then > assign the physical resources in EvtPrepareHw() based on this port number= .. > > > But it is much better to use device interfaces instead. > > Ugghh!! No thanks. These are actually custom communications ports and the= y > will never need to do detection. It's a closed system and each port has a > predetermined connection to the outside world. > > 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 do not like device interfaces - correct me if I'm wrong - because > they require a nonstandard API in the user side. what is non standard about using SetupAPI to enumerate the device interface? -- This posting is provided "AS IS" with no warranties, and confers no rights. "alberto" <amoreira@ieee.org> wrote in message news:01938386-bc6e-4d7a-ba45-6c8112d1f817@x38g2000vbx.googlegroups.com... > > I don't know if I quite understand your need, but maybe you can > preallocate your own array of device structure areas in the nonpaged > pool, have an atomic counter that increments for every device you > create, and store a pointer to its Device Object in the corresponding > slot. When the Open request comes your driver gets control anyway, and > from there you can quickly figure out which device you're talking > about. > > In other words, devices are primarily identified by your own > structure, not by the Device Object - you just use the Device Object > to keep Windows quiet. Instead of embedding your device-unique storage > in the Device Object as a device extension, you just maintain your > own array of device structures, and do not include a device extension > in your device object. > > I use a variation of this technique in my driver, and I have > successfully run production volume through up to 6-board > configurations. > > I do not like device interfaces - correct me if I'm wrong - because > they require a nonstandard API in the user side. > > > Hope this helps, > > > Alberto. > > > > > On Apr 19, 8:35 pm, Mark McDougall <ma...@vl.com.au> wrote: >> Maxim S. Shatskih wrote: >> > Use the global counter and ++ it on each creation. >> >> I have subsequently discovered that this is how the serial driver does >> it. >> In this case, IIUC there's no guaranteed correlation between the first >> PDO >> enumerated and the first AddDevice() call - ie. a PDO enumerated as >> MyPdo2 >> could conceivably get its AddDevice() called first, and the >> Assigned/Symbolic name could be "MyDev0" - right? >> >> FTR I think I can live with this anyway, since I can store the port >> number >> (global counter) in the FDO device extension in AddDevice() and then >> assign the physical resources in EvtPrepareHw() based on this port >> number. >> >> > But it is much better to use device interfaces instead. >> >> Ugghh!! No thanks. These are actually custom communications ports and >> they >> will never need to do detection. It's a closed system and each port has a >> predetermined connection to the outside world. >> >> 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]" <doron.holan@online.microsoft.com> wrote in message news:ufuG7lZ4KHA.5880@TK2MSFTNGP04.phx.gbl... >> I do not like device interfaces - correct me if I'm wrong - because >> they require a nonstandard API in the user side. > > what is non standard about using SetupAPI to enumerate the device > interface? No such thing in posix :-) -- pa > "alberto" <amoreira@ieee.org> wrote in message > news:01938386-bc6e-4d7a-ba45-6c8112d1f817@x38g2000vbx.googlegroups.com... >> >> I don't know if I quite understand your need, but maybe you can >> preallocate your own array of device structure areas in the nonpaged >> pool, have an atomic counter that increments for every device you >> create, and store a pointer to its Device Object in the corresponding >> slot. When the Open request comes your driver gets control anyway, and >> from there you can quickly figure out which device you're talking >> about. >> >> In other words, devices are primarily identified by your own >> structure, not by the Device Object - you just use the Device Object >> to keep Windows quiet. Instead of embedding your device-unique storage >> in the Device Object as a device extension, you just maintain your >> own array of device structures, and do not include a device extension >> in your device object. >> >> I use a variation of this technique in my driver, and I have >> successfully run production volume through up to 6-board >> configurations. >> >> I do not like device interfaces - correct me if I'm wrong - because >> they require a nonstandard API in the user side. >> >> >> Hope this helps, >> >> >> Alberto. >> >> >> >> >> On Apr 19, 8:35 pm, Mark McDougall <ma...@vl.com.au> wrote: >>> Maxim S. Shatskih wrote: >>> > Use the global counter and ++ it on each creation. >>> >>> I have subsequently discovered that this is how the serial driver does >>> it. >>> In this case, IIUC there's no guaranteed correlation between the first >>> PDO >>> enumerated and the first AddDevice() call - ie. a PDO enumerated as >>> MyPdo2 >>> could conceivably get its AddDevice() called first, and the >>> Assigned/Symbolic name could be "MyDev0" - right? >>> >>> FTR I think I can live with this anyway, since I can store the port >>> number >>> (global counter) in the FDO device extension in AddDevice() and then >>> assign the physical resources in EvtPrepareHw() based on this port >>> number. >>> >>> > But it is much better to use device interfaces instead. >>> >>> Ugghh!! No thanks. These are actually custom communications ports and >>> they >>> will never need to do detection. It's a closed system and each port has >>> a >>> predetermined connection to the outside world. >>> >>> 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 >>

The problem is, the SetupAPI is Windows-unique. Doesn't exist in Linux, Solaris, or MacOS. Forces me to write the application or test program more than once, meaning, I have to spend additional time and money to satisfy the vagaries of the OS. And, believe me, I like ifstream/ofstream way better! Alberto. On Apr 21, 5:27=A0pm, "Doron Holan [MSFT]" <doron.ho...@online.microsoft.com> wrote: > > I do not like device interfaces - correct me if I'm wrong - because > > they require a nonstandard API in the user side. > > what is non standard about using SetupAPI to enumerate the device interfa= ce? > > -- > > This posting is provided "AS IS" with no warranties, and confers no right= s >

>And, believe me, I like ifstream/ofstream way better! For me, the use of << or >> for file reads and writes is schizoid, but = well, this is a matter of taste. I never use these libraries, only printf and fprintf and = StringCb/CchPrintf POSIX API is OK, so is Win32. --=20 Maxim S. Shatskih Windows DDK MVP maxim@storagecraft.com http://www.storagecraft.com

alberto wrote: > I don't know if I quite understand your need, You do, but I've found the solution, which also solved another problem with friendly names in Device Manager. Firstly, the bus driver, which enumerates the PDOs, sets the UINumber member of the PnPCaps structure. For good measure, I also recorded it in the PDO's device-extension. The child device FDO then queries the UINumber device property to both name the device and create a symbolic link. Again for good measure, I recorded this in the child device FDO device-extension. Lastly, the coinstaller also queries the UINumber from the registry to use for the friendly name in Device Manager. Thusly, the bus driver, the child PDO, child FDO, FDO symbolic name and Device Manager friendly name all use the same indexing for the child devices! Phew! :) -- 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

Similiar Articles:

symbolic names for multiple instances of devices - microsoft ...
Hi, I've got a bus driver that (statically) enumerates a number of child devices (PDOs) for which I have a corresponding driver. FWIW this is a *...

How to get the Device Instance Path - microsoft.public.vb.general ...
symbolic names for multiple instances of devices - microsoft ... With using VB6, does anyone know how to get the device instance path if you know the device name (or any ...

WinUSB - iterating devices to get serial numbers. - microsoft ...
symbolic names for multiple instances of devices - microsoft ... WinUSB - iterating devices to get serial numbers ... In Page?... to have a unique callback function name ...

WDF to get the symbolic Name - microsoft.public.development.device ...
symbolic names for multiple instances of devices - microsoft ... I want to create ordered Symbolic names for each device - ie. MyDev0, MyDev1, ... etc, specifically so an ...

Open Multiple Instances of same Form - microsoft.public.access ...
symbolic names for multiple instances of devices - microsoft ..... multiple criteria in a report in Acc 2007 using a form ... symbolic names for multiple instances of ...

Don't Allow Two Instances of Excel - microsoft.public.excel ...
symbolic names for multiple instances of devices - microsoft ... Don't Allow Two Instances of Excel - microsoft.public.excel ... symbolic names for multiple instances of ...

KMDF driver METHOD_NEITHER and high CPU usage questions ...
symbolic names for multiple instances of devices - microsoft ... Hi, I've got a bus driver that (statically ... link name to an unnamed FDO if you want, KMDF will ...

WinUSB device path - microsoft.public.development.device.drivers ...
symbolic names for multiple instances of devices - microsoft ... WinUSB device path - microsoft.public.development.device.drivers ... symbolic names for multiple instances ...

Display Name in Device Manager - microsoft.public.development ...
symbolic names for multiple instances of devices - microsoft ... Display Name in Device Manager - microsoft.public.development ..... my USB mass storage device, the device ...

Multiuse (Single Instance) or Single Use (Multiple Instances ...
symbolic names for multiple instances of devices - microsoft ..... symbolic names for multiple instances of devices ... List: StorMiniport driver's multiple instance ...

create an index listing where specific names are mentioned ...
symbolic names for multiple instances of devices - microsoft ... create an index listing where specific names are mentioned ... Multiple Audio Devices Win CE - microsoft ...

Call Same Function for multiple controls - microsoft.public.access ...
symbolic names for multiple instances of devices - microsoft ... Call Same Function for multiple controls - microsoft.public.access ... WinUSB - iterating devices to get ...

How to open 2 excel instances by using XP schedule tasks ...
symbolic names for multiple instances of devices - microsoft ..... an application can open them unambiguously using ... Don't Allow Two Instances of Excel ...

Unexpected VSS error (30218) when restoring database to new instan ...
symbolic names for multiple instances of devices - microsoft ... Unexpected VSS error (30218) when restoring database to new instan ... symbolic names for multiple ...

How to programmatically get the library name by serial number ...
symbolic names for multiple instances of devices - microsoft ... remember that the number or even the name itself on the FDO has ... in the registry, or call the driver ...

Integration Manager - Additonal Criteria in Before Query ...
... against a particular persistent class. The Session is a factory for Criteria instances. ... MOMADAdmin <management group name> <AD Integration Security ... A sample LDAP ...

Undo jumps between multiple open workbooks - microsoft.public ...
symbolic names for multiple instances of devices - microsoft ... Undo jumps between multiple open workbooks - microsoft.public ... microsoft public development device ...

MmAllocateContiguousMemory and non-paged pool size - microsoft ...
symbolic names for multiple instances of devices - microsoft ... what is non standard about using SetupAPI to enumerate ... array of device structure areas in the nonpaged ...

SMTP Send creates *.eml file but does not dispatch email ...
Are these the properties of the instance of the smtpclient ... WDF to get the symbolic Name - microsoft.public.development.device ..... so, what is the part of your ...

How to hide my device in deivce manager? - microsoft.public ...
How to get the Device Instance Path - microsoft ... Manager Get list all the hardware devices installed in a ... Multiple ... Display Name in Device Manager - microsoft.public ...

symbolic names for multiple instances of devices [Device Drivers]
Hi, I've got a bus driver that (statically) enumerates a number of child devices (PDOs) for which I have a corresponding driver. FWIW this is a *closed* system and ...

Using Device Interfaces - Microsoft Corporation: Software ...
To obtain a device interface's symbolic link name, the user-mode application can call ... If the driver supports multiple instances of the interface, it can ...

INFO: Understanding Device Names and Symbolic Links
There can be multiple symbolic links to a Windows NT device name. However, only the MS-DOS device name that the system initially assigned to the internal ...

The NT Insider:Meandering Through the Object Manager -- How to Get ...
SetupDi returns the name of the symbolic links for each device instance that ... driver may create multiple symbolic links which reference the same target device.

OSR's ntdev List: StorMiniport driver's multiple instance
... for a multiple instance. My understanding is: If more than one device has ... For every instance, the storport will create an unique device-object with symbolic link name ...

Creating Raw Devices - Metro State Home | We Educate Colorado ...
... bypasses it by using raw devices. This allows nodes running different instances to ... disk that can be assigned multiple ... partitions can then be given symbolic link names ...

Multiple Instances of the Same Device - Device-Driver - Windows-XP
You have searched for "Multiple Instances of the Same Device". You might be interested in the following threads: Ethernet Vlan-aware ...

How to get the Serial Number from a USB disk
... USB hubs), and we also need the "Instance ID" of the device itself (sorta like a device driver name). ... the DeviceNumber ' of each of the device's Symbolic Name ...

7/23/2012 11:56:12 AM