Thread View: gnu.chess
4 messages
4 total messages
Started by Harry Edmon
Wed, 14 Mar 1990 00:09
Problem with gnuchess 3.0
Author: Harry Edmon
Date: Wed, 14 Mar 1990 00:09
Date: Wed, 14 Mar 1990 00:09
17 lines
1442 bytes
1442 bytes
Running gnuchessn 3.0 on a Sun 4/370 running 4.0.3 with gnuchess
compiled with gcc 1.37.1 or Sun cc fails with the following set
of moves when I play white and the computer plays black:
score depth nodes time score depth nodes time
d2d4 0 0 0 2 d7d5 0 0 0 0
e2e3 0 0 0 1 g8f6 -5 5 13061 8
f1d3 0 0 0 6 e7e6 3 5 15818 9
My next move is b1d2, which the computer labels as an Ambiguous move.
--
Harry Edmon INTERNET: harry@atmos.washington.edu
(206) 543-0547 UUCP: uw-beaver!atmos.washington.edu!harry
Dept of Atmospheric Sciences, AK-40
University of Washington
Re: Problem with gnuchess 3.0
Author: Hans-Erik Sandstrom LOG/SV
Date: Wed, 14 Mar 1990 12:19
Date: Wed, 14 Mar 1990 12:19
28 lines
1786 bytes
1786 bytes
In article <HARRY.90Mar13160918@stormy.atmos.washington.edu> harry@atmos.washington.edu (Harry Edmon) writes: >Running gnuchessn 3.0 on a Sun 4/370 running 4.0.3 with gnuchess >compiled with gcc 1.37.1 or Sun cc fails with the following set >of moves when I play white and the computer plays black: > > > score depth nodes time score depth nodes time > > d2d4 0 0 0 2 d7d5 0 0 0 0 > e2e3 0 0 0 1 g8f6 -5 5 13061 8 > f1d3 0 0 0 6 e7e6 3 5 15818 9 > >My next move is b1d2, which the computer labels as an Ambiguous move. It seems that you have been bitten by a rather nasty bug! Gnuchess is correct: b1d2 could also be B1d2 or Bd2. The ambiguity is between ECO/Informator style move entry and algebraic move entry. Until a bugfix appears nd2 will do what you want. Hans Eric -- Hans Eric Sandstr|m E-mail: hes@log-sv.se TeleLOGIC Sundsvall AB ...!uunet!sunic!log-sv!hes Box 883 Tel: +46 60 161098 S-851 24 Sundsvall, Sweden Telefax:+46 60 122944
Re: Problem with gnuchess 3.0
Author: Harry Edmon
Date: Wed, 14 Mar 1990 16:44
Date: Wed, 14 Mar 1990 16:44
6 lines
1067 bytes
1067 bytes
The problem is that Xchess will not work unless the bug is fixed. -- Harry Edmon INTERNET: harry@atmos.washington.edu (206) 543-0547 UUCP: uw-beaver!atmos.washington.edu!harry Dept of Atmospheric Sciences, AK-40 University of Washington
Re: Problem with gnuchess 3.0
Author: Hans-Erik Sandstrom LOG/SV
Date: Wed, 14 Mar 1990 19:05
Date: Wed, 14 Mar 1990 19:05
21 lines
1496 bytes
1496 bytes
In article <HARRY.90Mar14084426@stormy.atmos.washington.edu> harry@atmos.washington.edu (Harry Edmon) writes:
>The problem is that Xchess will not work unless the bug is fixed.
Oh, I did`nt realise that, here is a fast "bugfix" it just makes the
ECO/Move entry require Upper case for piece names:
Change this line in algbr() in the file nondsp.c:
if ((mvstr[1][0] = qxx[board[f]]) == 'p')
to
if ((mvstr[1][0] = pxx[board[f]]) == 'P')
Hope this is sufficient till someone fixes this properly, probably by
making algebraic or ECO notation different modes.
Hans Eric
Hans Eric Sandstr|m E-mail: hes@log-sv.se
TeleLOGIC Sundsvall AB ...!uunet!sunic!log-sv!hes
Box 883 Tel: +46 60 161098
S-851 24 Sundsvall, Sweden Telefax:+46 60 122944
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads