On Feb 19, 4:51 am, help bot wrote:

Rybka played wrong move thinking it will Mate in 2/3 But the King was
saved and Rybka Resigned saying Unable to Respone.


17. Qe5-a5{30} Be7-d6{8}
18. Nf3-e5{14} Qd7-e8{8}
19. Rb1-b7{22} Kb8-b7{10}
20. Rf1-b1{24} Kb7-a7{6}
--------------------------------------------------------------------------------

This is a forced mate, and in such cases,
a few programs "freeze up", just displaying
the next move in sequence. I hate this, but
don't know if it is a flaw of the engine itself,
or another "interesting facet" of the GUI; in
my case, that would be Arena.


I tried to test this by having various engines
analyze, to see if in fact the GUI (Arena) has
a bug (i.e. unique feature) or if the fault lay
with the engine itself. Unfortunately, all I get
are error messages, saying that my bundled
engines are missing. I had "installed" Spike,
or so I thought, along with some other free
engines; no doubt they are hiding somewhere
on my disk drive.

My guess is that Sanny was using the free
Rybka demo, beta version, and that either it
or else his GUI (mine is Arena) will not allow
the engine(s) to analyze the position when it
has spotted a forced mating sequence-- even
a suboptimal one. I don't like that at all; my
preference would be for the legal moves to be
both ranked in order, and scored numerically.
"Here you are, bot: your dumb move is
ranked 53rd out of 57 legal moves, and you
missed seven different ways to quickly force
checkmate...".

Maybe the commercial versions handle
things better. Maybe the non-beta versions
work correctly. In any case, Sanny keeps
talking about "Rybka", when I expect he
really means Rybka beta demo version 1.0
(which is supposedly stronger than almost
every commercial program anyhow).


-- help bot