Forum > Windows

Automatic test and benchmark package - includes installer (BETA)!

<< < (3/3)

alphax:
I have to say "Thanks Simon!"

I also want to relay my own experience:  I'm running Win XP Pro SP2

I tried running the test and benchmark tool straight after downloading, but got a "Application failed to initialize properly" error.

After I installed the .NET 1.1 Framework, then it's working perfectly and my AMD64 X2 3800+ can only take up to the SSE2 compile.

Simon:
That's perfectly normal. AMD chips won't run anything else than the generic MMX/SSE/SSE2 versions.

Regrettably, the test/benchmark tool does not run without .NET 1.1 or higher installed, but you got that fixed it seems :)

Oh, and thanks!
Simon.

KarVi:
It's not entirely true that the AMD chips won't run the non-generic executables.

The Intel compiler simply makes them not want to run on AMD chips, as described on this page:

http://www.swallowtail.org/naughty-intel.html

It is possible to patch the executables so they don't look for Intel chips, and the speed improvement is huge, about 10 seconds for every minute of crunching time.

I have it working on my system, currently running the SSE2 P4 version on my Athlon64, the SSE3 P4 version works too, but I don't think its faster, perhaps even a little slower on average. I'm trying to find out more precisely.

Simon:
Karvi,

I'm aware of that ;) However - as the legal situation is less than clear, I will not offer pre-patched executables (and the ones I released will only run on the CPUs I mentioned unpatched).

Also, I've been made aware that using ICCPatch may give computation errors on non-Intel CPUs - they have more registers, and if you try to address one of those on a CPU that doesn't have it, bad things can happen.

So - classic case of "caveat emptor" (buyer beware) - of course, nobody is stopping you from doing it ;)

Regards,
Simon.

IrishFBall32:
Simon - The JIT debugger error that was being experienced was not calling a Java debugger... JIT is used as a generic term for any debugger that can be popped up to do forensics when an app dies like that... Windows comes built in with that annoying Dr. Watson 'Send your error log to Microsoft' thing in place of a real debugger, and that will get replaced with whatever comes with VS/VB/Java/Delphi/Whatever language...

I have a nasty contention on my computer because I code in both Java and Delphi (and for a brief while VS before you had a compiler license), and only one gets to be *the* JIT debugger, so I have to manually switch the environment variable depending on what code I happen to be breaking that day  ;D


Also, Kudos for the automatic installer... It makes it far easier to get the best app instead of playing a guess-and-check with CPU-Z.

Any chance you're still looking for testers?

Edit: Oooh, looky, I'm a knave... hopefully and errant one at that  :D

Navigation

[0] Message Index

[*] Previous page