Moderator: Andres Valverde
H.G.Muller wrote:I really don't know PSWBTM that well, but I believe you when you say it does not work. Fixing up PSWBTM a bit is on my to-do list (e.g. with better controls in the engine manager to install UCI engines). I will check this point to.
The only work-around I see with the current version is to use time odds: before starting the tourney, add the options /firstTimeOdds=60 and /secondTimeOdds=60 in the winboard.ini, and enter the time in PSWBTM in seconds (so 155 in this case).
H.G.Muller wrote:Too bad my elaborate answer was rejected... Anyway, the solution is not to save settings. PSWBTM would not let WB save settings during a tourney.
H.G.Muller wrote:So setting the options through the menu only affects the current run. You would really have to edit them into the winboard.ini when you want to apply them globally.
H.G.Muller wrote:/firstXBook
Gábor Szots wrote:I am running a gauntlet in which one of the opponents (of Myrddin) is CyberPagno 2.1, an old WB engine. To my surprise, I got an error message telling me the game ended without starting. I also offered me I could take a pause. Now this was a 32-game match so I had to press 'No' 32 times before I could go on to the next opponent...
Previously I successfully ran CyberPagno under Arena and also under CB (via the WB2UCI adapter).
Shall I set protocol 1 manually or is there some other trick?
Guenther Simon wrote:Gábor Szots wrote:I am running a gauntlet in which one of the opponents (of Myrddin) is CyberPagno 2.1, an old WB engine. To my surprise, I got an error message telling me the game ended without starting. I also offered me I could take a pause. Now this was a 32-game match so I had to press 'No' 32 times before I could go on to the next opponent...
Previously I successfully ran CyberPagno under Arena and also under CB (via the WB2UCI adapter).
Shall I set protocol 1 manually or is there some other trick?
Are you sure you have set it up with the needed '-xboard' parameter?
Guenther
H.G.Muller wrote:I usually want to use the GUI book only for engines that have no own book. In that case I do not edit them in the winboard.ini, but add them to the engine(s) in the PSWBTM engine manager. To this end I add to the 'parameters':
WBopt /%sXBook
This will make PSWBTM pass the option with the engine name, which effectively is like it was on the command line for invoking WinBoard (so it does not have to be in the ini file).
Return to Winboard and related Topics
Users browsing this forum: No registered users and 23 guests