Hi Pete,

Please note that the comment of mine that you quote was intended to be in reference to the product(s) (the Baofeng UV-B5 and cable) I bought and not in reference to CHIRP. I'm sorry that my intention in that regard was not clear. It certainly seemed from what I knew at the time that the problem was with the hardware, and I thought that that was clear from my comments.

However, I now think the problem is a problem with CHIRP because I have been able to upload the HT's programming into the OEM software offered by miklor.com .

So Hooray! All is not lost! At least it seems I have not irreparably damaged the radio as I had feared.

But it does seem that a bug fix of CHIRP regarding the problem is in order. However, I have not checked whether this problem is already regarded as a bug that needs fixing.

Anyway, I thought folks would like to know in case anyone else is puzzled by this sort of problem.

Richard Haney

On Tue, Jun 10, 2014 at 5:11 PM, Pete Mackie <pete@seaquest.com> wrote:

You pays you money (zero $) and take your chance. There is no free lunch. Be thankful that some developers donate their extra personal time to make CHIRP available. If you want a better product, then I suggest you join the CHIRP development team to assist with better “basic engineering design.”

And just so you know, CHIRP is getting constantly better all the time thanks to hard work of donated software developers. If you do not like what CHIRP is providing for you in the way of an experience, then I suggest that you not use it.

Pete Mackie

On Jun 10, 2014, at 4:45 PM, Richard Haney <rfhaney@gmail.com> wrote:

But I am also dismayed that the system seems to be so temperamental. I would think that basic engineering design principles would be employed to guard against very common errors.

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users