Building a ZIP drive interface for the X68000 SCSI chain

The Sharp X68000’s SCSI interface can give a compact Japanese home computer a useful removable disk, but a ZIP drive is not a plug-and-play peripheral. The interface must respect the bus’s 5 V single-ended signalling, device addressing and termination rules. Get those details right and the project becomes a practical piece of hardware preservation; get them wrong and the symptoms can range from an invisible drive to intermittent parity errors and corrupted files.

This guide follows a bench approach: establish the host’s termination arrangement, select a compatible ZIP mechanism, build a small adapter with removable termination, and test each stage before attaching media. It applies most directly to original Iomega SCSI Zip hardware, while also covering newer mechanisms and adapters sold by specialist vendors. The aim is a reproducible design that an Australian hobbyist can maintain long after the original manuals have vanished from online listings.

Understanding the X68000 SCSI chain

The X68000’s narrow SCSI bus connects a controller to 8-bit, single-ended peripherals such as hard disks, scanners and CD-ROM drives. A Zip mechanism sits on that bus as a target device and must answer using a unique SCSI ID. The controller’s conventional ID, commonly 7 on X68000 systems, should remain untouched, while a peripheral such as the ZIP can use an unused low ID.

Signal cables carry data, parity and handshake lines between the host and every device. Each target watches for its selected ID and then joins the conversation; a duplicate ID can make two devices respond at once. Before choosing jumpers, identify the layout on the actual ZIP board because original Iomega cases, Zip 100+ units and modern replacements do not always use the same switch positions.

Practical records from the wider X68000 enthusiast community make it easier to learn how particular machines were configured. Compare controller revisions and photographs of known-working buses, but treat every external terminator and DIP setting as something to verify on the hardware in hand.

Choosing a ZIP drive and controller

Buy a mechanism with a genuine single-ended SCSI connector. Many Iomega Zip models sold today are USB models intended for a PC, and their enclosure says nothing about SCSI compatibility. Original Zip 100 units use 100 MB media, Zip 250 units use 250 MB disks, and later SCSI variants support other capacities. Confirm the interface label, connector type and supported media before dismantling anything.

Capacity is only the first consideration. The X68000’s firmware and software must recognise the reported size, and its partition utilities may impose limits different from those found in modern PC tools. Check the controller’s specifications for removable disks rather than assuming that any 512-byte SCSI disk will appear correctly. Retain the original Iomega cover and disk if possible, since it can help identify the mechanism and preserve the matching media.

Australian buyers can find occasional Zip hardware through specialist sellers, online auctions and retro-computing swap meets in cities such as Sydney and Melbourne. Imported mechanisms from Japan and the United States remain common, so prices may move with the Australian dollar and exchange rate. Low-value parcels can attract GST, duty or courier handling charges, while commercial buyers may need to account for them through their GST registration. Check the seller’s packing description and retain the invoice for customs purposes.

Designing a safe termination board

A simple X68000-to-ZIP interface needs a correctly wired DB25 connector, solid mechanical mounting and a way to configure termination. Keep the data and control paths short, add test points for the major signals and provide a keyed or clearly labelled connection to the drive. An activity indicator can be useful, but buffer it so the indicator circuitry cannot distort the bus or load a handshake line.

Termination requires particular care. A properly terminated SCSI segment needs suitable end-of-line networks at its physical ends and none in the middle. The X68000 may provide host-end termination on a particular controller revision, while the ZIP may also have resistor packs fitted by default. Trace the actual board or consult revision-specific documentation, and measure the unpowered hardware rather than relying on a generic diagram. Passive packs often use roughly 220–330 ohms on the relevant signal lines, but the installed design is the authority.

Design option	Signal path	Main advantage	Main caution	Practical use
Passive breakout	Direct connection	Low cost and minimum complexity	Adds no end termination	Short connection where existing termination is correct
Removable passive terminator	Direct connection with a switchable resistor pack	Termination can be changed without soldering	Fit only where required at a physical end	Most X68000 and single-ZIP builds
Active terminator	Direct data path with powered current-source termination	Better margins on long or noisy cables	More complexity and possible compatibility issues	Difficult installations after simpler options fail

