> I think this is a libusb-win32 problem and not a libftdi problem. > > You may want to subscribe to libusb-win32 mailing list and > ask there. > > I am the other admin of libusb-win32 but I am more on the > testing side and support side. I do not have a good answer for > you right now. For more difficult questions like this, > Travis (libusb-win32 main developer) may be able to give you > some suggestions. > > libusb-win32 mailing list: > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >
Okay I will try that. Thanks! One more question though... I figured out why it keeps changing comports, and that is because after the module gets programmed I am calling the usb_reset() function. So that resets the module and that is what takes the device manager so much time to recognize it and change comports. The reason I am resetting it though is because I need a way to recognize that the module has been programmed, and I don't know how to do that other than resetting the device and checking for the name of the new device in the device manager. So my question; Is there a better way to search for module to check if they have been programmed using libftdi, rather than resetting the device and looking for the module that way? I will ask the same thing on the other mailing list as well. -- Devon Lind Crystalfontz America, Inc. 12412 East Saltese Ave Spokane Valley, WA 99216-0357 Twitter @Crystalfontz [email protected] http://www.crystalfontz.com Phone: 1-509-892-1200, Fax: 1-509-892-1203, US Toll Free: 888-206-9720 -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
