Forum > Windows

New version of the KWSN Test & Benchmark Tool with Auto-Installer released

<< < (3/6) > >>

Simon:
Nope.

I took the sources I had already, modified as necessary and recompiled (VB .NET).

A test/bench/install platform in auto-it would be the next step, but I haven't had time to get into it yet.

Regards,
Simon.

BenHer:
If someone were very enterprising...and curious about such things...

They could observe the 2.0 crunchers in action and note that the code checks for the specific presence of an Intel processor four times in each of the intel specific .exe files.  The first 4 occurences of 'Genu' 'ineI' 'ntel' in the source code are solely to limit code to Intel only.  Any following occurences are for my CPUID code when identifying CPU. Just for curiosity sake. 

You might also notice that Simon neglected to compute an overall checksum over the entire EXE allowing naughty end users to potentially change the code and still have it run.  Naughty Simon!

Simon:

--- Quote from: ---Naughty Simon!
--- End quote ---

Damn straight! ;D

Youth:
I've installed the .Net Framework 1.1 on my laptop, but when i run the test tool, it still prompt to require the .Net Framework 2.0.50727.


--- Quote from: Simon on 20 Nov 2006, 05:21:03 am ---Vyper,

looks like you need Microsoft .NET 1.1 :)

Michael,

no, right now I hadn't had a Linux version planned, although I'm interested in getting one made - if you can help, I'd be much obliged.

HTH,
Simon.

--- End quote ---
>:(

Arnulf:

--- Quote from: BenHer on 20 Nov 2006, 12:40:57 pm ---If someone were very enterprising...and curious about such things...

They could observe the 2.0 crunchers in action and note that the code checks for the specific presence of an Intel processor four times in each of the intel specific .exe files.  The first 4 occurences of 'Genu' 'ineI' 'ntel' in the source code are solely to limit code to Intel only.  Any following occurences are for my CPUID code when identifying CPU. Just for curiosity sake. 

You might also notice that Simon neglected to compute an overall checksum over the entire EXE allowing naughty end users to potentially change the code and still have it run.  Naughty Simon!

--- End quote ---

And if someone should try to run the potentially changed code on an Opteron 265 they would notice that the generic SSE2 client is faster than the potentially changed one.  ;)

A.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version