A removable resistor network makes the adapter easier to reuse with different SCSI chains. Populate it only when it is required, and never combine active and passive termination at the same physical end. When the ZIP’s own termination is active, leave it out of the connector board; when the board supplies termination, disable the ZIP’s internal network if the manufacturer allows it.

For club or family archives, controlled documentation matters as much as the PCB. A schematic, wiring photographs and a revised parts list can live in a Microsoft 365 library, and the Microsoft SharePoint views material provides a useful reference for presenting those records. Record which termination arrangement is active and why, since that note may save the next person an afternoon of fault-finding.

Wiring power and protecting signals

Many original Zip 100 mechanisms expect both 5 V logic and 12 V for motors or auxiliary circuits, although later boards can differ. Follow the label and circuit diagram for the exact mechanism; never assume a modern replacement accepts the same rails. Keep motor current away from the logic supply, join signal grounds properly and check for ripple with an oscilloscope. Do not feed the SCSI connector’s termination-power rail into external circuitry unless the host documentation confirms that it is safe.

Original Japanese X68000 power supplies may be designed for 100 V mains and cannot be connected directly to an Australian 230 V outlet. A plug adaptor changes the physical connector, not the voltage. Use an appropriately rated isolated supply, preferably carrying Australian RCM certification, and keep mains wiring out of the interface board. Any work involving the X68000’s internal power supply is best checked by a qualified electrician, particularly if the unit has been stored for years.

Use a proper high-density DB25 SCSI cable with sound connector shells and strain relief. Ordinary serial-extension leads, ribbon adapters or moulded monitor cables may lack the correct conductor assignments. Route the cable away from motors and switching supplies, secure both connector shells and inspect the pins for bent contacts. A short, correctly terminated bench cable is usually quieter than a long cable assembled from uncertain parts.

Configuring X68000 software and media

Begin with the simplest configuration: assign the ZIP an unused ID, confirm the host’s termination, connect the drive without media and observe whether the X68000 reports it during startup. Insert a known-good disk and repeat the check. If the machine sees the target but reports a media error, test the disk in another SCSI enclosure and inspect the drive’s head movement, motor sound and error LEDs before changing the software.

Use X68000-compatible formatting and partition tools, following the controller’s removable-media procedures. Avoid formatting a disk with Windows unless a specific cross-platform filesystem and matching X68000 driver have been arranged. Check whether the operating system treats the target as removable or fixed, and prevent startup software from writing to it when that behaviour is inappropriate. An Australian keyboard layout also requires attention: map the Japanese keyboard in Human68k or the chosen application so that path names and command-line tools remain usable.

Keep a dated test log similar to the X68000 diary archive, recording the controller revision, drive model, SCSI ID, jumper positions and termination arrangement. Repeat cold starts, warm resets, reads of both sides of several disks and file-copy comparisons. Intermittent failures should be investigated at the lowest possible level, separating power noise, signal integrity, media condition and software detection.

Documenting the build for the community

Produce a reproducible package containing the schematic, PCB artwork, bill of materials, connector pinout, jumper settings and photographs of the assembled board. Label the SCSI ID and termination state on the enclosure. Keep notes about any departures from the original ZIP wiring, especially where a modern controller board differs from Iomega’s design.

Preservation also means retaining the parts that are easy to discard. Store spare resistor packs, jumper links, DB25 connectors, suitable cable and a known-good ZIP disk. Where replacement mechanisms are electrically similar but mechanically different, document those differences so the next collector does not assume the adapters are interchangeable.

Australian collectors in Sydney, Melbourne and other regional centres can reduce the risk of losing scarce hardware by sharing test equipment and duplicating important documentation. Keep images and software needed to recreate a setup, plus checksums for archived files and disk images. Physical Zip disks can suffer from sticky hubs and aged media, so test the originals and retain verified images before the shells become unreadable.

Build the interface in testable stages: verify termination, assign one unused ID, power the mechanism without media, and add it to the chain only after the host detects it. Photograph every stage and record the exact configuration. Then publish the schematic, wiring notes and test results for the wider X68000 community, helping this practical corner of retrocomputing remain usable rather than merely preserved behind glass.