DrSwizz

Thanks Actually I am not that much familiar with everest (I have only used the memory/cache benchmark). I'll have to check what "sepcs" is. :-)

Yes, it certainly is one amazing card! When I first started overclocking it (after I had modded it) I started Ati-Tool and used the "find max core"-feature (over whatever it is called). The clock speed started at 50Mhz (I guess that is the default for 2D-mode). Ati-Tool slowly, but surely kept increasing the gpu core speed. When it reached 400MHz I thought "this can't be right, Ati-Tool must be broken". Eventually windows crashed somewhere above 540Mhz.

I tried 7-8 times with more or less the same result. I suppose I could try harder to find a different version of the drivers or I could disable direct draw acceleration entirely. And I have second Rage Pro Turbo card that I also could try. I suppose I more recent version of directx wouldn't hurt either.

Unfortunately increasing the timeout value didn't help much. :-( The explosion seemed to progress a little further, but windows still killed the driver. I guess the upper limit for the timeout must be something lower than 65536. I thinking of giving up on this card and aquamark now.

Hmm... So the big explosion at the end of the benchmark is removed when the card is being clocked lower? When I look at windows/aquamark behaves when the big explosion is being rendered it seems that the driver is doing just fine, but since the driver is so busy with the explosion Windows thinks that the driver has crashed and therefore kills/restarts the driver. Is is possible to somehow increase the timeout before windows kills/restarts the driver? Edit: I did some googling and found this: http://technet.microsoft.com/sv-se/library/cc976062(en-us).aspx I have set the value to 65536 on my rig now, I think that should be enough ;-) I wonder if changing this value is enough, though. Could there be other timers in the kernel that could cause problems?

Yes, it is too bad 3dmark01 requires soo much video memory. :-/ Thank for the link. I am currently using those drivers too. I asked about it because I was figuring that it might be the drivers that was causing the crashes and I have looked in vain for a slightly newer/older versions of the drivers.

Nice! What drivers are you using for that card? I am currently benching a Rage Pro Turbo myself, but so far aquamark has always crashed after 5-6 hours :-(

Now I have apparently contributed 100 points to my nonexisting team. You might want to check so that there isn't a bug that causes my points to become attributed to some random team (not that it really matters to me personally, but it would not be fair to all the other teams).

Have you tried using software to OC the system bus? The PLL on my MVP3 boards has 103MHz setting that I can only access using software. :-) For me CPU-Z caused the mouse to lock up in NT4 (I used a serial mouse). So I tried using a PS/2 mouse instead, but then both the mouse and the keyboard locked up, very annoying. Printscreen did work for me though, but windows paint didn't work very well without a mouse. :-/ @speddy411: Nice score.

100MHz! Not bad at all. :-)

That is odd. I have not had such problems with CPU-Z except with really old hardware such as the first Pentium and K6 CPUs. The only advice I can think of giving you is to check your chipset drivers, they might be the cause of the problem. Also ask Antinomy for help, he seems to know allot about the inner workings of CPU-Z and hardware in general. :-) Thanks!

Use a K6-2 CPU: CPU-Z is able to get the bus speed and multiplier readings from those. :-)

Thanks!

CPU-Z probably relies on an EEPROM to be available on the DIMMs. I had a bit of problem with this myself: I found a really old DIMM that lacked the eeprom. The only way I found to indicate what kind of memory it was (EDO or SDRAM) was that the stick didn't work with SDRAM-only boards.

This is the only submission I have made with EDO so far: http://valid.canardpc.com/show_oc.php?id=1277286 as you can see CPU-Z doesn't recognize the RAM (or much else). It might work better with newer boards though as that particular board & CPU is ancient.

It is good to see a 386 alive and kicking! I can highly recommend a program called "syschk": I have an old copy of it on floppy disk that I have been using from time to time. I did a google search and to my surprise there actually was a homepage for that application: http://www.syschk.com/ It provides plenty of other system information too and seems to behave well running under windows. Stange: I only posted my reply one time, but yet it ended up being posted twice. Something must be wonky with the hwbot server.

It is good to see a 386 alive and kicking! I can highly recommend a program called "syschk": I have an old copy of it on floppy disk that I have been using from time to time. I did a google search and to my surprise there actually was a homepage for that application: http://www.syschk.com/ It provides plenty of other system information too and seems to behave well running under windows.

For some unknown reason I now got the "contribute 50 points to your team" achievement without ever having been member of a team. Also when I look at the page associated with this achievement it is all blank: http://hwbot.org/community/achievement/1061_contributing_to_the_team

Yes, in Linux the stock frequency (60MHz) as well as the current (overclocked: 66Mhz) frequency was shown, I was a little surprised when I first saw that.And since you seemed to be looking for input on how CPU-Z behaved on older hardware I figured I mention it. You mean that Linux performs some kind of trick to figure out that OCed my CPU? ;-) One more thing: Yesterday evening I uploaded that text-output you wanted: I only edited my last message on the competion-thread so I didn't show up as new message, so you might have missed it. http://hwbot.org/forum/showpost.php?p=63451&postcount=51

CPU-Z recognition of the original Pentium CPU (the 800nm, 5V CPU) needs to be improved; It shows up as a 500nm CPU and there is no indication of which frequency the CPU was made for whereas /proc/cpuinfo in Linux shows the correct value.

Sorry; I guess didn't read your request carefully enough. I'll upload that text-output soon. Edit: I have uploaded the textfiles you asked for here: http://rapidshare.com/files/406399770/mvp3g2_memsettings.tar.gz :-)

I have uploaded two CPU-Z files here with ~100MHz bus frequency and different divider/ratio for the memory here: http://rapidshare.com/files/406339016/mvp3_memsettings.tar.gz They are from version 1.54 though, does that matter?

If you still have need for CPU-Z output from an MVP3-board I am doing some benchmarking on such board right now. :-)

@Turrican: I am impressed that you had the patience to wait for the benchmark to finnish. 50 days is a long time! Good work!