Check back though the messages for the last 2 or 3 days. Someone described how they setup their Win 8 computer. I believe this is it.<div><br></div><div><a href="http://groups.yahoo.com/group/baofeng_uv5r/message/23154">http://groups.yahoo.com/group/baofeng_uv5r/message/23154</a></div>
<div><br></div><div>Jim KC9HI<br><br><div class="gmail_quote">On Mon, Mar 11, 2013 at 8:39 PM, Don <span dir="ltr">&lt;<a href="mailto:dbwjr1949@verizon.net" target="_blank">dbwjr1949@verizon.net</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-size:24px;font-family:Arial"><div>Is there a programming fix for the <span>Baofeng</span> UV-5RA transceiver with firmware BFB297?  I ordered the programming cable and <span>cd</span> from amazon.<span>com</span>, but was sent the <span>cd</span> for the UV-5R transceiver which does not work (I guess).  I have windows 8 so I really could not try this <span>cd</span> for obvious reasons.  Any help will be greatly appreciated.</div>
<div> </div><div>Thank you,</div><div> </div><div>Don, KB3ZUF</div><div> </div><div> </div><div style="BORDER-TOP:#bcbcbc 1px solid;MARGIN:5px 0px"></div><span style="font-size:12px;font-family:arial">On 03/11/13, <span>chirp_users-request@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></span> wrote:</span><div>
 </div><div style="font-size:12px;font-family:arial">Send chirp_users mailing list submissions to<br><a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>
