From: Ekkehard <edo...@ad...> - 2011-12-23 10:49:18
|
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. 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). 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. Thanx for helping!!! Happy xmas for all of you wishes Ekkehard -- View this message in context: http://libusb.6.n5.nabble.com/Driver-installation-failed-Error-39-Vista-64-bit-tp5088225p5096868.html Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com. |