Bridging the X68000 to a modern PC through serial

The Sharp X68000 has more than its share of admirers, and a stubborn streak of owners who refuse to let it gather dust. Bridging that early-1990s workstation to a contemporary machine over a humble serial cable sounds like a step backward, but it is often the only practical way to move software, debug code, or simply give the X68000 a window onto the modern internet without bolting on expensive, hard-to-source expansion hardware.

Australia has its own small but enthusiastic community of X68000 owners, scattered between weekend swap meets in Brisbane, hobby sheds in suburban Adelaide, and quiet Discord rooms where someone in Perth is always trying to source a working keyboard membrane. The same constraints affect everyone: aging hardware, vanishing parts, and a slow but steady stream of disk images that need a path from the internet onto 5.25-inch floppies. A serial bridge solves more of those problems than any single board replacement.

Why a serial bridge still makes sense in 2024

Most networking guides for vintage hardware assume Ethernet, but the X68000 predates that expectation in Japan and never shipped with an affordable aftermarket network card that survived the test of time. The two RS-232C ports on the back of the machine, however, are nearly indestructible and were designed for exactly the kind of asynchronous data exchange the hobbyist community now needs.

A serial bridge is also cheap. A null-modem cable costs the price of a takeaway flat white in Sydney's CBD, and a reliable USB-to-serial adapter based on an FTDI chipset can be ordered from a local supplier like Jaycar for under thirty Australian dollars. Compared with the cost of sourcing a working SCSI controller or a SCSI-to-IDE bridge board from overseas, the economics make sense for almost anyone who already owns the computer.

The bridge is also reversible. Nothing is soldered, nothing is flashed, and nothing prevents the machine from going back to standalone use the moment the cable is unplugged. For owners who treat their X68000 as a museum piece first and a working computer second, that reversibility matters.

Cabling and hardware choices for the X68000

The X68000's two RS-232C ports use the standard DB-9 male connector, with one port wired as DTE and the second as DCE, which is unusual and often catches newcomers out. To connect two X68000s directly, a straight-through cable works between the DTE port of one and the DCE port of the other. To connect to a modern PC, which almost always exposes a DTE-style USB-to-serial adapter, a null-modem cable is required.

Before worrying about software, it pays to verify the cable with a loopback plug. Shorting pins 2 and 3 on a DB-9 and watching characters typed locally bounce back in a terminal program is the fastest way to rule out a bad cable. Many of the cheap unbranded null-modem leads sold at computer fairs are wired for PC-to-PC rather than PC-to-router, and will silently drop handshaking lines that matter at 115200 baud.

If you are sourcing parts locally, both Jaycar and Altronics stock DB-9 hoods and pre-made serial cables, and the staff at the larger stores around Melbourne's Springvale electronics strip will even crimp custom pinouts on request. For those further afield, ordering from Japanese auction sites remains an option, though shipping and the weaker Australian dollar make this route expensive for a part that costs less than the postage.

While you are working on the hardware, it is worth thinking about other maintenance projects that keep the X68000 healthy. The site's notes on passive cooling solutions cover one of the most common failure points that bites machines that are left running for long file transfers.

Configuring the PC side for reliable transfers

Modern PCs no longer ship with built-in RS-232, so a USB-to-serial adapter is the first purchase. FTDI and CH340 are the two adapter chipsets worth bothering with, and FTDI is the safer option for older operating systems and odd baud rates. Drivers on Windows 10 and 11 install automatically for both, though the CH340 occasionally surfaces as an "unknown device" until the community-signed driver is manually selected.

Set the COM port to a sensible baud rate before worrying about anything else. The X68000's built-in UART tops out at 115200 baud reliably, and many real-world transfers settle at 38400 or 57600 because of how the machine handles interrupt latency under Human68k. A mismatched baud rate is the single most common reason transfers fail partway through, and most terminal programs will silently truncate or corrupt files rather than flag the problem.

