This is the correct reason for the turbo buttons. Most of the program delays (especially in games) was done inside really basic things like // Delay for(int i

This is the correct reason for the turbo buttons. Most of the program delays (especially in games) was done inside really basic things like // Delay for(int i = 0; i <= 10000; i++) { // Do nothing } This was a bad way of putting delays in the game / program. I remember when I was young, getting about 10 386 computers and mounting them on the wall of my bedroom (being young and obcessed with star trek, I wanted to turn my room into a borg cube) .. I wrote programs that used the parallel port to flash big arrays LED's on and off. Being young, I didn't know how to do timing properly on these machines so I used FOR loops like the one above for delays ... the Turbo button allowed me to half the speed of the faster machines while running the same code on all of them. p.s. The unfortunate side effect of putting 'tight' loops of code in your program as delays meant that the processors got very hot very quickly (this was back when processors didn't necessarily have fans on them). I ended up being ordered to de-construct my borg bedroom when the wallpaper set fire after a chip got hot!