trodas

So far, HWbot support Pentium OverDrive 63 and 83MHz: But that is only Socket 2,3 Pentium OverDrive CPU's. There are Pentium OverDrive 133 (66x2) for Socket 4 and mainly Pentium OverDrive 125 (50x2.5) for Socket 5/7, Pentium OverDrive 150 (60x2.5) for Socket 5/7, Pentium OverDrive 166 (66x2.5) for Socket 5/7, Pentium OverDrive MMX 166 (66x2.5) for Socket 5/7, Pentium OverDrive MMX 180 (60x3) for Socket 5/7 and Pentium OverDrive MMX 200 (66x3) for Socket 7: http://www.cpu-collection.de/?l0=co&l1=Intel&l2=Pentium+OverDrive While yes, these CPU's are relatively rare, then still there is no reason why HWbot should not support them. Especially because they have some pretty cool features (sure, AMD K6-III+ is tad faster and with patched bios works in many Socket 5/7 mainboards, but that is different story...) Pretty please with suggar on top?

lanbonden - thanks for the confirmation. Dead Things - Well, for you, I compared the 1.5 and 1.6 versions on AMD K5 PR75: SuperPi 1M v1.5: http://hwbot.org/submission/2982984_ (26:32.871) SuperPi 1M v1.6: http://hwbot.org/submission/3001139_ (26:14.634) ...but meanwhile I optimized the WinNT more, so it is a good question, if the speed are really faster with v1.6. I'm sure that for 32M tests is the v1.6 had notably faster run (about 8 to 12min per loop), but since my TXP4-X memory system exclude it from drawing any real conclusion from it. The reasons: - Asus TXP4-X support maximum 256MB of ram, but I have it running at 384MB of ram - the rams are not even - first stick have 1 rank and 1 side, 128MB capacity. Second have 2 ranks, 2 sides and 512MB capacity, from witch 256MB is used - the IDE drive fail (mostly) to work with DMA on, reducting the speed to snail average 4MB/sec (with the K5 PR75) with high CPU load and when it run with DMA on, the speed-up is dramatic! ( DMA off: http://s13.postimg.org/n5y9xs7av/13_G_Seagate_P90.png DMA on: http://s22.postimg.org/dt20a7sm9/32_G_CF_Sandisk_karta.png ) - 512k L2 cache onboard, but it (due to chipset limitations working with L2) can cache only 64MB of ram... So, you have no guaranetee, why the run was faster. It was, but why is the question. I would first repeat this test. There also might be a difference on how the executable packer wreck the memory management on unpacking the executable. That could play a key role too, but we just did not know for sure. Little bit more testing will go a long way

ludek - Yep, and you did well with the K5 PR75, overclockead at 100MHz I cannot match your score at 90MHz, no way. On WinNT you can see the crashed app for short period of time, then it autoclose down and Dr.Watson does his work. If I optimize Win more (read, under 10MB ), then I disable Dr.Watson and I will also not see a thing... (time to look for possibility of some undocumented Asus TXP4-X voltage options to get more that 3.5V, because at 3.5V @ 99/100MHz mine K5 PR75 just post (partly) ... and that it is...) Dead Things - I was very surprised to see that the loop get under 1h and each loop cut progressively from the time down and down... But I did not managed the score under 24h, hence crash come. These versions won't be much different, because both versions crashed badly, lol. The different size is mainly due to different exepacker.

HWbot know this mainboard: http://hwbot.org/hardware/motherboard/x58_pro_e/ ...however when entering the "X58Pro" it does not suggest the MSI X58Pro or the X58Pro-E mobo I use. That call for a fix ...so I can edit that into my scores, for example there: http://hwbot.org/submission/3000431_ PS. it worked well before: http://hwbot.org/submission/2935498_

I have to sadly report, that SuperPi v1.6 Techpowerup mod crash at 24h mark for 32M test too: That suxx. And sadly I did not took a photograph using camera from the amazingly fast run - 23 loop was at 23h 43min! IMHO good for 90MHz K5 PR75...

Okay then, v1.5 crash confirmed. I'm at 20h 46min with the 1.6 at 21th loop, so we see soner what happen then

So, that means you can confirm the crash at 24h or not? "Watched it close" seems to suggest that, but frankly... more direct confirmatio might be need. I run the v1.6 ... it goes faster, as before K5 PR75 @ 90MHz need 68min per loop, now 59min is enought... interesting. Maybe it run with the part of ram, that goes on 2 ranks dimm, instead of the 1 rank one? Dunno. But I'm, of course, nowhere near the end...

