How Commodore Made A Sync Splitter

Recently we featured an unusual Commodore 8-bit computer on the bench of [Tynemouth Software] — a Commodore 64 in a PET case. One of the unique parts it had was a board which took the composite output from the mainboard and split out the sync pulses for the monitor, and now they’re back to give it a full reverse engineer.

Perhaps the first surprise is why this board is necessary at all, after all one might expect an 8-bit machine to have those signals already at hand. It seems that the VIC chip inside the 64 did the combination to composite internally, so no such luck for the Commodore engineers. The board they designed then is a complete and very well-engineered sync splitter.

The technology of a video signal has its origins in the 1930s, so it’s not hard to extract both vertical and horizontal sync pulses with little more than a few passive components and a couple of transistors. The trouble with such a simple approach is that the output will work, but it will be messy and crucially, not have quite the required timing. The Commodore board uses the same approach as a simple discrete circuit of having a pair of filters with a time constant selected to catch the relevant sync, but extends it with extra logic. There are one-shots designed to provide clean pulses of exactly the right length, and gates that provide blanking to remove the chance of pulses ending up where they shouldn’t. The video path is the only part which might differ from a conventional sync splitter, because as the output from the 64 is all-digital, it takes a TTL-level through a gate rather than a more conventional analogue path.

You can see the rest of the machine in our original write-up, and we’re reminded that the boards haven’t been cleaned at their owner’s request, to preserve their patina.

Is It A Pet? No, It’s A Teacher’s Pet!

Here at Hackaday we cover the world of retrocomputing, which means that we see all manner of older computers in our everyday work. We might even claim that we’ve seen them all, were it not that every now and then something comes along which surprises us. [Tynemouth Software] has done just that, with an unexpected Commodore. It’s a Commodore 4064, something that was new to us, but which is best described as a Commodore 64 in a PET case. He’s bringing this one back to life.

For those with weak early-Commodore-fu, maybe it’s worth a quick recap. The PET was Commodore’s big hit from the late 1970s, and it took the form of an all-in-one machine with a CRT display built in. They packed a 6502, BASIC, blocky monochrome graphics, and unexpectedly an IEE-488, or GPIB port. Meanwhile the 64 was the company’s smash hit early 1980s home computer in a compact console design, with high-res color graphics for the time on your TV, and a synthesizer chip that’s still legendary in 2026. Combining a 64 mainboard with the super-robust PET case appears to have been part of Commodore’s business and education offerings.

This one appears to have been in the damp, because that board is definitely more than a bit grubby. After a lot of debugging its power and video circuits, including an unexpected sync splitter board to drive the non-composite monitor, he narrows down the problem to a dodgy ROM and some memory errors.

It seems there’s some question in Commodore enthusiast circles as to whether these machines were assembled from surplus PET parts, but he puts that one to bed by pointing out the custom metalwork and the few custom Commodore 64 features on the board. All in all it’s an interesting dive into an unusual 8-bit machine.

We’ve seen [Tynemouth] a few times here, perhaps most notably with their modern take on a ZX80.

AT&T’s Unix PC — We Hardly Knew You

Before Linux, there was Unix. It was great, but it was and has been plagued by problems with licensing and proprietary competition. [Vintage Appartus] recalls, for example, the AT&T Unix PC from the 1980s. It was awesome, but you’ve probably never heard of it. For 1985, it was a nice setup. You got a 10 MHz Motorola 68010, 512K of RAM (but upgradable to 4M), a floppy, a modem, a 720×384 monochrome screen, and a 10 or 20 MB hard drive. You can check out the video explaining the machine and its problems below.

