Ummmmm..... somebody tell my computer it isn't supposed to work with CHIRP. Somehow, despite this information, it still works here. Perhaps it is an issue with your computer? Using Windows-7 (64 bit), 4 GB ram. Running RT Systems cable, a known good cable from a reputable manufacturer.

Vy73 -- Mike -- KD5KC.

From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Eugene Baleme via chirp_users Sent: Wednesday, June 06, 2018 21:37 To: Discussion of CHIRP Subject: [Norton AntiSpam]Re: [chirp_users] New Daily Build

Thanks. I tried it but still will not work, error 2, on my port. chirp just does not work with windows 7 or 10.

On Wednesday, June 6, 2018, 12:18:41 AM PDT, Build System donotreply@danplanet.com wrote:

Greetings,

A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location:

http://trac.chirp.danplanet.com/chirp_daily/daily-20180606

A list of the changes included in this build (since the last daily) follows:

Changes for Build #527 [Dan Smith dsmith@danplanet.com] Fix Jetstream 270MH offset and mode/power bugs

The mode bit is elsewhere, and the power field is actually two bits. Also, the offset for the start of the alpha tags was wrong, causing the tags to be out of sync with the memory channels.

#5865

_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eugene Baleme at speedgene@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

CHIRP works with Windows 7 ,8 ,9 and 10 without any problems. Get a quality cable like those from RTSYSTEMS. com

On Wednesday, June 6, 2018 Eugene Baleme via chirp_users chirp_users@intrepid.danplanet.com wrote:

Thanks. I tried it but still will not work, error 2, on my port. chirp just does not work with windows 7 or 10.

On Wednesday, June 6, 2018, 12:18:41 AM PDT, Build System donotreply@danplanet.com wrote:

Greetings,

A new daily build of CHIRP is available.  This includes changes made

directly to the tree yesterday, and may include additional features,

bug fixes, and/or bugs.  If you are interested in trying it, grab it

from the following location:

http://trac.chirp.danplanet.com/chirp_daily/daily-20180606

A list of the changes included in this build (since the last daily)

follows:

Changes for Build #527

[Dan Smith dsmith@danplanet.com] Fix Jetstream 270MH offset and mode/power bugs

The mode bit is elsewhere, and the power field is actually two bits.

Also, the offset for the start of the alpha tags was wrong, causing the

tags to be out of sync with the memory channels.

#5865

_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eugene Baleme at speedgene@yahoo.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 Jock at kc6iih@aol.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

Or build your own. For less than10 bucks and some solder, you can have one that works and won't break the bank.

Chris KM4PUR

On Thu, Jun 7, 2018, 9:47 AM Mike-2007 mike-2007@elp.rr.com wrote:

I agree 110%. It seems that cables are the #1 cause for troubles across the board, not only with CHIRP, but with many other programs too. It stems from hams being too cheap to pay for quality. They have an old serial cable, and that was good enough back in the day. Yeah, it was! But no modern computer has a serial port anymore.

There are 4 possible solutions to the situation. One is cheap, three are more costly. The cheap solution is the $5 USB-serial adapter. And that will work. For a while. But for $5, you aren't getting one of the authentic adapters, you're getting a clone. And somewhere down the road an official Windows update is going to over-write that driver, and the headaches begin.

The second and perhaps most costly approach that still retains your original serial cable is to install a serial port board into your new computer. I haven't priced serial port boards in a while, but they are more than $5. A quick search shows a cheap 1-port board at $8, and the expensive 4-port board at $88. I'm not sure I would trust the quality of the $8 board. But I certainly don't need the 4-port $88 board either. So the cheap ham is still enticed to the USB-serial adapter, which will eventually quit working.

The third solution is to just suck it up and pay for a modern cable. It is going to cost something around $30. I just checked RT Systems for 3 popular cables. My Yaesu FTdx5000MP, the Yaesu FTdx3000, and the Icom IC-7300 are all $30 each. I've caught them cheaper on sale. RT systems writes their cable drivers, so Windows will not over-write them with something that will not work on the next update.

The fourth solution is to hold on to an older computer with a serial port. The problem is that nobody sells DOS anymore, and not many modern programs run under DOS anymore. But your serial cable will plug in just fine. Windows 3.1 anyone?

