OnlineWoerterBuecher.de
Internes

Lexikon


YMODEM


A file transfer protocol used between modems. YMODEM was developed by Chuck Forsberg as the successor to XMODEM and was itself succeeded by ZMODEM. XMODEM used 128-byte packets, YMODEM can also use 1 kilobyte packets. Whereas YMODEM is a batch protocol, YMODEM-G is a non-stop version. File sizes are included in the YMODEM header when sending both binary and text files. Thus files transferred via YMODEM should preserve their exact length. File modification times may also be present in the YMODEM header. YModem can fall back to smaller packets when necessary but there is no backward compatibility with XModem' s error detection. [Chuck Forsberg, "XMODEM/YMODEM Protocol Reference"]. (1995-02-02)

In addition suitable contents:
[ 2 ] [ = ] [ ad ] [ al ] [ am ] [ an ] [ ar ] [ arc ] [ as ] [ at ] [ b ] [ ba ] [ backward compatibility ] [ be ] [ bi ] [ binary ] [ bo ] [ bot ] [ by ] [ byte ] [ C ] [ ca ] [ cat ] [ cc ] [ Ch ] [ ch ] [ ck ] [ cl ] [ co ] [ com ] [ compatibility ] [ D ] [ de ] [ ding ] [ du ] [ E ] [ ec ] [ ed ] [ ee ] [ EM ] [ er ] [ error ] [ es ] [ et ] [ fall back ] [ fi ] [ file ] [ file transfer ] [ G ] [ gt ] [ h ] [ header ] [ hr ] [ hu ] [ id ] [ il ] [ in ] [ inc ] [ include ] [ io ] [ ir ] [ is ] [ it ] [ ke ] [ ki ] [ kilobyte ] [ kw ] [ ld ] [ Lex ] [ li ] [ ls ] [ lu ] [ M ] [ ma ] [ mall ] [ mo ] [ mod ] [ Mode ] [ mode ] [ modem ] [ module ] [ mp ] [ na ] [ nc ] [ ne ] [ ng ] [ no ] [ ns ] [ O ] [ om ] [ op ] [ pa ] [ packet ] [ pe ] [ ph ] [ pr ] [ protocol ] [ query ] [ rc ] [ re ] [ ro ] [ sa ] [ sb ] [ se ] [ serve ] [ sh ] [ si ] [ sm ] [ so ] [ st ] [ su ] [ successor ] [ T ] [ tc ] [ text ] [ text file ] [ th ] [ to ] [ tr ] [ tw ] [ us ] [ ve ] [ version ] [ vi ] [ X ] [ XMODEM ] [ Y ] [ YMODEM-G ] [ yt ] [ Z ] [ ZMODEM ]






Go Back ]

Free On-line Dictionary of Computing

Copyright © by OnlineWoerterBuecher.de - (5159 Reads)

All logos and trademarks in this site are property of their respective owner.

Page Generation in 0.2166 Seconds, with 17 Database-Queries
Zurück zur Startseite