A New Testbed for MASM32 Forum

[dedndave]

you have to click on his link, Alex   :U

[Antariy]

you have to click on his link, Alex   :U

No, I have FlashPlayer which is not integrated into browser. I can see flash only as file - after downloading. No have gread need in seeing of monkeys tricks and jumps at any web-page.



Alex

[dedndave]

lol  well you can right-click on the link - then Save As - to run it that way, too
that way, you'll know what Windows RG is  :P
(must stand for Random Generator)

[Antariy]

lol  well you can right-click on the link - then Save As - to run it that way, too
that way, you'll know what Windows RG is  :P

I have made that more than hour ago :P
I have written first reply on post with link at time when I download SWF :P



Alex

[frktons]

Hi guys.  :bg

I need your help. Before carrying on the coding of NewTestBed, I have to decide
how many algos to test and in what shape to display the results.

I attach three possibilties, that you can view with the last release posted.

[one] 12 algos tested 2 times.
[two] 24 algos tested 1 time.
[three] 12 algos tested 4 times.

What do you think about it, according to your past experiences?

Thanks

Frank

[Antariy]

Frank, there is updates and service packs for my yesterdays' code.
Have look into comments, and at include file needed to align DOS-screen.
I have addeded not only printing of CPUs string, but return the maximal supported instructions set, too - it will be useful for checking - is support CPU that test, or not.



Alex

[frktons]

Frank, there is updates and service packs for my yesterdays' code.
Have look into comments, and at include file needed to align DOS-screen.
I have addeded not only printing of CPUs string, but return the maximal supported instructions set, too - it will be useful for checking - is support CPU that test, or not.

Alex

Probably it needs a new Service Pack.  :lol
The last characters displayed bu your CPUID are repetitions of previous one, it looks like.

Good job by the way, carry on and we'll use it in the next release.

I've already implemented the Save Screen Function. Now I'm working on the last phase
to display the result of the tests in the grid, and I think I'll use the Third pattern posted above.

Frank

[Antariy]

The last characters displayed bu your CPUID are repetitions of previous one, it looks like.

Oh, that is because szMonoSpace removes spaces, but my CPU brand-string does not contain extra spaces. On my machile all is OK. On your - because your CPU have many spaces between "name" and numerical descriptor, szMonoSpace is *decrease* the size of the string.  But I have used *initial* string length, which is returned by CPUid printing proc. So, this is reason.

So, if you replace:

Code Select Expand


    shr eax,16

    push eax ; prepushed value of Length for DisplayAt proc

    invoke szMonoSpace,offset CpuBuffer

    push eax ; buffer with CPU string


with:

Code Select Expand


    mov esi,offset CpuBuffer
    invoke szMonoSpace,esi
    invoke lstrlen,esi
    push eax
    push esi


This will work. I guess, instead of returning the same pointer, which is passed to szMonoSpace, szMonoSpace should return the new string length - and things like "which is size of the string, which is computed already with easy" is not needed.



Alex

[Antariy]

By the way, Frank - you have "jubilee" - 700 posts  :lol

[frktons]

Oh, that is because szMonoSpace removes spaces, but my CPU brand-string does not contain extra spaces. On my machile all is OK. On your - because your CPU have many spaces between "name" and numerical descriptor, szMonoSpace is *decrease* the size of the string.  But I have used *initial* string length, which is returned by CPUid printing proc. So, this is reason.

So, if you replace:

Code Select Expand


    shr eax,16

    push eax ; prepushed value of Length for DisplayAt proc

    invoke szMonoSpace,offset CpuBuffer

    push eax ; buffer with CPU string


with:

Code Select Expand


    mov esi,offset CpuBuffer
    invoke szMonoSpace,esi
    invoke lstrlen,esi
    push eax
    push esi


This will work. I guess, instead of returning the same pointer, which is passed to szMonoSpace, szMonoSpace should return the new string length - and things like "which is size of the string, which is computed already with easy" is not needed.

Alex

Feel free to adjust the CPUiD code to your taste. At the end, when the routine is ready,
I'll insert it in the next release and give you credit for it in the source code.

As you can see I've a lot to do at the moment.  :lol

Frank

[Antariy]

Oh, that is because szMonoSpace removes spaces, but my CPU brand-string does not contain extra spaces. On my machile all is OK. On your - because your CPU have many spaces between "name" and numerical descriptor, szMonoSpace is *decrease* the size of the string.  But I have used *initial* string length, which is returned by CPUid printing proc. So, this is reason.

So, if you replace:

Code Select Expand


    shr eax,16

    push eax ; prepushed value of Length for DisplayAt proc

    invoke szMonoSpace,offset CpuBuffer

    push eax ; buffer with CPU string


with:

Code Select Expand


    mov esi,offset CpuBuffer
    invoke szMonoSpace,esi
    invoke lstrlen,esi
    push eax
    push esi


This will work. I guess, instead of returning the same pointer, which is passed to szMonoSpace, szMonoSpace should return the new string length - and things like "which is size of the string, which is computed already with easy" is not needed.

Alex

Feel free to adjust the CPUiD code to your taste. At the end, when the routine is ready,
I'll insert it in the next release and give you credit for it in the source code.

As you can see I've a lot to do at the moment.  :lol

Piece which is pointed is not CPUid code. This piece is in main procedure - to output CPU string.
The culprit is the szMonoSpace :P

Just find the "shr eax,16" string, and replace pointed piece with right, pointed too. I have addeded my code into your old release, so would be better if you incorporate the code yourself - otherwice we can have differences of the base code.



Alex

[Antariy]

Feel free to adjust the CPUiD code to your taste.

Current CPUid code, adapted for your test-bed, is right - it not only returns the length of the output CPU-string with all instruction sets, but return the maximal supported instr.set also.



Alex

[frktons]

Current CPUid code, adapted for your test-bed, is right - it not only returns the length of the output CPU-string with all instruction sets, but return the maximal supported instr.set also.

Alex

OK Alex, as I have time I'll have a look at it. That code is not mine, so I don't know exactly how it works.
I'll follow your suggestion in order to fix it.  :U

Frank

[Antariy]

I attach three possibilties, that you can view with the last release posted.

[one] 12 algos tested 2 times.
[two] 24 algos tested 1 time.
[three] 12 algos tested 4 times.

What do you think about it, according to your past experiences?

Second pattern is better, probably. This is mine opinion only, of course.



Alex

[frktons]

I attach three possibilties, that you can view with the last release posted.

[one] 12 algos tested 2 times.
[two] 24 algos tested 1 time.
[three] 12 algos tested 4 times.

What do you think about it, according to your past experiences?

Second pattern is better, probably. This is mine opinion only, of course.

Alex

That means you prefer to have a maximum of 24 algos to test at a time?

Frank