You can check for hardware acceleration, using "about:support" as a URL.
https://blog.mozilla.org/joe/2010/11/10/how-to-tell-if-youre-using-hardware-acceleration/
The preferences would likely mention it (or about:config would
have it, for preferences they don't want to put in the control
panel style preference thing). The suggestion in this image,
is the GPU is used to render fonts, rather than the CPU drawing
each letter into the window.
http://www.techlivez.com/wp-content/uploads/2011/03/firefox-gpu-enable.jpg
gfx.font_rendering.directwrite.enabled true (default)
As for the last release in Win2K, try this article. It's not
written with the kind of precision I'd like to see, but
it's better than nothing. This suggests up to Firefox 12
would be build with the older SDK suited to the purpose.
Now, whether the Firefox installer is doing an OS check, and
preventing other versions from running, that's a possibility.
(at this instant,
archive.org is down for maintenance...)
https://web.archive.org/web/20120128143126/http://weblogs.mozillazine.org/asa/archives/2012/01/end_of_firefox_win2k.html
And they don't particularly like you downloading releases
from here, but this is just to show that *every* release
can be found here if you need a copy.
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/12.0/win32/en-US/
You can start here if you want to select a particular release.
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases
*******
For stress testing...
1) Use Speedfan if you need to track CPU temperature.
http://www.almico.com/speedfan450.exe
If the CPU temperature is 65C, then come back and
give details. A whole page could be written on the
topic. Knowing your exact CPU model helps write that
page.
2) Use memtest86+ from
www.memtest.org to test the
computer memory. The downloads are half way down the
web page. Files are available to make various boot media.
I have some floppy versions here for example (to test the 8GB
on my Core2). They also have an ISO9660 for boot CD.
One "pass" of memtest86+ is sufficient for a quick test.
It's good for stuck-at faults, less good for transient
faults (because it may not be stressful enough). When you
press "esc" key, the computer reboots. Remove the boot
media before doing so.
3) Prime95 and specifically, the Torture Test option,
provide a good in-your-OS test. Versions are available
for Windows as well as Linux. You can specify how much memory
to test (up to the limits of the particular executable you're
using). On a 32 bit version of program, and with a
2GB OS/2GB UserSpace split, Prime95 should be limited to max 2GB.
Practical limit is 1.8GB or so. You can run multiple copies
(as long as each copy of Prime95 is housed in its own folder).
For Win2K, you want the "win32" version.
http://www.mersenne.org/download/
If it asks "Do you want to joing GIMPS", say "No, just testing"
as your answer. We're using this program to test computer stability,
rather than giving free computer time to the community search
for Mersenne Prime numbers. People who want to make their computers
available, would be testing the stability first, so that only
stable computers are used in the search for that particular flavor
of prime numbers. The numbers in question have 40 million digits,
and the math takes a long long time.
If none of the test threads exit before about four hours of
testing have completed... your system is stable. If the
coloration of a test thread turns "red", it's dead and has
encountered an error. A computer that throws an error in this
test, is no longer a computer - it's a boat anchor, until you
fix it.
Since Win2K desktop only supports 1 core or 2 cores, you won't
have that many test threads to contend with.
When I overclock a computer while testing, a program like Prime95
torture test option, can fail in under ten seconds. So it can
reach a negative conclusion fairly quickly, if the computer is not
stable. What the program does, is a math calculation with a known
answer. The test stops, if the answer that comes back is wrong by
even a tiny amount.
To run Prime95, I would
1) Start Speedfan. Monitor CPU temperature.
Prime95 could make a poorly cooled computer overhead.
2) Start Prime95. Set up the test. Select a small amount
of memory for a first run, like 512MB. The test program
uses various amounts of memory for each FFT run, so some
tests run "in-core", while others waste most of their time
doing memory read/write. In the first case, the CPU gets hot,
and in the second, a lot of memory locations are visited. Both
CPU and memory get tested, as well as the Northbridge with the
memory controller on it (on older computers).
3) If the PC shuts off, try to monitor temperature up to the
shutdown point with Speedfan. See if the shutdown seems related
to an excessive temperature (>65C is hot enough to burn you).
4) If Prime95 turns Red before the four hours is up, you can
still check temperatures to see how hot the CPU is. If all the
test threads stop, the computer will cool off again.
If temperature is going to be a problem, it'll likely show up
around the ten minute mark. If the machine makes it to ten minutes,
then it probably isn't a thermal problem. I use Prime95 because
it's a good way to test the cooling system on the PC.
You can continue to work while Prime95 is running. If you set
the memory setting rather high though, there might not be
a lot of memory left for your other activities.
Paul