Peter L. Peres wrote: > My impression was, that .HEX files are raw images (.HEX == .BIN). No, that's exactly the point; .HEX =/= .BIN Very specific here. > Anyway, most reasonable tools call this format 'object format', and > give it an extension of .OBJ or .S19... I'm not sure about the .OBJ bit. While the .HEX format has much embedded information; addresses for isolated segments, "type" fields and "run" addresses, I understand .OBJ format has much more, linking data to be specific. And this format can *not* be .S19 for the very simple reason - it *isn't* S1/S9 format! > The default .OBJ file output by PICALC under DOS is INHX16 which is > big endian. The INHX8M is the little endian version (and it > confused the hell out of the 1st parser I wrote for .OBJ files - the > only way to automatically tell the type is rewriting, as the checksum > applies correctly for each line if you swap the bytes around). Well, sounds like you *have* looked into this bit! > How can these edit 8-bit codes? I think that all Windows programs > will pop up something (a fuse ?) sooner or later as you try entering > secret codes . But .HEX files do not *contain* 8-bit codes. They are totally 7-bit *text* in which control characters have their ASCII meaning. Indeed, any ASCII editor will edit them just fine. You can edit the hex to alter the 8-bit values it *represents* as long as you fix the checksum accordingly. -- Cheers, Paul B.