text
stringlengths
0
99.6k
STX 02 FD Data[1024] CRC CRC
SOH 03 FC Data[128] CRC CRC
SOH 04 FB Data[100] CPMEOF[28] CRC CRC
EOT
ACK
G
SOH 00 FF NUL[128] CRC CRC
Chapter 6 XMODEM Protocol Enhancements
X/YMODEM Protocol Reference 10-27-87 18
7. XMODEM PROTOCOL OVERVIEW
8/9/82 by Ward Christensen.
I will maintain a master copy of this. Please pass on changes or
suggestions via CBBS/Chicago at (312) 545-8086, CBBS/CPMUG (312) 849-1132
or by voice at (312) 849-6279.
7.1 Definitions
<soh> 01H
<eot> 04H
<ack> 06H
<nak> 15H
<can> 18H
<C> 43H
7.2 Transmission Medium Level Protocol
Asynchronous, 8 data bits, no parity, one stop bit.
The protocol imposes no restrictions on the contents of the data being
transmitted. No control characters are looked for in the 128-byte data
messages. Absolutely any kind of data may be sent - binary, ASCII, etc.
The protocol has not formally been adopted to a 7-bit environment for the
transmission of ASCII-only (or unpacked-hex) data , although it could be
simply by having both ends agree to AND the protocol-dependent data with
7F hex before validating it. I specifically am referring to the checksum,
and the block numbers and their ones- complement.
Those wishing to maintain compatibility of the CP/M file structure, i.e.
to allow modemming ASCII files to or from CP/M systems should follow this
data format:
+ ASCII tabs used (09H); tabs set every 8.
+ Lines terminated by CR/LF (0DH 0AH)
+ End-of-file indicated by ^Z, 1AH. (one or more)
+ Data is variable length, i.e. should be considered a continuous
stream of data bytes, broken into 128-byte chunks purely for the
purpose of transmission.
+ A CP/M "peculiarity": If the data ends exactly on a 128-byte
boundary, i.e. CR in 127, and LF in 128, a subsequent sector
containing the ^Z EOF character(s) is optional, but is preferred.
Some utilities or user programs still do not handle EOF without ^Zs.
Chapter 7 Xmodem Protocol Overview
X/YMODEM Protocol Reference 10-27-87 19
+ The last block sent is no different from others, i.e. there is no
"short block".
Figure 8. XMODEM Message Block Level Protocol
Each block of the transfer looks like: