This has happened repeatedly after I unpack and install a new version of mystic via "sudo ./install" to /nmystic from mys112a31_l64.rar bcw@Lenotv:/nmystic $ ./mystic -cfg
(A couple of odd characters)ERROR: No theme configuration
That's the result of trying to do anything with it. The real purpose was to get the executables and such to upgrade A30 which worked fine, but it should run. What am I doing wrong?

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

This has happened repeatedly after I unpack and install a new version of mystic via "sudo ./install" to /nmystic from mys112a31_l64.rar

are you extracting the mys112a31_l64.rar or just opening it and trying to run the install?



--- Mystic BBS v1.12 A31 (Linux)
* Origin: SmokyThing BBS (21:1/142)

Hello bcw142,

This has happened repeatedly after I unpack and install a new version of mystic via "sudo ./install" to /nmystic from mys112a31_l64.rar

Why install as root using sudo? I run "./install" as the user that Mystic will
run as. In my case, as user "bbs".

Here on my Lin64 Mystic machine. I unrar the Mystic archive to a different directory. In my case /home/bbs/myst. After running ./install as user "bbs" the
newer Mystic gets installed to /home/bbs/myst/mystic. If being installed as an
upgrade I don't run /mystic -cfg. I just copy n replace the necessary executables and any other necessary files.

I tried your procedure as you described above and installed Mystic as "Root" and got the same results as you did. When I installed Mystic as a non root user
Mystic installed and I was able to load "Mystic -cfg without and problems.

Jeff



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

On 08/05/16, Gandor said the following...

This has happened repeatedly after I unpack and install a new version mystic via "sudo ./install" to /nmystic from mys112a31_l64.rar

are you extracting the mys112a31_l64.rar or just opening it and trying
to run the install?

I do the install to /nmystic then "cd /nmystic", followed by "./mystic -cfg" and the error ESC(UERROR: No theme configuration

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

This has happened repeatedly after I unpack and install a new ve mystic via "sudo ./install" to /nmystic from mys112a31_l64.rar

are you extracting the mys112a31_l64.rar or just opening it and tryin to run the install?

I do the install to /nmystic then "cd /nmystic", followed by "./mystic -cfg" and the error ESC(UERROR: No theme configuration

check you permissions sounds like you are trying to run ./mystic -cfg as a
user when you installed it with sudo likely setting the permissions to root



--- Mystic BBS v1.12 A31 (Linux)
* Origin: SmokyThing BBS (21:1/142)

On 08/05/16, Gandor said the following...

check you permissions sounds like you are trying to run ./mystic -cfg as
a user when you installed it with sudo likely setting the permissions to root
--- Mystic BBS v1.12 A31 (Linux)
* Origin: SmokyThing BBS (21:1/142)

Yup. Looks like that's it. I tried sudo ./mystic -cfg and it came up. I got confused by the fact that /mystic worked when I copied the same executables over as pi it works. Not thinking about creating it with sudo, that's permissions in Linux ;)

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

Yup. Looks like that's it. I tried sudo ./mystic -cfg and it came up. I got confused by the fact that /mystic worked when I copied the same executables over as pi it works. Not thinking about creating it with
sudo, that's permissions in Linux ;)

Glad you got it going... yeah permissions are easy to miss / mess up I feel your pain there. I run my mis in deamon mode via an init.d script and every time I start mystic the script resets all the permission just in case I goof something up ... I have goofed before its easy to do :)



--- Mystic BBS v1.12 A31 (Linux)
* Origin: SmokyThing BBS (21:1/142)