I dug a little deeper, and it turns out that the form of the time command that Knights is using is correct by the xboard specification, and Crafty handles it correctly when it is in xboard mode.
The problem appears to be the st command, which sets the search time limit, equivalent to a time limit per move. I commented out the line which sends this command in proto_xboard.cpp (line 368) and now Crafty runs just fine under Knights. This command is sent with a smaller value when the chess engine strength is set to easy, which is why that appeared to fix the problem. If the st command isn't removed as I did, it should at least send a time that is less than the remaining time as set by the time command. The default settings send "st 131072" which sets a time per move of over 21 minutes. Clearly this is nonsensical if the engine has only fifteen minutes (for example) to complete the entire game. -alex On Tue, 2006-07-18 at 20:32 +0200, Tommaso Moroni wrote: > reopen 366181 [EMAIL PROTECTED] > thanks > > Hi Alex! > I'm reopening the bug and setting your email address as the originator > address, > so when it will be closed you will be notified. > > > On Fri, Jul 14, 2006 at 09:02:58PM -0500, Alex Midgley wrote: > > I don't think this bug is related to CPU utilization. If you set a log > > in the chess engine configuration dialog, you can see that Knights tries > > to set the time with a command like > > time 12000 > > when the command should be > > time number_of_moves/minutes > > The only reference I've found on the web about the xboard protocol > (http://www.tim-mann.org/xboard/engine-intf.html) > seems to say that the time only sets a timer which doesn't have any influence > on the time spent searching for a move. However I could easily be wrong! :) > Do you know any other documentation about it? > > Moreover I looked a bit closer to the gnuchess logs and I've found that > knights > indeed uses some weird commands in order to set the difficulty. > In the next days I'll work on it and keep you informed. > > > Thanks for your help! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]