Komodo 2.03 release is imminent

[Don]

The Komodo 2.03 release is imminent. Release 2.01 was short lived due to problems.

Version 2.03 is to be viewed as a separate version, not just a bug fix release as it has some improvements, perhaps 5-10 additional ELO.

But it also has a major bug fix that has caused problems in testing. This bug has been in Komodo since the beginning of time ...

Get it here: http://komodochess.com

Komodo 2.03 is significantly stronger than Komodo 1.3.

Various platform specific versions will be posted as they become available and there may be multiple versions for your platform. If you don't see anything, check back frequently. At the time of this post only 2 version are ready, the Android version and the Mac version. But more will soon follow. Some versions may run better on your machine than others so you may wish to use the version that runs fastest on your hardware.

You can always get the latest release versions of Komodo here:

http://komodochess.com

Again, many thanks to Jim Ablett and Dann Corbit and Aart Bilk for helping me debug and compile. Clemens Keck was very helpful also in helping me test.

Feedback is always welcome.

Don and Larry

[JuLieN]

Thanks, Don and Larry: I just tried it in Sigma Chess 6.2 and it works like a charm!

[Dayffd]

Thank you for this new release and your prompt attention and work when bugs arise.

Best Regards,

David

[Don]

The Jim Ablett version is now available from Jim Abletts web site as well as the komodoches web site.

We are working on a PGO version that is GCC based and has sse4.2 support. When that is available you will want to see which version runs best on your particular platform.

The Komodo 2.03 release is imminent. Release 2.01 was short lived due to problems.

Version 2.03 is to be viewed as a separate version, not just a bug fix release as it has some improvements, perhaps 5-10 additional ELO.

But it also has a major bug fix that has caused problems in testing. This bug has been in Komodo since the beginning of time ...

Get it here: http://komodochess.com

Komodo 2.03 is significantly stronger than Komodo 1.3.

Various platform specific versions will be posted as they become available and there may be multiple versions for your platform. If you don't see anything, check back frequently. At the time of this post only 2 version are ready, the Android version and the Mac version. But more will soon follow. Some versions may run better on your machine than others so you may wish to use the version that runs fastest on your hardware.

You can always get the latest release versions of Komodo here:

http://komodochess.com

Again, many thanks to Jim Ablett and Dann Corbit and Aart Bilk for helping me debug and compile. Clemens Keck was very helpful also in helping me test.

Feedback is always welcome.

Don and Larry

[Sarciness]

Looking forward to using it. Cheers!

[Laskos]

Cannot test, it has an enormous (~25-30 secs) lag exiting and starting again (CPU usage 0%). I am talking about komodo-203-64-ja for windows.

Kai

[Don]

Cannot test, it has an enormous (~25-30 secs) lag exiting and starting again (CPU usage 0%). I am talking about komodo-203-64-ja for windows.

Kai

Kai,

I'm looking into it. I think I know what the problem is. The program starts up very quickly and runs fine, but when UCI sends "quit" I believe the process is not killed and I'm pretty sure I know why.

Unfortunately, I'm not a windows programmer so I am having to figure this out as I go - but I think it's the I/O thread Komodo sets up that is not closing down properly on exit.

If I start the program in a console it starts up immediately. Then if I type "quit" nothing happens until I press ENTER once, then it's done.

So I think your UI is probably waiting for Komodo to quit and when it doesn't it kills it after a timeout, that is my guess.

[Laskos]

Cannot test, it has an enormous (~25-30 secs) lag exiting and starting again (CPU usage 0%). I am talking about komodo-203-64-ja for windows.

Kai

Kai,

I'm looking into it. I think I know what the problem is. The program starts up very quickly and runs fine, but when UCI sends "quit" I believe the process is not killed and I'm pretty sure I know why.

Unfortunately, I'm not a windows programmer so I am having to figure this out as I go - but I think it's the I/O thread Komodo sets up that is not closing down properly on exit.

If I start the program in a console it starts up immediately. Then if I type "quit" nothing happens until I press ENTER once, then it's done.

So I think your UI is probably waiting for Komodo to quit and when it doesn't it kills it after a timeout, that is my guess.

Ok, thanks, this will be fixed soon probably. I will leave overnight even at this snail pace till the fixed Reptile will appear.

Kai

[Jim Ablett]

Cannot test, it has an enormous (~25-30 secs) lag exiting and starting again (CPU usage 0%). I am talking about komodo-203-64-ja for windows.

Kai

Hello Kai,

Here are new windows compiles which use the much stronger windows api function 'ExitProcess(0)' in place of 'exit(0).
These will exit immediately and all processes will be terminated. Very brute force & not very elegant, but gets the job done.

http://www.mediafire.com/?d27d64mq0emcyeu

Jim.

[Laskos]

Cannot test, it has an enormous (~25-30 secs) lag exiting and starting again (CPU usage 0%). I am talking about komodo-203-64-ja for windows.

Kai

Hello Kai,

Here are new windows compiles which use the much stronger windows api function 'ExitProcess(0)' in place of 'exit(0).
These will exit immediately and all processes will be terminated. Very brute force & not very elegant, but gets the job done.

http://www.mediafire.com/?d27d64mq0emcyeu

Jim.

Thanks, works perfectly now.

Kai