Differences

This shows you the differences between two versions of the page.

--- ref:zmodem [2021/06/29 15:34] – [ZFILE FRAME FILE INFORMATION SUBPACKET] footnote about path/file names with spaces (they are in fact supported in most ZMODEM implemenations) digital man
+++ ref:zmodem [2025/09/26 14:13] (current) – [ZMODEM Frame] Mention the Tera Term 0x8D 0x8A oddity digital man
@@ Line 74: / Line 74: @@
   <frame header> [CR] LF [XON]
-HEX frames are terminated with an ASCII linefeed character. Some ZMODEM implementations send the HEX frame terminating linefeed character with the high bit set (0x8A, that's ASCII-LF with an even-parity bit set). Also, for some HEX frame types, the frame terminator may be followed by an XON (0x11) character ("transmit on" in so-called "software flow control").
+HEX frames are terminated with an ASCII linefeed character. A carriage-return (CR) character may precede the linefeed (LF) character.
+Some ZMODEM implementations send this terminating LF with the high bit set (0x8A, that's ASCII-LF with an even-parity bit set). Some ZMODEM implementations (e.g. Tera Term) inexplicably send **both** CR and LF characters with the parity bit set (i.e. 0x8D 0x8A).
+Also, for some HEX frame types, the frame terminator may be followed by an XON (0x11) character ("transmit on" in so-called "software flow control").
 === Binary Frame ===

Trace: