<html><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:14pt"><font size="2">How the virtual device driver is written to the registry <br>usually determines the port associated with the cable.<br>Each USB port on a hub is given a unique ID of course. <br>And when the virtual device gets listed in the registry the port is<br>also written. Or something like that. I've been dealing with the <br>Windows driver and port Musical Chairs since 2000. Also in Linux<br>and OSX. But I believe there are three things needed to keep a <br>COM port associated with a USB ID and one is in the device driver.<br>I used to use a Windows 2000 virtual device driver for an old Radio<br>Shack USB to DB9 cable. 2000 was the most current driver. I got<br>it to work with Windows Vista and Windows 7 but it caused havoc<br>with the other COM port drivers. One driver for a Prolific cable would<br>suddenly re-appear with a yellow
question mark when the Windows <br>2000 driver was active. When the old cable was unplugged the yellow <br>question mark went away but the COM ports were all changed, two at that<br>time for two different 2303 cables. So I ended up booting into Vista and using<br>the old cable there. Was too much bother to rest the COMs back to there proper device. <br></font><div><span><br></span></div><div><br></div> <div style="font-family: verdana, helvetica, sans-serif; font-size: 14pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Jim Unroe <rock.unroe@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> Discussion of CHIRP <chirp_users@intrepid.danplanet.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, February 10, 2014 4:45 PM<br>
<b><span style="font-weight: bold;">Subject:</span></b> Re: [chirp_users] Windows 8<br> </font> </div> <div class="y_msg_container"><br><div id="yiv0629078822"><div><div dir="ltr"><div class="yiv0629078822gmail_extra"><div class="yiv0629078822gmail_quote">On Mon, Feb 10, 2014 at 8:42 AM, Michael Walker <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:va3mw@portcredit.net" target="_blank" href="mailto:va3mw@portcredit.net">va3mw@portcredit.net</a>></span> wrote:<br clear="none">
<blockquote class="yiv0629078822gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr">I also believe that the current FTDI chipset will remember its com port number even if you plug it into a different USB port which is nice and you aren't plugging the cable in only to tell you it is Com54. :) Hence the reason you might want to clean up your old ports with what I sent earlier.<div>
<br clear="none"></div><div>It is hard to solve if you only get the USB to radio programming cable and you have no choice but to back rev their driver.</div><div><br clear="none"></div><div>If you go for the RS232 to radio programming cable, then you do have the option of using a USB certified RS232 port. Going back to the RS232 (DB9 connector) is my failsafe that always works.</div>
<span class="yiv0629078822HOEnZb"><font color="#888888">
</font></span><div><br clear="none"></div><div>Mike va3mw</div></div><br clear="none"></blockquote></div><br clear="none"></div><div class="yiv0629078822gmail_extra">Mike,<br clear="none"><br clear="none"></div><div class="yiv0629078822gmail_extra">I believe you are correct about the FTDI cable using the same com port for different USB ports. I never tried, but I assume it is smart enough to change if 2 or more cables are plugged in at the same time.<br clear="none">
<br clear="none"></div><div class="yiv0629078822gmail_extra">Even though Windows installs another driver (the wrong one in the case of an unauthorized Prolific chip copy), you can then go into the Device Manager to select the older driver and same port as before. So if you take the time up front, you can set the front ports of your computer, for example, to the same driver version and com port number. Then it won't matter which port you plug the USB cable into.<div class="yiv0629078822yqt3201076830" id="yiv0629078822yqtfd00997"><br clear="none">
<br clear="none">Jim KC9HI<br clear="none"></div></div></div></div></div><br><div class="yqt3201076830" id="yqtfd78417">_______________________________________________<br clear="none">chirp_users mailing list<br clear="none"><a shape="rect" ymailto="mailto:chirp_users@intrepid.danplanet.com" href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br clear="none"><a shape="rect" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br clear="none"></div><br><br></div> </div> </div> </div></body></html>