Subj : Re: Debian Linux 10 w/Python 64-bit - Mystic scripts require Python 32 To : Adept From : dejavu Date : Mon Jun 15 2020 21:29:11 On 16 Jun 2020, Adept said the following... Ad> de> Good afternoon Gents, Ad> Ad> ...is this a boys' club thing? Ad> My apologizes, good evening Ladies :) I'll correct that moving forward. Ad> de> Error seen prior to logging into the BBS: Ad> de> Python 2.7 32-bit not detected, press a key. Ad> Ad> Did you follow the directions on the mysticbbs wiki? Ad> wiki.mysticbbs.com/doku.php?id=python_install Ad> Apparently not well enough. I'll go back and RTFM once again. Ad> There's even a bit about Ubuntu issues that can sometimes crop up. I Ad> used it, though I don't know if it solved my issue (and I also wound up Ad> on 2.7.18 rather than 2.7.15). Ad> That's my first issue, I choose to use Debian 10 verus Ubuntu... Ad> Beyond that, I'd be inclined to run "which python" and see what comes Ad> up, if I was trying to diagnose the problem. Ad> 'which python' isn't very helpful, output is: '/usr/bin/python' Ad> For me, the problem that I got stuck on the longest was getting Python to Ad> _do_ anything, rather than just not give errors. And I think that was Ad> caused by having scripts in the old location, rather than under the Ad> themes directory structure. Ad> I resolved the issue of /mystic/scripts, versus where they should be in /mystic/themes/default/scripts/ a few days ago. I don't understand why all the instructions indicate you put the scripts in /mystic/scripts/? It doesn't help the new Mystic users. Unfortunately moving the scripts to the proper scripts directory doesn't resolve the issue of the scripts not executing at all. In my case the system is screaming there is no Python installed. Thanks for the response, I'll RTFM again and see if there is something I overlooked. -Dejavu Ad> --- Mystic BBS v1.12 A45 2020/02/18 (Linux/64) Ad> * Origin: Storm BBS (21:2/108) --- Mystic BBS v1.12 A45 2020/02/18 (Linux/32) * Origin: 1984 BBS [1984bbs.net] Washington, DC (21:3/114) .