Prev: Question regarding COM ports
Next: For PDO: How to forward request to next lower driver stack automatically in KMDF?
From: Gianluca Varenni on 4 Jun 2007 17:42 <0dbell(a)gmail.com> wrote in message news:1180887471.597057.104260(a)k79g2000hse.googlegroups.com... > On Jun 1, 5:48 pm, "Gianluca Varenni" > <gianluca.vare...(a)community.nospam> wrote: >> For a non-pnp driver the easiest way is issuing a "net stop <drivername>" >> followed by a "net start <drivername>" on the command prompt. >> >> <0db...(a)gmail.com> wrote in message >> >> >> > I actually only need a way to copy over the .sys driver file each time >> > I recompile to test and debug. However, just copying over the older >> > copy doesn't mean the driver is reloaded. Is there a way to accomplish >> > that? (devcon.exe is simply too cumbersome and seems to not be working >> > in my case). >> > > Gianluca, are you sure we are talking about the same thing? My driver > is not a network driver but rather an audio driver. I don't think NET > STOP would do anything here. Or am I wrong? > I might be wrong in this case, I'm not an expert about audio drivers. If noone else is able to help you, and you can post your INF file, I can prolly give you some better idea. Have a nice day GV > Thanks, > Don >
From: Chris Doré on 4 Jun 2007 17:47
> devcon.exe hwids * > > but all I get is: "No matching devices found." Something's wrong. You should get a whole bunch of stuff from `devcon hwids *`. Which DDK/WDK? Did you compile devcon from it's source, or use it from the "tools" directory of the DDK install directory. As for the HWIDs, don't let the term "hardware ID" fool you, virtual devices still have hardware ID's. In the MSVAD inf some examples of HWIDs are "*MSVADSimple", "*MSVADMulti", etc. ....Chris |