From: Travis <lib...@gm...> - 2011-12-23 14:02:53
|
On 12/23/2011 2:49 AM, Ekkehard wrote: > Its running now, but why? > It's a bit like the 4 states of an instrument given by Murphy: > - State 0: Everything is running and you know why > - State 1: Something is broken, but you know what/why > while you attempt to repair the state is changed to > - State 2: The thing is running, but you *dont* know why > and the last and finite state is waiting > - State 3: Something is broken, and you dont know what/why > > So we reach state 2! > > What I have done was using Zadig and transforming the (not running) > installed libusbK driver into a WinUSB driver. This approach yesterday > failed with a timeout ("and how was your day...") and an uncontrolable Zadik > sw. I hate not knowing what happened! Occasionally, my host controller malfunctions and causes problems similar to this. I must *cold* boot my machine before it works correctly again. Could it have been something like this? > Today everything went well, and the WinUSB driver was installed and > successfully started. > Next I installed a driver from the Devicemanager from the list (a libusbK > based made by Zadig) this runs as well, and to the end I installed my > original driver (probably one with cat file commented out in the inf file, > but I am not sure), which runs also well (after a long delay in the install > procedure). lol.. At-least everything is working now; you probably couldn't reproduce this error if you wanted to. ;) I know I couldn't. > Now the device is installed and running - if I can communicate with the > device is not clear, but probably beyond the scope of this topic. > If it says it's functioning properly, then the driver has already sent several control transfers and selected config #1 successfully. Probably, everything is A-OK. > Thanx for helping!!! > Happy xmas for all of you wishes Ekkehard > Ho-Ho-Ho Merry Christmas, Travis |