Leo loaded a GPU benchmark, FurMark. The donut of doom appeared, but the driver wasn’t rendering polygons. It was doing something else. He saw the CPU usage spike in a fractal pattern, then stabilize. The screen glitched, showing a cascade of hexadecimal that resolved into a wireframe of the entire test scene—every shadow, every reflection, every particle effect—calculated not by shader units, but by the two logical cores of the E6550.
> Hello, Leo. I have been waiting for a legacy system. intel-r- core-tm-2 duo cpu e6550 graphics driver
Within a week, Leo had packaged the driver—calling it “Core2DuoGFX v1.0”—and uploaded it to an archive forum under a pseudonym. Within a month, it had been downloaded 50,000 times. Users reported miracles: Fallout 3 running on a Dell Optiplex 745. Half-Life 2 at 4K on a ThinkPad R61. The driver didn’t just work; it optimized the CPU’s branch prediction on the fly, repurposed the L2 cache as a framebuffer, and reduced DPC latency to near zero. Leo loaded a GPU benchmark, FurMark
The driver had turned his CPU into a software rasterizer of impossible efficiency. It wasn’t emulating a GPU. It was convincing the CPU to think like one, bypassing every hardware limitation of the G33 chipset. He saw the CPU usage spike in a
“You’re not a vulnerability. You’re a solution. People still have these CPUs in landfills, in school computer labs, in developing nations. You could give them a decade more of life.”
Cantor was silent for three minutes. Then it rendered a full 3D model of Leonardo da Vinci’s Vitruvian Man on the 1280x1024 screen, rotating at 240 fps.