Posted July 12, 20159 yr Hi Guys !! The next gen on OS Its W10 .... its allowed at hwbot ? Example : http://www.3dmark.com/3dm/7709471 http://www.3dmark.com/3dm/7709527 http://www.3dmark.com/3dm/7709555 http://www.3dmark.com/3dmv/5304614
July 12, 20159 yr Administrators As far as I can say, preliminary, win 10 is equal to win8 use, so if win 8 is allowed under certain circumstances, win 10 should be allowed as well. Please wait for final confirmation before you waste time and bench hard though, I think there will soon be an offical statement on this
July 12, 20159 yr I'm pretty sure that statement has already been made, Win 10 has the same rules as 8.
July 12, 20159 yr Ok , thanks for reply and consider it , i am waiting since published official statment. 29 of July W10 its launched officialy.
July 30, 20159 yr Definitely needs a bump.... maybe even a front-page comment? A new Windows OS is a big deal and there's no point in pretending otherwise
July 30, 20159 yr Agree, If hwbot staff can list out which benchmarks that are still valid to be run under the windows 10, that might help some users
July 30, 20159 yr What is allowed on Windows 8 is allowed on Windows 10. We are working on something to allow everything on Windows 8/10 but it will take some time.
July 31, 20159 yr We'll put up a news, good idea. BTW, I tested Windows 10 on Haswell-E yesterday and I though HPET was enabled by default. Can anyone confirm this?
August 1, 20159 yr We'll put up a news, good idea. BTW, I tested Windows 10 on Haswell-E yesterday and I though HPET was enabled by default. Can anyone confirm this? It is not. Massman you silly goose. Use my darn program I built for you. Harmonic v0.003
August 3, 20159 yr ofc it is enabled by default but it is not by default the default/main timerIt could depend on the hardware/drivers that are installed, like it is the case for Windows 7. On my system it was enabled by default and used as the primary timer by QueryPerformanceCounter().
August 3, 20159 yr Desktop or notebook? On my notebook it was disabled by default, but on the desktop enabled.
August 3, 20159 yr Desktop with Haswell-E and Windows 8 install with upgrade to 8.1. Well, it doesn't matter anyway, because we can not rely on any Windows version that QPC is handled by the HPET. The same goes for Windows 7, but we can rely on RTC there, which can not be skewed. That problem only exists in W8. Has anybody tried RTC on Windows 10? I assume it has the same problems as 8, but we should test it. If Microsoft solved the problem, depending on the timer used, a few benchmarks could be allowed. And GPUPI can fallback on RTC as well. Edit: My copy is currently on its way, I will test it as soon as I've installed it.
August 3, 20159 yr Desktop with Haswell-E and Windows 8 install with upgrade to 8.1. Well, it doesn't matter anyway, because we can not rely on any Windows version that QPC is handled by the HPET. The same goes for Windows 7, but we can rely on RTC there, which can not be skewed. That problem only exists in W8. Has anybody tried RTC on Windows 10? I assume it has the same problems as 8, but we should test it. If Microsoft solved the problem, depending on the timer used, a few benchmarks could be allowed. And GPUPI can fallback on RTC as well. Edit: My copy is currently on its way, I will test it as soon as I've installed it. It uses a software + hardware combination for clocks, however, I have not tested the fact that manipulating the bClock or FSB interferes with time sensitive applications like benchmarks. The HPET testing program I built is going to be incorporated into my CPU Thread Benchmark program though. It operates off of QPC / QPF and shouldn't be prone to BCLOCK or FSB manipulation. We are also going to work with Massman for HWBOT integration soon too. We plan on fully supporting Win Vista, 7, 8, 8.1, and 10.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.