g00r00,

Did something change with the startup.mps during one of the pre-alpha's? It does not seem to allow me to run a GY command like I had before but it does
run the remaining commands.

Thanks!

|15:|07: |15pequito |08<|07<|14.|11PH|15EN|11OM|14.|07>|08> |07:|15: |15:|07: |02telnet://|10twinklebbs.net |07:|15:

--- Mystic BBS v1.12 A43 2019/02/17 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

Did something change with the startup.mps during one of the pre-alpha's? It does not seem to allow me to run a GY command like I had before but
it does run the remaining commands.

I investigated this issue and here are my observations to help in the troubleshooting.

For this test, content of startup.mps is:

Begin
MenuCmd('GY', 'threatsentry')
End

Now, when I strace Mystic on start, I see it loads Python and at some point
it tried to open threatsentry.mpy but the open call looks very odd:

----CUT----

open("/home/mystic/mystic/scripts/threatsentry.mpy&4=to &5=subject &6=base name\r\n533 |15|$L02|&1 |11|&2 |14|$R25|&6 |10|$R35|&5\r\n; Message draft prompt &1 = high draft #\r\n534 |CR|09Select draft to resume (|111|09-|11|&1|09), (|11D|09)elete, or (|11Q|09)u,/home/mystic/mystic/scripts/threatsentry.mpy|12You have |15|MF
&:A", O_RDONLY) = -1 ENOENT (No such file or directory)

----CUT----

As you can see, the filename appears to have a portion of the prompts in it.

This is from a stock test BBS freshly upgraded to A43.
A42 works fine with the exact same code.

Once posted, if it's unreadable with the PIPE codes, I'll send it over by
email too.

Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A42 2019/02/01 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

On 19 Feb 2019, Pequito said the following...

Did something change with the startup.mps during one of the pre-alpha's? It does not seem to allow me to run a GY command like I had before but
it does run the remaining commands.

Mine stopped working as well when I upgraded to the latest pre-alpha this weekend.

Immortal

--- Mystic BBS v1.12 A43 2019/02/15 (Linux/64)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 19 Feb 2019, Immortal said the following...

Mine stopped working as well when I upgraded to the latest pre-alpha this weekend.
--- Mystic BBS v1.12 A43 2019/02/15 (Linux/64)

2019/02/17 is the latest i believe...

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic
|08[|15bbs|09.|15dreamlandbbs|09.|15org|08]

--- Mystic BBS v1.12 A43 2019/02/17 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

Did something change with the startup.mps during one of the pre-alpha's? It does not seem to allow me to run a GY command like I had before but
it does run the remaining commands.

I've not done anything with startup.mps in maybe around 20 years so its probably not specific to that.

--- Mystic BBS v1.12 A43 2019/02/17 (Linux/64)
* Origin: Sector 7 (21:1/108)

Did something change with the startup.mps during one of the pre-alpha It does not seem to allow me to run a GY command like I had before bu it does run the remaining commands.

I investigated this issue and here are my observations to help in the troubleshooting.

Thanks for the details!

Try upgrading to the latest A43 version and see if that helps. I also
changed the logging to log the path/file on the node log so we can see there
if its corrupted if it still doesn't work.

--- Mystic BBS v1.12 A43 2019/02/17 (Linux/64)
* Origin: Sector 7 (21:1/108)

Did something change with the startup.mps during one of the pre- It does not seem to allow me to run a GY command like I had befo it does run the remaining commands.

I investigated this issue and here are my observations to help in the troubleshooting.

Thanks for the details!

Try upgrading to the latest A43 version and see if that helps. I also changed the logging to log the path/file on the node log so we can see there if its corrupted if it still doesn't work.

New a43 of this morning fixes the issue, now it behave as expected.

Thanks a lot.

Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A42 2019/02/01 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (21:1/172)

On 20 Feb 2019, g00r00 said the following...

Did something change with the startup.mps during one of the pre- It does not seem to allow me to run a GY command like I had befo it does run the remaining commands.

I investigated this issue and here are my observations to help in the troubleshooting.

Thanks for the details!

Try upgrading to the latest A43 version and see if that helps. I also changed the logging to log the path/file on the node log so we can see there if its corrupted if it still doesn't work.

This seems to work, and able to run the startup without any issues again. =D

|15:|07: |15pequito |08<|07<|14.|11PH|15EN|11OM|14.|07>|08> |07:|15: |15:|07: |02telnet://|10twinklebbs.net |07:|15:

--- Mystic BBS v1.12 A43 2019/02/20 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

Try upgrading to the latest A43 version and see if that helps. I als changed the logging to log the path/file on the node log so we can se there if its corrupted if it still doesn't work.

New a43 of this morning fixes the issue, now it behave as expected.

Thanks a lot.

Awesome I took a guess on that one glad to here I guessed right! :)

--- Mystic BBS v1.12 A43 2019/02/17 (Linux/64)
* Origin: Sector 7 (21:1/108)