The long wait for a ZIP file

The most valuable thing on a BBS was sometimes the file you couldn't get anywhere else: a shareware game, a printer driver, a text document full of tips, a new ANSI collection or a tiny DOS utility that solved a frustrating problem. Finding it was only half the challenge. You still had to transfer it over a telephone connection that could fail at any moment.

Files had their own economy

SysOps organized downloads into file directories with descriptions, sizes and upload dates. Callers searched by name or browsed new additions. Uploading a useful file could earn status or download credits. Some boards enforced upload/download ratios, although policies varied widely. Other boards gave files away without restrictions or charged subscription fees to support expensive systems.

What the transfer protocols did

A file-transfer protocol defined how a communications program and the BBS exchanged data, checked for errors and handled interruptions. Common names included:

• XMODEM: an influential early approach using blocks and acknowledgements to catch errors. Usually a single file at a time.
• YMODEM: offered extensions and variants that could include filenames and multi-file transfers, depending on implementations.
• ZMODEM: popular for more automated transfers, with features such as batch handling and, in capable implementations, resuming interrupted downloads.

Transfers were not always plug-and-play. The terminal software had to match the selected protocol, and a misconfiguration could turn a promising download into a series of timeouts. A frozen progress indicator was an all-too-familiar sight.

Original illustrative progress display, not captured from historical software.

The ZIP file as a tiny package

Compressed archives conserved transfer time and made distribution easier. ZIP became ubiquitous in PC communities, although ARC, LHA, ARJ and other formats also appeared. A shareware application might arrive as a ZIP containing an executable, documentation, registration instructions and a FILE_ID.DIZ description used by file-listing systems.

A lesson in patience

Downloading a few hundred kilobytes over a slow modem could be a major event. You considered the time of day, the reliability of the line, whether someone needed the telephone and whether you had enough time left on the BBS. Completing a transfer carried real satisfaction: you had acquired something through an effort that was both technical and social.

That patience helped build software communities. BBS file libraries distributed patches, programming tools and shareware far beyond the reach of local stores. The bytes may have arrived slowly, but they traveled through a remarkable volunteer-powered network.