Bad advice.. prolific devices are terrible when data overruns happen and not
just for ham, but for gamers and labs too.

This is another klugde to make these crappy drivers work under windows 10.

Get an FTDI or SILabs chipset..  much more stable




-----Original Message-----
From: Elecraft [mailto:[email protected]] On Behalf Of hb9brj
Sent: Friday, March 18, 2016 2:39 PM
To: [email protected]
Subject: Re: [Elecraft] Prolific driver windows 10

Together with my K3 I ordered a KUSB back in 2008 (?) but never used it.
Today I opened the package. The instruction sheet is Revision A, dated
October 8, 2007. The enclosed mini-CD was unreadable, so I plugged the KUSB
into my Windows 10 PC and wondered what would happen. A driver was found but
the entry in Device Manager showed the famous yellow triangle plus an error
messge "The device cannot start (Code 10)".

After reading this and other threads in the Elecraft reflector I didn't want
to give up, but quickly found this solution:
http://leftbraintinkering.blogspot.ch/2013/05/usb-to-serial-prolific-2303-de
vice.html

Works great! No need to throw away your old Prolific PL2303 device!

73, Markus HB9BRJ



--
View this message in context:
http://elecraft.365791.n2.nabble.com/Prolific-driver-windows-10-tp7605939p76
15294.html
Sent from the Elecraft mailing list archive at Nabble.com.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html Message
delivered to [email protected]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]

Reply via email to