[chirp_users] Cannot read Baofeng BF-888S
I have strange issue with Windows 10, prolific serial adapter and BF-888S. It reports unable to download from radio.
Driver is proper (version 3.2.0.0, update is disabled), and Chirp works fine with the same adapter and other radio (Baofeng UV-B5) reading and writing.
I tried four different BF-888S and neither can be read.
However, when I use the same USB adapter on my old Windows XP computer, Chirp easily reads and writes those BF-888S.
Has anyone met with this problem?
Yah, i did. Below was my issue. I ended up using oem software finally.
About 6 weeks ago, i purchased the 2 radios listed in the subject line to test them out for work. I programmed them both to the frequencies assigned to our license. We were assigned a corporate license recently, with different frequencies, vs our stand alone site license which is going to expire. Using the same computer, same "fake prolific" Baofeng cloning cable and the updated daily CHIRP software i was able to reprogram the UV5R, but when i went to read the BF888S i received the error message "radio refused to enter programming mode". Any help would be appreciated. Thanks
On May 19, 2017 03:08, "YT9TP - Pedja" yt9tp@uzice.net wrote:
I have strange issue with Windows 10, prolific serial adapter and BF-888S. It reports unable to download from radio.
Driver is proper (version 3.2.0.0, update is disabled), and Chirp works fine with the same adapter and other radio (Baofeng UV-B5) reading and writing.
I tried four different BF-888S and neither can be read.
However, when I use the same USB adapter on my old Windows XP computer, Chirp easily reads and writes those BF-888S.
Has anyone met with this problem?
--
YT9TP, Pedja http://www.yt9tp.iz.rs
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to N.C. at mypersonalspamfilternc@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
On 19/05/17 11:22, Nate Alvin wrote:
going to expire. Using the same computer, same "fake prolific" Baofeng cloning cable and the updated daily CHIRP software i was able to reprogram the UV5R, but when i went to read the BF888S i received the error message "radio refused to enter programming mode". Any help would be appreciated. Thanks
I have had the same issue using Fedora. If I repeat trying to read/write the BF888S about 90% of the attempts fail, but every once in a while it works.
On Windows XP it works every time. On Windows 10, not a once.
On 19.05.2017. 13:32, Kirby wrote:
I have had the same issue using Fedora. If I repeat trying to : read/write the BF888S about 90% of the attempts fail, but every once in a while it works.
Roll back your Prolific driver to 3.2.0.0.
Jardy Dawson WA7JRD Ham Radio
Message relayed from secret Hillary Clinton server, located in the basement of her house. OOPS, you aren't supposed to know that!
On May 19, 2017, at 06:07, YT9TP - Pedja yt9tp@uzice.net wrote:
On Windows XP it works every time. On Windows 10, not a once.
On 19.05.2017. 13:32, Kirby wrote:
I have had the same issue using Fedora. If I repeat trying to : read/write the BF888S about 90% of the attempts fail, but every once in a while it works.
OK then; Who has had good experience reading the BF-888s, and how?
James Flanders w0oog@verizon.net
-----Original Message----- From: Kirby joekirby@gmail.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Fri, May 19, 2017 6:34 am Subject: Re: [chirp_users] Cannot read Baofeng BF-888S
On 19/05/17 11:22, Nate Alvin wrote:
going to expire. Using the same computer, same "fake prolific" Baofeng cloning cable and the updated daily CHIRP software i was able to reprogram the UV5R, but when i went to read the BF888S i received the error message "radio refused to enter programming mode". Any help would be appreciated. Thanks
I have had the same issue using Fedora. If I repeat trying to read/write the BF888S about 90% of the attempts fail, but every once in a while it works.
I have had no trouble with the 4 I have, using a Baofeng cable (that I originally bought for my first UV-5R) on Windows 7.
- Trevor, AG7GX
On 5/19/2017 8:50 AM, James Flanders wrote:
OK then; Who has had good experience reading the BF-888s, and how?
James Flanders w0oog@verizon.net
-----Original Message----- From: Kirby joekirby@gmail.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Fri, May 19, 2017 6:34 am Subject: Re: [chirp_users] Cannot read Baofeng BF-888S
On 19/05/17 11:22, Nate Alvin wrote:
going to expire. Using the same computer, same "fake prolific" Baofeng cloning cable and the updated daily CHIRP software i was able to reprogram the UV5R, but when i went to read the BF888S i received the error message "radio refused to enter programming mode". Any help would be appreciated. Thanks
I have had the same issue using Fedora. If I repeat trying to read/write the BF888S about 90% of the attempts fail, but every once in a while it works.
--
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jim at w0oog@verizon.net mailto:w0oog@verizon.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to trevor@holyoak.com at trevor@holyoak.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I don't have problem with fake or genuine cable, when they work at least. I've had good luck with those with the D sticker, in top left of battery compartment, almost every other sticker I have sent back. But I haven't ordered any for 6-8 months. Good sticker may have changed by now As I mentioned previously, if your current system/setup works fine with a uv5 or other baofeng, test out of box, if no connect send back for refund, re-order.
Sent from my iPhone
On May 19, 2017, at 7:50 AM, James Flanders w0oog@verizon.net wrote:
OK then; Who has had good experience reading the BF-888s, and how?
James Flanders w0oog@verizon.net
-----Original Message----- From: Kirby joekirby@gmail.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Fri, May 19, 2017 6:34 am Subject: Re: [chirp_users] Cannot read Baofeng BF-888S
On 19/05/17 11:22, Nate Alvin wrote:
going to expire. Using the same computer, same "fake prolific" Baofeng cloning cable and the updated daily CHIRP software i was able to reprogram the UV5R, but when i went to read the BF888S i received the error message "radio refused to enter programming mode". Any help would be appreciated. Thanks
I have had the same issue using Fedora. If I repeat trying to read/write the BF888S about 90% of the attempts fail, but every once in a while it works.
--
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jim at w0oog@verizon.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Don at 831forsale@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
They seem to be hit and miss I get from Amazon, if I can't connect with chirp out of the box I order another pair and start the refund process, repeat until successful
Don
Sent from my iPhone
On May 19, 2017, at 4:32 AM, Kirby joekirby@gmail.com wrote:
On 19/05/17 11:22, Nate Alvin wrote: going to expire. Using the same computer, same "fake prolific" Baofeng cloning cable and the updated daily CHIRP software i was able to reprogram the UV5R, but when i went to read the BF888S i received the error message "radio refused to enter programming mode". Any help would be appreciated. Thanks
I have had the same issue using Fedora. If I repeat trying to read/write the BF888S about 90% of the attempts fail, but every once in a while it works.
--
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Don at 831forsale@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of YT9TP - Pedja Sent: Friday, May 19, 2017 1:08 AM To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] Cannot read Baofeng BF-888S
I have strange issue with Windows 10, prolific serial adapter and BF-888S. It reports unable to download from radio.
Driver is proper (version 3.2.0.0, update is disabled), and Chirp works fine with the same adapter and other radio (Baofeng UV-B5) reading and writing.
I tried four different BF-888S and neither can be read.
However, when I use the same USB adapter on my old Windows XP computer, Chirp easily reads and writes those BF-888S.
Has anyone met with this problem?
I guess some update of win10 change some part of the driver without changing the driver version number. Redowngrading probably fix this. But this just a wild guess. The solution is important. The reason is less important
בתאריך 20 במאי 2017 18:09, "Herb Gerhardt" hgerhardt@wavecable.com כתב:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of YT9TP - Pedja Sent: Friday, May 19, 2017 1:08 AM To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] Cannot read Baofeng BF-888S
I have strange issue with Windows 10, prolific serial adapter and BF-888S. It reports unable to download from radio.
Driver is proper (version 3.2.0.0, update is disabled), and Chirp works fine with the same adapter and other radio (Baofeng UV-B5) reading and writing.
I tried four different BF-888S and neither can be read.
However, when I use the same USB adapter on my old Windows XP computer, Chirp easily reads and writes those BF-888S.
Has anyone met with this problem?
--
YT9TP, Pedja http://www.yt9tp.iz.rs
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to amnon at amnon.zohar@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
I wonder if you did not reboot windows soon enough to solidify the change. You would think that this would not matter, but maybe Windows needs to reboot for changes such as the driver setting. Glenn I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of YT9TP - Pedja Sent: Friday, May 19, 2017 1:08 AM To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] Cannot read Baofeng BF-888S
I have strange issue with Windows 10, prolific serial adapter and BF-888S. It reports unable to download from radio.
Driver is proper (version 3.2.0.0, update is disabled), and Chirp works fine with the same adapter and other radio (Baofeng UV-B5) reading and writing.
I tried four different BF-888S and neither can be read.
However, when I use the same USB adapter on my old Windows XP computer, Chirp easily reads and writes those BF-888S.
Has anyone met with this problem?
--
YT9TP, Pedja http://www.yt9tp.iz.rs
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to amnon at amnon.zohar@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
--------------------------------------------------------------------------------
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Glenn at glennervin@cableone.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt hgerhardt@wavecable.com wrote:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes.
Jim KC9HI
Unsubscribe me from this list NOW.
On Sat, May 20, 2017 at 3:36 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt hgerhardt@wavecable.com wrote:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I
too
rolled back the driver to 3.2.0.0 to get my "genuine" cable that I
purchase
from HRO to work once I upgraded to Win10. It worked fine on Win7 and
never
had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for
this
device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work
again.
Don't ask me what is going on but then set it back for auto updates. I
will
now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes.
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Wow! What a polite request. I just can't try and help you fast enough.
Not.
Jim McCorison Orcas Island, WA
On May 20, 2017, at 2:59 PM, Rich Baker rbakedq@gmail.com wrote:
Unsubscribe me from this list NOW.
On Sat, May 20, 2017 at 3:36 PM, Jim Unroe rock.unroe@gmail.com wrote: On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt hgerhardt@wavecable.com wrote:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes.
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- S. Richard Baker 250 Furnace Dock Road Cortlandt Manor, NY 10567
Home: 914-736-1350 Cell: 917-922-2463 Email: rbakedq@gmail.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K2SON at jimmcc@mccorison.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Tried to unsubscribe over 10 times both on the website and by sending emails.
On Sat, May 20, 2017 at 6:06 PM, Jim McCorison jimmcc@mccorison.com wrote:
Wow! What a polite request. I just can't try and help you fast enough.
Not.
Jim McCorison Orcas Island, WA
On May 20, 2017, at 2:59 PM, Rich Baker rbakedq@gmail.com wrote:
Unsubscribe me from this list NOW.
On Sat, May 20, 2017 at 3:36 PM, Jim Unroe rock.unroe@gmail.com wrote:
On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt hgerhardt@wavecable.com wrote:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I
too
rolled back the driver to 3.2.0.0 to get my "genuine" cable that I
purchase
from HRO to work once I upgraded to Win10. It worked fine on Win7 and
never
had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for
this
device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the
latest
driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work
again.
Don't ask me what is going on but then set it back for auto updates. I
will
now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes.
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrep id.danplanet.com
-- S. Richard Baker 250 Furnace Dock Road Cortlandt Manor, NY 10567
Home: 914-736-1350 <(914)%20736-1350> Cell: 917-922-2463 <(917)%20922-2463> Email: rbakedq@gmail.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K2SON at jimmcc@mccorison.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
Perhaps it you reached out with a polite request along the lines of “I’m having problems unsubscribing from this list. I’ve sent an unsubscribe request email without success and I’ve tried the website without success. Does any body have any ideas what I’m doing wrong?” Bonus points for sending it as a separate thread with s subject of something like “Need help. Problems unsubscribing." Such an inquiry will probably get you a lot more assistance than just throwing a grenade into the mailing list.
--- Jim McCorison Orcas Island, WA
On May 20, 2017, at 4:30 PM, Rich Baker rbakedq@gmail.com wrote:
Tried to unsubscribe over 10 times both on the website and by sending emails.
On Sat, May 20, 2017 at 6:06 PM, Jim McCorison <jimmcc@mccorison.com mailto:jimmcc@mccorison.com> wrote: Wow! What a polite request. I just can't try and help you fast enough.
Not.
Jim McCorison Orcas Island, WA
On May 20, 2017, at 2:59 PM, Rich Baker <rbakedq@gmail.com mailto:rbakedq@gmail.com> wrote:
Unsubscribe me from this list NOW.
On Sat, May 20, 2017 at 3:36 PM, Jim Unroe <rock.unroe@gmail.com mailto:rock.unroe@gmail.com> wrote: On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt <hgerhardt@wavecable.com mailto:hgerhardt@wavecable.com> wrote:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/ http://blog.nwaprs.info/
There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes.
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com mailto:rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
-- S. Richard Baker 250 Furnace Dock Road Cortlandt Manor, NY 10567
Home: 914-736-1350 tel:(914)%20736-1350 Cell: 917-922-2463 tel:(917)%20922-2463 Email: rbakedq@gmail.com mailto:rbakedq@gmail.com_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K2SON at jimmcc@mccorison.com mailto:jimmcc@mccorison.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com mailto:rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
-- S. Richard Baker 250 Furnace Dock Road Cortlandt Manor, NY 10567
Home: 914-736-1350 Cell: 917-922-2463 Email: rbakedq@gmail.com mailto:rbakedq@gmail.com_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K2SON at jimmcc@mccorison.com mailto:jimmcc@mccorison.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
Lol
Sent from my iPhone
On May 20, 2017, at 6:06 PM, Jim McCorison jimmcc@mccorison.com wrote:
Wow! What a polite request. I just can't try and help you fast enough.
Not.
Jim McCorison Orcas Island, WA
On May 20, 2017, at 2:59 PM, Rich Baker rbakedq@gmail.com wrote:
Unsubscribe me from this list NOW.
On Sat, May 20, 2017 at 3:36 PM, Jim Unroe rock.unroe@gmail.com wrote: On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt hgerhardt@wavecable.com wrote:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes.
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- S. Richard Baker 250 Furnace Dock Road Cortlandt Manor, NY 10567
Home: 914-736-1350 Cell: 917-922-2463 Email: rbakedq@gmail.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to K2SON at jimmcc@mccorison.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Puma at theprogramllc@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Unsub yourself.
Jardy Dawson WA7JRD Ham Radio
Message relayed from secret Hillary Clinton server, located in the basement of her house. OOPS, you aren't supposed to know that!
On May 20, 2017, at 14:59, Rich Baker rbakedq@gmail.com wrote:
Unsubscribe me from this list NOW.
On Sat, May 20, 2017 at 3:36 PM, Jim Unroe rock.unroe@gmail.com wrote: On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt hgerhardt@wavecable.com wrote:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes.
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Rich do it yourself. Read bottom of email.
Sent from my iPhone
On May 20, 2017, at 5:59 PM, Rich Baker rbakedq@gmail.com wrote:
Unsubscribe me from this list NOW.
On Sat, May 20, 2017 at 3:36 PM, Jim Unroe rock.unroe@gmail.com wrote: On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt hgerhardt@wavecable.com wrote:
I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase from HRO to work once I upgraded to Win10. It worked fine on Win7 and never had a problem with the latest driver but would not work on Win10 till I rolled the driver back. I then turned off the auto driver updates for this device. Everything worked fine after rolling the driver back.
A few months later when I tried to read the radio again, it would not connect. I checked the driver and it was still the 3.2.0.0 driver in my listing. It took me several days till I updated the driver to the latest driver which of course did not work, but when I rolled it back again the 3.2.0.0 driver from the pick list for this device, it began to work again. Don't ask me what is going on but then set it back for auto updates. I will now just roll the driver back every time I want to use this cable.
I suggest you try to update your driver and then roll it back again to 3.2.0.0 to see if that works for you. I know it sounds stupid but it is worth a try since it worked for me.
Herb, KB7UVC NW APRS Group, West Sound Coordinator Our WEB Site: http://blog.nwaprs.info/
There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes.
Jim KC9HI
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rich at rbakedq@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
-- S. Richard Baker 250 Furnace Dock Road Cortlandt Manor, NY 10567
Home: 914-736-1350 Cell: 917-922-2463 Email: rbakedq@gmail.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Puma at theprogramllc@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Joe,
He claims he's trried to do so both by the email link and by the website. Of course, I suspect most folks don't understand that it takes time for this to happen and expect to stop receiving messages immediately.
Matthew Pitts
N8OHU
On 5/21/2017 1:58 PM, Joe Puma via chirp_users wrote:
Rich do it yourself. Read bottom of email.
Sent from my iPhone
On May 20, 2017, at 5:59 PM, Rich Baker <rbakedq@gmail.com mailto:rbakedq@gmail.com> wrote:
Unsubscribe me from this list NOW.
On Sat, May 20, 2017 at 3:36 PM, Jim Unroe <rock.unroe@gmail.com mailto:rock.unroe@gmail.com> wrote:
On Sat, May 20, 2017 at 11:08 AM, Herb Gerhardt <hgerhardt@wavecable.com <mailto:hgerhardt@wavecable.com>> wrote: > I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too > rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase > from HRO to work once I upgraded to Win10. It worked fine on Win7 and never > had a problem with the latest driver but would not work on Win10 till I > rolled the driver back. I then turned off the auto driver updates for this > device. Everything worked fine after rolling the driver back. > > A few months later when I tried to read the radio again, it would not > connect. I checked the driver and it was still the 3.2.0.0 driver in my > listing. It took me several days till I updated the driver to the latest > driver which of course did not work, but when I rolled it back again the > 3.2.0.0 driver from the pick list for this device, it began to work again. > Don't ask me what is going on but then set it back for auto updates. I will > now just roll the driver back every time I want to use this cable. > > I suggest you try to update your driver and then roll it back again to > 3.2.0.0 to see if that works for you. I know it sounds stupid but it is > worth a try since it worked for me. > > > Herb, KB7UVC > NW APRS Group, West Sound Coordinator > Our WEB Site: http://blog.nwaprs.info/ There is no need to disable updates. If Windows does update your Prolific driver, the previous driver is still installed. All you have to do is go into Device Manager and re-select the driver version that you want to use. I keep several Prolific driver versions installed and switch between then at will for testing purposes. Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to Rich at rbakedq@gmail.com <mailto:rbakedq@gmail.com> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>-- S. Richard Baker 250 Furnace Dock Road Cortlandt Manor, NY 10567
Home: 914-736-1350 Cell: 917-922-2463 Email: rbakedq@gmail.com mailto:rbakedq@gmail.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Joe Puma at theprogramllc@yahoo.com mailto:theprogramllc@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Matthew Pitts at n8ohu@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (15)
-
831 -
Amnon Zohar -
Glenn At Home -
Herb Gerhardt -
James Flanders -
Jardy Dawson -
Jim McCorison -
Jim Unroe -
Joe Puma -
Kirby -
Matthew Pitts -
Nate Alvin -
Rich Baker -
Trevor Holyoak -
YT9TP - Pedja