The devcon approach is one I had looked at. I need to work it further perhaps. The issues are that first you need admin or at least debug priv to run some of the api's used and also reseting it only results in the following sequence. Reset, notification of change sent to widcomm watcher, driver changed again. So now we have a fight between the processes to see who can be the last to reset the driver. Anyway I am learning in that I should have been more complete in my description of the problem. Given that I was not I need to look at the devcon source -- its not redistributable so I can't put it with my product. So is this an answer? Hard question. It seems to be but contains less information than I had hoped. Also I apologize as this is my first post and I did not realize that an answer had posted. I got an email from EE saying nothing had posted but then the follow ups did not make it clear to me that something had posted.
Thanks
Main Topics
Browse All Topics





by: Netman66Posted on 2008-11-22 at 14:57:33ID: 23022618
This is fairly simple.
om/kb/3112 72
Use Devcon.exe to reinstall the correct driver to that PnP ID.
http://support.microsoft.c
I would assume the command you would use is Devcon32 updateni <inf> <hwid>. The syntax is a little cryptic.