Congratulations Michael!!
I know I was satisfied when I was first able to start figuring a few things out about setting up engines in the Winboard GUI. It took me time of seaching on the Internet, etc. till I got to that point and honestly a few times I gave up on using the Winboard GUI but for some reason kept coming back to it and attempting to get it right. There is absolutely nothing in my posts above that I found out on my own; I just collectively put into one place things I had found out in bits and pieces in postings of other people on the Internet.
A couple of things about what you posted above:
In a post above I wrote this-
Quote:Maybe in some other cases there might be exceptions to what is stated above, depends on which engine is being dealt with.
Michael you have hit upon two exceptions with Crafty and BugChess.
On CraftyMichael Ayton wrote on 07/05/09 at 21:58:23:
Crafty doesn't work -- I get a message saying "The system could not find the file specified" -- but I'm using the exact name of the .exe file I have.
Notice the engine name you posted for Crafty from your ini file - crafty-23.0-win32
From the Winboard GUI help file.
Quote:If the engine name has more than one period in it (for example, QChess1.5.exe), you must include the ".exe" extension; otherwise you can leave it out."
The Crafty engine name in the winboard.ini file you posted has a period [.] in it. So since the name already has a period in it
you do have to put the .exe extension on the end of it. So the engine name in the Winboard ini file should be - crafty-23.0-win32.exe
Adding the .exe extension to your winboard.ini file for the Crafty engine name should get it running. You still have to edit the Crafty.rc file if desired, but even if you were using the Crafty Winboard engine in the Arena GUI or some other GUI you would still have to deal with the .rc file. It isn't like the Winboard GUI alone is making us have to deal with this.
On BugChessI did not have BugChess installed so downloaded it. Like for you, BugChess stalled on startup and I had to use Ctrl+Alt+Del to close it.
Looking in the read me file that came with the engine I noticed this-
Quote:Line command parameters
-----------------------
---- compulsory to use with a interface using the winboard protocol
"-winboard"
---- hash size : comes in power of 2 as follow :
...
"- hashsize 16777216" -> means 16 MB of hash in human language.
"- hashsize 33554432" -> means 32 MB of hash in human language.
"- hashsize 67108864" -> means 64 MB of hash in human language.
"- hashsize 134217728" -> means 128 MB of hash in human language.
"- hashsize 268435456" -> means 256 MB of hash in human language.
etc...
> default : 32 MB
Doing a search engine search on the engine found this page.
http://wbec-ridderkerk.nl/html/details1/BugChess2.htmlNotice this part on the above web page.
Quote:WinBoard.ini lines:
"BugChess2 -winboard -hashsize 33554432" /fd=d:\Winboard\BugChess2
"BugChess2 -winboard -hashsize 33554432" /sd=d:\Winboard\BugChess2
Especially this part.
Quote:BugChess2 -winboard -hashsize 33554432
This is my entry for BugChess in my winboard.ini file. And the engine started and when I made a move the engine responded. I did not finish a full game so if other problems exist I am not aware of them. Sometimes problems do exist with engines and if problems do exist it is not necessarily a Winboard GUI problem, it may well just be a problem with the engine.
}
/firstChessProgramNames={"Hiarcs 10" /fd="C:\Program Files\Chess\Polyglot" /fcp='polyglot hiarcs10.ini'
"Marquis 0.1.6" /fd="C:\Program Files\Chess\Chess Engines\Marquis" /fcp='marquis'
"Rybka 1.2f" /fd="C:\Program Files\Chess\Polyglot" /fcp='polyglot rybka12f.ini'
"ProDeo 1.4" /fd="C:\Program Files\Chess\Polyglot" /fcp='polyglot prodeo14.ini'
"Ufim 8.02" /fd="C:\Program Files\Chess\Polyglot" /fcp='polyglot ufim802.ini'
"Bugchess" /fd="C:\Program Files\Chess\Chess Engines\Bugchess" /fcp='BugChess2_V1_6_3 -winboard -hashsize 33554432'
}
/secondChessProgramNames={"Hiarcs 10" /sd="C:\Program Files\Chess\Polyglot" /scp='polyglot hiarcs10.ini'
"Marquis 0.1.6" /sd="C:\Program Files\Chess\Chess Engines\Marquis" /scp='marquis'
"Rybka 1.2f" /sd="C:\Program Files\Chess\Polyglot" /scp='polyglot rybka12f.ini'
"ProDeo 1.4" /sd="C:\Program Files\Chess\Polyglot" /scp='polyglot prodeo14.ini'
"Bugchess" /sd="C:\Program Files\Chess\Chess Engines\Bugchess" /scp='BugChess2_V1_6_3 -winboard -hashsize 33554432'
}
One other thing. In my first post in this thread I had suggested that you delete the Winboard GUI package that you first had. I think it is called 'Winboard Gold Pack'.
Just to let you know you can still keep that Gold Pack setup and have it, and your current Winboard setup in different program folders. There will be no conflict between the two Winboards. Except they will have to use their own winboard.ini file. It is best not to interchange winboard.ini files between different versions of Winboard. Some changes may exist in the winboard.ini files for one version of Winboard that do not exist in a previous or future versions of Winboard.
I have three different Winboard versions at this time. (
Graphic)
1). Winboard_X
2). Winboard_F (I just have the folder labelled Winboard_F to distinguish it, It is just H.G. Muller's Winboard version.)
3). And a test version that H.G. Muller recently released.
There is no conflict between these three versions. So if you want the Gold Pack version, do put it also on your OS.
By my post in this thread it may seem that I am a Winboard GUI nut or something. I'm not. I was just trying to help Michael Ayton, and maybe some others, out. I think the Winboard GUI could be used by someone to do serious chess study, but then so could Arena. And no doubt that for serious chess study Chessbase or Convekta products are a/the way to go.
BTW, if you play chess variants I can't help you set them up in Winboard. I have no experience. You are on your own.
Let us know how you get on with the UCI engines. And Michael, I'd like to see you set up a ProDeo chess engine as a Winboard engine and change the engine personalities through the winboard.ini file.
Info on doing that here.