David G <> wrote:
>
>My environment is that I have one of these: http://www.x10.com/products/x10_cm19a.htm
>and the drivers available for it have no documentation at all.
>Therefore it's impossible to write 3rd party software that can talk to
>it. I've taken the Linux driver source as a reference point, and have
>got to the stage that I can open the device, and the two pipes on it.
>
>The big problem I face is the development cycle time. Every time I
>rebuild the driver, it appears I have to reboot to get it recognized.
>Even though I can overwrite the old one in \windows\system32\drivers,
>changes don't take effect till I reboot. Is there a faster way to do
>this, some way to tell windows to stop using the old driver and start
>using the new?
One viable way is to unplug and replug the device.
Another way is to use the "devcon" tool from the DDK/WDK:
devcon restart usb\vid_xxxx^&pid_xxxx*
Substitute your own VID and PID. The ^ is there to escape the &, which has
meaning to the cmd shell.
>Secondly, once you do have a driver candidate, is it even possible for
>an individual working on a driver, evenings and weekends, to get
>Miscrosoft to certify something, and if so, exactly how would I go
>about doing this?
No, but for complicated reasons. In order to submit for WHQL, you have to
open a Winqual account. To open a Winqual account, you must have a
Verisign signature certificate. Verisign will not issue certificates to
individuals -- only to corporations.
--
Tim Roberts,
Providenza & Boekelheide, Inc.
Similar Threads
Linear Mode
