komodo with shredder

[Don]

I need to know if anyone is still having trouble with the shredder interface.

I have received conflicting reports about this for the past couple of versions.

Is that still the case? If so, please report to me which version/platform etc and I'll see if I can make some sense out of it.

I also think I've solved the console issue - I'm waiting for Jim Ablett to verify this but we have been working together on it. It's possible that this is a related issue.

[yanquis1972]

i don't think i've ever to my knowledge had any problems with komodo under the shredder 12 GUI. latest version doesn't seem to be an exception.

[alpha123]

Komodo 1.0 worked great, I have yet to test 1.1. As long as you didn't change the UCI handling much, it should still work fine. I'll see how searchmoves and MultiPV work.

Peter

[tomgdrums]

I need to know if anyone is still having trouble with the shredder interface.

I have received conflicting reports about this for the past couple of versions.

Is that still the case? If so, please report to me which version/platform etc and I'll see if I can make some sense out of it.

I also think I've solved the console issue - I'm waiting for Jim Ablett to verify this but we have been working together on it. It's possible that this is a related issue.

I just got done installing the brand new version of Komodo in Shredder 12 and worked great. I checked infinite analysis, multiple move analysis, and analyze game mode. They all worked great. I also played a game against Komodo (and got crushed) and I ran a quick 4 game match of Naum 4.1 sp against Komodo 1.1. Everything ran just perfect. Komodo even won it's quick match against Naum 4.1 by the score of 2.5-1.5.

[fern]

No problems at at all with Sh 12. My OS is windows 7.

Fernb

[Andre]

With the latest Shredder GUI when analyzing positions with 1mn time per move (exact time), Komodo 1.1 x64 goes way beyond the 1mn limit (sometimes 2 or 3mn) when this setting has been working fine for other engines.
I've been testing on Windows 7 using Eigenmann Ending Test suite.

[Don]

With the latest Shredder GUI when analyzing positions with 1mn time per move (exact time), Komodo 1.1 x64 goes way beyond the 1mn limit (sometimes 2 or 3mn) when this setting has been working fine for other engines.
I've been testing on Windows 7 using Eigenmann Ending Test suite.

Komodo does not implement fixed time or fixed node levels. I'll put that on the todo list for the NEXT release.

[IWB]

Hi Don

I am not sure if this is limited to the classic ...

At the moment i have 357 games and 3 crashes with 1.1. The 1.0 was definately worse as it crashed 8 to 10% of all games.

The crash itself is always identical. AFTER the game is finished the GUI is closing the engine and reloading it. For the cases which are ein doubt I get a window message that Komodo caused an exception. But everything is running on, the last game is saved, the tourney continues, the "old" engine is deleted out of the memory ... it is just the windows error message.

To me it happens with Windows XP64 and the 64bit Kommodo 1.0 and 1.1 versions.


Bye
Ingo

[Don]

Hi Don

I am not sure if this is limited to the classic ...

At the moment i have 357 games and 3 crashes with 1.1. The 1.0 was definately worse as it crashed 8 to 10% of all games.

The crash itself is always identical. AFTER the game is finished the GUI is closing the engine and reloading it. For the cases which are ein doubt I get a window message that Komodo caused an exception. But everything is running on, the last game is saved, the tourney continues, the "old" engine is deleted out of the memory ... it is just the windows error message.

To me it happens with Windows XP64 and the 64bit Kommodo 1.0 and 1.1 versions.


Bye
Ingo

So it doesn't actually affect games themselves. That's good. But I would still like to solve the problem if I can identify what it is. I have a feeling it could be related to the console issue.