That way they would learn about the situation and the need to upgrade driver (it takes 3 minutes for an enduser to upgrade after 500 mins of headache caused by apparently application problems, and maybe 0.01 min / sold cable for the manufacturer to update the zipfile on the CD). Maybe it's a good idea to notify manufacturers who purchase millions of these chips with broken drivers released. Somehow the information did not make it to the 10 cable manufacturers prolific sells millions of these (HW-wise great!) chips. The broken 2003-2005 drivers are more common than one would think, included on many CD's even several years after prolific found out it's broken and fixed in new releases. (2007-xx-xx_ seemed to work on at least one windows-XP, but not recommended anyway.2.0.0.26 () seems to work on at least one windows-XP, but not recommended anyway.other drivers from 2003 also suspected to be broken (reports from non-developers).Verify in the device manager / com ports / properties that you do not have this. Prolific windows-XP driver version 2.0.2.1 () is broken without any doubt. What's worse, they seemed to work with TerminalProgram, and under some circumstances (not sending too much data at a time, waiting a lot, etc.). Most of the WINDOWS drivers released by prolific over the years were seriously broken. For more information, release notes are included in ZIP file. , which contains the 2.0.13.130 XP driver.The driver from the adapter-cable CD is likely to cause you many problems. (only as a last chance after you tried everything else without luck, but that should never happen). DO NOT USE THE DRIVER CD from the USB-RS232 adapter box.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |