• Switched to Mystic

    From Matt Ianson@21:3/185 to All on Friday, April 26, 2024 07:29:55
    Hi All

    Starting to get back into hosting a BBS since pulling the pin about 30 years ago. Used to run on an Amiga back in the day (and even looked at emulating it, etc as there is still some dev on the software I was working on).

    However switched to Synchro, and now to Mystic (which I have landed on). BBS is running however more or less in a stock format at the moment while I get functionality in.

    Couple of questions:

    - I'm running on Windows (was originally under linux), due to possibly better DOS emulation being available (linux and dosemu seems to be problematic?). I'm comfortable in either environment so what is the opinion out there - windows or linux?

    - Python: I just don't get the setup. Understanding that there is some built into Mystic, but you need to install either 2 or 3. I keep getting some errors either though I have 2.7 installed (more from the thoughts that it will be more compatible with older scripts?). Typical error tha I am seeing relates to the "Python C API Mismatch". No real idea why though.

    - Resources: Seem to pick through the wiki, Avon's YT videos and other old content online. Any suggestions on best places for scripts, etc?

    Next steps will be "making it my own" - but as with anything, want to make sure the base is solid before building...

    Cheers!

    ... BREAKFAST.COM Halted... Cereal port not responding.

    --- Mystic BBS v1.12 A48 (Windows/64)
    * Origin: Retroverse BBS - bbs.retroverse.au:24554 (21:3/185)
  • From Accession@21:1/200 to Matt Ianson on Friday, April 26, 2024 17:26:14
    Hello Matt,

    On Fri, Apr 26 2024 02:29:54 +0000, you wrote:

    - I'm running on Windows (was originally under linux), due to possibly better DOS emulation being available (linux and dosemu seems to be problematic?). I'm comfortable in either environment so what is the opinion out there - windows or linux?

    I don't think there's much issue in either one, to be honest. I think the most problems lie with 64bit Windows, though.

    - Python: I just don't get the setup. Understanding that there is some built into Mystic, but you need to install either 2 or 3. I keep getting some errors either though I have 2.7 installed (more from the thoughts that it will be more compatible with older scripts?). Typical error tha
    I am seeing relates to the "Python C API Mismatch". No real idea why though.

    If I remember right, I believe Python2 is the way to go with Mystic. Still too many issues with Mystic and Python3.

    As for your "Python C API Mismatch" issue, You mentioned you're running Windows, check the Mystic wiki and/or documentation on putting a (or some) DLL files in a location Mystic will see them.

    - Resources: Seem to pick through the wiki, Avon's YT videos and other
    old content online. Any suggestions on best places for scripts, etc?

    Best place for scripts? the /scripts subdirectory, of course! Or are you looking for more documentation? whatsnew.txt and the wiki are probably your best bets.

    Next steps will be "making it my own" - but as with anything, want to
    make sure the base is solid before building...

    While solidifying that base, please make sure to not flood FSX net messages into Dovenet any more. Not sure if you recently changed your BBSID from RETROVRS to RETRO, but if so, I believe your QWKnet account has been given posting restrictions on Dovenet until you fix whatever it was you're working on, FYI.

    Regards,
    Nick

    ... Take my advice, I don't use it anyway.
    --- slrn/pre1.0.4-9 (Linux)
    * Origin: _thePharcyde distribution system (Wisconsin) (21:1/200)
  • From Matt Ianson@21:3/185 to Accession on Saturday, April 27, 2024 11:49:01
    I don't think there's much issue in either one, to be honest. I think
    the most problems lie with 64bit Windows, though.

    So better to be running under 32 than 64? Any particular reasons (other than potentially dos door issues?)

    As for your "Python C API Mismatch" issue, You mentioned you're running Windows, check the Mystic wiki and/or documentation on putting a (or
    some) DLL files in a location Mystic will see them.

    For some reason that error went away. It has been when I've been trying to get old scripts to play nicely, so perhaps I have finally overcome the issues with the python install. I had tried dropping the DLL into the root dir and also referncing it in the config (which threw a completely different error).

    Best place for scripts? the /scripts subdirectory, of course! Or are you

    Ahh, should have clarified this - more for actual mystic scripts for running on the BBS (to get it away from stock build).

    While solidifying that base, please make sure to not flood FSX net Ac> messages into Dovenet any more. Not sure if you recently changed your

    Absolutley unaware of this! I don't recall seeing any issues on my end, so not sure why.where this would be happening...

    Perhaps it was while I was getting the messge areas all setup - however had left DOVE until the end. Unsure if it is still happening or was while I was just setting up the configs...

    I'll double check the config and if someone can let me know if it is still happening, I'll pull dove for the time being..

    Cheers
    Blinx

    ... Real Programmers balance their checkbooks in hex

    --- Mystic BBS v1.12 A48 (Windows/64)
    * Origin: Retroverse BBS - bbs.retroverse.au:24554 (21:3/185)
  • From Accession@21:1/200 to Matt Ianson on Saturday, April 27, 2024 07:19:16
    Hello Matt,

    On Sat, Apr 27 2024 06:49:00 +0000, you wrote:

    So better to be running under 32 than 64? Any particular reasons (other than potentially dos door issues?)

    Really, *only* because of the potential dos door issues. But then again, now there is Doorparty and BBSLink, if you would rather just link to those rather than having to setup 100s of local door games that may never get used.

    Ahh, should have clarified this - more for actual mystic scripts for running on the BBS (to get it away from stock build).

    I see. Besides what is already in the scripts directory after install, you can check the Phenom website, https://www.phenomprod.com/Mods. And if there's anywhere else maybe others can chime in. When I was modding Mystic, I had done all of the mods myself, and never bothered packaging them up for a release of any kind. :(

    While solidifying that base, please make sure to not flood FSX net
    messages into Dovenet any more. Not sure if you recently changed your

    Absolutley unaware of this! I don't recall seeing any issues on my end,
    so not sure why.where this would be happening...

    This is the first place I saw you post, so I figured I'd try to get your attention!

    Perhaps it was while I was getting the messge areas all setup - however had left DOVE until the end. Unsure if it is still happening or was
    while I was just setting up the configs...

    Maybe it was while you were setting up Dovenet, it happened. And for more specifics, I think it was from this echo, "FSX_MYS", and I'm fairly certain those messages were flooded into Dovenet General. So those two areas would be a good place to start looking.

    I'll double check the config and if someone can let me know if it is
    still happening, I'll pull dove for the time being..

    Like I was trying to tell you, I believe your system had it's posting priviledges removed temporarily by Digital Man. Give your config a combover and make sure everything is good, then you will probably have to contact Rob/DM to lift the block.

    Was your BBSID RETROVRS?

    Is your BBSID now RETRO?

    This flood happened twice. The first time was from the bbsid RETROVRS. The second time it was from bbsid RETRO. I had just assumed it was your system both times, but if it wasn't - that would be good to know so someone can track down the other system, too.

    Regards,
    Nick

    ... Take my advice, I don't use it anyway.
    --- slrn/pre1.0.4-9 (Linux)
    * Origin: _thePharcyde distribution system (Wisconsin) (21:1/200)