I guess we'll keep this going 'till we get run off
as I mentioned to Les, don't go too much by the old data
I was initially going to title the rad article "A Poor Man's Calorimeter", until JoeC told me I had to define calorimeter.
that 98% business is fine until one of the calcs comes in at 102% and it is apparent that something is not properly calibrated;
but for sure, I can always compare the applied power to the cartridge heater to that heat being transported by the coolant
this is the point I was making; if you calculate the wb Btus what you have is the CPU generated heat LESS the secondary losses
- so if I adjust my power supply to the same wb Btu/Watt level
BINGO, we now know the secondary heat losses (for that board, conditions, etc)
-- nor would it be difficult to generate a curve related to the power level
and then to check that against other mobos
did you see saba's combined burn-in program ?
quote
Although it sounds rather drastic, try perhaps installing a simple web-server program and using Intel's IOMeter program to literally continuously hammer your system. Although it wont tell you specifically whats dead or not working, I find it really does put a huge amount of stress onto the system, which is always what stability tests are all about!
If I personally wish to stress-test my system, I normally install IIS (from your windows 2000 / XP cd's) and share some largish files (DivX movies work well). I set up IOMeter for 16 continuous WWW testing threads.
Starting a full recursive defragmentation within OO Defrag 2000 (
www.oo-software.de, damn good defragger!) atop this is also very good. I also run two concurrent sessions of Quake II in a window, and let them demo cycle. Finally running 3dmark over the top of all this chaos.
unquote
I dunno, not my field
be cool