Hi code dc!
On 20 Feb 2020, code dc said the following...
yes it shows 127.
It might be that you are launching fidopoll as "fidopoll" instead of "./fidopoll" -- Mystic switches to the Mystic "root" directory
when executing events, and unless you have that directory (or "." =
always the current directory) somewhere in the Mystic user's PATH, you
need to invoke fidopoll with "./fidopoll" on Linux, or it won't find
the fidopoll binary.
Hope this helps! :)
(I'm actually not 100% sure that adding the Mystic "root" directory to PATH would help either -- depending on how Mystic launches the shell, it might be that it does not read ~/.profile or ~/.bashrc or similar, where one typically sets the PATH.)
Best regards
Zip
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)