greetz g00r00 -

When upgrading / updating to a39 I loose mystic -cfg (just goes black screen)

My first go I copied all the binarys , ran update, mplc , and added lines to the default.txt, Mystic server will load fine and I can log into the bbs but mystic -cfg will not work ( just goes black screen )

My second try I renamed install to go and tried the auto update somthing like go replace c:\mystic and got can not find mystic.dat error .

Third test I installed a39 cold , just a stock install and mystic -cfg everything worked fine .

so I am stuck at a38 not sure how to get around this .

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
* Origin: Error 404 BBS (21:1/102)

On 03/17/18, solaris said the following...

When upgrading / updating to a39 I loose mystic -cfg (just goes black screen)

I'm having issues with nodespy on a39, but it's likely me since I don't see others having issues. When you do mystic -ver what shows up? G00r00 has added error checking in to things like that which helped me enough that I'm using Windows 10 64bit nodespy to send this. Check all the exe's got updated, upgrade.exe is correct and was run, and default.exe got copied over or the added prompts were added. I can say that mystic -cfg is working normally for me under v1.12 A39 Windows/64 Compiled 2018/03/12 12:51:05 and that is what shows when I do mystic -ver

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)