- Users - lists.chirpmyradio.com

[chirp_users] Concurrance
by Al Jones 10 Jan '18

10 Jan '18

I like the give and take from all the people here *except* that there are times when it's not helpful at all. We get a new member who doesn't know what he's doing, thinks he's read everything and is still missing "something" --- and one of our beneficent members replies "RTFM!" or someone else chimes in with "get the right cable!" or better yet "That won't work!" Those one line zingers are not only NO help, they're probably going to turn off some guy who might eventually be the one to help someone else, down the line. I have a friend who had a Linux problem and the response he got here was - "It works fine with *my* Ubuntu!" Sometimes confirmation that something works is a big help, it just means that we're not looking in the right place. When I phrased his question differently I got some great assistance ... there are some good guys here and to them I say "Thanks!" << tripping off my soapbox, sorry >>

5 4

Re: [chirp_users] Concurrance
by Walt Childson 09 Jan '18

09 Jan '18

Hey guys, you are all awesome. Keep up the good work. I'm on my boat in Mexico, and have not been interested in chirp for 7 months. But even though I only get some coverage when I'm in port, I still read most of the threads. I do agree that it might be frustrating with newbe's but answers or links to the answer will help us all. Adios Walt N6STM On Jan 9, 2018 3:32 PM, "Al Jones" <al(a)aljones.us> wrote: I like the give and take from all the people here *except* that there are times when it's not helpful at all. We get a new member who doesn't know what he's doing, thinks he's read everything and is still missing "something" --- and one of our beneficent members replies "RTFM!" or someone else chimes in with "get the right cable!" or better yet "That won't work!" Those one line zingers are not only NO help, they're probably going to turn off some guy who might eventually be the one to help someone else, down the line. I have a friend who had a Linux problem and the response he got here was - "It works fine with *my* Ubuntu!" Sometimes confirmation that something works is a big help, it just means that we're not looking in the right place. When I phrased his question differently I got some great assistance ... there are some good guys here and to them I say "Thanks!" << tripping off my soapbox, sorry >> _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Walt Childson at wchildson(a)gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com

1 0

[chirp_users] Subject lines
by Jardy Dawson 09 Jan '18

09 Jan '18

You mean such as "Please"? Jardy Dawson WA7JRD Ham Radio We keep trying to interfere with elections, but pesky moose and squirrel keep interfering! On Jan 9, 2018, at 10:31, Ted Timmons <ted(a)perljam.net> wrote: Also: use good subject lines. There's no reason you can't state the topic of the message rather than something short or misleading. _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jardy at jardy72(a)yahoo.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

3 2

[chirp_users] Please!
by Chas 09 Jan '18

09 Jan '18

When I joined this list, I expected to find tech- savy individuals working to enhance a great piece of free software. However, I keep getting digests filled with the total previous digest copied multiple times. If you simply clean up your reply, maybe include a relevant quote, and add a meaningful subject - some of us would be inclined to read it and help. - That concludes my vent. Please be brief and don't be lazy. CT No tree, hard or soft, has been harmed by the senfing of this email; but many electrons have been inconvenienced.

3 2

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 8, "D.J.J. Ring, Jr." <n1ea@arrl.net>
by Mike McCabe 08 Jan '18

08 Jan '18