Well, there is one other solution. Once you get it working, do not update windows. It is a possibility, but I wouldn't do that. Of course, another possible solution is to not run Windows. But we're talking main-stream here, not specialized. Howl as you will, Unix/Linux/Mac are just not main-stream.

So here is the question. You spent several hundred dollars or more on a new radio. You also spent a few hundred dollars or more on a new Windows-10 computer. Your investment in antennas and tower, quality coax, and other equipment to make a reliable station all adds up. Then you go cheap on a USB-serial converter? And when Windows over-writes the driver, you struggle to get it working again. Isn't your time and frustration worth a $30 cable to avoid all of that? After days of poking at it, cussing and discussing it on the forum, and declaring the software doesn't work, isn't $30 a cheap price to pay to avoid all that?

Get a good cable. No matter what software you use, no matter what O/S you run, a good cable is an investment in sanity.

Vy73 -- Mike -- KD5KC.

*From:* chirp_users-bounces@intrepid.danplanet.com [mailto: chirp_users-bounces@intrepid.danplanet.com] *On Behalf Of *Jock via chirp_users *Sent:* Wednesday, June 06, 2018 22:08 *To:* chirp_users@intrepid.danplanet.com *Subject:* [Norton AntiSpam]Re: [chirp_users] New Daily Build

CHIRP works with Windows 7 ,8 ,9 and 10 without any problems. Get a quality cable like those from RTSYSTEMS. com

---

On Wednesday, June 6, 2018 Eugene Baleme via chirp_users < chirp_users@intrepid.danplanet.com> wrote:

Thanks. I tried it but still will not work, error 2, on my port. chirp just does not work with windows 7 or 10.

On Wednesday, June 6, 2018, 12:18:41 AM PDT, Build System < donotreply@danplanet.com> wrote:

Greetings,

A new daily build of CHIRP is available. This includes changes made

directly to the tree yesterday, and may include additional features,

bug fixes, and/or bugs. If you are interested in trying it, grab it

from the following location:

http://trac.chirp.danplanet.com/chirp_daily/daily-20180606

A list of the changes included in this build (since the last daily)

follows:

Changes for Build #527

[Dan Smith dsmith@danplanet.com] Fix Jetstream 270MH offset and mode/power bugs

The mode bit is elsewhere, and the power field is actually two bits.

Also, the offset for the start of the alpha tags was wrong, causing the

tags to be out of sync with the memory channels.

#5865

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eugene Baleme at speedgene@yahoo.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 Jock at kc6iih@aol.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 Chris at chrispetry1971@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

FTDI chipset was also cloned now, there is no longer the blanket guarantee that an FTDI chip set will work. Buyer beware.

Vy73 -- Mike -- KD5KC.

From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jerry Sent: Thursday, June 07, 2018 09:14 To: Discussion of CHIRP Subject: Re: [chirp_users] New Daily Build - DOESN'T WORK.

Or buy an FTDI based cable. They're not expensive. I have three different ones and all worked first time, every time. Jerry R W7JER

Guard it well. Not all cables work, and not all cables continue to work. If you have a good one, hang on to it.

There are many ways to skin a cat. I prefer a basketball needle and an air pump.

Vy73 -- Mike -- KD5KC.

From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Dennis Wage Sent: Thursday, June 07, 2018 11:55 To: Discussion of CHIRP Subject: Re: [chirp_users] New Daily Build - DOESN'T WORK.

This cable came to me when I bought an entire rig of a ham getting out. This driver works fine. And I keep my Win 10 computer up to date and clean.

​

Dennis M. Wage (W9BOQ)

245 Corum Hill Road Castalian Springs, TN 37031 (615) 310-4242 Cell (615) 562-5128 Home http://hammondb3organ.net/ http://hammondb3organ.net http://overdubs.net http://overdubs.net

On Thu, Jun 7, 2018 at 12:09 PM, Mike-2007 mike-2007@elp.rr.com wrote: FTDI chipset was also cloned now, there is no longer the blanket guarantee that an FTDI chip set will work. Buyer beware.

Vy73 -- Mike -- KD5KC.

