That's what I tried searching for, but could not find anything like that
in the MTX9250 CPS. Like you, I have not seen this on other models.
It's odd to me.
Thanks,
> you go the route of
hamfiles.co.uk <
http://hamfiles.co.uk>, you can
> find CPS R02.03.00 already modified for ham bands and I did verify
> that one worked too.
>
> Thanks,
>
> On Wed, Jan 23, 2019 at 6:41 PM John Miller <
n1um...@gmail.com
> <mailto:
n1um...@gmail.com>> wrote:
>
> I did that tight up to programming the radio then I get the
> error. Sounds like I'm doing it right something else is wrong.
>
>
> On Wed, Jan 23, 2019, 6:08 PM John Mullaney
> <
k1...@scanboston.com <mailto:
k1...@scanboston.com> wrote:
>
> Here is the steps. Read your radio and save your code plug.
> Always the best way to start so you can back up. Then close
> your code plug and open up the new code plug. Now this was
> not made with your radio so you can’t write as is right into
> your radio. What you do go to the clone menu and clone it
> into your radio. When you clone you’ll read serial number
> then do a clone. That now clones the new code plug into your
> radio. After that read your radio again and save it with a
> date if your new code plug.
>
> John K1BOS
>
> Sent from my iPhone
>
> On Jan 23, 2019, at 5:22 PM, John Miller
> <
n1um...@gmail.com <mailto:
n1um...@gmail.com>> wrote:
>
>> Hi, I have a question. A updated mtx9250 code plug was
>> posted I believe here a week or so ago. I tried to update
>> my mtx9250 radios today and for whatever reason when I go
>> to program it in to them it comes up with an error, I can
>> get the specific error but when I got mad and shut it off
>> I wasn’t thinking to note it right away, anyway, about a
>> key too short and programmer has to close. It reads the
>> radio, reads the serial number, does anyone have any idea
>> what this is or how to fix it? I’d rather not brick them.
>> I think they worked with my old computer I used for that
>> stuff, another windows 98 box with similar specs but that
>> one lost the hard drive, and a couple other things so is
>> no longer among us I had to contact a friend to grab
>> another similar machine then this started. I’m not in a
>> rush to get this done I can’t hit anything from my house
>> anymore anyway but once spring hits I’ll be out and about
>> a lot and want to update them for then if I can. I’m not
>> sure how out of date my current code plug even is right
>> now but I know it is out of date.____
>>
>> Thanks, John N1UMJ____
>> <mailto:
near-900-u...@googlegroups.com>
>> ---
>> You received this message because you are subscribed to
>> the Google Groups "Near-900" group.
>> To unsubscribe from this group and stop receiving emails
>> from it, send an email to
>>
near-900+u...@googlegroups.com
>> <mailto:
near-900+u...@googlegroups.com>.
> <mailto:
near-900-u...@googlegroups.com>
> ---
> You received this message because you are subscribed to the
> Google Groups "Near-900" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to
>
near-900+u...@googlegroups.com
> <mailto:
near-900+u...@googlegroups.com>.
> <mailto:
near-900-u...@googlegroups.com>
> ---
> You received this message because you are subscribed to the
> Google Groups "Near-900" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to
near-900+u...@googlegroups.com
> <mailto:
near-900+u...@googlegroups.com>.
> <mailto:
david.l....@gmail.com>>
> <mailto:
near-900-u...@googlegroups.com>
> ---
> You received this message because you are subscribed to the Google
> Groups "Near-900" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to
near-900+u...@googlegroups.com
> <mailto:
near-900+u...@googlegroups.com>.
> <mailto:
near-900+u...@googlegroups.com>.
WH6DSN |
https://www.burdell.org/