Help with command line

[elorejano]

Hi!
I want to use Typhoon engine by Scott Gasch, but have problems with the command line in winboaed.ini
Can somebody post the right COMPETE line in winboard.ini fot Typhoon?
Thanks in advance

[Richard Allbert]

/firstChessProgramNames={
"typhoon" -fcp typhoon -fd "C:/Chess/typhoon"
}

[elorejano]

Thanks but im reffering with hash and egtb paths
Manual guide say for hash

--hash 128
and fot egtb path

--egtbpath "e:\TB"
but this commands makes a colision with "
And both commands have to be separated with --??
Any ides?

[H.G.Muller]

Why don't you simply browse to the typhoon.exe for engine file in the Load Engine dialog, and then type in the command-line parameters field

--hash 128 --egtbpath "e:\TB"

before pressing 'OK', and then look with Edit Engine List to see what WinBoard has written in the winboard.ini file?

[elorejano]

Because i use "old" winboard + Thomas McBurney tool EngMan
My typhoon line is

"Typhoon --hash 128M--egtbpath " /fd="e:\winboard\engines\typhoon" ; /name="Typhoon"

See? the quotes are the problem, because typhoon use quotes for TBs location and winboard use this for engines path, then

"Typhoon --hash 128M--egtbpath "E:\TB"" /fd="e:\winboard\engines\typhoon" ; /name="Typhoon"

This produces colision between two quotes ("") and winboard refuse it

Nobody use Typhoon?

[H.G.Muller]

Because i use "old" winboard + Thomas McBurney tool EngMan

Yeah, that is what you get, using stone-age tools when there are space craft...

The trick is that you can use 3 different ways to 'quote' strings that would otherwise be seen as multiple entities: single quotes, double quotes, or braces {}. The latter only work at the outer level, and do not allow nesting: everything between them is taken totally literally. Single and double quotes can be nested, and can be escaped with a back-slash when you want them to occur literally in a quoted string.

So to prevent the conflict between the various levels of quoting you should use

'Typhoon --hash 128 --egtbpath "e:\TB"' -fd "e:\winboard\engines\typhoon"

i.e. use sigle quotes to 'protect' the engine command to not conflict with the double quotes you used to protect the egtb path name. In the current case it seems that path name does not really need protection (it contains no spaces), so you could probably have left out those double quotes, and then it would not have mattered which quotes you used around the entire engine command.

Of course the best thing to do would be to complain to Scott that his engine needs those silly command-line options, rather than supporting the memory and egtpath commands to let WinBoard set them.

[Edit] Perhaps it would be better to use {} as outer quoting, rather than single quotes, because there is a backslash somewhere inside the command, and it might not behave inside quotes as you want. So:

{Typhoon --hash 128 --egtbpath "e:\TB"} -fd "e:\winboard\engines\typhoon"

[elorejano]

I agre with you, Scott have to change this.
Any of those option works.
I dont believe: any winboarder have tried Typhoon?