🚀 go-pugleaf

Newsgroups: gnu.chess
Subject: Re: gnu chess 4.0
Summary: 
Expires: 
References: <1992Jul6.094839.13044@Informatik.TU-Muenchen.DE>
Sender: 
Followup-To: 
Distribution: 
Organization: DEC Systems Research Center
Keywords: 

Sorry; I don't know what could be causing this problem for you.  No
one else has reported it, and I can't think of a mistake in setting
flags or compiling that would cause it.

If you (and gnuchess) make the specified number of moves before time
control, both clocks should be reset to the amount of time in the next
time control period.  If you miss your time control, your clock stays
at zero regardless of how many more moves you play, and the other
clock continues counting down until it reaches zero, regardless of how
many moves your opponent plays.  This seems like reasonable behavior
when you are playing out a game that one side has already lost on
time.  I take it this is not the behavior you're seeing, though.

	--Tim