Author: David Wilke
Date: 12:54:35 01/18/01
Go up one level in this thread
On January 18, 2001 at 14:43:08, Robert Hyatt wrote: >On January 18, 2001 at 10:11:57, Ulrich Tuerke wrote: > >>On January 18, 2001 at 10:04:38, Robert Hyatt wrote: >> >>>On January 18, 2001 at 09:14:47, David Wilke wrote: >>> >>>>I have noticed that when people just bring a program onto a server, for some odd >>>>reason the engine does _not_ respond to the first match request. >>>> >>>>I have noticed this myself when I tried the new Crafty, yet doesn't happen when >>>>using an older version of Winboard. >>>> >>>>Could this be a bug? >>> >>> >>>There is possibly a small timing hole. Tim uses "ping" after any command >>>that might take a while to execute. When the engine finishes, it then sends >>>a "pong". As the thing first logs on, starting crafty can take a few seconds >>>while it sanity-checks the EGTB files. If a match comes in before crafty says >>>"pong" then xboard rejects the match request immediately... >> >>Winboard sends the ping only in case the engine had registered this feature. >>So, older engines (not adapted to protver 2) do not get the "ping" from Tim. >> >>Uli >>> > > >Right. But he specifically mentioned the "new crafty" which registers this >feature. And that _could_ account for the first match request getting refused >by xboard. > > > >>>perhaps that is what you are seeing... another program is issuing a match very >>>quickly and xboard/engine are not quite ready. I have tried several other engines and the only ones that seem to have this problem are: Crafty 18.0/18.1 Little Goliath 3.0 Comet B27 Many others do not have this problem, including Gandalf, Crafty 17.14 among others... I said I tried it with the new Crafty as that was the first engine I had available.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.