From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jerry Sent: Thursday, June 07, 2018 09:14 To: Discussion of CHIRP Subject: Re: [chirp_users] New Daily Build - DOESN'T WORK.

Or buy an FTDI based cable. They're not expensive. I have three different ones and all worked first time, every time. Jerry R W7JER

_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dennis Wage at dwage@dwage.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

There's always the convert the cable for $1.50 solution. http://www.miklor.com/COM/UV_ProgrCable.php

John K3NXU

-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jim Unroe Sent: Thursday, June 7, 2018 4:16 PM To: Discussion of CHIRP Subject: Re: [chirp_users] New Daily Build - DOESN'T WORK.

On Thu, Jun 7, 2018 at 1:55 PM, Dennis Wage dwage@dwage.com wrote:

This cable came to me when I bought an entire rig of a ham getting out. This driver works fine. And I keep my Win 10 computer up to date and

clean.

This is the type of programming cable (manufactured with a FTDI chip) you want to get if you want it to just work. It costs a bit more, but it reduces the amount of twiddling that you have to do to get it working to nearly zero.

Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to John LaMartina at johnla@usa.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

Well all of that said, I would still get me a little ol' machine that will run some light version of Linux be done with it.

Oh by the way, Linux may not be DESKTOP mainstream but almost every flat screen TV, home router, GPS and other "smart" devices run on it. Add the Android (Linux kernel) and I am sorry but I think that dealing with the pain and agony of MS windows is just not worth it when my Linux boxen just keep going, and going and going and going...

You could always get a RPi and run it on that, I have one I use exactly for that so I can have something small to run Chirp on for those times when I want to use a tablet or phone to program a radio...

So yes there are plenty of alternatives, but you have to be willing to look at those alternatives, the authors chose and chose well, I have some DMR radios and all of them fall into M$ hell in one form or another, I generally try to use them on Wine, but they are all cantankerous. Chirp just works, (Not for DMR but that is a whole other can of worms)

BIG THANK YOU TO THE GUYS WHO WRITE THE CODE!! KEEP IT UP IT IS VERY FINE CODE.

I had to deal with Windows in various industries, it was a real education in how something so messed up can become so pervasive just because the organization behind it is more of a marketing org.

My mom has a Win 10 machine, the applications will not talk to the printer, but the printer application will do so, all of the applications can SEE the printer, they just cannot talk to it. I tried to fix it, the logs were obnoxious, she brought in someone paid to fix it, he came way and said "there is something wrong with the OS". I am getting ready to move her to Linux and stop that sort of thing.

As amateur radio ops we need to be more open, when you are stuck on one OS, it is like being in a mono-culture country, when that particular mono-culture ag product gets a plague the whole country is up a creek.

I can run Chip on LInux (prefered) probably most any other Unix based OS without too much work, Mac and if needed Windows... I have tried not to be mono-culture, but have my preferred solution.

On Thu, Jun 7, 2018 at 4:36 PM, Nigel A. Gunn G8IFF/W8IFF nigel@ngunn.net wrote:

However, most of my radio require TX and rx on one wire so I guess there is an alternative for that.

...

On 07 June 2018 at 16:50 John La Johnla@usa.net wrote:

There's always the convert the cable for $1.50 solution. http://www.miklor.com/COM/UV_ProgrCable.php

John K3NXU

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com

I do not need soldering skills for Linux and all them ol' pirated USB dongles work on Linux, so it is not even an issue.

But you also know where to punch the OS you deal with and if it floats the boat you can leave with the outgoing tide...

On Thu, Jun 7, 2018 at 8:24 PM, Jardy via chirp_users < chirp_users@intrepid.danplanet.com> wrote:

I, for 1, don’t want to learn Apple, although I have an iPhone, 2 ipads, and an iwatch. I don’t want to learn Linux, my soldering skills suck, and I guess I am too cheap to spend $30-35 each to replace my fake Prolific cables with RT Systems, especially when it is so easy to roll back 1 driver for ALL affected cables I have.

To each their own.

Jardy Dawson WA7JRD Message sent through sub space hailing frequencies using the Universal Translator.

On Jun 7, 2018, at 18:14, Chuck Hast kp4djt@gmail.com wrote:

