From bcw142@21:1/145.1 to g00r00 on Saturday, March 17, 2018 09:56:21
Great error checking! I had nodespy problems with my inital update to A39 on Windows 10 64 bit, but 'mystic -ver' showed that my batch file didn't run or copy upgrade.exe correctly, I ran that and found nodespy was old, updated
that and I'm using nodespy to type this on my old 1.11 Nystic BBS that I run
as a point off my main. Nodespy isn't running locally or something is still wrong with the upgrade from A38 to A39 on my Windows 10 setup, but I need to check everything over vs the upgrade.txt before I can say there's any issues with v1.12 A39 Windows/64 Compiled 2018/03/12 12:51:05 which is what I just tried to upgrade to. I can say mystic -ver and mystic -cfg are both working fine for me only due to the added error checking ;)
--- Mystic BBS v1.11 (Raspberry Pi)
* Origin: Old Mystic Pi BBS bcw142.zapto.org:2324 (21:1/145.1)