• Updates

    From Ib Joe@1:342/201 to All on Fri Nov 9 18:09:13 2018
    Are there people having the same problem I've had, it doesn't make sense to me.
    If I run mystic Alpha 35, the version I ran for some time... the BBS worked fine. I updated to the current version Alpha 39 and now I cannot have my fidonet, or any any FTN address, be saved...

    Is anyone having problems, or is there something I'm over looking??

    Thanx
    IB Joe
    AKA Joe Schweier
    SysOp of Joe's Computer & BBS
    Since 1991 joesbbs.com
    --- SBBSecho 3.05-Linux
    * Origin: Joe's Computer & BBS (1:342/201)
  • From Dan Richter@1:317/3 to Ib Joe on Fri Nov 9 20:06:45 2018
    On 11/09/18, Ib Joe said the following...

    Are there people having the same problem I've had, it doesn't make sense to me. If I run mystic Alpha 35, the version I ran for some time... the BBS worked fine. I updated to the current version Alpha 39 and now I cannot have my fidonet, or any any FTN address, be saved...

    Is anyone having problems, or is there something I'm over looking??

    Try setting the address in the second space down. The first one is reserved
    for a local address.

    It's something that caught a lot of us off-guard...


    ---

    Black Panther
    a.k.a. Dan Richter
    Sysop - Castle Rock BBS (RCS)
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again....

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (1:317/3)
  • From Paul Quinn@3:640/1384 to Dan Richter on Sat Nov 10 15:20:17 2018
    Hi! Dan,

    On 09 Nov 18 20:06, you wrote to Ib Joe:

    Is anyone having problems, or is there something I'm over
    looking??

    Try setting the address in the second space down. The first one is reserved for a local address.

    It's something that caught a lot of us off-guard...

    +2

    It got me twice on two different Linux configs. It was then I twigged to having to RTFM (in fact: little print in some readme/manual type doc). I haven't got back to polish-off the third config yet but I'll twist its tail in the coming weeks.

    Cheers,
    Paul.

    ... Features should be discovered, not documented.
    --- GoldED+/LNX 1.1.5-b20130515
    * Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)
  • From Ib Joe@1:342/201 to Dan Richter on Sat Nov 10 09:17:58 2018
    Re: Re: Updates
    By: Dan Richter to Ib Joe on Fri Nov 09 2018 08:06 pm

    Is anyone having problems, or is there something I'm over looking??

    Try setting the address in the second space down. The first one is reserved for a local address.

    It's something that caught a lot of us off-guard...

    I did that... I have found and install copy of A35 and it works, to have a FTN address, I upgrade to A39 I cannot put one in where it saves. I did a fresh install of A39, same thing. I just found a copy of the A35 hanging around and it works fine, I can add a FTN address in.

    :)
    IB Joe
    AKA Joe Schweier
    SysOp of Joe's Computer & BBS
    Since 1991 joesbbs.com
    --- SBBSecho 3.05-Linux
    * Origin: Joe's Computer & BBS (1:342/201)
  • From Todd Yatzook@1:142/799 to Ib Joe on Sat Nov 10 12:03:27 2018
    On 11/10/18, Ib Joe said the following...

    It's something that caught a lot of us off-guard...

    I did that... I have found and install copy of A35 and it works, to have
    a FTN address, I upgrade to A39 I cannot put one in where it saves. I
    did a fresh install of A39, same thing. I just found a copy of the A35 hanging around and it works fine, I can add a FTN address in.

    Is it running on Linux, and have you recursively changed ownership/execution
    of the entire directory and files within? It might be one/both of those. a35 might be using a different data file to store the addresses, which might already have rwx and ownership.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)
  • From mark lewis@1:3634/12.73 to Ib Joe on Sat Nov 10 11:22:14 2018
    On 2018 Nov 09 18:09:12, you wrote to All:

    Is anyone having problems, or is there something I'm over looking??

    are you remembering that new mystic versions have to be ""installed"" to a *temp* directory? then you copy over the new binaries, recompile the scripts, and update the default ""language"" file with new additions by overwriting it like you do with the binaries or if you have modified it you edit yours to fill
    in the new prompts/phrasess/words...

    it has been a long time since i've updated a mystic setup but you definitely must install the new version to a temp directory and then copy the binaries over and recompile the scripts... that much i definitely remember ;)

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Click...click...click..damn, out of taglines!
    ---
    * Origin: (1:3634/12.73)
  • From Jeff Smith@1:282/1031 to Mark Lewis on Sat Nov 10 12:04:20 2018
    Hello mark,

    are you remembering that new mystic versions have to be ""installed"" to a *temp* directory? then you copy over the new binaries, recompile the scripts, and update the default ""language"" file with new additions by overwriting it
    like you do with the binaries or if you have modified it you edit yours to fil
    in the new prompts/phrasess/words...

    it has been a long time since i've updated a mystic setup but you definitely must install the new version to a temp directory and then copy the binaries over and recompile the scripts... that much i definitely remember ;)

    The one addition I would make is that if it were a fresh install the install directory must not already exist or the install would fail. I can't recall if g00r00 made an update to allow a pre-existing directory or not. I recall running into that situation with linux installs of Mystic a couple times. I had
    to let Mystic create the /home/mystic install directory and then create the user "mystic" in linux. I know this scenario is different from the update procedure.

    Jeff

    --- BBBS/Li6 v4.10 Toy-3
    * Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.ne\ (1:282/1031)
  • From Ib Joe@1:342/201 to Todd Yatzook on Sat Nov 10 11:17:48 2018
    Re: Re: Updates
    By: Todd Yatzook to Ib Joe on Sat Nov 10 2018 12:03 pm

    Is it running on Linux, and have you recursively changed ownership/execution of the entire directory and files within? It might be one/both of those. a35 might be using a different data file to store the addresses, which might already have rwx and ownership.


    I'm starting to hate linux... :) I have installed A39 on my Windows 10 32Bit vertual box and, last night, installed it on my Windows 10 64Bit host and I get the same. I enter in my address, or any for the matter, I fill it out complete ... and it dose not save when I back out.

    :)
    IB Joe
    AKA Joe Schweier
    SysOp of Joe's Computer & BBS
    Since 1991 joesbbs.com
    --- SBBSecho 3.05-Linux
    * Origin: Joe's Computer & BBS (1:342/201)
  • From Tony Langdon@3:633/410 to mark lewis on Sun Nov 11 07:32:00 2018
    On 11-10-18 11:22, mark lewis wrote to Ib Joe <=-

    it has been a long time since i've updated a mystic setup but you definitely must install the new version to a temp directory and then
    copy the binaries over and recompile the scripts... that much i
    definitely remember ;)

    In short, follow ALL of the instructions for upgrading from A35 to A39, which as Mark (quoted above) says above starts with installing into a temporary directory and copying the binaries. The steps beyond that vary, depending on the exact upgrade you're doing, but are detailed. Look for the section in the upgrading document for upgrading from A35, and complete ALL of those steps. It should work perfectly once done.

    There have been many changes since A35, I think the upgrade list will be particularly extensive. Yep, I've found the relevant upgrade docs for the OP's benefit.You don't have to upgrade incrementally, but ensure that ALL the steps mentioned have been performed.


    .-----------------------------------.
    | UPGRADING FROM 1.12 A29-35 to A36 |-------------------------
    `-----------------------------------'

    - Replace existing binaries with the new alpha binaries:

    mystic.exe
    mis.exe
    fidopoll.exe
    mutil.exe
    mbbsutil.exe
    nodespy.exe
    qwkpoll.exe
    mplc.exe (in scripts directory)
    mide.exe (in scripts directory)

    - Delete mis2.exe (the old mis is now gone and mis2 is now named mis) so
    you will need to be aware of that and possibly reconfigure your servers
    in the System Configuration and edit any auto-start scripts you may use
    - Recompile all MPL programs (run mplc -all in scripts directory)
    - Note that the phonebook in NodeSpy has changed slightly in A35, and in
    some cases you may need to edit out the "port" from the address field
    if you use NodeSpy's Terminal.


    .------------------------------------.
    | UPGRADING FROM 1.12 A36 to A37/A38 |-------------------------
    `------------------------------------'

    - Replace existing binaries with the new alpha binaries:

    mystic.exe
    mis.exe
    fidopoll.exe
    mutil.exe
    nodespy.exe
    qwkpoll.exe
    upgrade.exe
    mplc.exe (in scripts directory)
    mide.exe (in scripts directory)

    - Run upgrade.exe once to update your data files then you can
    delete it.
    - Copy cfgroot1.ans, cfgroot2.ans, and cfgroot3.ans to your DATA directory
    - mbbsutil.exe is no longer used, delete it from your Mystic directory

    .------------------------------------.
    | UPGRADING FROM 1.12 A37/A38 to A39 |-------------------------
    `------------------------------------'

    - Replace existing binaries with the new alpha binaries:

    mystic.exe
    mis.exe
    fidopoll.exe
    mutil.exe
    nodespy.exe
    qwkpoll.exe
    upgrade.exe
    mplc.exe (in scripts directory)
    mide.exe (in scripts directory)

    - Run upgrade.exe once to update your data files then you can
    delete it.

    - Add prompts #528-#537 to the prompt file for all themes you have
    on your BBS. If you use the default prompts and have not customized,
    then you can simply replace default.txt in the DATA folder with that
    from the fresh installation. These new prompts can be found below or
    in default.txt in the fresh installation. See whatsnew for more
    information.

    - Copy over msgsearch.asc from the A39 installation to your TEXT directory
    if you use the default prommpts.

    - Replace "mis_events.ans" in your DATA folder with the newer one
    from the A39 installation

    - Replace "areafixhelp.txt" in your DATA folder with the newer one

    - Replace "filefixhelp.txt" in your DATA folder with the newer one

    - Replace "bulletin.mps" in your SCRIPTS folder with the newer one

    - Replace "onlyonce.mps" in your SCRIPTS folder with the newer one

    - Replace your msg_editor.ini from the text folder with the newer
    one from the A39 installation. If you use a custom msg_editor.ini then
    you will need to modify "str7" to include the Draft option by adding a
    F at the end of the hotkey list and then adding "D-Save as Draft" into
    the list of options. Use the default msg_editor.ini to guide you if
    you need help.

    - Recompile MPL programs (mplc -all in SCRIPTS directory)

    ... It's best to be judged by twelve than carried by six.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From nugax@1:19/37 to All on Sat Nov 10 16:57:42 2018
    That’s the same thing I just thought. But I don’t think mystic will even open mystic.dat if it can’t write to it.

    I’d check permissions - lots of people are using Linux and windows A39

    On 06:03 10/11 , Todd Yatzook wrote:
    On 11/10/18, Ib Joe said the following...

    It's something that caught a lot of us off-guard...

    I did that... I have found and install copy of A35 and it works, to have a FTN address, I upgrade to A39 I cannot put one in where it saves. I
    did a fresh install of A39, same thing. I just found a copy of the A35 hanging around and it works fine, I can add a FTN address in.

    Is it running on Linux, and have you recursively changed ownership/execution >of the entire directory and files within? It might be one/both of those. a35 >might be using a different data file to store the addresses, which might >already have rwx and ownership.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Linux/64)
    * Origin: The ByteXchange BBS | bbs.thebytexchange.com (1:19/37)
  • From Todd Yatzook@1:142/799 to Ib Joe on Sat Nov 10 21:44:55 2018
    On 11/10/18, Ib Joe said the following...

    I'm starting to hate linux... :) I have installed A39 on my Windows 10 32Bit vertual box and, last night, installed it on my Windows 10 64Bit host and I get the same. I enter in my address, or any for the matter,
    I fill it out complete ... and it dose not save when I back out.

    That might be a corrupted data file then. I'm not sure which data file it stores those in. Looks like it might be in the MYSTIC.DAT file, which if it
    is corrupted, would definitely suck since it keeps a bunch of other stuff in there as well. I'm not sure what you could do.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)
  • From Todd Yatzook@1:142/799 to nugax on Sat Nov 10 21:47:08 2018
    On 11/10/18, nugax said the following...

    That’s the same thing I just thought. But I don’t think mystic will even open mystic.dat if it can’t write to it.

    I’d check permissions - lots of people are using Linux and windows A39

    Nah, turns out he missed the replies that said not to use the first slot,
    it's reserved for local mail. =) He figured it out.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)
  • From Chad Adams@1:19/37 to All on Sat Nov 10 22:32:45 2018
    Ah, yes. The first slot is for your local address for local mail. I’m not sure why g00r00 even shows that address. I can see how it can be confusing.

    On 15:47 10/11 , Todd Yatzook wrote:
    On 11/10/18, nugax said the following...

    That’s the same thing I just thought. But I don’t think mystic will even open mystic.dat if it can’t write to it.

    I’d check permissions - lots of people are using Linux and windows A39

    Nah, turns out he missed the replies that said not to use the first slot, >it's reserved for local mail. =) He figured it out.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Linux/64)
    * Origin: The ByteXchange BBS | bbs.thebytexchange.com (1:19/37)
  • From mark lewis@1:3634/12.73 to Jeff Smith on Sun Nov 11 12:57:56 2018
    On 2018 Nov 10 12:04:20, you wrote to me:

    it has been a long time since i've updated a mystic setup but you
    definitely must install the new version to a temp directory and then
    copy the binaries over and recompile the scripts... that much i
    definitely remember ;)

    The one addition I would make is that if it were a fresh install the install directory must not already exist or the install would fail.

    yeah, i remember that, too... i was trying to keep it short'n'sweet but couldn't... my "temp" directory that i installed to was always changed to the version umber being installed...

    eg:
    ~/mystic_a51/
    ~/mystic_a52/
    ~/mystic_a53/
    ~/mystic_a54/
    ~/mystic_a55/
    ~/mystic_a56/
    ~/mystic_a57/
    ~/mystic_a58/
    ~/mystic_a59/
    ~/mystic_a60/
    ~/mystic_a61/
    ~/mystic_a62/
    ~/mystic_a63/

    the real working install is actually in ~/bbs/ ;)

    yeah, those are old v1.11 betas, too... probably should have included the version number as well...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Georgia is NOT on my mind.
    ---
    * Origin: (1:3634/12.73)
  • From IB JOE@1:342/201 to Todd Yatzook on Mon Nov 12 20:43:15 2018
    On 11/10/18, Todd Yatzook said the following...

    On 11/10/18, Ib Joe said the following...

    I'm starting to hate linux... :) I have installed A39 on my Windows 32Bit vertual box and, last night, installed it on my Windows 10 64Bi host and I get the same. I enter in my address, or any for the matte I fill it out complete ... and it dose not save when I back out.

    That might be a corrupted data file then. I'm not sure which data file it stores those in. Looks like it might be in the MYSTIC.DAT file, which if it is corrupted, would definitely suck since it keeps a bunch of other stuff in there as well. I'm not sure what you could do.


    Is there a way to fix this file??

    Thanx

    IB JOE
    AKA Joe Schweier
    SysOp of Joe's Computer & BBS
    Telnet: joesbbs.com

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Joe's Computer & BBS -=joesbbs.com=- (1:342/201)
  • From Todd Yatzook@1:142/799 to IB JOE on Tue Nov 13 08:49:12 2018
    On 11/12/18, IB JOE said the following...

    That might be a corrupted data file then. I'm not sure which data fil stores those in. Looks like it might be in the MYSTIC.DAT file, which it is corrupted, would definitely suck since it keeps a bunch of othe stuff in there as well. I'm not sure what you could do.

    Is there a way to fix this file??

    Nah, you figured it out, I'd thought? That it was the first line that was reserved for local mail, and that's why it wouldn't save? You should be good, no?

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)
  • From Paul Hayton@3:770/100 to All on Sat Jan 25 10:52:20 2020
    Just an update that work is afoot to release a new alpha for Mystic that will address the issue I posted about a week or so ago. This new update when released will also offer significant changes to the way Mystic handles themes along with other tweaks to the code. More to follow when it's out.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Bud Spencer@3:770/3 to Paul Hayton on Sat Jan 25 11:54:16 2020
    On Sat, 25 Jan 2020, Paul Hayton wrote:

    Just an update that work is afoot to release a new alpha for Mystic that will address the issue I posted about a week or so ago. This new update when released will also offer significant changes to the way Mystic handles themes along with other tweaks to the code. More to follow when it's out.

    This is wonderful news! Looking forward to test out new and shiny ..
    probably one day one can get BBS online ... Finally!


    /
    Bud
    /

    a1=S0
    b1=[1..2,'L0L']
    a2=2*a1
    a3=S1.4#b1
    a4=(a2,a3)
    a5=64*a4

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Paul Hayton@3:770/100 to Bud Spencer on Sun Jan 26 17:07:38 2020
    On 25 Jan 2020 at 11:54a, Bud Spencer pondered and said...

    This is wonderful news! Looking forward to test out new and shiny .. probably one day one can get BBS online ... Finally!

    :)

    I'll keep you (and others here) posted when it's out.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From IB Joe@1:342/200 to All on Wed Feb 16 12:07:01 2022
    I have updated to the latest Pre-Alpha... I have never updated any of my prompts... I saw mention of them in the update file... If I have never in the past updated prompts I can just ignore their mention...??

    Thanx

    IB Joe
    AKA Joe Schweier
    SysOp of Joe's BBS
    -=JoesBBS.com=-

    --- Mystic BBS v1.12 A48 2022/02/15 (Windows/64)
    * Origin: JoesBBS.com, Telnet:2323 SSH:2222 HTTP:80 (1:342/200)
  • From g00r00@1:129/215 to IB Joe on Wed Feb 16 16:13:24 2022
    I have updated to the latest Pre-Alpha... I have never updated any of my prompts... I saw mention of them in the update file... If I have never
    in the past updated prompts I can just ignore their mention...??

    Yes you should be fine. Mystic updates its default prompts on its own. :)

    ... The person who snores the loudest will fall asleep first

    --- Mystic BBS v1.12 A48 2022/02/15 (Windows/64)
    * Origin: Sector 7 * Mystic WHQ (1:129/215)