Well all of that said, I would still get me a little ol' machine that will run some light version of Linux be done with it.

Oh by the way, Linux may not be DESKTOP mainstream but almost every flat screen TV, home router, GPS and other "smart" devices run on it. Add the Android (Linux kernel) and I am sorry but I think that dealing with the pain and agony of MS windows is just not worth it when my Linux boxen just keep going, and going and going and going...

You could always get a RPi and run it on that, I have one I use exactly for that so I can have something small to run Chirp on for those times when I want to use a tablet or phone to program a radio...

So yes there are plenty of alternatives, but you have to be willing to look at those alternatives, the authors chose and chose well, I have some DMR radios and all of them fall into M$ hell in one form or another, I generally try to use them on Wine, but they are all cantankerous. Chirp just works, (Not for DMR but that is a whole other can of worms)

BIG THANK YOU TO THE GUYS WHO WRITE THE CODE!! KEEP IT UP IT IS VERY FINE CODE.

I had to deal with Windows in various industries, it was a real education in how something so messed up can become so pervasive just because the organization behind it is more of a marketing org.

My mom has a Win 10 machine, the applications will not talk to the printer, but the printer application will do so, all of the applications can SEE the printer, they just cannot talk to it. I tried to fix it, the logs were obnoxious, she brought in someone paid to fix it, he came way and said "there is something wrong with the OS". I am getting ready to move her to Linux and stop that sort of thing.

As amateur radio ops we need to be more open, when you are stuck on one OS, it is like being in a mono-culture country, when that particular mono-culture ag product gets a plague the whole country is up a creek.

I can run Chip on LInux (prefered) probably most any other Unix based OS without too much work, Mac and if needed Windows... I have tried not to be mono-culture, but have my preferred solution.

On Thu, Jun 7, 2018 at 4:36 PM, Nigel A. Gunn G8IFF/W8IFF <nigel@ngunn.net

...

wrote:

...

However, most of my radio require TX and rx on one wire so I guess there is an alternative for that.

...

On 07 June 2018 at 16:50 John La Johnla@usa.net wrote:

There's always the convert the cable for $1.50 solution. http://www.miklor.com/COM/UV_ProgrCable.php

John K3NXU

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrep id.danplanet.com

-- Chirp + Editcp + MD380Tools on Linux Celestial!!! Chuck -- KP4DJT

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jardy at jardy72@yahoo.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 Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com

On Thu, Jun 7, 2018 at 8:52 PM, Mike-2007 mike-2007@elp.rr.com wrote:

Won't argue with a thing you said..... EXCEPT..... ham radio isn't my only hobby, and I have some software for another hobby that just will not function outside of windows. Tried on a MAC, tried on Linux, tried some other thing my friend locally has. Nothing worked. And this other hobby is more important to me than ham radio. So I'll just struggle along on Windows-7 (64 bit) and hopefully with the RT Systems cable I won't have the troubles others seem to have here. Heck, I'd still be using XP if they hadn't quit supporting it!

Perhaps someday someone will write good software for Android, and I'll take my tablet instead of the little Net-Book I carry out now. But until it happens, I'm on Win-7. Funny, but I've had no problems on my end. In fact, this E-mail address was first used in Dec of 2006, and I don't feel a need to change it either, still no SPAM, no virus, no update problems. I must be doing something right!

Vy73 -- Mike -- KD5KC.

Yes I have one like that too, CPS for the MD-9600, it will not run under wine and when it runs under windows if you want to load the contacts list you also have to have Excel installed on your computer, for a stinking csv file at that.

For that I have a virtual machine running Win10 (I want to get a copy of Win7 that was the one I liked. Win10 I really am getting a real dislike for)

The thing I like about my Linux boxen is they never give me issues, they just run, the updates are fast and never intrusive, I do not have to reboot the machine every time it does an update (that is one of the reasons I do not like to run the VM, first thing it does is complain about needing updates as I run it about every Feb 29th on a blue moon) At least with running Win10 in a VM I can give it some additional protection in the host system.

Well if you get a Raspberry Pi you can do almost what you want, you run the RPi headless and access it from your tablet/phone whatever.

