Adding wireless file transfers to an X68000

The Sharp X68000 remains a remarkably capable machine for a computer designed in the late 1980s. Its SCSI storage, generous expansion options and strong software library make it practical for games, music, programming and preservation work. Moving files to and from a modern computer, however, can be less convenient than using the machine itself. Floppy disks are slow, ageing and increasingly difficult to replace, while removable media often involves a chain of adapters.

A small Wi-Fi bridge provides a cleaner alternative. The most accessible approach is to connect an ESP32 or similar module to the X68000’s RS-232C serial port, then use a terminal transfer protocol across the wireless network. Owners with an Ethernet expansion board can take a different route by placing a wireless bridge between the board and the home network. Neither method makes the X68000 behave like a modern network drive automatically, but both can make routine file transfers quick and reliable.

Approach	Hardware required	Transfer method	Difficulty	Best use
Serial Wi-Fi bridge	ESP32 or ESP8266, RS-232 level converter, regulated supply	ZMODEM, XMODEM or Kermit	Moderate	General file exchange
Wireless Ethernet bridge	Nereid-X or another Ethernet interface, travel router or bridge	FTP, network tools or TCP services	Moderate to high	Existing network software
Wi-Fi-enabled storage adapter	Compatible storage interface and supported firmware	Device-specific	High	Disk image and bulk storage work
USB-to-serial computer link	Modern computer, USB serial adapter, RS-232 cable	Terminal transfer protocols	Low	Testing before installing Wi-Fi

Choosing the right wireless architecture

For most hobbyists, a serial Wi-Fi bridge is the sensible starting point. The X68000 already provides a serial interface, and transfer software based on XMODEM, YMODEM, ZMODEM or Kermit is mature and well documented. The Wi-Fi module handles the network connection, while the X68000 simply sees a fast serial device. This keeps the modification reversible and avoids relying on obscure networking software for the Sharp platform.

An ESP32 is generally preferable to an ESP8266 for a new build. It has greater processing headroom, flexible serial support and broad availability through Australian electronics retailers. A compact ESP32 development board can join a 2.4 GHz WPA2 network and run firmware that provides a transparent TCP connection or a small file-transfer service. Many current routers still support 2.4 GHz, but a 5 GHz-only guest network will not work with these older wireless chipsets.

An Ethernet route suits an X68000 that already has a Nereid-X or a similar expansion board. In that case, a small travel router configured as a wireless client can connect the wired interface to Wi-Fi. This avoids modifying the serial port, although configuration is more involved and software support varies between X68000 operating systems. It can also be a neat solution for a desk in Brisbane, Perth or regional New South Wales where running a long Ethernet cable across the room is inconvenient.

Before buying parts, decide whether the goal is occasional transfer of disk images, regular movement of source code, or network access from within Human68k. A terminal protocol is usually enough for the first two. A full network stack is only worthwhile when the software you intend to use can actually speak TCP/IP and access the chosen interface.

Preparing the X68000 and the module

A serial Wi-Fi installation must respect the electrical differences between the computer and the wireless board. The X68000’s RS-232C port uses voltage levels that are unsuitable for direct connection to the 3.3-volt UART pins on an ESP32. Use a proper RS-232 transceiver, such as a MAX3232-compatible board, between the computer and the module. A simple voltage divider is not a substitute because RS-232 uses bipolar signalling and inverted logic.

The module also needs a stable 5-volt or 3.3-volt supply, depending on the development board. Wi-Fi transmit bursts can cause current spikes, so do not rely on a marginal regulator or an old internal supply rail without checking it first. A separate, well-regulated USB supply is useful during testing. If the board is eventually fitted inside the X68000, add suitable strain relief and insulation, and ensure that its antenna is not trapped against a metal shield.

Inspect the serial connector, cable and ground connection before powering anything. Old connectors can have oxidised contacts, and a poorly crimped cable may produce intermittent failures that look like software problems. Confirm the transmit and receive paths with a loopback test on the modern computer before connecting the Sharp. Keep the first test external and reversible; permanent mounting can wait until the transfer process is dependable.

Power-supply condition matters as much as signal wiring. A restored machine may still have tired capacitors, heat-damaged connectors or an unstable auxiliary rail. The same careful approach used when restoring the X68000 monitor applies here: document the original wiring, measure before modifying it, and avoid treating an unknown fault as a software issue.

Installing firmware and establishing a link

The easiest firmware arrangement is a transparent serial-to-TCP bridge. The ESP32 joins a specified wireless network, opens a TCP listener or connects to a known host, and forwards bytes between its UART and the network socket. On the X68000, a terminal program can then send a file using ZMODEM or another supported protocol. On the host computer, a Linux, macOS or Windows terminal utility receives the data.

Set a conservative serial speed for the first tests, such as 9,600 or 19,200 baud. Once the connection is stable, increase the rate if the X68000 software, level converter and firmware can handle it. Higher speeds may work well, but a fast transfer is not useful if dropped characters corrupt disk images. Hardware flow control deserves attention too. If the selected software expects RTS/CTS and the bridge does not provide it, disable that requirement or wire the signals correctly rather than relying on luck.

