From: 0dbell on
I am trying to use devcon.exe to ease the pain of repetitively re-
installing a device driver under development for test & debug
purposes.

The device driver I am developing is based on MSVA (i.e. has no real
hardware).

When I attemp invoking it like this:

devcon.exe update msvad.inf

I get the error message: "devcon.exe: Invalid use of update."

It seems that it also requires hwid as the second parameter?

So I typed:

devcon.exe hwids *

but all I get is: "No matching devices found."

What could be not matching in the wild card * ?????????

What does devcon.exe do? Does it work at all?

Or am I so sleepless and tired that I can't even get a clue how to use
a simple tool like this?

Thanks,
Don

P.S. If there is another way to re-install a driver (specified by .inf
and a path to the actual location of the .sys driver file) without the
annoying required mouse clicking on the update driver wizard, I would
appreciate describing it here.

From: Gianluca Varenni on
devcon update works for plug and play devices only (in fact you don't have
an HWID).

I would try to use devcon install (although i'm not 100% sure it will work,
and i cannot find the this MSVA sample).

Have a nice day
GV


<0dbell(a)gmail.com> wrote in message
news:1180698646.324561.232290(a)g4g2000hsf.googlegroups.com...
>I am trying to use devcon.exe to ease the pain of repetitively re-
> installing a device driver under development for test & debug
> purposes.
>
> The device driver I am developing is based on MSVA (i.e. has no real
> hardware).
>
> When I attemp invoking it like this:
>
> devcon.exe update msvad.inf
>
> I get the error message: "devcon.exe: Invalid use of update."
>
> It seems that it also requires hwid as the second parameter?
>
> So I typed:
>
> devcon.exe hwids *
>
> but all I get is: "No matching devices found."
>
> What could be not matching in the wild card * ?????????
>
> What does devcon.exe do? Does it work at all?
>
> Or am I so sleepless and tired that I can't even get a clue how to use
> a simple tool like this?
>
> Thanks,
> Don
>
> P.S. If there is another way to re-install a driver (specified by .inf
> and a path to the actual location of the .sys driver file) without the
> annoying required mouse clicking on the update driver wizard, I would
> appreciate describing it here.
>


From: 0dbell on
On Jun 1, 12:43 pm, "Gianluca Varenni"
<gianluca.vare...(a)community.nospam> wrote:
> devcon update works for plug and play devices only (in fact you don't have
> an HWID).
>
> I would try to use devcon install (although i'm not 100% sure it will work,
> and i cannot find the this MSVA sample).
>

Than you, Gianluca. I actually meant to write MSVAD sample, not MSVA.
This was a typo.

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).

Thanks,
Don


From: Gianluca Varenni on
For a non-pnp driver the easiest way is issuing a "net stop <drivername>"
followed by a "net start <drivername>" on the command prompt.

Have a nice day
GV

<0dbell(a)gmail.com> wrote in message
news:1180723948.931682.83750(a)p47g2000hsd.googlegroups.com...
> On Jun 1, 12:43 pm, "Gianluca Varenni"
> <gianluca.vare...(a)community.nospam> wrote:
>> devcon update works for plug and play devices only (in fact you don't
>> have
>> an HWID).
>>
>> I would try to use devcon install (although i'm not 100% sure it will
>> work,
>> and i cannot find the this MSVA sample).
>>
>
> Than you, Gianluca. I actually meant to write MSVAD sample, not MSVA.
> This was a typo.
>
> 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).
>
> Thanks,
> Don
>
>


From: 0dbell on
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?

Thanks,
Don