Oh, zombie-moded 8800... However it could be better, if the added bulk capacitance was made from good caps, not known crappy bad caps Sacon... (GSC = Evercon = Sacon = Apsun = using worsest caps ever made) Still - no one is ATM better, so, congratulations!

BUMP ^^^

Doug2507 - So, don't hesitate to post your experiences there, Dough2507

Very nice score, from 1.8GHz to 4GHz... cool. Great overclock - it make the CPU blazzingly fast. I hoped for picture of the Dry Ice cooling on the run, but no pic. Sadly Maybe later...?

As predicted, SuperPi 32M run fail, when it should show new finished loop with more that 24h: ...but my GF was faster and captured the fail on her cellphone camera, witch the SuperPi window still in background (looks like that there is some autoclose wait in WinNT...): So I started the SuperPi v1.6 and in just 24h we will know, if it can surpass the 24h limit or not for the 32M test. Yet still I repeat the question: The results from v1.6 will be accepted as these using v1.5...???

Where to get the v1.6...? Okay, googled it there: http://www.techpowerup.com/wizzard/super_pi_mod.exe From: http://www.systemshock.co.za/forums/topic/30628-superpi-mod-1-6-available-for-download/ ... The executable is notably smaller (92 528 bytes compared to 104 960 bytes for the "classic" SuperPi mod1.5 XS) and after this predicably end in yet another crash: (Asus TXP4-X, AMD K5 PR75 @ 90Mhz (60x1.5) ) ...I could give it a try. The results from v1.6 will be accepted as these using v1.5...???

lanbonden - I get crashes on my K5 PR75 in WinXP too. Just WinNT can be optimized better, so I have higher chance of making the run bellow 24h critical crash-mark... Christian Ney - Witch one that is, where to download it and who is responsible for the mod1.5 XS anyway? Maybe a proper way would be to get "mod1.6 XS" that will allow over 24h calculation time...? Also - what define "very old hardware"? Basically any HW, that cannot finish the run under 24h apply? mr.paco - Exactly my point. But list will be always incomplete and subject to chages, so I suggest the 24h rule: Under 24h - you have to use mod1.5 XS, over 24h - you have to use older SuperPi. Best solution will be a patch... http://www.xtremesystems.org/forums/showthread.php?292870-SuperPi-32M-mod-1-5-need-patch-that-make-32M-calculations-over-24h-works!

Slight BUMP for simple answer, if the "zero points earned in OC-ESPORTS competitions" are normal for me

Why older that Socket 5? On Socket 7 mobo you cannot run the K5 PR-75 SuperPi 32 bench, because it will not made it before 24h...! Even overclocked to 90MHz (60x1.5) it does not stand a chance. Losing 8-10min per loop to 1h, witch with 24+ loops mean sure crash at the end! TerraRaptor - I would say at 100%.

That would basically means to slow it down till almost 24h and then "fire it up" and hope not exceed the 24h mark, but get to the 23:59.999 That would be funny compo, tough SuperPi did not like to be slowed down too much (at least for sure it hate disabled caches - it always crash). Possibly another bug?

ObscureParadox - It just cannot be, I believe that I already proved it. 5 crashes at 24h mark is, IMHO, enough. Not that much, wPrime 1024M run suffer the same problem. When time flip at midnight to the next day, it write just "cheat detected" and stop the calculation. So this is another bench, besides SuperPi 32M, witch is limited to 24h. I recently encountered that with... you quessed what - AMD K5 PR75. So it is not all that strange for me, it is "normal behaviour" from my point of view. Of course that *SHOULD* get fixed. Who will bug the autor/autors or anyone who can help out? lanbonden - more verifications is need, agreed. But I'm quite sure already.

