just because a program uses all the cpu doesn't mean that it is a good stress test. the code segment "while(1)" will use the cpu all the way, but it is nowhere as good as seti or rc5. and those should be tested in conjunction with other programs as well. rc5 is mainly integer, and seti does fourier transforms which is fpu intensive, so each will stress a different part of the cpu. get these two puppies going, maybe defrag a slave drive with garbage on it, play a fps game in a window or run a quake 3 loop, and do normal browsing and stuff. sometimes i scan 100 meg images in photoshop, run a filter, defrag, run q3a in a window with max nightmare bots, run rc5, seti, and play 5 or so streaming divx movies and mp3's. the idea is to stress as many of your i/o subsystems as possible, ie graphics, disk, etc...