Question@CCRL about Counter 1.2

[Guenther]

For some rating calculations I need to know if Counter 1.2 e.g. in the
40/4 list really is 32-bit. (it is not marked as 64-bit)
I am asking, because all I have here and found in research is a 64-bit version of Counter 1.2. (released 02/2010)
The download at SDChess also is a 64-bit version according to the taskmanager.

Thanks in advance,
Guenther

[Graham Banks]

For some rating calculations I need to know if Counter 1.2 e.g. in the
40/4 list really is 32-bit. (it is not marked as 64-bit)
I am asking, because all I have here and found in research is a 64-bit version of Counter 1.2. (released 02/2010)
The download at SDChess also is a 64-bit version according to the taskmanager.

Thanks in advance,
Guenther

Must be 64-bit then.
I'll get Ray to change it.

[Modern Times]

I think we need to get the testers concerned to check their exes and confirm.

[tmokonen]

Now this is interesting. I am able to run Counter 1.2 just fine in a 32 bit version of Windows XP. If I run it on my Windows 10 box, Process Explorer states that Counter is running as a 64 bit process.

Just to make sure we are working with the same version, the executable of the version of Counter 1.2 I am running is 48,128 bytes long, with a CRC32 value of 52DBBEF2.

If you add Counter 1.2 as an engine in Arena, the Command Line entry field is not highlighted in blue, as it is with most 64 bit engines. Arena gets the info from the EXE file header, and the info in the file header says 32 bit.

I could be totally wrong here, but the EXE file seems to be some sort of .NET wrapper, and the program runs as 32 or 64 bit, depending on the OS and .NET framework that are installed.

[tmokonen]

I use a program called HashTab to display this information, but you can also create an archive with with a program like WinZip, WinRAR or 7Zip, and then open the archive within one of these programs to view the CRC32 value.

[Modern Times]

I wonder in that situation if there is actually any Elo difference.

[Guenther]

I checked via Process Explorer and it showed Counter as a 64-bit process. I did not know that.
As I have only one Counter 1.2 that means that all the games I submitted under the name Counter 1.2 were actually played by Counter 1.2 64-bit.
The list shall be corrected. Apologies to everyone and thanks Guenther.

No apologies needed. I guess this was released in the transition time before 64 bit was commonly used on mainstream user hardware.
BTW I have exactly the same size and CRC fingerprint as reported from Tony.

I checked some archives now and even Counter 0.1 already appears as 64 bit here.

[Modern Times]

I'm pretty sure that the vast majority of our games would have been played under a 64-bit OS. Given the passage of time it may not be possible to establish conclusively, in which case we'd just re-name it as the only practical solution.

[Guenther]

I'm pretty sure that the vast majority of our games would have been played under a 64-bit OS. Given the passage of time it may not be possible to establish conclusively, in which case we'd just re-name it as the only practical solution.

I think it should be possible at least to subtract all games with 64-bit opponents and create a different entity.
(If the opponent was 64-bit the environment also was 64-bit.
Also if there are no more testers with 32-bit all games after a certain
point in time could be added to the 64-bit entity too.)

If I am not wrong the difference for both entities should be noticeable.
Of course this depends on how much work it is for CCRL.

[Guenther]

Vadim wrote:

Counter 1.2 requires .NET Framework to run.
When I developed Counter 1.2, I used 32 bit computer with 32 bit OS Windows
(probably Windows XP) and 32 bit Microsoft .NET Framework.
But the same binary file become 64-bit process when run on 64-bit OS and 64
bit .NET Framework installed (at present times it is almost always true).

Anyway Counter 1.2 has 12x10 board representation and 64 bit probably
should not give noticeable increase.

Thanks Gabor.