Synchronet v3.21e-Win32 (install) has been released (Mar-2026).

You can donate to the Synchronet project using PayPal.

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
ref:zmodem [2020/12/01 22:14] – [ZMODEM Frame] typo digital manref: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]   <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). 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 === === Binary Frame ===
Line 681: Line 685:
 The pathname (conventionally, the file name) is sent as a The pathname (conventionally, the file name) is sent as a
 null terminated ASCII string.  null terminated ASCII string. 
-No spaces are included in the pathname. +No spaces are included in the pathname. ((some ZMODEM implementations support path/file names that include spaces))
  
 Filename Considerations Filename Considerations

Trace: