[chirp_users] New Daily Build - DOESN'T WORK.

Dennis Wage dwage at dwage.com
Thu Jun 7 07:47:08 PDT 2018


These constant emails about Chirp not working must drive Dan and his
cohorts absolutely crazy.

>>>IT'S NOT CHIRP!! IT'S THE CABLES AND THE DRIVERS. LEARN WHAT'S GOING ON
THERE AND YOU'LL BE FINE!<<<

One thing I will say though is sometimes you have to unplug and plug back
in both cloned and un-cloned data cables. I am not sure what's going on
there.. but remember, Device Manager is your friend.



Dennis M. Wage (W9BOQ)

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

On Thu, Jun 7, 2018 at 9:40 AM, Jardy Dawson via chirp_users <
chirp_users at 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?
>
> On Jun 7, 2018, at 06:46, Mike-2007 <mike-2007 at 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 at intrepid.danplanet.com [
> mailto:chirp_users-bounces at intrepid.danplanet.com
> <chirp_users-bounces at intrepid.danplanet.com>] *On Behalf Of *Jock via
> chirp_users
> *Sent:* Wednesday, June 06, 2018 22:08
> *To:* chirp_users at 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 at 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 at 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 at 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 at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Eugene Baleme at speedgene at yahoo.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrep
> id.danplanet.com
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Jock at kc6iih at aol.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrep
> id.danplanet.com
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Jardy at jardy72 at yahoo.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrep
> id.danplanet.com
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Dennis Wage at dwage at dwage.com
> To unsubscribe, send an email to chirp_users-unsubscribe at intrep
> id.danplanet.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180607/45f806fe/attachment-0002.html 


More information about the chirp_users mailing list