Hahaha
Jack, I was reading it real-time. Have you any idea of the number of edits in your posts within this thread?![]()
My PC had been infected by Bavriax.exe virus which attaches itself to trojan downloaders and then someone takes over your system to act as a farmbot (warning: downloaded UT3Demo from a legitimate server, extracted and it had this virus execute automatically - was not picked up by AV/FW (fileplanet IIRC)). It's next to impossible to get rid of (new) and only picked by online updated scanners since the virus is kernel level, Safe Mode won't help, it escapes all detection and has no visible processes running. It won't let you execute any software at all and rewires your keyboard mappings. At that time, I knew it was sending and retriving data online heavily but while gearing to deal with it and the hacker who kept writing text all over my screen in a large notepad and changing screensize to 800x600, I was online on and off, reading this thread. Trying to download the attached zip file. It was broken and giving me this error:
So I couldn't read. After that I couldn't execute anything at all so no net access to read updates. Took me 7 hours manually to deal with it. No software worked. What a bloody PITA. It's working now but still won't be fully clean, it's botched my Fx %AppData% dir and everything I download is going somewhere where it's not supposed to and a place I don't see. Thus it's added much more delays to my schedule now and what I can test right now. Basically, nothing for now until I get this all fixed.
Thanks for the files. I've checked them out now, they're good.
Re the sigma: I was using an experimental, completely JS written scientific tool coded by a friend. It was supposed to be stable and running basic calcs fine. However, yesterday when running these values through, it gave me the answers I had posted, repeatedly. Later on I had time to debug it and it was a bug. I'm not sure how but it's caused, but the coding for n-1 kept defaulting to n so the squared variance was dividing by 6 values whereas it should divide by 5 and then square root. That led to the error in end values, apologies for the extra hydra. Those results you posted I hand checked early morning, and they are correct including the new values.
Thanks. I'll look through it with better time, resources and opportunity - may well be a while yet though.
Previously, I have benched UT3/Prey/Crysis/FarCry/FEAR on Q6600 G0 and Phenom 9600BE using a 3870 but only at generally played resolutions mid (1680x1050) to high (1920x1200). It was a mixed scenario since the GPU was bottlenecked many times but the CPU had enough code being fed to still scale with 100MHz speed changes. Overall, at those resolutions it was showing UT3/Prey being very Intel favoring while Crysis was near same for both (wasn't a CPU dependent game, nor was it a quad-core optimized game, as this of a few thread shows), but FEAR favored Phenom. FarCry, I don't really remember the output of and I don't have the data drives with me here, but from cached instinct, I would wager that it was showing Core2/Penryn favoritism clock for clock.
Add: I played FarCry just now with a Q6600 and it used 27-29% of the cores consistent at 1024x768 full-screen and the same for 800x600 full-screen. FEAR was just a little less.




) ... you are right, it is not there...
Reply With Quote

Bookmarks