The exclamation mark means you have a conflict. Fix your port settings.
Jock KC6IIH Sent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone
-------- Original message -------- From: Wes kb9oic@gmail.com Date:02/09/2014 7:56 PM (GMT-08:00) To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] Windows 8
I used Chirp on my XP machine with a Boefeng UV-5R and on Kenwood D72. I had no problems connecting until I went to Windows 8 Now when I use the cables and start with download from radio the box for the Com port does not comes up. Nothing happens. I check device manager and it shows an exclamation mark in the com port setting. Any suggestions
Here is how delete your old ports that are left over from other adapters. Click Start Click Run Type cmd.exe in the textbox and click OK Type set devmgr_show_nonpresent_devices=1 and hit ENTER Type cd\windows\system32 and hit ENTER Type start devmgmt.msc and hit ENTER When the device manager opens, click the View menu Click Show Hidden Devices Click on the + sign next to the Ports to see the full list of Com ports being used Highlight the port you wish to delete and then press delete Mike va3mw
On Feb 10, 2014, at 12:00 AM, kc6iih kc6iih@aol.com wrote:
The exclamation mark means you have a conflict. Fix your port settings.
Jock KC6IIH Sent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone
-------- Original message -------- From: Wes Date:02/09/2014 7:56 PM (GMT-08:00) To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] Windows 8
I used Chirp on my XP machine with a Boefeng UV-5R and on Kenwood D72. I had no problems connecting until I went to Windows 8 Now when I use the cables and start with download from radio the box for the Com port does not comes up. Nothing happens. I check device manager and it shows an exclamation mark in the com port setting. Any suggestions
-- Wes 73's KB9OIC _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
You will have a few COM ports that are written to the registry that may not have been used in years yet still prevent the automatic driver assignment. You can use Jim Mitchell's cabletest utility that will read the list of COM ports and check for a cable. When it comes upon an empty port it advises "invalid port" and that port can be over written by a manual driver install. I've done it with many older programs that don't address COM ports over 8 and I have a cable that got COM 9. Since I know what ports my other equipment occupy I just install the driver and choose a "invalid port" and tell the driver install to yes, use this port when it complains if it's already in use.
________________________________ From: Mike va3mw va3mw@portcredit.net To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Monday, February 10, 2014 12:24 AM Subject: Re: [chirp_users] Windows 8
Here is how delete your old ports that are left over from other adapters. 1. Click Start 2. Click Run 3. Type cmd.exe in the textbox and click OK 4. Type set devmgr_show_nonpresent_devices=1 and hit ENTER 5. Type cd\windows\system32 and hit ENTER 6. Type start devmgmt.msc and hit ENTER 7. When the device manager opens, click the View menu 8. Click Show Hidden Devices 9. Click on the + sign next to the Ports to see the full list of Com ports being used 10. Highlight the port you wish to delete and then press delete Mike va3mw
On Feb 10, 2014, at 12:00 AM, kc6iih kc6iih@aol.com wrote:
The exclamation mark means you have a conflict. Fix your port settings.
Jock KC6IIHSent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone
-------- Original message -------- From: Wes Date:02/09/2014 7:56 PM (GMT-08:00) To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] Windows 8
I used Chirp on my XP machine with a Boefeng UV-5R and on Kenwood D72. I had no problems connecting until I went to Windows 8 Now when I use the cables and start with download from radio the box for the Com port does not comes up. Nothing happens. I check device manager and it shows an exclamation mark in the com port setting. Any suggestions
On Mon, Feb 10, 2014 at 12:00 AM, kc6iih kc6iih@aol.com wrote:
The exclamation mark means you have a conflict. Fix your port settings.
Jock KC6IIH
Jock,
You are partially correct.
The exclamation mark is because there is a conflict with the driver and the chip in the programming cable.
Most inexpensive programming cables have an unauthorized copy of Prolific's USB-to-Serial chip in them. These copied chips use the same Prolific driver that the genuine Prolific chips require. Prolific eventually changed their drivers after v3.3.2.105 to not function (hence the error) with the unauthorized copies.
Windows Vista and newer (ie: 7, 8 & 8.1), will automatically install the latest driver when a USB cable with a Prolific type chip is plugged into a USB port that doesn't already have a driver configured. If the cable has an unauthorized chip, the driver installation is guaranteed to fail.
The only fix that will eliminate the conflict with an unauthorized Prolific chip is to downgrade the driver to at least v3.3.2.105. Some of the Chinese programming software have a conflict with the v3.3.2.102 or v3.3.2.105 Prolific driver versions (CHIRP has no such issues and runs fine) so the general recommendation is to downgrade to the v3.2.0.0 driver.
Windows XP does not automatically install the latest driver, but is recommended that v2.0.2.1 is the driver version to install to avoid a conflict with an unauthorized copy of the Prolific chip.
Other solutions would be to purchase and use a programming cable with genuine Prolific chip or a programming cable with another brand of chip (FTDI for example).
Jim KC9HI
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.
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.
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.
Mike va3mw
On Mon, Feb 10, 2014 at 6:06 AM, Jim Unroe rock.unroe@gmail.com wrote:
On Mon, Feb 10, 2014 at 12:00 AM, kc6iih kc6iih@aol.com wrote:
The exclamation mark means you have a conflict. Fix your port settings.
Jock KC6IIH
Jock,
You are partially correct.
The exclamation mark is because there is a conflict with the driver and the chip in the programming cable.
Most inexpensive programming cables have an unauthorized copy of Prolific's USB-to-Serial chip in them. These copied chips use the same Prolific driver that the genuine Prolific chips require. Prolific eventually changed their drivers after v3.3.2.105 to not function (hence the error) with the unauthorized copies.
Windows Vista and newer (ie: 7, 8 & 8.1), will automatically install the latest driver when a USB cable with a Prolific type chip is plugged into a USB port that doesn't already have a driver configured. If the cable has an unauthorized chip, the driver installation is guaranteed to fail.
The only fix that will eliminate the conflict with an unauthorized Prolific chip is to downgrade the driver to at least v3.3.2.105. Some of the Chinese programming software have a conflict with the v3.3.2.102 or v3.3.2.105 Prolific driver versions (CHIRP has no such issues and runs fine) so the general recommendation is to downgrade to the v3.2.0.0 driver.
Windows XP does not automatically install the latest driver, but is recommended that v2.0.2.1 is the driver version to install to avoid a conflict with an unauthorized copy of the Prolific chip.
Other solutions would be to purchase and use a programming cable with genuine Prolific chip or a programming cable with another brand of chip (FTDI for example).
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Or you could use linux, Mike. The day that prolific publishes the source code for its DRM function is the day that the counterfeiters will change their design to get around it!
73 de Nigel ve3id
On 02/10/2014 08:42 AM, Michael Walker wrote:
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.
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.
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.
Mike va3mw
On Mon, Feb 10, 2014 at 6:06 AM, Jim Unroe rock.unroe@gmail.com wrote:
On Mon, Feb 10, 2014 at 12:00 AM, kc6iih kc6iih@aol.com wrote:
The exclamation mark means you have a conflict. Fix your port settings.
Jock KC6IIH
Jock,
You are partially correct.
The exclamation mark is because there is a conflict with the driver and the chip in the programming cable.
Most inexpensive programming cables have an unauthorized copy of Prolific's USB-to-Serial chip in them. These copied chips use the same Prolific driver that the genuine Prolific chips require. Prolific eventually changed their drivers after v3.3.2.105 to not function (hence the error) with the unauthorized copies.
Windows Vista and newer (ie: 7, 8 & 8.1), will automatically install the latest driver when a USB cable with a Prolific type chip is plugged into a USB port that doesn't already have a driver configured. If the cable has an unauthorized chip, the driver installation is guaranteed to fail.
The only fix that will eliminate the conflict with an unauthorized Prolific chip is to downgrade the driver to at least v3.3.2.105. Some of the Chinese programming software have a conflict with the v3.3.2.102 or v3.3.2.105 Prolific driver versions (CHIRP has no such issues and runs fine) so the general recommendation is to downgrade to the v3.2.0.0 driver.
Windows XP does not automatically install the latest driver, but is recommended that v2.0.2.1 is the driver version to install to avoid a conflict with an unauthorized copy of the Prolific chip.
Other solutions would be to purchase and use a programming cable with genuine Prolific chip or a programming cable with another brand of chip (FTDI for example).
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
- -- Nigel Johnson MSc., MIEEE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
http://nigel.homelinux.net http://va3mcu.ham-radio-op.net
You can reach me by voice on Skype: TILBURY2591
If time travel ever will be possible, it already is. Ask me again yesterday
This e-mail is not and cannot, by its nature, be confidential. En route from me to you, it will pass across the public Internet, easily readable by any number of system administrators along the way. Nigel Johnson nw.johnson@ieee.org
Please consider the environment when deciding if you really need to print this message
OT for anyone who is interested…
there is no drm, per-se.. it's simply a few extra ways that genuine pl2303 chips respond differently compared to the copies. It's been known for some time, plus a simple decompilation and trace through the driver code shows what is causing the issue…
Here is a few year old blog post that explains some of the differences ;) http://dreamlayers.blogspot.com/2011/10/pl-2303-code-10-error.html
If it weren't for the fact that the workaround is so simple (use older version) with no appreciable loss of features, someone might be inclined to package a modified driver ;)
Actually I'm quite surprised the counterfeiters havent modified the chips to react the same as genuine chips. Probably a combination of factors (mainly that old drivers work fine ;)
-J
________________________________ From: "Nigel Johnson, MIEEE" nw.johnson@ieee.org To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Monday, February 10, 2014 7:49 AM Subject: Re: [chirp_users] Windows 8
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Or you could use linux, Mike. The day that prolific publishes the source code for its DRM function is the day that the counterfeiters will change their design to get around it!
73 de Nigel ve3id
On 02/10/2014 08:42 AM, Michael Walker wrote:
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.
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.
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.
Mike va3mw
On Mon, Feb 10, 2014 at 6:06 AM, Jim Unroe rock.unroe@gmail.com wrote:
On Mon, Feb 10, 2014 at 12:00 AM, kc6iih kc6iih@aol.com wrote:
The exclamation mark means you have a conflict. Fix your port settings.
Jock KC6IIH
Jock,
You are partially correct.
The exclamation mark is because there is a conflict with the driver and the chip in the programming cable.
Most inexpensive programming cables have an unauthorized copy of Prolific's USB-to-Serial chip in them. These copied chips use the same Prolific driver that the genuine Prolific chips require. Prolific eventually changed their drivers after v3.3.2.105 to not function (hence the error) with the unauthorized copies.
Windows Vista and newer (ie: 7, 8 & 8.1), will automatically install the latest driver when a USB cable with a Prolific type chip is plugged into a USB port that doesn't already have a driver configured. If the cable has an unauthorized chip, the driver installation is guaranteed to fail.
The only fix that will eliminate the conflict with an unauthorized Prolific chip is to downgrade the driver to at least v3.3.2.105. Some of the Chinese programming software have a conflict with the v3.3.2.102 or v3.3.2.105 Prolific driver versions (CHIRP has no such issues and runs fine) so the general recommendation is to downgrade to the v3.2.0.0 driver.
Windows XP does not automatically install the latest driver, but is recommended that v2.0.2.1 is the driver version to install to avoid a conflict with an unauthorized copy of the Prolific chip.
Other solutions would be to purchase and use a programming cable with genuine Prolific chip or a programming cable with another brand of chip (FTDI for example).
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
- -- Nigel Johnson MSc., MIEEE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
http://nigel.homelinux.net http://va3mcu.ham-radio-op.net
You can reach me by voice on Skype: TILBURY2591
If time travel ever will be possible, it already is. Ask me again yesterday
This e-mail is not and cannot, by its nature, be confidential. En route from me to you, it will pass across the public Internet, easily readable by any number of system administrators along the way. Nigel Johnson nw.johnson@ieee.org
Please consider the environment when deciding if you really need to print this message
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On Mon, Feb 10, 2014 at 8:42 AM, Michael Walker va3mw@portcredit.netwrote:
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.
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.
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.
Mike va3mw
Mike,
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.
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.
Jim KC9HI
How the virtual device driver is written to the registry usually determines the port associated with the cable. Each USB port on a hub is given a unique ID of course. And when the virtual device gets listed in the registry the port is also written. Or something like that. I've been dealing with the Windows driver and port Musical Chairs since 2000. Also in Linux and OSX. But I believe there are three things needed to keep a COM port associated with a USB ID and one is in the device driver. I used to use a Windows 2000 virtual device driver for an old Radio Shack USB to DB9 cable. 2000 was the most current driver. I got it to work with Windows Vista and Windows 7 but it caused havoc with the other COM port drivers. One driver for a Prolific cable would suddenly re-appear with a yellow question mark when the Windows 2000 driver was active. When the old cable was unplugged the yellow question mark went away but the COM ports were all changed, two at that time for two different 2303 cables. So I ended up booting into Vista and using the old cable there. Was too much bother to rest the COMs back to there proper device.
________________________________ From: Jim Unroe rock.unroe@gmail.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Monday, February 10, 2014 4:45 PM Subject: Re: [chirp_users] Windows 8
On Mon, Feb 10, 2014 at 8:42 AM, Michael Walker va3mw@portcredit.net wrote:
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.
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.
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.
Mike va3mw
Mike,
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.
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.
Jim KC9HI
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
participants (7)
-
Jens J. -
Jim Unroe -
kc6iih -
Michael Walker -
Mike va3mw
-
Milton Hywatt -
Nigel Johnson, MIEEE