Give the bridge a predictable network address. A DHCP reservation on the home router is usually safer than hard-coding an address that may overlap with another device. Use a separate wireless network or an isolated VLAN if the firmware exposes an unauthenticated TCP port. An old computer does not need to be placed directly on the public internet, and port forwarding should never be required for local file exchange.

Australian home networks have a few practical wrinkles. NBN routers supplied by different providers can expose separate guest-network settings, band steering and client-isolation options, all of which can affect a small embedded device. If the ESP32 joins Wi-Fi but the host cannot connect, check that both devices are on the same local network and that guest isolation is disabled. A basic 2.4 GHz SSID with WPA2 and a fixed DHCP lease is often less troublesome than a clever mesh configuration.

Sending files without damaging them

Wireless connectivity only transports bytes; the transfer protocol protects the file. ZMODEM is a strong choice because it can resume interrupted transfers and checks the received data. XMODEM is simpler and is supported by more vintage software, though it is slower and less forgiving. Kermit remains useful when the available terminal program supports it, particularly for text files and systems with unusual serial behaviour.

Disk images require extra care. Transfer them in binary mode, not text mode, and compare checksums after reception. A single altered byte can make a floppy image fail to boot or cause a compressed archive to report an error. On a modern computer, calculate a SHA-256 or CRC32 value before sending and again after receiving. On the X68000, use an available checksum utility or write a small verification program if the system tools are limited.

File naming can also cause trouble. Human68k software may expect particular extensions, directory formats or 8.3-style names, while a modern host may preserve characters that the older environment cannot display. Keep names short and plain during initial testing. Transfer a small text file, then a program, then a disk image. This sequence separates serial problems, protocol problems and media-writing problems instead of mixing them together.

When using an Ethernet-based bridge, FTP can be convenient, but avoid anonymous services and unencrypted exposure outside the local network. For a serial bridge, a temporary TCP connection is adequate if the wireless network is trusted and the bridge is not reachable from the internet. Once a file arrives, copy it to the appropriate X68000 storage device and verify that it opens correctly before deleting the original.

Mounting, testing and keeping it serviceable

A removable installation is usually better than permanently drilling the case. A small enclosure containing the ESP32, RS-232 transceiver and regulator can sit beside the X68000, with a short cable to the rear serial port. This arrangement makes troubleshooting easier and allows the same bridge to be used with another vintage computer. Label the cable and record the pinout, baud rate, firmware version and network address inside the enclosure.

If internal installation is important, choose a mounting point away from the power supply, CRT circuitry and fan airflow. Keep the wireless antenna clear of large metal panels where possible. Do not route signal wires alongside mains wiring or high-voltage monitor components. The X68000 is compact inside, and an attractive modification can become a repair problem if it obstructs ventilation or complicates future servicing.

Test the complete workflow with several file types and a cold start. Check that the module reconnects after the router is restarted, that the X68000 can still use its ordinary serial functions, and that a failed transfer does not leave the receiving program locked. Try the setup with the machine’s normal storage hardware fitted, because SCSI activity, accelerator boards and other expansions can expose power or grounding weaknesses.

Keep a second transfer method available. A USB-to-serial adapter, compact flash solution or floppy emulator can rescue the system if the wireless firmware becomes incompatible. Record working firmware and configuration details in a local text file, and preserve a copy of the host-side terminal software. The ongoing notes in the X68K.NET project diary illustrate the value of documenting small hardware and software changes while their details are still fresh.

Making wireless transfers part of the workshop

Once the bridge works, create a simple routine rather than treating every transfer as an experiment. Store X68000 utilities, disk images and source files in clearly named folders on the host computer. Use a dedicated transfer directory, calculate checksums for important images and keep original files read-only. This makes it easier to identify whether a problem came from the wireless link, the storage device or the application.

A practical Australian setup might pair the X68000 with a small 2.4 GHz access point, a modern laptop and a separate power adapter purchased from Jaycar or an established electronics supplier. Local availability is useful: parts listed on Australian eBay or Gumtree can vary in quality, and imported boards may arrive with unfamiliar USB plugs, questionable regulators or incomplete documentation. Spending a little more on a known MAX3232 board and a reputable development module is usually cheaper than chasing intermittent faults.

Do not assume that wireless means fast enough for every job. Large disk images may still take time at conservative serial speeds, and a busy household network can introduce interruptions. For day-to-day use, though, the convenience is substantial: download a preservation tool on the modern computer, send it to the X68000 without hunting for a working floppy, and retain the original image for later verification. That workflow supports both regular experimentation and careful historical preservation.

Build the bridge externally, verify its electrical levels, configure a protected 2.4 GHz network and begin with small binary transfers. Once checksums match and reconnects are reliable, install it in a tidy enclosure and document the result. This gives the X68000 a practical wireless file-transfer path while preserving the character, serviceability and expandability that make the platform worth keeping alive.