How to copy a file from a 30-year-old laptop

Original Article ↗ Hacker News Discussion ↗

Overall reaction to the hack

  • Many readers found the fax/OCR solution clever, entertaining, and “Rube Goldberg–ish.”
  • Several note the data was likely sentimentally important and appreciate the persistence.
  • Others see it as intentionally convoluted: they feel the author skipped more straightforward methods in favor of a better story.

Serial/modem and classic transfer protocols

  • Repeated suggestion: use the laptop’s serial (COM) port with a null-modem cable and X/Y/ZMODEM or Kermit to transfer files.
  • Some point out that fax software of that era often bundled a terminal emulator capable of ZMODEM transfers.
  • Debate over practicality: older Macs often lacked obvious terminal apps; getting the right cable and RS‑422/RS‑232 wiring right can be tricky.

Disk, SCSI, and filesystem approaches

  • Many argue the “hard drive uses odd SCSI connector” is solvable: adapters and SCSI‑USB cables exist, often cheaply (including used).
  • Multiple commenters state Linux, BSD, and older macOS can mount HFS volumes or images with existing tools.
  • Digital forensics practice: best is to make a single “forensically sound” image of the disk, then experiment on the image.

Networking and AppleTalk

  • Several insist classic Mac OS had built-in AppleTalk networking and file sharing; the comment that there was “no networking software” is viewed skeptically or interpreted as “no TCP/IP stack.”
  • Ideas: use LocalTalk over serial, an AppleTalk–Ethernet bridge, or vintage Mac with both AppleTalk and Ethernet as a “bridge” machine.

OCR, error handling, and alternatives

  • Many think photographing the screen and OCR’ing that would beat fax quality; others counter that fax images and camera photos both produce ambiguous blobs at small font sizes.
  • Proposed OCR improvements:
    • Use OCR-friendly fonts (OCR‑A/OCR‑B) or custom character mappings to avoid confusable glyphs.
    • Do multiple faxes with varying fonts/sizes and combine outputs statistically.
    • Add parity/CRC or full error-correcting codes to the hex dump.
    • Specialized tools to cluster glyphs by character and visually spot misclassifications.
  • Several emphasize that LLMs or language-based “denoising” are useless for pure hex, since there’s no linguistic redundancy.

Audio-based and hardware-tap approaches

  • Some would have simply recorded the audio through the speakers with another device, accepting lossy quality for voice.
  • Others suggest tapping the speaker lines or DAC output directly to get a cleaner analog capture.
  • A few propose encoding data as modem-like audio over the speakers and decoding on a modern machine, similar to old cassette tape storage.

Retrocomputing anecdotes and nostalgia

  • Thread includes stories of past recoveries via serial printing, ZIP drives, SCSI imaging, and Amiga/Mac/CP/M setups.
  • Mention of modern SCSI emulators (e.g., BlueSCSI), floppy emulators, and the enduring usefulness of X/Y/ZMODEM in embedded and radio contexts.