Author: Lex Loep
Date: 23:10:01 02/09/05
Go up one level in this thread
On February 09, 2005 at 17:20:44, Mark Smits wrote: > >>>Not on FICS. The message does not come up, but the engine does think it has >>>moved already when the board it is not updated. He had to type "refresh" >>>repeatedly to get it to move. >> >>Then it obviously a different problem. Perhaps some problem with the engine. >>(which engine?) > >Typing refresh does not always help, at least with Pro Deo. Usually I can type >the move from the suggested PV by hand and that will cure things. > >> >>Lex >> >> >>> >>>I tried it as well on FICS with the UCI engine and I had no problems. Again >>>though my opponent "Hera" had the same problem. >>> >>>Peter > >Hera is Pro Deo 1.1. It 's running on the normal telnet port 23. There is even >100 ms move time delay. > >Kronos on ICC is it's brother, but still running 1.0. Also on port 23, also with >100ms delay. Having problems there as well. Maybe the following is of interest. > >Once I saw a message go by saying something like "corrupt data in timestamp" or >something like that. The result was that timestamp got disabled. I logged off >and back on. Never seen that message again. After that I am doing a lot more >pinging on me just to check if timestamp is still there... Thanks for the info. Looks like there is something strange in timestamp/timeseal. Unfortunately these programs are outside my control. On FICS I have played around 14000 games and never have seen this problem. Also on ICC I have never seen the 'not your move' problem. I have one option I may investigate further, CP uses the timestamp program in local server mode where most other programs use timestamp in stdio mode. I may add an option in CP to also use stdio mode. Don't know yet when I have time to do this. Lex
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.