<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Yes, I've done that many times, and as a result, Chirp is only
reporting the actual COM ports I have connected.<br>
<br>
When I said, "I use COM ports w/ Chirp into the hundreds", I didn't
mean that I <b>have</b> hundreds of COM ports (I only have
sixteen); I meant that they are <b>numbered</b> into the
hundreds. The numbers are (intentionally) not sequential.<br>
<br>
For one example, when using a Prolific USB-to-serial port converter,
moving the converter to another USB port also changes the COM port.
My Dell Windows 7 box came with 12 externally available USB ports.
In order to tell what USB port is connected to what COM port in
Windows Device Manager, I've renumbered the COM ports to correspond
to the USB port/device indexes.<br>
<br>
As an aside, I also use Digi International's PortServer devices,
that support a remote serial port (anywhere in the world) over
Ethernet. I use one in the garage to connect to my Icom IC-2820H,
from my computer in the house. Yes, I have an Ethernet connection
in almost every room in my house, plus the garage. It took a bit of
crawling around in the attic about ten years ago, but it has been
worth it !!!<br>
<br>
Digi also makes wireless versions. You can pick up the wired ones
(two or four serial ports) on eBay for around $60. An added benefit
is that I can connect to my (seven) radios from any computer in the
house, once I've installed Digi drivers on that computer.<br>
<br>
Unlike some hardware manufacturers, Digi actively supports old
devices with firmware upgrades and drivers for new operating
systems. My two Digi "PortServer" models were released around 2005,
and the older one had a new firmware release in 2011; the newer
one, in 2012. Both have Windows 7 64-bit driver support.<br>
<br>
-- Dean<br>
<br>
<div class="moz-cite-prefix">On 2013-02-12 13:56, Phaeton wrote:<br>
</div>
<blockquote
cite="mid:5A6A2B16-92BD-4D89-8C96-6CAEB98E1508@neo.rr.com"
type="cite">...Those are ports still written in the registry
previously used.
<div><br>
</div>
But they can be used again; I've done it several times.
<div><br>
</div>
When you change the driver com port and it says "In Use", just
ignore and ok the change.
<div><br>
</div>
<div>
<div>On Feb 12, 2013, at 4:04 PM, Dean Gibson AE7Q <<a
moz-do-not-send="true" href="mailto:data@ae7q.net">data@ae7q.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000"> <br>
<div class="moz-cite-prefix">On 2013-02-08 22:21, Dean
Gibson AE7Q wrote:<br>
</div>
<blockquote cite="mid:5115EAFA.8020904@ae7q.net" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
...<br>
<br>
Well, I use COM ports w/ Chirp into the 100s. I agree
that enumerating or "blindly" extending the list is a bad
idea. My suggestion is to remember any valid (1-256) COM
port(s) manually entered into the "COM box", and present
them in future invocations.<br>
<br>
-- Dean AE7Q<br>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>