On Fri, Sep 28, 2012 at 4:13 PM, Robert Terzi <rct@r-t.org> wrote:

Ahh that's very interesting. If I'm following what you did on some version
of windows, what you did was to replace the driver that was associated with
the RT VID/PID with the current FTDI driver, which let you then tell it to
provide a Virtual COM Port (VCP) in addition to the FTDI Direct I/O interface.

(In other words you associated the FTDI drivers with the RT VID/PID without
having to edit the .inf file.)

On 9/28/2012 6:54 PM, Cory (NQ1E) wrote:
>
> Here's what worked:
>
> - Download the VCP driver zip file and expand it to a folder - http://www.ftdichip.com/FTDrivers.htm
> - Open up the device manager and update the driver for the RT cable device
> - Go though the "let me choose" and "have disk" options to point it at the folder where the files were unzipped.
> - Install the driver that shows up even if it warns about it not being compatible.
> - The device now shows up as "USB Serial Converter", go to its properties/advanced tab and check the box called "Load VCP".
> - Unplug the device and plug it back in
> - A new com port device will show up, but a driver will not load for it automatically.
> - Go thought the same process as before to install the driver from that unzipped folder.

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users