Selon Ejner Borgbjerg <[EMAIL PROTECTED]>:

> On 10/18/07, pgeorges <[EMAIL PROTECTED]> wrote:
> > Michal Rudolf a écrit :
> > > Ejner Borgbjerg,  czwartek, 18 pa¼dziernika 2007:
> > >
> > > Please check following position:
> > > 3r4/2KP4/8/3R3p/6k1/8/8/8 b - - 2 66
> > >
> > > Here Crafty works correctly in pre-EGTB positions, but not in positions
> from
> > > ChessX has similar problems, so probably Crafty's output in EGTB
> positions is
> > > non-standard and neither Scid nor ChessX parse it correctly
> > >
> > This is the explanation for me : Crafty takes no CPU time when the
> > position is in the tablebases, but it does not display anything
> > interesting. So, maybe the best thing to do is to check Scid's UI to get
> > information, since engine's output is meaningless when we are in
> > tablebases.
>
> This sounds like the most probable explanation to me too.
> But when using Crafty for practising e.g. RP:R positions, then Scid as
> it is now seems useless (I will have to use XBoard/Winboard - if I
> don't manage to fix Scid code...). In this case, I don't agree with
> the Scid code, if this was intentional. If Winboard manages to let
> Crafty play the ending then it is at least possible. Michal may be
> right though that Craftys output is non-standard - I can't judge as I
> am not aware of what the standard is.

when practicing endings with Scid you have all informations in the "information
panel" (just below the main board) and also a dedicated window showing all moves
result. So I don't get why you think Scid is useless here.

Pascal

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to