View Single Post
  #62 (permalink)  
Old 02-04-2007, 05:45 PM
ImCoKeMaN's Avatar
ImCoKeMaN
Retired Staff
Offline
Threadstarter
 
Join Date: Dec 2006
Posts: 918
Reputation: 3178
ImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
USB driver update

I was looking at other OEM packages that seem to reference the USB and or the same memory area that was causing problems with the ms2_usbfn.dll package and it looks like the ohci.dll package may be related/conflicting. There are reg entries in there for QCT1.DLL, but the package builds a QCT.dll. This piqued by curiosity so i decided to rename the reg entry to the actual DLL name.

After flashing a rom with this change a USB connection was made, but it wasn't for activesync. It pops up "composite USB Device" in the found new hardware bubble then, "HTC Diagnostic Interface (PID 0B03)" and asks for the qcmdmxp.sys driver on my PC. So i am pretty sure this isn't gonna help too much with the active sync as it's not the usbfn driver, but it was nice have windows at least recognize that i connected a device.
Reply With Quote