I have a spare tablet I am going to put Linux on to see if I can run Chirp on it. That would be neat to not have to carry anything more than the tablet and cables...

I also have 4 Thinkpads (I LIKE Thinkpads) that I can use for that sort of thing one of them is a small 12" screen running Ubuntu Mate has an i7 processor and a SSD, it boots very fast and moves very fast. That is my little field machine when I need more than the Pi.

Ham radio is not my only hobby either, and there is some other stuff out there that falls in the same area as the MD-9600 software, but I would say that I have found 98% of what I need in some form for Linux.

I used to have a rr addy when we lived in Tampa, but it got so loaded with spam that I got this gmail addy (2004) and it has stayed with me ever since.

Of course now having lived in 3 places where there is no TW, I would not have one anyhow.

Ciao...

What headache? Big deal if Windows updates the driver! If it does, it takes less than about 2 minutes to roll it back. I have several different radios that use a cable with the fake Prolific chip. Many different ends on the cables, but they all act as the same, as long as you use the same physical USB port. It's not like you have to reprogram your radios everyday now, is it? Sure, I have some of the RT Systems stuff, but I usually had to buy that before CHIRP was available. But, I find that on the rare occasion my drivers have been 'updated ', I take 2 minutes of my valuable time, do one reset that takes care of all my cables, and life goes on. NOT A BIG DEAL!! Get over it!

Jardy Dawson WA7JRD Ham Radio

Message sent by... Oh who the heck really cares?

On Jun 7, 2018, at 06:46, Mike-2007 mike-2007@elp.rr.com wrote:

I agree 110%. It seems that cables are the #1 cause for troubles across the board, not only with CHIRP, but with many other programs too. It stems from hams being too cheap to pay for quality. They have an old serial cable, and that was good enough back in the day. Yeah, it was! But no modern computer has a serial port anymore.

There are 4 possible solutions to the situation. One is cheap, three are more costly. The cheap solution is the $5 USB-serial adapter. And that will work. For a while. But for $5, you aren't getting one of the authentic adapters, you're getting a clone. And somewhere down the road an official Windows update is going to over-write that driver, and the headaches begin.

The second and perhaps most costly approach that still retains your original serial cable is to install a serial port board into your new computer. I haven't priced serial port boards in a while, but they are more than $5. A quick search shows a cheap 1-port board at $8, and the expensive 4-port board at $88. I'm not sure I would trust the quality of the $8 board. But I certainly don't need the 4-port $88 board either. So the cheap ham is still enticed to the USB-serial adapter, which will eventually quit working.

The third solution is to just suck it up and pay for a modern cable. It is going to cost something around $30. I just checked RT Systems for 3 popular cables. My Yaesu FTdx5000MP, the Yaesu FTdx3000, and the Icom IC-7300 are all $30 each. I've caught them cheaper on sale. RT systems writes their cable drivers, so Windows will not over-write them with something that will not work on the next update.

The fourth solution is to hold on to an older computer with a serial port. The problem is that nobody sells DOS anymore, and not many modern programs run under DOS anymore. But your serial cable will plug in just fine. Windows 3.1 anyone?

Well, there is one other solution. Once you get it working, do not update windows. It is a possibility, but I wouldn't do that. Of course, another possible solution is to not run Windows. But we're talking main-stream here, not specialized. Howl as you will, Unix/Linux/Mac are just not main-stream.

So here is the question. You spent several hundred dollars or more on a new radio. You also spent a few hundred dollars or more on a new Windows-10 computer. Your investment in antennas and tower, quality coax, and other equipment to make a reliable station all adds up. Then you go cheap on a USB-serial converter? And when Windows over-writes the driver, you struggle to get it working again. Isn't your time and frustration worth a $30 cable to avoid all of that? After days of poking at it, cussing and discussing it on the forum, and declaring the software doesn't work, isn't $30 a cheap price to pay to avoid all that?

Get a good cable. No matter what software you use, no matter what O/S you run, a good cable is an investment in sanity.

Vy73 -- Mike -- KD5KC.

From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jock via chirp_users Sent: Wednesday, June 06, 2018 22:08 To: chirp_users@intrepid.danplanet.com Subject: [Norton AntiSpam]Re: [chirp_users] New Daily Build

