Hello There,

I am currently running both the Win32 and
the Lin64 versions of Mystic A36.

While monitoring event execution on both
systems I am seeing different result codes
when the event processes exit/complete.

In Windows 32b I see "Process result 127"
while in Linux 64b I see "Process result 0"


I do not see any mention of result codes in
the Mystic docs or it's significance if any.




Jeff

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Fsxnet: The Ouijaboard III (21:1/128.2)

On 10/28/17, JeffS pondered and said...

In Windows 32b I see "Process result 127"

Has not run correctly... check the way you call the shell line and the
pathing syntax :)

while in Linux 64b I see "Process result 0"

Working fine :)

Best, Paul

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hello Avon,

On 10/28/17, JeffS pondered and said...

In Windows 32b I see "Process result 127"

Has not run correctly... check the way you call the shell line and the pathing syntax :)

Yeah, that makes sense. I guess I am a tad rusty when it comes to
Windows as I don't work with it that much in recent years.

while in Linux 64b I see "Process result 0"

Working fine :)

Kewl. Thanks


Jeff

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Fsxnet: The Ouijaboard III (21:1/128.2)

In Windows 32b I see "Process result 127"
while in Linux 64b I see "Process result 0"

They're from the operating system or the program that ran, not Mystic.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hello g00r00,

In Windows 32b I see "Process result 127"
while in Linux 64b I see "Process result 0"

They're from the operating system or the program that ran, not Mystic.

In my case in both instances the programs were FIDOPOLL and MUTIL that were run
as MIS event tasks. Once I included the full path to the executable then the process result changed to zero.


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

In my case in both instances the programs were FIDOPOLL and MUTIL that were run as MIS event tasks. Once I included the full path to the executable then the process result changed to zero.

Yep error 127 is returned by "bash" and it means "command not found"...
usually that just means you need to put a path in there, or you have a typo, etc.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)