Originally posted by: FlyingPenguin
Well as an old fart who grew up with this...
The Turbo switch was used to underclock the CPU so that older apps that were CPU timing depended would run properly.
Older games in particular would have this problem, but even old business apps might use (for example) a simple loop counter to create a delay for scrolling text instead of using a clock timer. Use that app on a newer faster computer and the text may scroll to fast to read.
Once computers had more memory, clock based timing loops became the norm and you never see this problem anymore. You rarely saw a turbo switch after the x386 era.
You rarely saw a turbo switch after the x386 era.
Case manufacturers should but it back, and make it so that when you press it, your FSB goes up 5% or something
It's true that enaged = normal speed, dis = underclocked, but the reason why is as FlyingPenguin said, program timing, not for quiet or cooling.Originally posted by: YOyoYOhowsDAjello
Originally posted by: FlyingPenguin
Well as an old fart who grew up with this...
The Turbo switch was used to underclock the CPU so that older apps that were CPU timing depended would run properly.
Older games in particular would have this problem, but even old business apps might use (for example) a simple loop counter to create a delay for scrolling text instead of using a clock timer. Use that app on a newer faster computer and the text may scroll to fast to read.
Once computers had more memory, clock based timing loops became the norm and you never see this problem anymore. You rarely saw a turbo switch after the x386 era.
My turbo buttom made things run faster though...
mdchesne's explanation seems to match what was happening with my computer back then.
Originally posted by: Maluno
What years was this in? I don't remember a thing, but most likely cause I am too young...![]()