To view parent comment, click here.
To read all comments associated with this story, please click here.
Yeah, and I played Wolfenstein on my 286. Certainly it was rather highly optimized code, but it was also doing a hell of a lot less, with much lower visual detail. You simply couldn't play modern games, at an acceptable framerate on my old P166.
As for sound, there are certainly modern bitrates and codecs that would tax the P166, if not pegging the CPU, making it much more likely to skip when doing something else. And just forget about any modern video codec.
My point is that there are tasks that actually utilize much of the power available in modern systems - those tasks don't happen to involve editing office documents.
http://en.wikipedia.org/wiki/MDK_(video_game)
at a decent framerate, while doing the 3d rendering entirely in software.
Agreed. I also ran Battlzone (http://en.wikipedia.org/wiki/Battlezone_%28computer_game%29) on AMD-K5 with 100MHz frequency and 16Mb ram - it worked very fine even in software rendering mode (my video card did not support 3D acceleration at that time).
I think a P166 would be plenty good enough for Quake. (But I barely ever bothered running it, seemed fine though.) And I guess .MP3 wasn't the best example (runs easily), but you may (?) have a point. Just saying, you don't need all these newer computers with tons of RAM just for multimedia and games. Heck, look at ye olde XBox 1 (PIII 733 Mhz) or even the (old but cool) Atari Lynx. Quite good without all the extra fluff! :-)




Member since:
2005-12-31
" For example, that P166 couldn't do video encoding/decoding for crap. It could barely handle MP3s, and forget about 3D games."
I beg to differ.
My P166 MMX laptop uses about 5-10% CPU playing back mp3s with Mplayer.
It can also run MDK:
http://en.wikipedia.org/wiki/MDK_(video_game)
at a decent framerate, while doing the 3d rendering entirely in software.
Software is not highly optimised nowadays because programmers no longer need to do so. This is a good thing as it makes code faster to write and more maintainable. It also encourages reusable code rather than tightly written special purpose code.
MULTICS is an example of this. The later *nix clones were simpler and more reliable as they no longer needed all the optimisation and memory sharing tricks required to run a multiuser OS in only 32kB of ram.