When you import the file into your burner you may 
be importing it incorrectly... Two formats are 
common, Intel and Motorola. If you have a copy of 
hex workshop, look at the file and see if it is 
an s19 Motorola record image. I went through this 
as I programmed a lot of the T800's a while back 
but do not recall which format they were....
Intel Hex and Motorola are not interchangeable. 
but your burner likely will import either....

Last resort I can do them for you, but it has 
been a while so I would need to dig into it to 
see how I did them last time. I do not recall it 
being an ordeal, just need the correct file format....

Doug
KD8B



At 10:36 AM 8/26/2005, you wrote:
>I have recently acquired 5 Tait T800 series 1 repeaters.
>
>I have an EPROM burner, new 27C64 chips, the Tait T800 programming software.
>
>PGM800  V2.21    DOS Based        Sept 1995
>
>PGM800  V4.05    Windows Based
>
>I burned a few EEPROMs from .bin images created in the Tait software.
>
>I cannot get any of them to work.  When I read 
>the image, I get “Corrupt Image” error, but the EEPROM loads.
>
>It shows the frequencies in the order I programmed them.
>
>I am not using internal PL, so PL is set at off.
>
>Is there something I am missing?
>
>Is there anyone that could burn a dozen EEPROMs for T800’s?
>
>Thanks,
>
>Andrew D. Hudanish
>KCØEJX
>
>
>
>
>
>
>
>
>
>
>
>----------
>YAHOO! GROUPS LINKS
>
>    *  Visit your group 
> "<http://groups.yahoo.com/group/Repeater-Builder>Repeater-Builder" on the web.
>    *
>    *  To unsubscribe from this group, send an email to:
>    * 
> <mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED] 
>
>    *
>    *  Your use of Yahoo! Groups is subject to 
> the <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.
>
>
>----------






 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/Repeater-Builder/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to