Ah, both solutions work perfectly! chmod +x and the direct executable
path works! So does wine with the exe path in the parameters!
many, many thanks!
Sam
On Mon, Aug 15, 2011 at 7:28 PM, Larry Isaacs wrote:
> What happens if you run the just the executable path in a terminal. If
> you se
What happens if you run the just the executable path in a terminal. If
you see "Permission denied", it probably means you need to enable the
"Execute" permission. I think Wine can run program files without the
executable bit being set, but since the engine is only doing console
I/O, it doesn't ap
Le 15 août 2011 à 13:11, Sam Copeland a écrit :
> Interesting, I tried just the exe path, but I still get the same error
> message.
>
> Sam
Hi there,
Personally I have to use the full *absolute* path to wine in "command"
(/opt/local/bin/wine =>installed with macport)
then something like
Interesting, I tried just the exe path, but I still get the same error
message.
Sam
On Mon, Aug 15, 2011 at 7:19 AM, Larry Isaacs wrote:
> I didn't include "wine", just the exe path. My command is just:
>
> /home/larry/Games/Chess/Engines/Houdini_15a_w32.exe
>
> I would expect the followin
I didn't include "wine", just the exe path. My command is just:
/home/larry/Games/Chess/Engines/Houdini_15a_w32.exe
I would expect the following to work for you:
/home/miller/Software/Houdini_15a/Houdini_15a_w32.exe
It has been a while, but I seem to recall avoiding the double quotes and
backs
