Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!ucbvax!VLSI.JPL.NASA.GOV!blc
From: blc@VLSI.JPL.NASA.GOV
Newsgroups: comp.os.cpm
Subject: Re : Details of Intel Hex Format
Message-ID: <870930141010.034@VLSI.JPL.NASA.GOV>
Date: Wed, 30-Sep-87 17:10:10 EDT
Article-I.D.: VLSI.870930141010.034
Posted: Wed Sep 30 17:10:10 1987
Date-Received: Sun, 4-Oct-87 23:04:24 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14

The problem of the PROmM programmer which wouldn't accept home grown
Hex files in my case turned out to be the lack of an end of file
record (record type 01.) I had an "unload" program which took a binary
file and generated a hex file from it. When I sent it to the PROM
programmer, the whole thing locked up. It turned out that until it
saw the EOF record, the programmer still wanted more data. The solution
was to add the following line to the file:

:00000001ff

and everybody was happy.

         Bruce Conroy
         BLC@JPL\E[M[%?/0,N