Physically, the computer looked like a high-end Apple ][ with a removable keyboard and a built-in monitor. Expansion was via three slots. Cold start took about three minutes, and then you have a fairly normal Unix setup for the period.

Continue reading “AT&T’s Unix PC — We Hardly Knew You”

Transcribing The Source Of The First DOS For The IBM PC

Doing software archaeology can be a harrowing task, as rarely do you find complete snapshots of particular versions of software. Case in point the development of MS-DOS – also known as IBM PC DOS – from 86-DOS, which recently got a lucky break in the form of printed source listings. These printouts come courtesy of [Tim Paterson], the creator of 86-DOS and of MS-DOS during his time working for Microsoft.

These code listings contain the sources of the 86-DOS 1.00 kernel, multiple development snapshots, and also listings for utilities like CHKDSK. These printed listings additionally contain many handwritten notes, making transcribing it into working source code somewhat of a chore. The results can be found on the GitHub project page, with the original scans available on Archive.org.

Of the ten bundles of continuous feed paper prints all but two have been transcribed so far, though with the various DOS kernels and the Seattle Computer Products (SCP) assembler source already ready for compilation. This includes 86-DOS 1.00, MS-DOS 1.25 and PC-DOS 1.00-dev, requiring the same SCP assembler to create a binary.

In the project page README a number of blog posts are also linked that add even more technical detail. Anyone who wants to pitch in with transcribing and/or testing recovered source code is welcome to do so.

Using A VT-100 Today

You may not know what a ADM-3, a TV910, or a H1420 are, but you probably have at least heard of a VT-100. They are all terminals from around the same time, but the DEC VT-100 is the terminal that practically everything today at least somewhat emulates. Even though a real VT-100 is rare, since it defined what have become ANSI escape sequences, most computers you’ve used in the last few decades speak some variation of the VT-100’s language. [Nikhil] wanted to see if you could use a VT-100 for real work today.

While the VT-100 wasn’t a general-purpose computer, it did have an 8080 inside. It only had about 3K of RAM, which was enough to act as a serial terminal. A USB serial port and a terminal with modern Linux, how hard could it be?

Continue reading “Using A VT-100 Today”

Sega Master System Controllers, Now With USB C

USB wasn’t even a gleam in an engineer’s eye when the Sega Master System hit the market in 1985. Today, we’re up to USB 4 or something, and the USB C connector is becoming a defacto standard for just about everything except desktop computers. [Retrostalgia] is embracing this by mating the control pad from Sega’s first international console with the connector of today.

Naturally, the Sega Master System did not use the Universal Serial Bus to talk to its controllers, so some conversion was in order. That’s achieved with the use of a RP2040 microcontroller, which reads the D-pad and action buttons via its GPIO pins. It then acts as a HID device when plugged into a computer or other USB host, showing up as a simple game controller. This is a particularly easy hack as the Master System controller is so simple, there’s no need to decipher any protocols or anything like that. It’s just about wiring up a few simple buttons. Beyond that, it’s just a matter of hot-gluing the RP2040 into the Master System controller housing, and making some room for the USB C port to sneak out the top. We’d have loved to seen a little extra hackery on this one, perhaps adding some rumble to a controller that was never, ever supposed to have it.

If you want to adapt authentic old controllers to work with modern computers and emulators, this project is a great place to start. It doesn’t get much simpler than the Master System, after all. You can always work your way up to more advanced feats later, like working with the beloved Wavebird. Video after the break.

Continue reading “Sega Master System Controllers, Now With USB C”

Building An IBM PCjr BIOS From Source Using Original Printed Source Code

As unloved as IBM’s PCjr was, with only a one-year production run, it’s hard to complain about the documentation available for it. This includes the x86 assembly listing for the BIOS, which [dbalsom] recently used this print version to create an ASM project that can be built into a byte-identical copy of the PCjr BIOS.

In order to build the BIOS image, a ZIP file has been made available that contains the requisite assembler and linker tools, all of which can be run in DOS (or DOSBox) using the provided build.bat file. This creates an executable file, which can then be converted into a BIN file using the provided exe2bin.py Python script, or of course, manually.

Continue reading “Building An IBM PCjr BIOS From Source Using Original Printed Source Code”