Ok.. I got Nov. 30 Windows 32 Mystic pre alpha installed and running good.
So i went to upgrade the Pi version for my other board. I must have missed something because after i copied over the files and stuff it read version A35 :(. I noticed it had BOTH mis and mis2 in there where the Windows version had just the mis. Can someone explain the right way to get the pre alpha going
on my Pi? Or what i may have missed?

Lucky i backed my Pi version up :) Had to restore it after my snafoo.

I need to get to Wizard level. Thanks mates.. + YARR

²ß±ß° {tHE.pIRATE.kING} ÜßÛßÜ
ß²Ü°ß HOIST THE COLOURS ßÛÜÛß
þþþ NEVER SHALL WE DIE. ÝÝÞ

--- Mystic BBS v1.12 A36 2017/11/30 (Windows/32)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

the Windows version had just the mis. Can someone explain the right way
to get the pre alpha going on my Pi? Or what i may have missed?

I only compile a Pi version once every week or two because it takes a lot of effort/time to do it.

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

I only compile a Pi version once every week or two because it takes a
lot of effort/time to do it.

Ok i didn't realize that. I'll hold off until the final A36 alpha for the Pi

²ß±ß° {tHE.pIRATE.kING} ÜßÛßÜ
ß²Ü°ß HOIST THE COLOURS ßÛÜÛß
þþþ NEVER SHALL WE DIE. ÝÝÞ

--- Mystic BBS v1.12 A36 2017/11/30 (Windows/32)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

Caphood wrote to All <=-

Ok.. I got Nov. 30 Windows 32 Mystic pre alpha installed and running
good. So i went to upgrade the Pi version for my other board. I must
have missed something because after i copied over the files and stuff
it read version A35 :(. I noticed it had BOTH mis and mis2 in there
where the Windows version had just the mis. Can someone explain the
right way to get the pre alpha going on my Pi? Or what i may have
missed?

WHat vwrsion are you upgrading from? I upgraded from A35 to A36 on my Pi, and had to do the following (not mentioned in upgrade.txt, which only says to copy in the new binaries):

Recomple MPLs -
cd /mystic/scripts
./mplc -all

Delete /mystic/mis2 (to avoid it being run by accident).

Change startup and monitoring scripts to remove references to mis2 and change the mis startup option from "-d" to "DAEMON".

Configure "missing" servers in Mystic's configuration. I was already using MIS2 (now MIS) for telnet, SSH, Rlogin and binkp. I had to add a server entry for NNTP, SMTP, POP3 and FTP. This can be done using mystic -cfg or the sysop menu when logged in. You need to restart mis when done.

I haven't investigated the A37 prealphas yet, will wait for A37. :)


... A Canadian? It's like an American, without the gun, with health care.
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)