Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!hao!ames!pasteur!ucbvax!SIMTEL20.ARPA!WANCHO From: WANCHO@SIMTEL20.ARPA ("Frank J. Wancho") Newsgroups: comp.os.cpm Subject: CP/M-86 Message-ID: Date: 17 Feb 88 03:07:00 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 26 John, The number, in hex, after the colon, is the number of data bytes to follow after the PC (two hex bytes, low hex byte first) and a 00h. Thus, if the number after the colon is 10h (16d), the line length, in characters, would be: colon 1 count 2 address of PC 4 type (0 = bin) 2 data in hex 32 checksum 2 -- 43 or, an overhead of 11 characters. Thus, if the line is 71 characters long, the two characters after the colon would be 1Eh. If it were 65 characters long, the two characters would be 16h. In any event, DDT and LOAD both know how to handle counts other than 10h. All HEXIFY is trying to do is reduce the number of lines requiring that 11 character overhead by packing more data per line, all of which is perfectly legal in the Intel HEX format. --Frank