_mat_

Great stuff! I only had a late part of an evening again, but it didn't take very long to remove the obfuscation of XTU to have about 90% of the code readable and ready for debugging. I also removed the anti tampering check with switching a single IL instruction. What does that mean exactly? Well, I basically have my own custom XTU version and can make my own scores. That said, the new version is better when it comes to Anti Tampering. Just not by a lot. The problem here is C#. Like Java it's the wrong tool for the job. @0.0 I guess your wrapper is for the XTU1 score only, right? The XTU2 benchmark option is implemented by calling native code from XtuBenchmark.dll and registering a callback to fetch the score. I didn't go into it in all its depth, but this is a lot harder than to wrap the p95bench.exe.

Not necessary to be rude here. This is a dicussion to get the most fun out of the comp and I'm trying to give my two cents. And you might have missed the point of my post although you quoted it: I don't know how much fun it is to not be able to beat the Win 10 scores of others.

Is Geekbench 3 on AMD really a good idea? BenchMate is not going to support it with its next version, the old version won't can't be available for download as well soon. And Geekbench is faster on Windows 10 (since 1903), if I recall it correctly.

In my opinion both is needed. A theoretical research to check what the benchmark does (or doesn't do) and a small competition to see if it scales well, there are no oddities under extreme conditions and to figure out if it's fun to bench.

I only had a quick look, because I'm short on time currently. But I can already say that there are security fixes in there, so it's actually better. The bench itself is better as well, it fully loads an 9900K during the whole test. Regarding timers things don't look very bright. I'm pretty sure that there is no mitigation for Pre-Skylake in there, so timers will skew on older systems. I will have an in-depth look soon. So I guess the goal is to give XTU points again if it does alright?

Can't find anything online. Any chance I can get a hand on this?

BenchMate prior to 0.9 didn't support Windows 7 well enough to be usable. Please download the latest version and try again: https://benchmate.org The next version will improve support for Windows 7, especially the 32 bit version.

This is not a validated score that has been uploaded with BenchMate. After you get the score like you did in the screen, you have to press "Save Result" in BenchMate. The BenchMate main dialog will disappear and the result dialog shows. Take the screenshot with the button on the result dialog (or F5). Press "Submit Score" in BenchMate to upload the score to HWBOT. I will make a video soon, it's long overdue.

Is this about BenchMate, GPUPI or Geekbench 5?

GPUPI only works if OpenCL works on the platform/OS and there is support for double precision. There is also a (carefully crafted, but slower) Legacy Version of GPUPI 3.3, that will be necessary on any systems, that can't install OpenCL 2.0. I also have multiple alpha versions of GPUPI 4 ready, that completely removes the necessity of OpenCL and will run on nearly every x86 system I can think of. But it's not finished yet due to my work on BenchMate, which has much more value for the future of this community and benchmarking in general. I will finish it at some point of course, and I'm actually looking forward to it. It's relatively easy to code in comparison to anything that relates to BenchMate. But I guess I don't give a rat's ass. <3

Doesn't work on me, I obviously love the pain.

Good one! The "commander of experienced programmers" (whatever the hell that is) wasn't even aware of reliability problems when using certain timer functions in Windows 8 and 10. I also doubt that there will be any solution for Geekbench to mitigate these problems, although it was promised (weeks ago). The commander also publicly stated in the end that he doesn't care if his benchmark is used here. Which implicitly means that he doesn't care about any of our requests as well. So if we have got a problem with competitively benchmarking Geekbench, it will not be fixed. Old operating systems as well as very old platforms have no chance of being fixed. They don't have the necessary technical requirements to meet the minimum standard, that I'm trying to create here. For example old platforms are missing timer sources with enough reliability and precision, while XP for instance can't be seriously secured against the many possible attacks. I don't see that as a problem. If you are benching old stuff on old OS versions, just bench like you did before. Also, if you have any problems with the latest version of BenchMate, please post in the support thread and/or let me know with a bug report. It can't be perfect right out of the womb, that's not possible for such an extremely complex task! But in time it will be good enough to be used with all modern platforms without even thinking about it twice. It will just work, and that's a promise. As for how many people need to be involved to make this work, I don't think that you have the experience to make an educated guess here. Not to forget that there is about no money at all in this for now, so having a team working on this without any funding is unrealistic (and not necessary at this point). Time will tell and my guess is that there might be opportunities with vendors and their benchmarks. If that happens it's not only the one benchmark with funding that will get improvements. All benchmarks will be improved, even old ones, because every new feature and every bugfix will happen for them as well. That's the beauty of BenchMate. Oh, and in case I die, the source code goes to @Splave. It's already in my will, he will receive a key from my family to access the repositories. And even if that doesn't happen for one reason or another, you can always go back to use the old methods to bench.

Nowhere in this universe. Please read the posts above, I will not answer questions about Geekbench anymore.

I will remove the categories "with BenchMate" with the release of BenchMate 0.10. Geekbench will no longer be supported due to reasons stated in the post above yours. What happens to Geekbench 5 here on HWBOT is nothing I really care about. It's not a safe benchmark to compare results competitively, that's for sure.

Thank you for the clarification, Frederik. MrGenius, you should consider not posting here when drunk.

Domains are renewed automatically each year. If the debt can not be paid, the domain provider can give it back to tld provider. Happens mostly on bankruptcy cases. Even then the domain will be flagged as deleted and enter a redemption phase of 30 days, where it can be bought back by the previous owner at any time (with extra fees). An impeachment of Trump will be more likely.

It would be the recommended way to instantly start with forensics on the server and get behind this issue. If HWBOT was indeed hacked, it's not only HWBOT's security that suffers, but also our own. Our mail addresses might be out floating around in the open, passwords might be compromised. To kill this off without any research by stating that Norton got compromised is really not the right way to respond to this.

Weird, it seems like the GPUPI result didn't get captured in BenchMate. If this happens again, could you send me a bug report right after the run? You can find it in BenchMate's menu.

Do you have a problem with BenchMate? If so, please explain it with more detail.

Crazy!

Ok, I will have a look at it. ?

If you want texture and model verification, please use BenchMate 0.9.3. There will be another File Hash entry right below the executable. The number will always be the same unless something was tampered. Edit: Please don't use any NVIDIA resolution trickery with BenchMate, Windows native functions won't detect it and BenchMate will capture a wrong screenshot. I will look into it though, it's on my list. The real solution here is to make CPU-Z optional with BenchMate. It doesn't add anything that's not already on there (and much better because it's captured during the run). Unless SPD info is necessary, but that would be a single additional CPU-Z window (for now).

