Why an “upgrade” could slow a PC down
Early PC games often measured time by how quickly the processor completed a task. A game might advance an object or repeat a sound routine a set number of times, assuming the computer would take roughly the same time to finish. When newer PCs ran those routines faster, the game could race ahead: characters moved too quickly, menus flashed past, or sound played at the wrong pace.
The Turbo button addressed that mismatch. On many machines, it switched between a faster processor setting and a slower one, helping older software run closer to the speed its designers expected. Depending on the computer, the change could involve lowering the processor’s clock rate—the pace of its internal operations—or adding delays to its work.
What “Turbo” meant on the case
The label usually described the computer’s faster mode, not what happened when the button was pressed. With Turbo enabled, the PC ran at its higher speed; turning it off selected the slower, more compatible setting. That made the button’s behavior seem backward if you assumed pressing it should always make the machine faster.
The workaround exposed a limitation in how early software kept time: it often treated processor speed as a dependable clock. Later software could use dedicated timing hardware or other methods to measure elapsed time, so it did not have to rely as heavily on how many operations the CPU could complete. But for an old game built around a fixed-speed machine, a physical switch could be the difference between a playable challenge and a blur.
