I've read all the references in this string of e-mails (Wikipedia and sometimes further) and believe that I understand the scope of the problem. I am though a few levels too lightweight to work this out myself. Many thanks for the effort getting to this point.
Instead of just booting Windows and getting on with it I would like to solve this problem. You guys can probably gauge how much hand-holding I would require. Off-list I'd be glad to tell you about my background. I'd be glad to document the solution. (I don't know anything about Wikis but I can read.) I'm not in a hurry and can work with people who work 80 hour days and take vacations.
If this is worth pursuing I am available.
thanks,,, Alan,,, n4lbl
On Thu, Feb 12, 2015 at 1:22 PM, Tom Hayward tom@tomh.us wrote:
On Thu, Feb 12, 2015 at 12:08 PM, Aubrey Turner aubrey.c.turner@gmail.com wrote:
I finally found the driver installer and unpack it (using WINE on Ubuntu
so
as not to mess up my Windows laptop).
What I found is that the Windows driver is just a repackaged version of
the
FTDI drivers using the vendor and device IDs that RATOC has assigned to
the
cable.
So, you might be able to try using modprobe to load the the FTDI driver (ftdi_sio) and the RATOC IDs. It's not guaranteed to work, but it may be worth a try.
You should be able to automate this with a udev rule, too. There's more information here: http://chirp.danplanet.com/projects/chirp/wiki/CableGuide_FTDI_OEM_Cables
Who was that complaining about the Chirp website?
Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users Unsubscribe: http://intrepid.danplanet.com/mailman/options/chirp_users