Winboard Forum

Hi there

I have just setup Winboard 4.4.3 with Rybka 4 which works perfectly however I'm trying to also setup Rybka 3 in the same way to benchmark the two engines, however I run into a problem. When ever I start up the Rybka 3 engine from the startup dialog box the following error appears "DeepRybka3w32.exe has encountered a problem and needs to close." After pressing close button the engine process stays open and must be manually shut down from the task manager.

I thought maybe it was the version of polyglot used with Winboard 4.4.3 becasue I can get Deep Rybka 3 working perfectly with Winboard 4.2.7 however still doesn't work.

I tried the following in winboard.ini:

DeepRybka3w32 /fd="../Rybka3" /fUCI

and also

"polyglotXXX ../Rybka3/rybka3.ini"

with XXX being the polyglot version (exactly the same as the fruit example setup when you install Winboard 4.4.3)


Can anybody help me fix this?

Much appreciated.

Thanks
Al Nicholls

Deep Rybka 3 barfs if argv[0] doesn't contain the path, which is probably the case here.

Thanks for that but how do I set argv[0] for Deep Rybka 3?

Unbelieveably I've just fixed the error however it is a hack and hoping there is a better way. I'm particularly interested in Teemu's response as maybe this is the real fix I just don't know how to set argv[0], does anybody know?

Anyway here is my fix. I did the following.

The proper way for Winboard 4.4.3 doesn't work with Rybka 3, for example:

DeepRybka3w32 /fd="../Rybka3" /fUCI fails.

However if I change this to the way older versions of Winboard worked like this:

-cp -fcp polyglot /fd="../Rybka3"

it works! Took me a long time to figure this one out and it seems the /UCI flags fail with Deep Rybka 3, maybe. The downside with this is that I need a separate copy of polyglot.exe and polyglot.ini in the folder Rybka3.

Is this a known bug? Can somebody fix it?

Thanks

Alistair

When you give the engine name, give the full path.
e.g. something like this:
C:\chess\winboard\Rybka\Rybkav2.3.2a.mp.x64.exe

You don't need to give the full path. A relative path will do just fine. Here is what I have for regular Rybka3:
"Rybka 3 w32.exe" /fd="Engine\Rybka3" -fUCI

Try adding .exe to the engine name. For some reason it fails without it. Also stick it in quotes for good measure, although it shouldn't make a difference if it is only one word but who knows. I don't know anything about an argv[0] setting but I'm pretty positive this will fix your problem.