YMODEM

YMODEM is a <a href="/facts/Protocol_for_file_transfer/XGBF8I9C">file transfer protocol</a> used between <a href="/facts/Microcomputer/ETW22UTv">microcomputers</a> connected together using <a href="/facts/Modem/9H0Xwtq0">modems</a>. It was primarily used to transfer files to and from <a href="/facts/Bulletin_board_system/22d9c9s2">bulletin board systems</a>. YMODEM was developed by <a href="/facts/Chuck_Forsberg/1GQ7kf8H">Chuck Forsberg</a> as an expansion of <a href="/facts/XMODEM/TIadURGQ">XMODEM</a> and was first implemented in his <a href="/facts/CP/M/n5rTgXdC">CP/M</a> YAM program. Initially also known as YAM, it was formally given the name "YMODEM" in 1985 by <a href="/facts/Ward_Christensen/2ECmbe7W">Ward Christensen</a>, author of the original XMODEM.
YMODEM extended XMODEM in three ways, combining features found in other extended XMODEM varieties. Like XMODEM-CRC, YMODEM replaced the 8-bit <a href="/facts/Checksum/AqxQ0I8g">checksum</a> with a 16-bit <a href="/facts/Cyclic_redundancy_check/u2exo4sv">cyclic redundancy check</a> (CRC), but made it the default form of correction instead of optional. From TeLink it added the "block 0" header that sent the filename and size, which allowed batch transfers (multiple files in a single session) and eliminated the need to add <a href="/facts/Data_padding/Bqk6zMNS">padding</a> at the end of the file. Finally, YMODEM allowed the block size to be increased from the original 128 bytes of data to 1024, as in <a href="/facts/XMODEM/TIadURGQ">XMODEM-1k</a>, which greatly improved throughput on faster modems.
Forsberg built the standard with all of these features as runtime options, allowing a single protocol driver to fall back to XMODEM-CRC or even XMODEM when connecting to non-YAM systems. He believed that programmers would want to implement as many of these features as possible on any given platform. He was dismayed to find that the majority of implementations were actually providing nothing more than 1k block size with CRC-16, failing to implement the "block 0" while continuing to use the YMODEM name. The result was the release of many mutually incompatible YMODEM implementations, and the use of the name YMODEM Batch to clearly indicate those versions that did support the complete standard.

YMODEM open-in-new

YMODEM