<br>To subscribe or <span>unsubscribe</span> via the World Wide Web, visit<br><a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>mailman</span>/<span>listinfo</span>/chirp_users</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br><a href="mailto:chirp_users-request@intrepid.danplanet.com" target="_blank">chirp_users-request@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>
<br>You can reach the person managing the list at<br><a href="mailto:chirp_users-owner@intrepid.danplanet.com" target="_blank">chirp_users-owner@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br><br>When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of chirp_users digest...&quot;<br><br><br>Today&#39;s Topics:<br><br>1. Re: <span>Yaesu</span> FT-7900R driver needed. I think :) (Tom <span>Hayward</span>)<br>2. win <span>xp</span> (<span>jim</span>)<br>
3. Re: <span>Yaesu</span> FT-7900R driver needed. I think :)<br>(<a href="mailto:chirp.cordless@xoxy.net" target="_blank">chirp.<span>cordless</span>@<span>xoxy</span>.net</a>)<br>4. Re: win <span>xp</span> (<span>Bry</span> <span>Carling</span>)<br>
5. Re: win <span>xp</span> (<span>Alan</span> Hill)<br>6. Re: <span>Yaesu</span> FT-7900R driver needed. I think :) (Apple //GS)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>
Date: <span>Mon</span>, 11 Mar 2013 12:18:54 -0700<br>From: Tom <span>Hayward</span> <a href="mailto:esarfl@gmail.com" target="_blank"><span>esarfl</span>@<span>gmail</span>.<span>com</span></a>&gt;<br>Subject: Re: [chirp_users] <span>Yaesu</span> FT-7900R driver needed. I think :)<br>
To: Discussion of CHIRP &lt;<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a>&gt;<br>Message-ID:<br>&lt;CAFXO5Z3MZNLC5G-_aLEjzpJQmZTtph<a href="mailto:Vd9=Bvcr9JTXJX-R9a4A@mail.gmail.com" target="_blank">Vd9=Bvcr9JTXJX-R9a4A@mail.<span>gmail</span>.<span>com</span></a>&gt;<br>
Content-Type: text/plain; <span>charset</span>=UTF-8<br><br>On <span>Mon</span>, Mar 11, 2013 at 11:52 AM, M.F. <a href="mailto:apple2gs@sbcglobal.net" target="_blank">apple2gs@<span>sbcglobal</span>.net</a>&gt; wrote:<br>
&gt; <span>Hi</span> Tom,<br>&gt;<br>&gt; I an in Windows mode right now, and I did <span>download</span> the FTDI-FT-Device: 0<br>&gt;<br>&gt; Now what? I feel so dumb, but I have no idea what to do. I am sorry to all<br>
&gt; of you for asking what must be simple stuff.<br><br>I don&#39;t remember exactly what it looks like, but in FT_Prog, select<br>the Vendor ID and reset to default, then select the Product ID and<br>reset to defaults. Note that this will make the cable incompatible<br>
with RT Systems software. You can, however, reverse the process by<br>typing the original Vendor and Product <span>IDs</span> back into FT_Prog.<br><br>Tom KD7LXL<br><br><br>------------------------------<br><br>Message: 2<br>
Date: <span>Mon</span>, 11 Mar 2013 12:23:48 -0400<br>From: <span>jim</span> <a href="mailto:jmsrandazzo@gmail.com" target="_blank"><span>jmsrandazzo</span>@<span>gmail</span>.<span>com</span></a>&gt;<br>Subject: [chirp_users] win <span>xp</span><br>
To: <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>Message-ID: &lt;<a href="mailto:513E0514.90509@gmail.com" target="_blank">513E0514.90509@<span>gmail</span>.<span>com</span></a>&gt;<br>
Content-Type: text/plain; <span>charset</span>=ISO-8859-1; format=flowed<br><br>To any one out there .. that have Windows XP <span>i</span> have Windows XP with service<br>pack 3 and <span>i</span> do not have any problems with XP what <span>i</span> have found out about<br>
<span>chrip</span> is find the right cable or drivers and you well not have any problems<br>at all <span>i</span> have used <span>chrip</span> with win 7 win 8 win <span>xp</span> come on out there study<br>your Radio or radios you are going to buy get the right stuff and and use<br>
<span>chrip</span> you well not have any problems with this program..<br><br><br><br>------------------------------<br><br>Message: 3<br>Date: <span>Mon</span>, 11 Mar 2013 12:28:54 -0700<br>From: <a href="mailto:chirp.cordless@xoxy.net" target="_blank">chirp.<span>cordless</span>@<span>xoxy</span>.net</a><br>
Subject: Re: [chirp_users] <span>Yaesu</span> FT-7900R driver needed. I think :)<br>To: <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>
Message-ID: &lt;54E08EEA-104A-40<a href="mailto:B1-A698-AEBED03D11B1@cox.net" target="_blank">B1-A698-AEBED03D11B1@<span>cox</span>.net</a>&gt;<br>Content-Type: text/plain; <span>charset</span>=us-<span>ascii</span><br><br>
Not quite my experience. Note I&#39;m the author of the second link<br>below, under &quot;Modify OS X driver&quot;. That&#39;s what I _ENDED UP_ doing,<br>because it amused me, and there were some small benefits, as that<br>
post explains.<br><br>However, go back to earlier in that same thread, here:<br><a href="http://intrepid.danplanet.com/pipermail/chirp_users/2012-September/002585.html" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>pipermail</span>/chirp_users/2012-September/002585.<span>html</span></a><br>
<br>You can get this working in a turnkey manner by loading the <span>Mac</span><br>driver that RT systems provides. And BTW, I don&#39;t know where you<br>got your RT Systems cable, but it likely comes with a CD with the<br>
Windows driver you need.<br><br>In the middle of that post is the link you want for the <span>Mac</span> driver:<br><a href="http://www.rtsystemsinc.com/kb_results.asp?ID=9" target="_blank"><span>http</span>://<span>www</span>.<span>rtsystemsinc</span>.<span>com</span>/kb_results.asp?ID=9</a><br>
and if you search around on that same support site, I think<br>you&#39;ll find the windows drivers. Here:<br><a href="http://www.rtsystemsinc.com/kb_results.asp?ID=15" target="_blank"><span>http</span>://<span>www</span>.<span>rtsystemsinc</span>.<span>com</span>/kb_results.asp?ID=15</a><br>
<br>If you want more details, please read those two posts, and maybe<br>some more of that same thread.<br><br>-<span>dan</span><br><br>On Mar 11, 2013, at 10:30 AM, &quot;Tom <span>Hayward</span> - <a href="mailto:esarfl@gmail.com" target="_blank"><span>esarfl</span>@<span>gmail</span>.<span>com</span></a>&quot; wrote:<br>
&gt; On <span>Mon</span>, Mar 11, 2013 at 10:20 AM, Apple //GS <a href="mailto:apple2gs@sbcglobal.net" target="_blank">apple2gs@<span>sbcglobal</span>.net</a>&gt; wrote:<br>&gt;&gt; Hello Dan :)<br>&gt;&gt; <br>&gt;&gt; The cable is CT29B Radio Cable:<br>
&gt;&gt; <br>&gt;&gt; CT29B Radio Cable:<br>&gt;&gt; <br>&gt;&gt; Product ID: 0x9e54<br>&gt;&gt; Vendor ID: 0x2100<br>&gt;&gt; Version: 6.00<br>&gt;&gt; Serial Number: RTWA39NN<br>&gt;&gt; Speed: Up to 12 <span>Mb</span>/<span>sec</span><br>
&gt;&gt; Manufacturer: RT Systems<br>&gt;&gt; Location ID: 0xfa123000 / 8<br>&gt;&gt; Current Available (<span>mA</span>): 500<br>&gt;&gt; Current Required (<span>mA</span>): 90<br>&gt; <br>&gt; RT Systems cables are designed to work *only* with RT Systems<br>
&gt; software. There are two options for getting this cable to work with<br>&gt; any other programming software: modify your OS X driver, or modify<br>&gt; your cable. I modified my cable (this is a firmware <span>mod</span>, no soldering<br>
&gt; required).<br>&gt; <br>&gt; Modify the <span>cable&#39;s</span> FTDI firmware:<br>&gt; <a href="http://intrepid.danplanet.com/pipermail/chirp_users/2013-January/002988.html" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>pipermail</span>/chirp_users/2013-January/002988.<span>html</span></a><br>
&gt; <br>&gt; Modify OS X driver:<br>&gt; <a href="http://intrepid.danplanet.com/pipermail/chirp_users/2012-September/002612.html" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>pipermail</span>/chirp_users/2012-September/002612.<span>html</span></a><br>
<br><br><br><br>------------------------------<br><br>Message: 4<br>Date: <span>Mon</span>, 11 Mar 2013 16:45:56 -0400<br>From: &quot;<span>Bry</span> <span>Carling</span>&quot; <a href="mailto:bcarling@cfl.rr.com" target="_blank"><span>bcarling</span>@<span>cfl</span>.<span>rr</span>.<span>com</span></a>&gt;<br>
Subject: Re: [chirp_users] win <span>xp</span><br>To: <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>Message-ID: &lt;<a href="mailto:513E4284.1172.3B2C10@bcarling.cfl.rr.com" target="_blank">513E4284.1172.3B2C10@<span>bcarling</span>.<span>cfl</span>.<span>rr</span>.<span>com</span></a>&gt;<br>
Content-Type: text/plain; <span>charset</span>=&quot;us-<span>ascii</span>&quot;<br><br>This makes it sound easy but it wasn&#39;t at all.<br><br>The program failing to start has noting to do with the cable or the radio.<br>
<br>It has to do with the fact that Chirp requires SP3 and Windows XP is not something<br>that upgrades easily to SP3 from SP1 or SP2. If you don&#39;t believe me, read the hundreds of <br>horror stories all over the web. If it was just me that would be one thing. In the case of my <br>
<span>laptop</span>, Chirp would not start at all, so I know it hasn&#39;t checked what radio, drivers or cable is <br>connected.<br><br>On 11 Mar 2013 at 12:23, <span>jim</span> wrote:<br><br>&gt; To any one out there .. that have Windows XP <span>i</span> have Windows XP with<br>
&gt; service<br>&gt; pack 3 and <span>i</span> do not have any problems with XP what <span>i</span> have found out<br>&gt; about<br>&gt; <span>chrip</span> is find the right cable or drivers and you well not have any<br>&gt; problems<br>
&gt; at all <span>i</span> have used <span>chrip</span> with win 7 win 8 win <span>xp</span> come on out there <br>&gt; study<br>&gt; your Radio or radios you are going to buy get the right stuff and <br>&gt; and use<br>&gt; <span>chrip</span> you well not have any problems with this program..<br>
&gt; <br>&gt; _______________________________________________<br>&gt; chirp_users mailing list<br>&gt; <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>
&gt; <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>mailman</span>/<span>listinfo</span>/chirp_users</a><br>
&gt; <br>&gt; <br>&gt; -----<br>&gt; No virus found in this message.<br>&gt; Checked by AVG - <a href="http://www.avg.com/" target="_blank"><span>www</span>.<span>avg</span>.<span>com</span></a><br>&gt; Version: 2013.0.2904 / Virus Database: 2641/6164 - Release Date:<br>
&gt; 03/11/13<br>&gt; <br><br><br>-------------- next part --------------<br>An HTML attachment was <span>scrubbed</span>...<br>URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20130311/ed8bbe33/attachment-0001.html" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>pipermail</span>/chirp_users/attachments/20130311/ed8bbe33/attachment-0001.<span>html</span></a> <br>
<br>------------------------------<br><br>Message: 5<br>Date: <span>Mon</span>, 11 Mar 2013 13:54:27 -0700<br>From: <span>Alan</span> Hill <a href="mailto:alan.r.hill@gmail.com" target="_blank"><span>alan</span>.<span>r</span>.hill@<span>gmail</span>.<span>com</span></a>&gt;<br>
Subject: Re: [chirp_users] win <span>xp</span><br>To: <span>Brian</span> <span>Carling</span> AF4K <a href="mailto:bcarling@cfl.rr.com" target="_blank"><span>bcarling</span>@<span>cfl</span>.<span>rr</span>.<span>com</span></a>&gt;, Discussion of CHIRP<br>
&lt;<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a>&gt;<br>Message-ID:<br>w<a href="mailto:==KZQxco6mGAygpkoE2g@mail.gmail.com" target="_blank">==KZQxco6mGAygpkoE2g@mail.<span>gmail</span>.<span>com</span></a>&gt;<br>
Content-Type: text/plain; <span>charset</span>=&quot;<span>iso</span>-8859-1&quot;<br><br>I&#39;ve found that you have to run it as administrator to work. It will not<br>show menus until it can access the serial <span>i</span>/<span>o</span>.<br>
73,<br><span>Alan</span> - W6ARH<br>P.S. It doesn&#39;t work at all with my <span>Yeasu</span> radios under 32 bit Win 7. It<br>does work on the same computer with the live CD.<br><br><br><br><br>On <span>Mon</span>, Mar 11, 2013 at 1:45 PM, <span>Bry</span> <span>Carling</span> <a href="mailto:bcarling@cfl.rr.com" target="_blank"><span>bcarling</span>@<span>cfl</span>.<span>rr</span>.<span>com</span></a>&gt; wrote:<br>
<br>&gt; **<br>&gt; This makes it sound easy but it wasn&#39;t at all.<br>&gt;<br>&gt; The program failing to start has noting to do with the cable or the<br>&gt; radio.<br>&gt;<br>&gt; It has to do with the fact that Chirp requires SP3 and Windows XP is not<br>
&gt; something<br>&gt; that upgrades easily to SP3 from SP1 or SP2. If you don&#39;t believe me, read<br>&gt; the hundreds of horror stories all over the web. If it was just me that<br>&gt; would be one thing. In the case of my <span>laptop</span>, Chirp would not start at all,<br>
&gt; so I know it hasn&#39;t checked what radio, drivers or cable is connected.<br>&gt;<br>&gt; On 11 Mar 2013 at 12:23, <span>jim</span> wrote:<br>&gt;<br>&gt; *&gt; To any one out there .. that have Windows XP <span>i</span> have Windows XP with*<br>
&gt; *&gt; service*<br>&gt; *&gt; pack 3 and <span>i</span> do not have any problems with XP what <span>i</span> have found out*<br>&gt; *&gt; about*<br>&gt; *&gt; <span>chrip</span> is find the right cable or drivers and you well not have any*<br>
&gt; *&gt; problems*<br>&gt; *&gt; at all <span>i</span> have used <span>chrip</span> with win 7 win 8 win <span>xp</span> come on out there *<br>&gt; *&gt; study*<br>&gt; *&gt; your Radio or radios you are going to buy get the right stuff and *<br>
&gt; *&gt; and use*<br>&gt; *&gt; <span>chrip</span> you well not have any problems with this program..*<br>&gt; *&gt; *<br>&gt; *&gt; _______________________________________________*<br>&gt; *&gt; chirp_users mailing list*<br>
&gt; *&gt; <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a>*<br>&gt; *&gt; <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users*" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>mailman</span>/<span>listinfo</span>/chirp_users*</a><br>
&gt; *&gt; *<br>&gt; *&gt; *<br>&gt; *&gt; -----*<br>&gt; *&gt; No virus found in this message.*<br>&gt; *&gt; Checked by AVG - <a href="http://www.avg.com*/" target="_blank"><span>www</span>.<span>avg</span>.<span>com</span>*</a><br>
&gt; *&gt; Version: 2013.0.2904 / Virus Database: 2641/6164 - Release Date:*<br>&gt; *&gt; 03/11/13*<br>&gt; *&gt; *<br>&gt;<br>&gt;<br>&gt;<br>&gt; _______________________________________________<br>&gt; chirp_users mailing list<br>
&gt; <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>&gt; <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>mailman</span>/<span>listinfo</span>/chirp_users</a><br>
&gt;<br>&gt;<br>-------------- next part --------------<br>An HTML attachment was <span>scrubbed</span>...<br>URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20130311/27186d76/attachment-0001.html" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>pipermail</span>/chirp_users/attachments/20130311/27186d76/attachment-0001.<span>html</span></a> <br>
<br>------------------------------<br><br>Message: 6<br>Date: <span>Mon</span>, 11 Mar 2013 18:27:00 -0400<br>From: Apple //GS &lt;<a href="mailto:apple2gs@sbcglobal.net" target="_blank">apple2gs@<span>sbcglobal</span>.net</a>&gt;<br>
Subject: Re: [chirp_users] <span>Yaesu</span> FT-7900R driver needed. I think :)<br>To: Discussion of CHIRP &lt;<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a>&gt;<br>
Message-ID: &lt;D0CC7AAD-6D55-4A<a href="mailto:AE-B409-835FDA90E1D0@sbcglobal.net" target="_blank">AE-B409-835FDA90E1D0@<span>sbcglobal</span>.net</a>&gt;<br>Content-Type: text/plain; <span>charset</span>=windows-1252<br>
<br>Okay.<br><br>First thank you all so very much trying to help me<br>CHIRP now has &quot; /<span>dev</span>/<span>cu</span>.<span>usbserial</span>-RTWA39NN &quot; in the pull down menu.<br>I picked both the 7800 and the 8900 to test to see if one of them would work.<br>
<br>This is what it said to be on both tries:<br>Failed to communicate with radio: Failed to read header (0)<br><br><br>??.. :(<br><br>-Mark<br><br><br><br>On Mar 11, 2013, at 3:28 PM, <a href="mailto:chirp.cordless@xoxy.net" target="_blank">chirp.<span>cordless</span>@<span>xoxy</span>.net</a> wrote:<br>
<br>&gt; Not quite my experience. Note I&#39;m the author of the second link<br>&gt; below, under &quot;Modify OS X driver&quot;. That&#39;s what I _ENDED UP_ doing,<br>&gt; because it amused me, and there were some small benefits, as that<br>
&gt; post explains.<br>&gt; <br>&gt; However, go back to earlier in that same thread, here:<br>&gt; <a href="http://intrepid.danplanet.com/pipermail/chirp_users/2012-September/002585.html" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>pipermail</span>/chirp_users/2012-September/002585.<span>html</span></a><br>
&gt; <br>&gt; You can get this working in a turnkey manner by loading the <span>Mac</span><br>&gt; driver that RT systems provides. And BTW, I don&#39;t know where you<br>&gt; got your RT Systems cable, but it likely comes with a CD with the<br>
&gt; Windows driver you need.<br>&gt; <br>&gt; In the middle of that post is the link you want for the <span>Mac</span> driver:<br>&gt; <a href="http://www.rtsystemsinc.com/kb_results.asp?ID=9" target="_blank"><span>http</span>://<span>www</span>.<span>rtsystemsinc</span>.<span>com</span>/kb_results.asp?ID=9</a><br>
&gt; and if you search around on that same support site, I think<br>&gt; you&#39;ll find the windows drivers. Here:<br>&gt; <a href="http://www.rtsystemsinc.com/kb_results.asp?ID=15" target="_blank"><span>http</span>://<span>www</span>.<span>rtsystemsinc</span>.<span>com</span>/kb_results.asp?ID=15</a><br>
&gt; <br>&gt; If you want more details, please read those two posts, and maybe<br>&gt; some more of that same thread.<br>&gt; <br>&gt; -<span>dan</span><br>&gt; <br>&gt; On Mar 11, 2013, at 10:30 AM, &quot;Tom <span>Hayward</span> - <a href="mailto:esarfl@gmail.com" target="_blank"><span>esarfl</span>@<span>gmail</span>.<span>com</span></a>&quot; wrote:<br>
&gt;&gt; On <span>Mon</span>, Mar 11, 2013 at 10:20 AM, Apple //GS <a href="mailto:apple2gs@sbcglobal.net" target="_blank">apple2gs@<span>sbcglobal</span>.net</a>&gt; wrote:<br>&gt;&gt;&gt; Hello Dan :)<br>&gt;&gt;&gt; <br>
&gt;&gt;&gt; The cable is CT29B Radio Cable:<br>&gt;&gt;&gt; <br>&gt;&gt;&gt; CT29B Radio Cable:<br>&gt;&gt;&gt; <br>&gt;&gt;&gt; Product ID: 0x9e54<br>&gt;&gt;&gt; Vendor ID: 0x2100<br>&gt;&gt;&gt; Version: 6.00<br>&gt;&gt;&gt; Serial Number: RTWA39NN<br>
&gt;&gt;&gt; Speed: Up to 12 <span>Mb</span>/<span>sec</span><br>&gt;&gt;&gt; Manufacturer: RT Systems<br>&gt;&gt;&gt; Location ID: 0xfa123000 / 8<br>&gt;&gt;&gt; Current Available (<span>mA</span>): 500<br>&gt;&gt;&gt; Current Required (<span>mA</span>): 90<br>
&gt;&gt; <br>&gt;&gt; RT Systems cables are designed to work *only* with RT Systems<br>&gt;&gt; software. There are two options for getting this cable to work with<br>&gt;&gt; any other programming software: modify your OS X driver, or modify<br>
&gt;&gt; your cable. I modified my cable (this is a firmware <span>mod</span>, no soldering<br>&gt;&gt; required).<br>&gt;&gt; <br>&gt;&gt; Modify the <span>cable&#39;s</span> FTDI firmware:<br>&gt;&gt; <a href="http://intrepid.danplanet.com/pipermail/chirp_users/2013-January/002988.html" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>pipermail</span>/chirp_users/2013-January/002988.<span>html</span></a><br>
&gt;&gt; <br>&gt;&gt; Modify OS X driver:<br>&gt;&gt; <a href="http://intrepid.danplanet.com/pipermail/chirp_users/2012-September/002612.html" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>pipermail</span>/chirp_users/2012-September/002612.<span>html</span></a><br>
&gt; <br>&gt; <br>&gt; _______________________________________________<br>&gt; chirp_users mailing list<br>&gt; <a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>
&gt; <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>mailman</span>/<span>listinfo</span>/chirp_users</a><br>
<br><br><br>------------------------------<br><br>_______________________________________________<br>chirp_users mailing list<br><a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@<span>intrepid</span>.<span>danplanet</span>.<span>com</span></a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank"><span>http</span>://<span>intrepid</span>.<span>danplanet</span>.<span>com</span>/<span>mailman</span>/<span>listinfo</span>/chirp_users</a><br>
<br><br>End of chirp_users Digest, <span>Vol</span> 51, Issue 24<br>*******************************************<br></div></div>
<br>_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
<br></blockquote></div><br></div>