K3: latest Prolific drivers for the KUSB

[Chris Gibson-3]

Dick:

In a recent posting you provided a link for the latest Prolific PL-2303
USB-to-serial drivers for the KUSB cable. Is there anything to be gained by
installing the the most recent version, rather than sticking with the
version provided by the link on the Elecraft website?

73 Chris, M0PSK
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Julian, G4ILO]

My abiding principle with anything to do with computers is, if it ain't broke don't fix it!

Chris Gibson-3 wrote

Dick:

In a recent posting you provided a link for the latest Prolific PL-2303
USB-to-serial drivers for the KUSB cable. Is there anything to be gained by
installing the the most recent version, rather than sticking with the
version provided by the link on the Elecraft website?

[Dick Dievendorff]

I think some users were having trouble with applications like N1MM.  There's
was a Prolific driver issue with the MSCOMMCTL32.ocx (I think that's right)
that VB apps use that was fixed in this most recent version.

 

As a matter of general practice I have to try/use the most recent drivers
and learn what's up with them because usually our customers can install the
most recent but rarely are they able to get an n-1 version from the vendor.

 

I'll ask Eric/Brian to update the Elecraft web site versions.

 

73 de Dick, K6KR



 

From: Chris M0PSK [mailto:[hidden email]]
Sent: Thursday, April 08, 2010 2:22 AM
To: Elecraft Reflector; Dick Dievendorff
Subject: K3: latest Prolific drivers for the KUSB

 

Dick:

In a recent posting you provided a link for the latest Prolific PL-2303
USB-to-serial drivers for the KUSB cable. Is there anything to be gained by
installing the the most recent version, rather than sticking with the
version provided by the link on the Elecraft website?

73 Chris, M0PSK

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

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Guy, K2AV]

Windows 7 64 bit at my place was an issue, replete with BSOD if things
not started up in correct order.  New drivers fixed it.  YMMV   No
knowing how many other things were actually involved.  Many use the
old drivers without problem on their existing boxes.  I started over
brand new OS, high end quad core, lots of fast memory, knowing the
price I would pay.  : >)

73, Guy.

On Thu, Apr 8, 2010 at 8:11 AM, Dick Dievendorff <[hidden email]> wrote:

> I think some users were having trouble with applications like N1MM.  There's
> was a Prolific driver issue with the MSCOMMCTL32.ocx (I think that's right)
> that VB apps use that was fixed in this most recent version.
>
>
>
> As a matter of general practice I have to try/use the most recent drivers
> and learn what's up with them because usually our customers can install the
> most recent but rarely are they able to get an n-1 version from the vendor.
>
>
>
> I'll ask Eric/Brian to update the Elecraft web site versions.
>
>
>
> 73 de Dick, K6KR
>
>
>
>
>
> From: Chris M0PSK [mailto:[hidden email]]
> Sent: Thursday, April 08, 2010 2:22 AM
> To: Elecraft Reflector; Dick Dievendorff
> Subject: K3: latest Prolific drivers for the KUSB
>
>
>
> Dick:
>
> In a recent posting you provided a link for the latest Prolific PL-2303
> USB-to-serial drivers for the KUSB cable. Is there anything to be gained by
> installing the the most recent version, rather than sticking with the
> version provided by the link on the Elecraft website?
>
> 73 Chris, M0PSK
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>

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

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[lstavenhagen]

Generally, no, unless you're having a specific problem with it it's best to leave it be.

The hazard of upgrading is breaking a previously working configuration - i.e. the old bugs get replaced with new bugs. This is particularly true of Windows because it's such a nightmarish and expensive platform to develop for - both the API/ABIs and the dev tools are extensively changed from version to version in both gross and subtle ways. It takes a very adept developer to keep track of the changes - he or she has to be rich too because of the cost of endlessly having to buy the dev tools over and over again. .NET levels this a little bit, but even there you find wholesale changes that can really take some digging to find and can really make life tough on you (i.e. the way asynchronous handling of the standard streams for Process objects was pretty much redone in .NET 2.0 and on and on).

For good designs like MacOS X, this isn't as big of a deal, but even there you want to exercise some conservatism (i.e. the wierdness with the recent 64 bit prolific driver release).

My mottos are:
If it ain't broke, that don't necessarily mean it ain't broke.
But if it truly ain't broke, don't fix it.

73,
LS
W5QD