Some hair turned gray already, so I guess I will go for the Sean Connery look when BenchMate has its first production release. I have "fixed" this bug by not touching the 32 bit mode configuration for HPET's Timer0 on Windows 7 anymore, even if a 64 bit main counter is available. It seems to be a hardware bug I could not get rid of, even when I disable the interrupts and the main counter. Some internal flaw in the Intel implementation I guess, that was never revealed because the OS always sets up the HPET timer properly before the first rollover happens. I have no clue why this doesn't happen on Windows 10 though. In any case, I've read over on OSR that a Windows kernel dev recommended to always use HPET in 32 bit mode, especially on 32 bit systems. There is also the problem of the main counter possibly not being latched correctly when it's 64 bit on a 32 bit platform, because reading 8 bytes is not atomic for 32 bit architecture. So the counter has to be read multiple times and checked for validity, which makes the already slow HPET even slower. Of course a 32 bit implementation has to handle the rollover that happens about every 5 minutes, so there are more instructions involved to make it work. For 64 bit I don't do rollover checks because it needs 9 million days with a 24 MHz frequency until that happens. I would call that safe for non-server/workstation applications. So consider the HPET64 implementation as faster, which is another reason to use Windows 10 if you can.

I had a gook look at this and BenchMate 0.10 will work correctly on Windows 7 with 32 bit. It doesn't support kernel code integrity checks and there were other minor bugs that needed to be addressed. It should work with the next release and I hope you will have the time to take another look.

Yes, BenchMate 0.10 will NOT support Geekbench. It will come with new benchmarks though like pifast. All integrations are in agreement with their respective developers. I will not throw days of work into the garbage anymore.