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 so the AI thinks it has a lot of time to search for a move and appears to lock up. Changing difficulty settings makes no difference.
I am unable to play against both GNUChess 5.07 and Crafty 20.9 because of this. Both programs play fine in command mode and with XBoard. I don't know why it would work for some people and not for others. -alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
