Author: Robert Hyatt
Date: 21:08:16 07/26/99
Go up one level in this thread
On July 26, 1999 at 23:23:39, Ralf Elvsén wrote: >On July 26, 1999 at 21:59:28, Gustavo Pereira wrote: > >>In this position from Kasparov-Topalov in Hoogovens 99 the new Crafty16.13 from >>Chessbase literally hangs... >> >>3r3r/1R3p1p/6p1/1p6/2q5/5PPB/1Q5P/1K1k4 w - - 0 1 >> >>It gets stuck on Bd7 showing an eval of #0 (mate in zero!) which is obviously a >>mistake. >>The moment I put it in multi-play analysis it works. >>Does anybody have the same problem? >> >>Anyway, the move played by Kasparov is 36. Bf1!! >>Complete and utter shredding by the Champ ;) >> >> >>PS: At first I thought it was a problem in the newly released engines, but >>CometB04 doesn't have this problem. > > >I don't know if this is related, but I just downloaded wcrafty-16.13.exe >from Bob's ftp-site. Running it with Winboard in analysis mode I get >one of the usual cryptic error messages from Windows 98 in a specific position >in a game. The message concerns Crafty, not Winboard. The program terminates. >The error is reproducible. It also happened when I analyzed another game. > >I am running this version of Crafty under exactly the same conditions >as older versions. Of course I checked: the older versions could handle >the game I looked through. Something is different... > >Btw, I am not so happy that (in analysis mode) Crafty no longer displays >the order number of the move it is analyzing at the moment. Older versions did, >like 7/38 meant that it was checking move nr 7 out of 38 (at least I think >that is what it meant). > >Has anyone else had problems with wcrafty16.13 in analysis mode? > > thanks for any help in adavance This should still happen (display moves) which shows the 8/32 thing. I haven't changed that at all so far as I know... There are lots of things that are 'different'. Whenever you find a bug that crashes the program, please let me know asap... I don't intend to do those kinds of things and they are affecting probably everyone and not just you. In this case (16.13) it is possible that the king safety bug killed other positions too... to see what is wrong, set up the bug position and type 'score' and check the king safety score (+infinity). That is a 'clue' something is bad. :)
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.