Adding a Second Floppy Controller to an X68000

The Sharp X68000 was designed around a two-drive floppy arrangement, which was perfectly sensible when software was distributed on one or two 5.25-inch disks. Modern owners often use the machine differently. A system may have an operating-system disk, a game disk, a development disk and a utility disk ready at the same time. Swapping media constantly is inconvenient, and external SCSI or CompactFlash storage does not reproduce every aspect of the original floppy workflow.

A second floppy disk controller can provide four independently selectable internal drives, provided the modification is designed as a complete hardware and software project. This is more involved than wiring two extra mechanisms to the existing connector. The controller, drive-select signals, interrupt or DMA behaviour, cable loading, termination and operating-system assumptions all need to agree.

The safest approach is to treat the X68000 as a family of related machines rather than assume every model has identical wiring. An ACE, XVI, Compact or early tower may differ in board layout, connector placement, ROM support and available space. Photograph the original arrangement, record every wire before removal and obtain the service documentation for the exact computer being modified.

Four internal drives are especially useful for preservation work. Several disk images can be mounted during testing, original disks can be compared without repeated handling, and software that expects a second physical drive can be used in a way that remains close to the period configuration. The modification also creates a useful platform for studying how X68000 firmware and operating systems address storage hardware.

Understanding The Original Drive Architecture

A standard X68000 floppy subsystem generally supports two drives through one controller. The controller generates the step, direction, read-data, write-data, motor and head-load activity, while drive-select lines choose which mechanism responds. In a conventional arrangement, the controller is shared and the two drives appear as separate units because each has its own select input.

That arrangement is the first point at which many modifications go wrong. Adding a pair of drive connectors to the existing bus does not create two more logical devices. If both mechanisms receive the same drive-select signal, they may respond together. If they share an unbuffered line over a longer cable, signal edges can become unreliable. If the firmware only knows about units zero and one, the extra hardware may be electrically sound but invisible to software.

A four-drive design therefore needs a second controller or an equivalent switching and decoding scheme. The second controller should have its own data path, control lines and selected drive pair. Its address, interrupt and DMA requirements must be considered alongside the original controller rather than bolted on after the wiring is complete.

Before designing a circuit, identify the exact floppy controller integrated circuit, its clock source, reset arrangement and connection to the X68000 main bus. Follow the schematic or trace the board with a continuity meter. Mark active-low signals carefully, because names such as /DRIVESELECT, /IRQ and /DACK describe logic polarity and are easy to misread during a late-night repair.

Choosing A Practical Second Controller Design

The cleanest arrangement is a second controller operating in parallel with the original but selected at a different I/O address. An address decoder can enable one controller for the standard register range and the other for a new range. The data bus is then shared only when the relevant chip-select signal is active. Proper buffering and bus isolation are essential; two controller outputs must never drive the bus simultaneously.

The second controller also needs a complete set of drive-control signals. Depending on the controller device, this can include drive select, motor enable, side select, density or data-rate control, write gate, track zero, write protect and index. Some signals are inputs to the controller, while others are outputs to the drive. Mixing those directions at a connector can damage a device or create symptoms that look like bad media.

Interrupt and DMA handling deserve special attention. A floppy controller that asserts an interrupt onto the same line as the original may work when tested alone but create duplicate service requests during simultaneous activity. A second DMA request can be even more troublesome if the X68000’s DMA hardware cannot distinguish the source. Use the documented interrupt and DMA architecture where possible, and provide a clear method to disable the second controller during early testing.

A small CPLD or carefully decoded logic board may be preferable to a collection of loose gates. It can provide address selection, reset defaults, controller enable signals and optional status registers in one documented design. This is where a project such as the Nereid-X can inspire a tidy expansion-board approach, although a floppy controller still needs its own electrical validation and firmware support.

Managing Drive Selects, Cables And Termination

Each pair of drives should have unambiguous select assignments. The primary controller might own drives 0 and 1, while the secondary controller owns drives 2 and 3 from the operating system’s perspective. The labels do not need to match the physical order, but the mapping must be recorded in the schematic, cable markings and software configuration.

X68000 floppy mechanisms may use conventions that differ from a modern PC drive. Do not automatically apply a PC cable twist or move jumpers based on a generic 34-pin diagram. Check whether drive select is configured by a jumper, solder bridge or cable position. Confirm the motor-enable behaviour as well. A drive that spins continuously may have its motor line tied incorrectly, while a drive that never spins may be receiving a select signal with the wrong polarity.

Keep ribbon cables short, routed away from the power supply and secured against the chassis. Old connectors can have oxidised contacts, and a cable that works on the bench may fail once folded into the case. Use keyed connectors only when their keying matches the original socket; forcing a modern keyed plug onto an incompatible header can shift every signal by one position.

