The Commodore 128 is really two computers sharing a keyboard, and the proof is that it has two completely separate video systems. For its 40-column face it kept the C64’s VIC-II, sprites and all. For its serious face it carried the 8563 Video Display Controller — the VDC — a chip with its own private memory, its own registers reachable only through a two-register keyhole at $D600 and $D601, and a specification sheet that promised crisp 80-column text in sixteen colours at 640×200. Business users got the best text screen Commodore ever made. And then, for roughly twenty-five years, almost nobody asked the chip what else it could do. The answer, when the demo scene finally asked, was: far, far more than Commodore ever told anyone.
Understand first why the VDC feels so alien to program. It was not designed for the C128 at all — it began life in the CBM 900 workstation programme, a descendant-in-spirit of the 6845 cathode-ray tube controllers that powered a generation of business terminals. It has no sprites, no raster tricks in the VIC sense, no direct memory mapping: the CPU whispers to it through an address register and a data register, setting up one of its dozens of internal registers and polling a status bit to learn when the chip is ready for more. Its display RAM — 16K in the original machines, 64K in the C128DCR and in user upgrades — is a separate country that the main processor visits by post. Everything about it optimises for one task: perfect, flicker-free text, 80 columns wide, on an RGB monitor.
The text chip with a bitmap soul
Buried in the register set, though, the VDC is a bitmap graphics chip. It can abandon character cells entirely and paint pixel-addressable screens; with interlace it can double its vertical resolution; with the right register coaxing it can produce colour cells far finer than its text grid suggests. Commodore’s own software barely touched any of this. BASIC 7.0, for all its hundreds of commands, offered no VDC graphics statements at all — drawing on the 80-column screen required machine code or third-party extensions such as BASIC 8. The commercial 128 library is consequently a library of text: word processors, databases, terminals, Infocom’s 80-column editions. The games mostly stayed on the VIC side of the house. An entire graphics processor sat in millions of machines doing secretarial work.
There were structural reasons. In 16K form the VDC’s memory was tight for large bitmaps; the indirect register access made pixel-plotting slow — every byte written involves handshakes with a chip that answers in its own time; and the audience for 80-column graphics needed an RGB monitor many owners never bought. Publishers looked at the installed base of RGB-equipped 128s, looked at the programming cost, and walked away. The chip’s graphics career would have to wait for people who programmed for love.
What the wizards found
The awakening came in stages. In 2006, Crest and Oxyron’s Risen from Oblivion VDC treated the chip as a demo platform, even building a “system analysis” screen that measured real VDC timing against the computer’s CIA timers. In 2012, Tokra and Mike of Akronyme Analogiker released VDC Mode Mania, a BASIC-driven slideshow that paraded the chip’s rare modes one by one — interlaced and non-interlaced, colour and monochrome, at resolutions that climb past anything the VIC-II can dream of; extended over the following decade, it reached a 960×540 monochrome mode in 2023. In 2021 the same circle taught the VDC to decode ZX Spectrum screen dumps, in VDC SpectruMania and Crest’s Colour Spectrum — the business chip wearing its rival’s pictures. And the modern vdcmaniac project rebuilt the whole mode family in compiled C, adding smooth bitmap panning larger than the screen itself, and documenting the register-level detective work — including a bug that turned out to be its own register-write ordering, found only after a nine-value diagnostic sweep against real 128D hardware.
The VDC spent the 1980s typing letters and the 2010s painting the Great Wave at 640×400. The chip did not change. The questions did.
There is a poignancy in the numbers. The modes the scene unlocked — FLI-style colour cells, interlaced 640×480 and beyond, monochrome at 800×600 — are precisely the capabilities that might, in 1986, have made the C128 a different proposition: the 640×200 colour graphics machine that reviewers kept wishing Commodore had built, present all along, undocumented and uninvited. Whether commercial software could have lived with the VDC’s slow CPU interface is a fair question; arcade games, probably not. But the paint programs, the adventure games with illustrated screens, the desktop publishing with true high-resolution preview — those were possible, and the installed base never knew.
The memory question: 16K or 64K
One specification divides the VDC’s career in two. The original flat C128 carries 16KB of dedicated video RAM — ample for text screens with attributes, tight for the big bitmap modes — while the C128DCR fits 64KB as standard, and the chip’s registers were designed with the larger space in mind. Owners upgraded flat machines for decades (the soldering is fiddly, the reward immediate), because the difference is the difference between the VDC as a terminal and the VDC as a canvas: the interlaced high-resolution modes, the double-buffered colour pictures and the smooth oversized panning bitmaps of the modern demonstrations assume the full 64K. It is a very Commodore situation — the flagship capability present in the design, costed out of the base model, restored by the cost-reduced revision — and the demo scene’s output quietly standardised on the configuration Commodore treated as optional. When the buying guide in this collection tells you to ask a seller which video RAM is fitted, this is why.
The same memory explains the chip’s odd reputation among programmers of the era. With 16K and a word processor to feed, the VDC looked like exactly what it was marketed as. The bitmap modes existed in the data sheets, but exploring them meant owning the rarer configuration and writing through the register keyhole for a screen most customers didn’t have. The wilderness was fenced by economics, not by the silicon.
Two chips, one machine, no referee
It is worth pausing on how strange the VDC’s coexistence with the VIC-II really is, because it explains both the neglect and the eventual fascination. The two chips share nothing: separate memory, separate outputs (the VIC feeds televisions and composite monitors, the VDC feeds the RGBI port), separate philosophies — one a games artist with sprites in its blood, the other a terminal professional with a bitmap hobby it kept quiet. A 128 program must pick a face, or run the considerable engineering gauntlet of using both at once. Commercial software picked by market: games took the VIC and 64 mode took care of itself; serious software took the VDC and treated it as a typewriter screen with perfect manners. Nobody’s job description said “explore the business chip’s art modes on the off chance”. The demo scene, answerable to no market, eventually asked the question the industry couldn’t afford to — and the chip, patient for twenty-five years, answered in 640×400.
The verdict of history
Today the VDC is the C128’s most interesting chip precisely because its story inverts the usual retro narrative. The VIC-II was exploited to exhaustion within its commercial life; the VDC’s exploitation began a quarter-century after its commercial death, at the hands of hobbyists with cross-compilers, register documentation and patience. When the demo scene feature in this collection calls the VDC work “wizardry”, it is not flattery — it is a technical judgement. The 80 columns nobody used turned out to be the deepest rabbit hole Commodore ever shipped.