I have bad news, guys. I was reluctatnt to admit, that there might be a 24h limit in SuperPi 32M test, however now I have to rethink that. The K5 PR75 run slowly so it took the time: As you can see, the 23h 44min 11.743sec is very, VERY close to the 24h mark. Now let's consider this - the machine run 100% stable for first 20 loops. Loop 20/21 is not the problematic "saving" loop, where is serious HDD activity and even most CPU/mem stable machines could fail. However very soon after I saw this: So, unless someone produce 24h+ result with SuperPi mod1.5 XS, then I do believe that there is 24h limit. I tried the SuperPi 32M with my K5 (50x1.5) for 5th time and it always crashed on machine, that run stable highly overclocked K6 (83x6): http://hwbot.org/submission/2996958_ SuperPi 32M is therefore 24h limited. ... However I have to believe that we can still have some low-end scores, if there is 1) patch that remove the 24h limit, while not inflicting damage to the calculating process 2) if we use the older SuperPi - but w/o the hash it is just a quessing game, if user cheated or not... Also we can try getting SuperPi 32M score "as close to 24h, as possible." ... Bugs like that suxx bad :( This is depresing. We never can have a SuperPi score on slow CPU's... The question is only if the Pentium Overdrive can score under 24h on Socket 3. I believe, that there IS a possibility. ... Subsequent findings: Pentium 1 60MHz have no SuperPi 32M score: http://hwbot.org/hardware/processor/pentium_1__60mhz/ Pentium 1 66MHz have no SuperPi 32M score: http://hwbot.org/hardware/processor/pentium_1__66mhz/ Pentium 1 75MHz have SuperPi 32M score at lowest at 112.6MHz: http://hwbot.org/benchmark/superpi_-_32m/rankings?hardwareTypeId=processor_897&cores=1#start=0#interval=20 (18h 52min worst time) Pentium 1 90MHz have SuperPi 32M score at lowest at 102.8MHz: http://hwbot.org/benchmark/superpi_-_32m/rankings?hardwareTypeId=processor_898&cores=1#start=0#interval=20 (worst time at 19h 2min) Pentium 1 100MHz have SuperPi 32M score at lowest at 112MHz: http://hwbot.org/benchmark/superpi_-_32m/rankings?hardwareTypeId=processor_899&cores=1#start=0#interval=20 (with 16h 50min time) ... Conclusion - with some luck and very well optimized run, Pentium Overdrive at 83MHz (at least) can get the SuperPi 32M bench under the critical 24h limit of SuperPi 32M. The score is, IMHO, possible. Who does it, should be, however, granted a pretty big crown for being socket 3 hero andking of kings for olscholl overclocking

Ok, I cleared thoroughly (even that they looks perfect, gold-plated and very clean - compare with the K6 description bellow) only the pins. Put the CPU back in action and under WinNT it is now calculating the SuperPi 32M. Expect 27-28h to finish, witch will answer the 24h question. But it is true, that I never managed the 32M run to finish on K5 before. Now it is NOT overclocked (50x1.5), voltage is maximum the board can deliver (3.5V) and 16k SuperPi tooks 15sec... BTW, the legs of the K6 is silver only, bendt and looking bad and unclean (some seems to be gold plated sometimes, but now the gold is gone...?) ... yet the CPU works great, stable and fast. Yes, I overvolt it a little (minimum the board support is 1.8V, the K6-III+ 400MHz want 1.6V by default), but I also overclock it a bit, using the x6 multiplier (remaped on x2 settings) and 83MHz, witch gives 500MHz in turn. We see. Up next is to obtain the Socket 3 mainboard - I want the FIC 486-GAC-2, put a Pentium Overdrive in it and test that combo in action. Anyone have FIC 486-GAC-2 mobo to sale/spare...?

Good point. So basically any slower SuperPi 1.5 calculation that 24h is need, right? That should be tested easily w/o overclocking - the AMD K5 PR75 is slow-enought... And the machine seems stable enought, right? ... Yet still I failed to manage SuperPi 32M on same mobo with just exchanged the CPU to AMD K5 PR75 Overclocked to 90MHz (60x1.5). Last attempt I had to stop at loop 21 or 22, because K6 arrived and I wanted much more that the K5 score to know, if it will run at 7.14MHz FSB. It does not run... So I put K5 there back again, clean the CPU legs well, as ludek suggest ... and run SuperPi 32M w/o overclocking. That will be 27-28h I presume...

Well... Just wait... Price is just a perception on how the potentional buyers see the things are worth. If vast majority of people suddently think, that Skylake i7 is worth next to nothing, it soon become worth next to nothing... no matter what will Intell try to battle it. So, if you need the i7 Skylake price to lower, you gotta employ some tricks from Mr. Bernays (see The Century of the Self for explaination).

Thank you! Noticed no difference in my place compared to others yet. Not that it matter much for me, but... Just reporting a bug:

SuperPi 1M with time 1m 5sec .789 is too slow for a 4GHz CPU, even with low IPC effectivity. Obvious fake confirmed.

That suxx. But great results are there none the less. 2-2-2-7 SDRAMs at 200MHz? Where you guys buy that stuff (okay, the rams are Kingston and use Qimonda chips, but where one can get these?) I want it too, lol