I am new here so please forgive me if I am dealing with my issue improperly I am trying to program a yeast vx8dr handheld It goes to clone but then gives the message to the effect that the radio is not transferring data Windows10, USB shows the cable, rebooted computer. Always the same result Can anybody help? Mike > On Jan 8, 2018, at 5:16 PM, Skip <rockyvista(a)windstream.net> wrote: > > So that is how Hillary did it! > > From: Christopher F. Beesley > Sent: Monday, January 08, 2018 2:03 PM > To: chirp_users(a)intrepid.danplanet.com > Subject: Re: [chirp_users] chirp_users Digest, Vol 109, Issue 8, "D.J.J. Ring, Jr." <n1ea(a)arrl.net> > > Hi David (and others), > I'm using default Windows 10 coding/decoding. It works perfectly with almost everything I use, including Word, Access, Excel, Visio, Audition, Winamp, Firefox, EditPad, Paint, an AMR converter, Bulk Rename, and several Canon utilities to name but a few. It also works perfectly with older versions of several of the above. Emails in both directions via Yahoo! and MSN are no problem. > I find incorrect punctuation in a fair number of 'Comments' made about various news items as well as the chirp-users messages. It has been suggested that the incorrect punctuation is because of data mis-handling by systems in other countries where the apostrophe is not recognised in their language and the question-mark is substituted at that point. I like that explanation, it fits in with the world-wide nature of Amateur Radio as well as news-item comments from all over the world. Such activities would be out of the control of both the sender and recipient. > This has legal implications - the email that someone sends may not look like the email that is received, and therefore will be useless as evidence. > Thanks for yours and everyone else's interest, > 73, Chris > > > From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of chirp_users-request(a)intrepid.danplanet.com <chirp_users-request(a)intrepid.danplanet.com> > Sent: 08 January 2018 20:00 > To: chirp_users(a)intrepid.danplanet.com > Subject: chirp_users Digest, Vol 109, Issue 8 > > Send chirp_users mailing list submissions to > chirp_users(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > or, via email, send a message with subject or body 'help' to > chirp_users-request(a)intrepid.danplanet.com > > You can reach the person managing the list at > chirp_users-owner(a)intrepid.danplanet.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chirp_users digest..." > > > Today's Topics: > > 1. Re: chirp_users Digest, Vol 109, Issue 6 and many others > (D.J.J. Ring, Jr.) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 8 Jan 2018 02:14:17 -0500 > From: "D.J.J. Ring, Jr." <n1ea(a)arrl.net> > Subject: Re: [chirp_users] chirp_users Digest, Vol 109, Issue 6 and > many others > To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> > Message-ID: > <CADO5RbiZU9VbjTVB6G-gO3sNn8rMMr2d6j4u1ED05-O-TG_z3w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Chris, > > Check your language settings? What encoding are you using? > > I use UTF-8 on my desktop for the locale. If someone sends me a different > encoding it often appears as you say it does. > > I am using an Android at the monent, so I have no idea of tge encoding, but > probably UTF-8. > > 73 > > David N1EA > On Jan 6, 2018 3:16 PM, "Christopher F. Beesley" <chrisbees2(a)hotmail.com> > wrote: > > > Hi, Chris here. What's all this utter nonsense that is becoming more and > > more common whereby the question mark is used instead of the apostrophe? > > I'm fed up of seeing stuff that won't read easily because of it, e.g. I?m > > fed up of seeing stuff that won?t read easily because of it. It?s rubbish! > > Where did you lot learn English grammar' > > > > Chris. N.B. All punctuation errors above are deliberate, designed to > > emphasise the point of this message. > > > > > > ------------------------------ > > *From:* chirp_users-bounces(a)intrepid.danplanet.com < > > chirp_users-bounces(a)intrepid.danplanet.com> on behalf of > > chirp_users-request(a)intrepid.danplanet.com <chirp_users-request@intrepid. > > danplanet.com> > > *Sent:* 06 January 2018 20:00 > > *To:* chirp_users(a)intrepid.danplanet.com > > *Subject:* chirp_users Digest, Vol 109, Issue 6 > > > > Send chirp_users mailing list submissions to > > chirp_users(a)intrepid.danplanet.com > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > > or, via email, send a message with subject or body 'help' to > > chirp_users-request(a)intrepid.danplanet.com > > > > You can reach the person managing the list at > > chirp_users-owner(a)intrepid.danplanet.com > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of chirp_users digest..." > > > > > > Today's Topics: > > > > 1. Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) > > 2. Re: Fwd: FDTI chip compatibility with Mac (Fred Dalzell) > > 3. Re: Fwd: FDTI chip compatibility with Mac (Jim McCorison) > > 4. Re: Fwd: FDTI chip compatibility with Mac > > (Nigel A. Gunn G8IFF/W8IFF) > > 5. Re: Fwd: FDTI chip compatibility with Mac (Aubrey Turner) > > 6. Re: Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) > > 7. Wouxun KG-UV8E KG-UV8T KG-UV8D Plus (D.J.J. Ring, Jr.) > > 8. Linux PPA problem? (Tom Consodine ND5Y) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 5 Jan 2018 17:31:13 -0600 > > From: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com> > > Subject: [chirp_users] Fwd: FDTI chip compatibility with Mac > > To: chirp_users(a)intrepid.danplanet.com > > Message-ID: <1A0978D7-3545-46A5-9A60-FAEF20F9553C(a)yahoo.com> > > Content-Type: text/plain; charset="us-ascii" > > > > Here is the answer I got from FTDI regarding their cable chipsets! > > Let me ask again: how many of you are Mac iOS users, and where did you get > > your cloning cables from? > > THanks. > > Tip N9MVX > > > > > Begin forwarded message: > > > > > > From: Cameron Forbes <cameron.forbes(a)ftdichip.com> > > > Subject: RE: FDTI chip compatibility with Mac > > > Date: January 5, 2018 at 16:41:00 CST > > > To: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com>, US Support < > > us.support(a)ftdichip.com> > > > > > > Tipton: > > > > > > FTDI does not support iOS. > > > > > > > > > Best Regards, > > > > > > Cameron Forbes > > > Customer Support Engineer > > > > > > Future Technology Devices International Limited > > > 7130 SW Fir Loop > > > Tigard, OR 97223-8160 > > > Tel: 503.726.5415 > > > Fax: 503.547.0987 > > > > > > > > > -----Original Message----- > > > From: T.E. Klamberg Klamberg [mailto:n9mvx@yahoo.com <n9mvx(a)yahoo.com>] > > > Sent: Tuesday, January 02, 2018 8:37 AM > > > To: US Support > > > Subject: FDTI chip compatibility with Mac > > > > > > My question has to do with the FTDI chipset and Apple computers. I have > > a MacBook Pro with iOS High Sierra version 10.13.2 installed. > > > Is your chipset compatible with that iOS? > > > Thank you. > > > > > > Tipton Klamberg > > > Mascoutah, Il 62258 > > > (618) 670-1502 > > > [FT-X]<http://www.ftdichip.com/FT-X.htm?utm_source= > > EmailfooterApril17&utm_medium=EmailfooterApril17&utm_ > > campaign=EmailfooterApril17&utm_term=EmailfooterApril17& > > utm_content=EmailfooterApril17> > > > Registered in Scotland No 136640 > > > This message contains confidential information and is intended only for > > the individual named. If you are not the named addressee you should not > > disseminate, distribute or copy this e-mail. Please notify the sender > > immediately by e-mail if you have received this e-mail by mistake and > > delete this e-mail from your system. E-mail transmission cannot be > > guaranteed to be secure or error-free as information could be intercepted, > > lost, destroyed, arrive late or incomplete. The sender therefore does not > > accept liability for any errors or omissions in the contents of this > > message, which arise as a result of e-mail transmission. Future Technology > > Devices International Ltd has taken every reasonable precaution to ensure > > that any attachment to this e-mail has been swept for viruses. However, we > > cannot accept liability for any damage sustained as a result of software > > viruses and would advise that you carry out your own virus checks before > > opening any attachment. > > > >

2 1

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 8, "D.J.J. Ring, Jr." <n1ea@arrl.net>
by Christopher F. Beesley 08 Jan '18

08 Jan '18

Hi David (and others), I'm using default Windows 10 coding/decoding. It works perfectly with almost everything I use, including Word, Access, Excel, Visio, Audition, Winamp, Firefox, EditPad, Paint, an AMR converter, Bulk Rename, and several Canon utilities to name but a few. It also works perfectly with older versions of several of the above. Emails in both directions via Yahoo! and MSN are no problem. I find incorrect punctuation in a fair number of 'Comments' made about various news items as well as the chirp-users messages. It has been suggested that the incorrect punctuation is because of data mis-handling by systems in other countries where the apostrophe is not recognised in their language and the question-mark is substituted at that point. I like that explanation, it fits in with the world-wide nature of Amateur Radio as well as news-item comments from all over the world. Such activities would be out of the control of both the sender and recipient. This has legal implications - the email that someone sends may not look like the email that is received, and therefore will be useless as evidence. Thanks for yours and everyone else's interest, 73, Chris ________________________________ From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of chirp_users-request(a)intrepid.danplanet.com <chirp_users-request(a)intrepid.danplanet.com> Sent: 08 January 2018 20:00 To: chirp_users(a)intrepid.danplanet.com Subject: chirp_users Digest, Vol 109, Issue 8 Send chirp_users mailing list submissions to chirp_users(a)intrepid.danplanet.com To subscribe or unsubscribe via the World Wide Web, visit http://intrepid.danplanet.com/mailman/listinfo/chirp_users or, via email, send a message with subject or body 'help' to chirp_users-request(a)intrepid.danplanet.com You can reach the person managing the list at chirp_users-owner(a)intrepid.danplanet.com When replying, please edit your Subject line so it is more specific than "Re: Contents of chirp_users digest..." Today's Topics: 1. Re: chirp_users Digest, Vol 109, Issue 6 and many others (D.J.J. Ring, Jr.) ---------------------------------------------------------------------- Message: 1 Date: Mon, 8 Jan 2018 02:14:17 -0500 From: "D.J.J. Ring, Jr." <n1ea(a)arrl.net> Subject: Re: [chirp_users] chirp_users Digest, Vol 109, Issue 6 and many others To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Message-ID: <CADO5RbiZU9VbjTVB6G-gO3sNn8rMMr2d6j4u1ED05-O-TG_z3w(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Chris, Check your language settings? What encoding are you using? I use UTF-8 on my desktop for the locale. If someone sends me a different encoding it often appears as you say it does. I am using an Android at the monent, so I have no idea of tge encoding, but probably UTF-8. 73 David N1EA On Jan 6, 2018 3:16 PM, "Christopher F. Beesley" <chrisbees2(a)hotmail.com> wrote: > Hi, Chris here. What's all this utter nonsense that is becoming more and > more common whereby the question mark is used instead of the apostrophe? > I'm fed up of seeing stuff that won't read easily because of it, e.g. I?m > fed up of seeing stuff that won?t read easily because of it. It?s rubbish! > Where did you lot learn English grammar' > > Chris. N.B. All punctuation errors above are deliberate, designed to > emphasise the point of this message. > > > ------------------------------ > *From:* chirp_users-bounces(a)intrepid.danplanet.com < > chirp_users-bounces(a)intrepid.danplanet.com> on behalf of > chirp_users-request(a)intrepid.danplanet.com <chirp_users-request@intrepid. > danplanet.com> > *Sent:* 06 January 2018 20:00 > *To:* chirp_users(a)intrepid.danplanet.com > *Subject:* chirp_users Digest, Vol 109, Issue 6 > > Send chirp_users mailing list submissions to > chirp_users(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > or, via email, send a message with subject or body 'help' to > chirp_users-request(a)intrepid.danplanet.com > > You can reach the person managing the list at > chirp_users-owner(a)intrepid.danplanet.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chirp_users digest..." > > > Today's Topics: > > 1. Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) > 2. Re: Fwd: FDTI chip compatibility with Mac (Fred Dalzell) > 3. Re: Fwd: FDTI chip compatibility with Mac (Jim McCorison) > 4. Re: Fwd: FDTI chip compatibility with Mac > (Nigel A. Gunn G8IFF/W8IFF) > 5. Re: Fwd: FDTI chip compatibility with Mac (Aubrey Turner) > 6. Re: Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) > 7. Wouxun KG-UV8E KG-UV8T KG-UV8D Plus (D.J.J. Ring, Jr.) > 8. Linux PPA problem? (Tom Consodine ND5Y) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 Jan 2018 17:31:13 -0600 > From: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com> > Subject: [chirp_users] Fwd: FDTI chip compatibility with Mac > To: chirp_users(a)intrepid.danplanet.com > Message-ID: <1A0978D7-3545-46A5-9A60-FAEF20F9553C(a)yahoo.com> > Content-Type: text/plain; charset="us-ascii" > > Here is the answer I got from FTDI regarding their cable chipsets! > Let me ask again: how many of you are Mac iOS users, and where did you get > your cloning cables from? > THanks. > Tip N9MVX > > > Begin forwarded message: > > > > From: Cameron Forbes <cameron.forbes(a)ftdichip.com> > > Subject: RE: FDTI chip compatibility with Mac > > Date: January 5, 2018 at 16:41:00 CST > > To: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com>, US Support < > us.support(a)ftdichip.com> > > > > Tipton: > > > > FTDI does not support iOS. > > > > > > Best Regards, > > > > Cameron Forbes > > Customer Support Engineer > > > > Future Technology Devices International Limited > > 7130 SW Fir Loop > > Tigard, OR 97223-8160 > > Tel: 503.726.5415 > > Fax: 503.547.0987 > > > > > > -----Original Message----- > > From: T.E. Klamberg Klamberg [mailto:n9mvx@yahoo.com <n9mvx(a)yahoo.com>] > > Sent: Tuesday, January 02, 2018 8:37 AM > > To: US Support > > Subject: FDTI chip compatibility with Mac > > > > My question has to do with the FTDI chipset and Apple computers. I have > a MacBook Pro with iOS High Sierra version 10.13.2 installed. > > Is your chipset compatible with that iOS? > > Thank you. > > > > Tipton Klamberg > > Mascoutah, Il 62258 > > (618) 670-1502 > > [FT-X]<http://www.ftdichip.com/FT-X.htm?utm_source= > EmailfooterApril17&utm_medium=EmailfooterApril17&utm_ > campaign=EmailfooterApril17&utm_term=EmailfooterApril17& > utm_content=EmailfooterApril17> > > Registered in Scotland No 136640 > > This message contains confidential information and is intended only for > the individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately by e-mail if you have received this e-mail by mistake and > delete this e-mail from your system. E-mail transmission cannot be > guaranteed to be secure or error-free as information could be intercepted, > lost, destroyed, arrive late or incomplete. The sender therefore does not > accept liability for any errors or omissions in the contents of this > message, which arise as a result of e-mail transmission. Future Technology > Devices International Ltd has taken every reasonable precaution to ensure > that any attachment to this e-mail has been swept for viruses. However, we > cannot accept liability for any damage sustained as a result of software > viruses and would advise that you carry out your own virus checks before > opening any attachment. > >

2 1

Re: [chirp_users] chirp_users Digest, Vol 109, Issue 6 and many others
by Christopher F. Beesley 07 Jan '18

07 Jan '18

Hi, Chris here. What's all this utter nonsense that is becoming more and more common whereby the question mark is used instead of the apostrophe? I'm fed up of seeing stuff that won't read easily because of it, e.g. I?m fed up of seeing stuff that won?t read easily because of it. It?s rubbish! Where did you lot learn English grammar' Chris. N.B. All punctuation errors above are deliberate, designed to emphasise the point of this message. ________________________________ From: chirp_users-bounces(a)intrepid.danplanet.com <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of chirp_users-request(a)intrepid.danplanet.com <chirp_users-request(a)intrepid.danplanet.com> Sent: 06 January 2018 20:00 To: chirp_users(a)intrepid.danplanet.com Subject: chirp_users Digest, Vol 109, Issue 6 Send chirp_users mailing list submissions to chirp_users(a)intrepid.danplanet.com To subscribe or unsubscribe via the World Wide Web, visit http://intrepid.danplanet.com/mailman/listinfo/chirp_users or, via email, send a message with subject or body 'help' to chirp_users-request(a)intrepid.danplanet.com You can reach the person managing the list at chirp_users-owner(a)intrepid.danplanet.com When replying, please edit your Subject line so it is more specific than "Re: Contents of chirp_users digest..." Today's Topics: 1. Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) 2. Re: Fwd: FDTI chip compatibility with Mac (Fred Dalzell) 3. Re: Fwd: FDTI chip compatibility with Mac (Jim McCorison) 4. Re: Fwd: FDTI chip compatibility with Mac (Nigel A. Gunn G8IFF/W8IFF) 5. Re: Fwd: FDTI chip compatibility with Mac (Aubrey Turner) 6. Re: Fwd: FDTI chip compatibility with Mac (T.E. Klamberg Klamberg) 7. Wouxun KG-UV8E KG-UV8T KG-UV8D Plus (D.J.J. Ring, Jr.) 8. Linux PPA problem? (Tom Consodine ND5Y) ---------------------------------------------------------------------- Message: 1 Date: Fri, 5 Jan 2018 17:31:13 -0600 From: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com> Subject: [chirp_users] Fwd: FDTI chip compatibility with Mac To: chirp_users(a)intrepid.danplanet.com Message-ID: <1A0978D7-3545-46A5-9A60-FAEF20F9553C(a)yahoo.com> Content-Type: text/plain; charset="us-ascii" Here is the answer I got from FTDI regarding their cable chipsets! Let me ask again: how many of you are Mac iOS users, and where did you get your cloning cables from? THanks. Tip N9MVX > Begin forwarded message: > > From: Cameron Forbes <cameron.forbes(a)ftdichip.com> > Subject: RE: FDTI chip compatibility with Mac > Date: January 5, 2018 at 16:41:00 CST > To: "T.E. Klamberg Klamberg" <n9mvx(a)yahoo.com>, US Support <us.support(a)ftdichip.com> > > Tipton: > > FTDI does not support iOS. > > > Best Regards, > > Cameron Forbes > Customer Support Engineer > > Future Technology Devices International Limited > 7130 SW Fir Loop > Tigard, OR 97223-8160 > Tel: 503.726.5415 > Fax: 503.547.0987 > > > -----Original Message----- > From: T.E. Klamberg Klamberg [mailto:n9mvx@yahoo.com] > Sent: Tuesday, January 02, 2018 8:37 AM > To: US Support > Subject: FDTI chip compatibility with Mac > > My question has to do with the FTDI chipset and Apple computers. I have a MacBook Pro with iOS High Sierra version 10.13.2 installed. > Is your chipset compatible with that iOS? > Thank you. > > Tipton Klamberg > Mascoutah, Il 62258 > (618) 670-1502 > [FT-X]<http://www.ftdichip.com/FT-X.htm?utm_source=EmailfooterApril17&utm_medium=E…> > Registered in Scotland No 136640 > This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, lost, destroyed, arrive late or incomplete. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Future Technology Devices International Ltd has taken every reasonable precaution to ensure that any attachment to this e-mail has been swept for viruses. However, we cannot accept liability for any damage sustained as a result of software viruses and would advise that you carry out your own virus checks before opening any attachment.

7 10

Re: [chirp_users] Linux PPA problem?
by Dave B 06 Jan '18

06 Jan '18

It seems that the entire Ubuntu Launchpad build computer farm is undergoing kernel patching for the recent Spectre and Meltdown Intel (and a few others) CPU problems. Other project groups have said. Sit tight and await the inevitable flood of updates once that lot is done. 73. Dave G0WBX. On 06/01/18 20:00, chirp_users-request(a)intrepid.danplanet.com wrote: > Message: 8 > Date: Sat, 6 Jan 2018 12:46:46 -0600 > From: Tom Consodine ND5Y <nd5y(a)yahoo.com> > Subject: [chirp_users] Linux PPA problem? > To: chirp_users(a)intrepid.danplanet.com > Message-ID: <3aec84c7-5b3e-19fe-cedf-8620a0036639(a)yahoo.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > I'm using Ubuntu linux here and a couple days ago I got the new daily > build available e-mail notice but I never got the new version when I did > a system upgrade. > > Today I looked at the Chirp Launchpad PPA page and it shows the latest > chirp-daily is 20180104 but then it says "5 packages waiting to build". > > Is the PPA broken or something?

2 2

[chirp_users] Linux PPA problem?
by Tom Consodine ND5Y 06 Jan '18

06 Jan '18

I'm using Ubuntu linux here and a couple days ago I got the new daily build available e-mail notice but I never got the new version when I did a system upgrade. Today I looked at the Chirp Launchpad PPA page and it shows the latest chirp-daily is 20180104 but then it says "5 packages waiting to build". Is the PPA broken or something? -- Tom ND5Y

2 1

[chirp_users] Wouxun KG-UV8E KG-UV8T KG-UV8D Plus
by D.J.J. Ring, Jr. 05 Jan '18

05 Jan '18

To all who have been following the work on Wouxun KG-UV8E issue #3943. I uploaded a debug log and I wasn't expecting my username and password to be in plain text, so the entire issue had to be deleted. (Thanks Dan) The project is moved: Wouxun KG-UV8E KG-UV8T KG-UV8D Plus <https://chirp.danplanet.com/issues/5481> https://chirp.danplanet.com/issues/5481 73 David N1EA

1 0