Everything posted by Antinomy
-
Frequency detection bug with old Socket 5 CPUs
Just my $.02 - language barrier can be a bitch for some of the members. Sometimes it makes things easier to explain and understand. It's up to forum mods to clean it up though. If any of our exUSSR guys want to clear things out in Russian, feel free to PM me or create a topic on Russian forums. I'm not about ranting but can give you the technical details you think this thread is lack of.
-
Frequency detection bug with old Socket 5 CPUs
I'd like to remind you what HWBot was initially about - it's a hardware performance database. Think about it, reread it and think again. It's only three words, you can handle it, I'm sure. Points, rankings, leagues, teams - it's all secondary. It's simply a gamification made for fun. Fun is another thing most forget in their long discussions. So the main purpose is to keep the DB as accurate as possible, not about your points. @max1024it's NOT about crystal oscillator deviation you are talking about AT ALL. You simply don't understand the bug then. Xtal deviation affects frequency and will be seen in every realtime frequency utility. The topic is about CPU-Z bug only. If you didn't understand my two little quotes, feel free to ask for details. It's not rocket science. @Gumanoid, looks like you don't get the situation. The results were blocked not because everyone is a cheater but because we can't be sure they are real. How dare you mention Carl and talk about rules applied to old results. I'll give all of you a nice example - a long time ago there was a category called Celeron 350MHz (Covington). You'll never find such a CPU because it doesn't exist. I've found out that CPU-Z couldn't tell a Pentium 2 Deschutes with L2 cache disabled in BIOS from a Celeron Covington (they share the same core) which doesn't have cache at all. How do you think, how many people commented that their scores were bugged, how many reported to CPU-Z? Don't try to "they might not know" - you can't disable L2 cache in BIOS by accident. And Pentium cartridge and PCB looks whole different way from Celeron. So Carl deleted the whole category along with results. And I've reported to CPU-Z and got this issue fixed. And nobody got banned. Some of them were teammates of those who participated in this topic. Would you really continue with this "rules don't apply backwards" and let fake category with false results stay? Important to not - results weren't painted, neither they were fake in general way. But they were erroneous in terms of hardware performance database. That's how it was done and how Turrican reacted in such a case. Back to this issue - it should be sorted out. Maybe we could make exceptions for some cases like non-overclockable boards if a result seems normal and doesn't cross the bug mechanism. Not for me to decide though, it's up to results mods.
- alexmaj467 - Athlon 64 3000+ (Venice, s939) @ 2969MHz - 7421 marks PCMark04
-
PLEASE ADD MOTHERBOARD THREAD:
added: http://hwbot.org/hardware/motherboard/x399_sli_plus_ms_7b09/
-
Please add this motherboards to database =)
http://hwbot.org/hardware/motherboard/z370_aorus_ultra_gaming_20/
- wytiwx - Pentium 4 2.4Ghz (Northwood, 133 FSB) @ 4792.4MHz - 29sec 62ms SuperPi - 1M
- macsbeach98 - GeForce GTX 260 216SP @ 1114/1264MHz - 53971 marks 3DMark05
- macsbeach98 - GeForce GTX 260 216SP @ 1114/1264MHz - 95565 marks 3DMark03
- wytiwx - Pentium 4 2.4Ghz (Northwood, 200 FSB) @ 4992.2MHz - 4992.18 mhz CPU Frequency
- kotori - EP-7KXA @ 138.2MHz - 138.2 MHz Reference Frequency
-
BSEL and VID mods for old rusty Socket P CPUs (Intel X9100)
So you're upgrading logic analyzers now? Nice to know. The bigger problem here is not the FSB (either the board supports 266 and it'll use it or if it doesn't, it should boot at 200. Mod only needed if it'll boot lower than 200 FSB), but the Penryn core. Your T7500 is Merom so an upgrade to X9100 requires Penryn support from MoBo. It might boot if unsupported but sometimes it won't. DFI with Award didn't boot without supported BIOS version, Asus with AMI BIOS did work.
- GeorgeStorm - Core 2 Duo E6320 @ 4448.8MHz - 4448.84 mhz CPU Frequency
-
BSEL and VID mods for old rusty Socket P CPUs (Intel X9100)
Hello, old friend! Long time no see. I've got an article covering BSEL mods here: https://overclockers.ru/blog/antinomy/show/10241/Razgon_Intel_Xeon_Pentium_M_Celeron_M_Core_Mobile But there's only Socket M which is a bit different. Though gives a remind how it works in general. As for your case, I doubt it will work. GM965 had official support up to 200MHz. The problem here is the clockgen. Most likely it has straps only up to 200MHz but might be able to clock higher with software. I really doubt the clockgen has a 266 strap support but you could try to find a datasheet and check it out.
-
Please add this motherboards to database =)
Added: http://hwbot.org/hardware/motherboard/j1800nh3/
-
Please add this motherboards to database =)
Added: http://hwbot.org/hardware/motherboard/m7sxd/
-
Please Add GPU
Added: http://hwbot.org/hardware/videocard/adreno_308/
-
Please add this motherboards to database =)
added: http://hwbot.org/hardware/motherboard/ferrari5/
- The official Old School is Best School Season 4 Round 2 thread
- Antinomy - Celeron 533MHz (Mendocino, s370) @ 666MHz - 666 mhz CPU Frequency
- The official Old School is Best School Season 4 Round 2 thread
-
Looking for a team
How much did they pay you?
- GRIFF - Celeron 533MHz (Mendocino, s370) @ 940MHz - 940 mhz CPU Frequency
-
Submit score page - bug report and feature request
Yesterday I've got caught a glitch from the submit page. It's quite an old one but annoying nevertheless. I think we should work hard pushing the hardware, not fighting with submission engine. Bug report: 1) Images selected for attachment are removed if you get a error message, both "verification screenshot" field and "pictures of your system" (except ones being prepopulated from previous submissions) . Adding the fact you have to scroll way down to re-check this, it's a nasty one. 2) internal exception errors are seen, "Property score threw exception; nested exception is java.lang.NullPointerException". And there are two of them, above and below the input field. Feature requests: 1) On CPU-Z result page we have two "CPU frequency" input fields. Can we grey-out the second one and dupe from the other as long as one of them gets filled? It'll be the best solution. Or at least make one input field. It's kinda counter-productive having to input the same thing twice. 2) We have a motherboard database, why don't we fill up motherboard vendor and chipset if you select a certain model? If it's not in the database, O.K. let them fill all three fields. But if it's in, you can prepopulate the other two from model name. 3) Last but not least - could we nail the "I've read the rules and agree to them till the next time they change". I understand why this thing got light when rules have changed. But this doesn't happen often. We could nail it once per benchmark and reset when benchmark rules or general rules have been change. It is annoying. TIA
- The official Old School is Best School Season 4 Round 2 thread
- The official Old School is Best School Season 4 Round 2 thread