CHIRP works with Windows 7 ,8 ,9 and 10 without any problems. Get a quality cable like those from RTSYSTEMS. com

On Wednesday, June 6, 2018 Eugene Baleme via chirp_users chirp_users@intrepid.danplanet.com wrote:

Thanks. I tried it but still will not work, error 2, on my port. chirp just does not work with windows 7 or 10.

On Wednesday, June 6, 2018, 12:18:41 AM PDT, Build System donotreply@danplanet.com wrote:

Greetings,

A new daily build of CHIRP is available. This includes changes made

directly to the tree yesterday, and may include additional features,

bug fixes, and/or bugs. If you are interested in trying it, grab it

from the following location:

http://trac.chirp.danplanet.com/chirp_daily/daily-20180606

A list of the changes included in this build (since the last daily)

follows:

Changes for Build #527

[Dan Smith dsmith@danplanet.com] Fix Jetstream 270MH offset and mode/power bugs

The mode bit is elsewhere, and the power field is actually two bits.

Also, the offset for the start of the alpha tags was wrong, causing the

tags to be out of sync with the memory channels.

#5865

_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eugene Baleme at speedgene@yahoo.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 Jock at kc6iih@aol.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 Jardy at jardy72@yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

Not a big deal - for you. Obviously others are more challenged than you are. Otherwise there wouldn't be the proliferation of CHIRP DOESN'T WORK E-mails.

But you do have the last line right.

Vy73 -- Mike -- KD5KC.

On Thu, Jun 7, 2018 at 9:40 AM, Jardy Dawson via chirp_users chirp_users@intrepid.danplanet.com wrote: What headache? Big deal if Windows updates the driver! If it does, it takes less than about 2 minutes to roll it back. I have several different radios that use a cable with the fake Prolific chip. Many different ends on the cables, but they all act as the same, as long as you use the same physical USB port. It's not like you have to reprogram your radios everyday now, is it? Sure, I have some of the RT Systems stuff, but I usually had to buy that before CHIRP was available. But, I find that on the rare occasion my drivers have been 'updated ', I take 2 minutes of my valuable time, do one reset that takes care of all my cables, and life goes on. NOT A BIG DEAL!! Get over it! Jardy Dawson WA7JRD Ham Radio

Message sent by... Oh who the heck really cares?

Jardy help me and it worked on Windows 10.

On Wed, Jun 6, 2018, 10:38 PM Eugene Baleme via chirp_users < chirp_users@intrepid.danplanet.com> wrote:

Thanks. I tried it but still will not work, error 2, on my port. chirp just does not work with windows 7 or 10.

On Wednesday, June 6, 2018, 12:18:41 AM PDT, Build System < donotreply@danplanet.com> wrote:

Greetings,

A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location:

http://trac.chirp.danplanet.com/chirp_daily/daily-20180606

A list of the changes included in this build (since the last daily) follows:

Changes for Build #527 [Dan Smith dsmith@danplanet.com] Fix Jetstream 270MH offset and mode/power bugs

The mode bit is elsewhere, and the power field is actually two bits. Also, the offset for the start of the alpha tags was wrong, causing the tags to be out of sync with the memory channels.

#5865

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Eugene Baleme at speedgene@yahoo.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 Danny at dlamarbrown@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

On Wed, Jun 6, 2018 at 11:37 PM, Eugene Baleme via chirp_users chirp_users@intrepid.danplanet.com wrote:

Thanks. I tried it but still will not work, error 2, on my port. chirp just does not work with windows 7 or 10.

On Wednesday, June 6, 2018, 12:18:41 AM PDT, Build System donotreply@danplanet.com wrote:

The problem has to do with your programming cable, not CHIRP. If you have a programming cable that reports to Windows that it is a Prolific chip based programming cable, then the USB-to-Serial chip it is made with is of the counterfeit variety. The device driver written by the Prolific company and supplied to Microsoft is intentionally incompatible with counterfeit copies of their chip. The workaround for Windows Vista and newer is to download, install and select the older Prolific v3.2.0.0 device driver that is not crippled in this way.

http://www.miklor.com/COM/UV_Drivers.php

Jim KC9HI