It is also worth disabling Bluetooth serial services on Windows laptops before plugging the adapter in, since Bluetooth's virtual COM port can grab the same COM number and leave the X68000 unable to claim the port. Setting a fixed COM number above COM9 in the adapter's advanced settings sidesteps the conflict entirely.

The actual bridge: protocols and software

Once the cable works, the next decision is the protocol. XMODEM was the original standard and remains the most universally supported, with chunked packets and a checksum that catches most line-noise errors. YMODEM adds batch file transfer and a more robust CRC, and ZMODEM adds streaming recovery so that a brief cable glitch resumes the transfer rather than restarting it.

For the X68000, the classic tool is LT, the link-terminal program bundled with later versions of Human68k, paired with a corresponding terminal program on the PC side. LT understands XMODEM and YMODEM out of the box, and a small RAM-resident patch circulates in the community that adds ZMODEM support. On the PC, Tera Term, PuTTY with a serial profile, or the older HyperTerminal Private Edition all work without drama.

The interesting question is whether to treat the serial link as a one-off pipe for moving files, or as a permanent network bridge. The latter is achievable with a piece of software called tcpser, which presents a serial port as a TCP socket, and a complementary tool that does the reverse on the X68000 side. With a small amount of configuration, the X68000 can become a sluggish but functional terminal onto a Linux host that has full internet access. File transfers over the bridge are slower than direct XMODEM, but the bridge allows interactive SSH sessions, BBS logins, and email, which is more than the serial port alone can offer.

Here is how the common file-transfer protocols compare on a typical X68000-to-PC serial link:

Protocol	Effective throughput at 38400 baud	Error recovery	X68000 support
XMODEM-128	~3.0 KB/s	Checksum, restart on error	Built into LT
XMODEM-CRC	~3.1 KB/s	CRC16, restart on error	LT patch required
YMODEM-batch	~3.3 KB/s	CRC16, batch restart	LT patch required
ZMODEM	~3.4 KB/s	streaming resume	Community patch
TCP via tcpser	~2.8 KB/s	Built into TCP	Needs bridge software

For owners who use the X68000 on a laptop tethered to a phone, securing the modern end of the connection is also worth thinking about. Reading through the iPhone VPN guide covers the same public-Wi-Fi threat model that any Linux box running an exposed serial bridge has to think about, since the bridged traffic inherits whatever trust the host PC has on the wider network.

Common pitfalls and how to avoid them

The most frequent failure is the silent baud-rate mismatch described earlier. The X68000 has two serial ports, and the operating system will sometimes bind a program to whichever port it considers default, leaving the user staring at a frozen screen on the other. Always confirm the COM port number in the X68000's configuration utility, and always confirm the PC-side COM port number in Device Manager before assuming the cable is bad.

The second most common issue is flow control. None of the cheap serial cables include RTS/CTS wiring on pins 7 and 8, and software flow control using XON/XOFF will quietly drop data under load. If transfers of files larger than a few hundred kilobytes stall or arrive with blocks full of zeros, the first fix is to re-crimp the cable with handshaking lines connected, not to chase phantom software bugs.

Hardware failures are rarer but worth considering before chasing software fixes. The site's notes on power supply repair describe how marginal output voltages cause flaky serial behaviour that looks exactly like a cable problem. If the bridge works one day and fails the next without anything else changing, the rails are worth measuring before swapping cables again.

Finally, do not underestimate the value of a working loopback test. A few bent paper clips in a DB-9 connector can replace a missing loopback plug, and the two-minute investment can save an evening of chasing the wrong culprit.

Get started and share what you find

The X68000 community has always been small and generous, and the easiest way to give back is to write down what worked. Photos of working cable pinouts, configuration files for tcpser, baud-rate measurements on real hardware, and patches for Human68k all circulate freely when somebody takes the time to document them. Start with the bridge, get a single file transfer working end to end, and then publish the steps on a personal site, a mailing list, or the wiki pages maintained by enthusiasts in Sydney, Brisbane, and beyond. Every working bridge is one more reason the machine stays out of a cupboard.