Termination should be present only where the design expects it, normally at the electrically last device on a bus. Extra resistor packs can distort signals and increase loading, while missing termination can produce intermittent index or read-data errors. Examine the actual drive boards rather than relying on the label alone. A replacement mechanism may have a different termination arrangement from the original Sharp unit.

Power, Space And Australian Workshop Safety

Four mechanisms draw more startup current than two, particularly when several motors begin spinning together. Measure the 5-volt rail during motor start and check the supply’s capacitors, rectifiers and connectors before installing additional drives. A weak supply may appear stable at idle and collapse during simultaneous access. Modern low-power mechanisms can reduce the load, but their interface behaviour still needs checking.

The X68000 contains hazardous voltages, especially around the monitor and power sections. Australian mains power is nominally 230 volts at 50 hertz, commonly described as 240 volts in everyday technical conversation, and an unplugged CRT can retain a dangerous charge. Work on the floppy logic with the computer isolated from mains, and keep high-voltage repairs separate from digital modification work. The detailed flyback transformer buzz repair is a useful reminder that unusual noises from the display section should not be treated as harmless background activity.

Mechanical layout is just as important as the schematic. Four 5.25-inch mechanisms may require a custom bracket, altered front bezel, longer mounting screws or a change to the airflow path. Avoid placing a drive directly against a hot regulator or trapping the cable beneath a sharp metal edge. Add insulating washers where a board or bracket could contact the chassis, and maintain clearance around the disk insertion path.

Australian owners often source parts through eBay Australia, Gumtree or local retro-computing groups, with Sydney, Melbourne, Brisbane and Adelaide having particularly active pools of used hardware. Condition varies widely, so test each mechanism independently before committing it to the modification. Failed CRTs and electronic assemblies should go through a council transfer station or approved e-waste service; state rules differ, and CRTs should not be placed in ordinary household bins.

Firmware And Operating-System Support

Hardware discovery is rarely automatic on a vintage computer. The X68000 ROM and operating systems may initialise only the original controller and may assume that the floppy status registers exist at fixed addresses. A second controller at a new address will require software that knows where to find it, how to select its drives and how to report errors.

Start with a diagnostic program that can read and write controller registers without attempting a full operating-system boot. Verify reset state, status reads, command completion, index pulses, track stepping and write-protect detection. Test one secondary drive at a time. A simple sequence that seeks from track zero to several tracks and returns is more informative than immediately trying to boot a large disk image.

Once the controller responds, establish a stable device naming scheme. If the software presents the added drives as units 2 and 3, document that arrangement in boot scripts and disk-image tools. If it exposes a second controller through a special driver, keep the driver and its source with the hardware documentation. Future owners should not have to reverse-engineer an unfamiliar I/O map from a non-booting machine.

Disk images also need careful handling. A four-drive setup does not make every disk interchangeable. Confirm the expected sector size, track count, number of heads, data rate and density before writing an image. Preserve the original image files as read-only masters, use verified copies for testing and record which physical mechanism was used for each transfer.

Testing, Fault Finding And Preservation

Bring the modification up in stages. First test the original two drives with the secondary controller disabled. Then test the second controller with one known-good mechanism and a short cable. Add the fourth drive only after the first secondary drive can seek, read, write and report write protection consistently. This isolates logic faults from mechanical faults and prevents four uncertain variables from appearing at once.

A logic analyser is valuable for observing chip select, read and write strobes, drive select, motor enable and interrupt activity. An oscilloscope can reveal slow or ringing edges that a continuity test cannot detect. When a drive fails, compare its signals with a working drive at the same stage of an operation. “No disk” can result from a missing index pulse, incorrect motor timing, reversed data polarity or a controller that never receives the expected interrupt.

Drive alignment and head condition remain separate issues. A mechanism may pass a format test but fail to read an original disk because its heads are dirty or its alignment differs. Keep a verified reference disk, avoid aggressive cleaning solvents and use known-good media. For valuable software, prefer read-only examination until the drive and controller have demonstrated reliable operation.

The display system can complicate diagnosis because a floppy fault may be mistaken for a video fault when the machine boots to a blank or unstable screen. Keep a known-working display path available, and document symptoms before changing several subsystems. The account of a dead CRT repair illustrates why display faults deserve their own methodical diagnosis rather than being folded into a storage modification.

Label the completed machine inside the case with the controller address, drive mapping, cable orientation and any disable jumper settings. Store the schematic, PCB files, ROM patches, test logs and photographs in more than one location. A reversible modification with clear records is far more valuable to the X68000 community than an undocumented machine that happens to work for one owner.

Four internal floppy drives can make the X68000 significantly more convenient without turning it into an anonymous modern storage appliance. Design the second controller around the machine’s actual bus, verify every signal, support it in software and preserve the original configuration where practical. Build the circuit in a serviceable form, test each stage with known media and publish the measurements, diagrams and compatibility notes on X68K.NET so the next repairer can extend the work safely.