|
i would try devcon again.. i had the exact same issue, dev manager shows it there fine, but widcomm drivers say its disabled, unplugging it and pluging it back in again works fine. same as when i run devcon it fixes it too. i havent tried restarting a device via devcon but writing a script to make devcon disable the device then enable the device works great. have ou tried this? another thing to note is to make the script pause until the device is disabled otherwise it won't work.
heres the script i made using autohotkey, the stuff in brackets after each line should be deleted, i just added it here to say what each line does. the pause at the end can be made smaller or not there, trial and error will tell you. also you may need to change the code for the device, i used pid_200a as it was part of the pid of my device, and didnt interfere with any other devices. there is info around here for hwo to use devcon.. if you are like me just type devcon /? and work it out from there. i think i used something like devcon find *usb* and that listed all usb devices, and from there looked for something in their codes that was unique to the bluetooth adapter, the * on either side indicated "(any number of any characters)pid_200a(any number of any characters)
runwait devcon disable *pid_200a* (disables bluetooth adapter)
runwait devcon enable *pid_200a* (enables bluetooth adapter)
sleep, 10000 (pause for 10 seconds to give time for bluetooth software to load and enable the adapter before starting xport)
run c:\xport3\xport.exe
anyways if u need any more help just ask.
|
Linear Mode
