• Upgrade

    From ib joe@1:342/200 to All on Fri Sep 8 21:22:14 2017
    Upgraded to the current alpha and lost my message editor... bailed on that
    and went back to my 1.11...

    Should I just start rom scratch?? copied the "exe" files over...ran
    upgrade... it worked... as far as I could tell... went to write a message and lost the full screed editor...

    ideas??

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

    --- Mystic BBS v1.11 (Raspberry Pi)
    * Origin: joesbbs.com (1:342/200)
  • From ib joe@1:342/200 to All on Sat Sep 9 12:00:05 2017
    I tried to update and it didn't work out for me. I would like to do a
    complete install of the latest version and just move over the txt files I
    have altered... I can just make alterations to the menu files as needed...

    The only consern I have is the message areas... there is a file in the data directory that looks like its related to the message areas... is that where
    the information is stored for the message areas... can I just copy this file over after the instal to maintain the current message area setup...

    Thanx

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

    --- Mystic BBS v1.11 (Raspberry Pi)
    * Origin: joesbbs.com (1:342/200)
  • From g00r00@1:129/215 to ib joe on Sat Sep 9 13:31:40 2017
    Upgraded to the current alpha and lost my message editor... bailed on
    that and went back to my 1.11...

    Should I just start rom scratch?? copied the "exe" files over...ran upgrade... it worked... as far as I could tell... went to write a
    message and lost the full screed editor...

    You didn't follow the upgrade instructions. If you want to upgrade from 1.11 to 1.12 A35 you'll have a good amount of steps to perform because you're doing a couple years of upgrades at once.

    Your other option is to just start fresh with 1.12 A35 and the reconfigure
    your BBS.

    Here are the instructions to upgrade:

    ,----------------------.
    | UPGRADING MYSTIC BBS |------------------------------------------------------ `----------------------'

    1. FIRST and ALWAYS create a backup of your BBS before upgrading. Generally
    upgrading goes pretty smooth, but there is always the chance of something
    going wrong whether it is Mystic or operator error!

    2. There is no automatic upgrade process. The process is to install the full
    installation to a temporary directory, so that you have access to the
    latest version of the files. Then follow the upgrade instructions provided
    below for your specific version. Usually this just means replacing new
    binary files contained in the new alpha. DO NOT ATTEMPT TO INSTALL OVER
    YOUR EXISTING SETUP!

    3. REVIEW THE WHATSNEW.TXT for this alpha. The WHATSNEW is structured to show
    what has been added/fixed between alphas, and also provides documentation
    for new or changed features.

    4. REMEMBER #1 TO BACKUP YOUR BBS DIRECTORY! :)

    .----------------------------.
    | UPGRADING FROM 1.11 TO A35 |-------------------------
    `----------------------------'

    - Replace existing binaries with the new alpha binaries:

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

    - Run upgrade.exe to upgrade data files

    - Perform the following in the DATA folder:

    - Copy protocol.dat from new alpha into DATA folder
    - Delete CFGROOT.AN1 from DATA folder
    - Copy CFGROOT1.ANS from the new alpha into your DATA folder
    - Copy mis_*.ans from the DATA directory to your DATA directory
    - Copy servers.dat from the DATA directory to your DATA directory

    - Perform the following steps in TEXT folder for themes:

    - Copy archive_view* from the new alpha into TEXT folders
    - Copy msg_editor* from the new alpha into TEXT folders
    - Copy file_index* from new alpha into TEXT folders
    - Copy ansimidx.ini from new alpha into TEXT folders
    (if you use a custom one then you'll have to update it)

    - Perform the following steps in SCRIPTS directories:

    - Copy menucmd.mps from new alpha scripts directory
    - Copy automessage.mps from new alpha scripts directory
    - Execute "mplc -all" to recompile MPL programs

    - Perform the following PROMPTS updating:

    If you use default prompts, you can simply copy default.txt from the
    new alpha DATA directory into yours. If you have custom themes, then
    you'll need to update the following prompts in default.txt or any other
    custom themes you have:

    ; Press ENTER to start file transfer &1=selected protocol
    ; First word is input chars, followed by display text
    065 SQ |CR|09Press |01[|15ENTER|01/|15S|01]|09tart or |01[|15ESCAPE|01/|15Q|01]|09uit your |15|&1 |09transfer: |XX

    ; Message from another node footer. First word contains input keys, followed by prompt
    145 RC |CR|09Node Message: |01[|10R|01]|09eply, |01[|10C|01]|09hat,
    or |01[|10ENTER|01/|10Continue|01]|09: |15

    ; Select scanned file bases prompt
    202 Toggle: |09[|11#-#,#|09], Select [|11A|09]dd All, [|11R|09]emove All, [|11?|09/|11List|09]: |XX

    ; Ask for character translation (DOS CP437 or UTF8)
    ; &1 = Detected terminal type (or Unknown)
    315 |CR|14[|150|14] MS-DOS CP437|CR[|151|14] UTF-8|CR|CRSelect Terminal Codepage [|15Enter = CP437|14]: |XX

    ; TELNET/RLOGIN: Connecting prompt &1 = address &2 = port
    354 |CR|08> |07Escape sequence is |08|15CTRL+|15]|08.|CR|08> |07Connecting to |15|&1 |07port |15|&2|08.|CR

    ; TELNET/RLOGIN: Connected successfully
    355 |08> |07Connected.

    ; TELNET/RLOGIN: Unable to connect
    356 |08> |12Unable to connect: Press a key|PN

    ; Login prompt: User enters a username found in trashcan.dat
    375 |CR|12That user name is unacceptible.

    - Perform the following final steps:

    - You must run MUTIL's file base packer in order to regenerate index
    files for your file areas.'

    - If you use QWK networking, go into your QWK networks in the
    configuration and set them to "Active" as they can now be toggled off
    or on.

    - If you've configured a preset upload base in the File Base settings
    make
    sure it matches the correct ID in the file base editor for the base you
    want uploads to be placed.

    - Similar to the above, if you use the MX menu command to post text
    files,
    make sure the ID matches the ID in the message base editor for the base
    you want to post to.

    --- Mystic BBS v1.12 A35 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
  • From ib joe@1:342/200 to g00r00 on Mon Sep 11 16:25:33 2017
    Does Mystic have an ability to import/export the message areas... like an areas.bbs... or are all the message areas lost from one version to the next??

    Thanx

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

    --- Mystic BBS v1.11 (Raspberry Pi)
    * Origin: joesbbs.com (1:342/200)
  • From IB JOE@1:342/200 to All on Mon Jul 30 10:35:32 2018
    I am currently running Mystic 1.12 A35 ... Raspberry Pi ... I want to upgrade to A39. Did I mess things up too bad by not doing the versions in between??

    Thanx

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

    --- Mystic BBS v1.12 A35 (Raspberry Pi/32)
    * Origin: Joe's Computer & BBS -=joesbbs.com=- (1:342/200)
  • From Alan Ianson@1:153/757.1 to IB JOE on Mon Jul 30 10:24:11 2018
    On 07/30/18, IB JOE said the following...

    I am currently running Mystic 1.12 A35 ... Raspberry Pi ... I want to upgrade to A39. Did I mess things up too bad by not doing the versions
    in between??

    No, I don't think you'll have any problems. You'll want to check the upgrade.txt and do all the steps for upgrading between A35 and A39 but it didn't look to complex to me. There are some new scripts in the scripts directory so don't forget to compile those with mplc -all in that directory. That's a step that I sometimes miss and it causes me confusion.. :)

    Ttyl :-),
    Al

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Al's Little Shop of Horrors - Penticton, BC Canada (1:153/757.1)
  • From IB JOE@1:342/200 to Alan Ianson on Mon Jul 30 12:06:01 2018
    On 07/30/18, Alan Ianson said the following...

    No, I don't think you'll have any problems. You'll want to check the upgrade.txt and do all the steps for upgrading between A35 and A39 but it didn't look to complex to me. There are some new scripts in the scripts directory so don't forget to compile those with mplc -all in that directory. That's a step that I sometimes miss and it causes me confusion.. :)


    I'll give it a shot.... in a bit... I did the new install in a temp
    directory. I'll do the upgrade in a few days.

    Thanx

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

    --- Mystic BBS v1.12 A35 (Raspberry Pi/32)
    * Origin: Joe's Computer & BBS -=joesbbs.com=- (1:342/200)
  • From Tony Langdon@3:633/410 to IB JOE on Tue Jul 31 06:41:00 2018
    On 07-30-18 10:35, IB JOE wrote to All <=-

    I am currently running Mystic 1.12 A35 ... Raspberry Pi ... I want to upgrade to A39. Did I mess things up too bad by not doing the versions
    in between??


    No, just make sure you do ALL the steps in the documentation to upgrade from A35 to A39.


    ... We are operating on many levels here.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Paul Hayton@3:770/100 to Tony Langdon on Tue Jul 31 10:07:03 2018
    On 07/31/18, Tony Langdon pondered and said...

    No, just make sure you do ALL the steps in the documentation to upgrade from A35 to A39.

    I agree, what he said ;)

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From IB JOE@1:342/200 to Alan Ianson on Mon Jul 30 17:36:02 2018
    On 07/30/18, Alan Ianson said the following...
    No, I don't think you'll have any problems. You'll want to check the upgrade.txt and do all the steps for upgrading between A35 and A39 but it didn't look to complex to me. There are some new scripts in the scripts directory so don't forget to compile those with mplc -all in that directory. That's a step that I sometimes miss and it causes me confusion.. :)


    Didn't go so well... I went to start mis and it looked all funky ... I didn't delete all my work but I did copy back the version I had working.

    I'll pock at it again some time later I guess.

    :)

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

    --- Mystic BBS v1.12 A35 (Raspberry Pi/32)
    * Origin: Joe's Computer & BBS -=joesbbs.com=- (1:342/200)
  • From Al@1:153/757 to IB JOE on Mon Jul 30 18:28:44 2018
    Re: Re: Upgrade
    By: IB JOE to Alan Ianson on Mon Jul 30 2018 05:36 pm

    Didn't go so well... I went to start mis and it looked all funky ... I didn't delete all my work but I did copy back the version I had working.

    I wonder if that was UTF-8 as opposed to CP437? There are settings for that in the config. I wonder if something in there has changed between A35 and A39.

    I'll pock at it again some time later I guess.

    Yep, I'm sure you'll get it if you take your time.. :)

    Ttyl :-),
    Al


    ... Remember when safe sex meant not getting caught?
    --- SBBSecho 3.05-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Tony Langdon@3:633/410 to Paul Hayton on Tue Jul 31 18:53:00 2018
    On 07-31-18 10:07, Paul Hayton wrote to Tony Langdon <=-

    On 07/31/18, Tony Langdon pondered and said...

    No, just make sure you do ALL the steps in the documentation to upgrade from A35 to A39.

    I agree, what he said ;)

    Can't go wrong if you do that. The "failed" upgrades I've seen have been due to a step not being done, often ones like recompiling MPLs, easily missed. :)


    ... Amiga: The Computer They Couldn't Kill
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From Phillip Kimble@1:128/2 to IB JOE on Fri Aug 3 14:04:16 2018

    Hello IB!

    30 Jul 18 10:35, you wrote to all:

    I am currently running Mystic 1.12 A35 ... Raspberry Pi ... I want to upgrade to A39. Did I mess things up too bad by not doing the versions
    in between??
    Dont think so. Just make sure you do a good backlup before you start.


    IB JOE
    AKA Joe Schweier
    SysOp of Joe's Computer & BBS
    Telnet: joesbbs.com
    Is this any relation to Joe's Garage?



    Phillip


    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Bayhaus.net::pushing pkts across the net (1:128/2)
  • From IB JOE@1:342/200 to All on Tue Aug 7 12:25:04 2018
    I tried to upgrade a few days ago, had problems. Anyway, I have a few questions...

    If upgrading from A35... do I need to find all the upgrade files between A35 and the latest version A39 and then follow all the steps set aside in the upgrade TXT file?? or can I just work with the latest version ???

    I was able to install the A39 version on my Pi box and it ran fine, unlike
    what I did during the upgrade process..... So.... If I just did a fresh install... what files can I move over from a backup???

    User base ?? File Base (Not a big deal) ... Message Groups and Areas... I
    have made some changes on the menu files...

    I'd rather work through the upgrade process, if I can... just ideas

    Thanx

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

    --- Mystic BBS v1.12 A35 (Raspberry Pi/32)
    * Origin: Joe's Computer & BBS -=joesbbs.com=- (1:342/200)
  • From Ben Ritchey@1:393/68.8 to Ib Joe on Tue Aug 7 14:07:58 2018
    * An ongoing debate between IB JOE and All rages on ...

    If upgrading from A35... do I need to find all the upgrade files
    between A35 and the latest version A39 and then follow all the steps
    set aside in the upgrade TXT file?? or can I just work with the latest version ???

    If you install A39 fresh then everything will be fine, no upgrade needed :)

    I'd rather work through the upgrade process, if I can... just ideas

    Ok, here ya go, backup A35 stuff, install A39 to a temp directory then:

    === Cut ===

    ,----------------------.
    | UPGRADING MYSTIC BBS |------------------------------------------------------ `----------------------'

    1. FIRST and ALWAYS create a backup of your BBS before upgrading. Generally
    upgrading goes pretty smooth, but there is always the chance of something
    going wrong whether it is Mystic or operator error!

    2. There is no automatic upgrade process. The process is to install the full
    installation to a temporary directory, so that you have access to the
    latest version of the files. Then follow the upgrade instructions provided
    below for your specific version. Usually this just means replacing new
    binary files contained in the new alpha. DO NOT ATTEMPT TO INSTALL OVER
    YOUR EXISTING SETUP!

    3. REVIEW THE WHATSNEW.TXT for this alpha. The WHATSNEW is structured to show
    what has been added/fixed between alphas, and also provides documentation
    for new or changed features.

    4. REMEMBER #1 TO BACKUP YOUR BBS DIRECTORY! :)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


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

    - 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)

    - 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

    - Add prompts #528, 529, 530, and 531 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.

    - mbbsutil.exe is no longer used, delete it from your Mystic 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.

    === Cut ===

    That's it, you should be up & running!


    .- Keep the faith, --------------------------------------------------.
    | |
    | Ben aka cMech Web: http|ftp|binkp|telnet|ssh://cmech.dynip.com |
    | vvvvvv Email: fido4cmech(at)lusfiber.net |
    | { O O } Home page: http://cmech.dynip.com/homepage/ |
    | __m___oo___m__ |
    `--| | | |- WildCat! BBS 24/7 +1-337-984-4794 any BAUD 8,N,1 -'

    ... A country boy can survive.
    --- GoldED+/W32-MSVC v1.1.5-g20180717 ... via Mystic BBS!
    * Origin: FIDONet - The Positronium Remote (1:393/68.8)
  • From Tony Langdon@3:633/410 to IB JOE on Wed Aug 8 08:09:00 2018
    On 08-07-18 12:25, IB JOE wrote to All <=-

    I tried to upgrade a few days ago, had problems. Anyway, I have a few questions...

    If upgrading from A35... do I need to find all the upgrade files
    between A35 and the latest version A39 and then follow all the steps
    set aside in the upgrade TXT file?? or can I just work with the latest version ???

    No, all you need to do is:

    1. BACKUP! :)
    2. install A39 to a new directory
    3. follow ALL of the steps in the upgrade documentation between A35-A39. So if it says to do something when upgrading from (say) A36 to A37, you need to do that step along the way. Of course, if a step is mentioned twice (say in A35 to A36 and A38 to A39, you only need to do that step once. But read VERY careflly, some steps may look similar, but refer to different details. :)


    ... Amish safe sex: painting an "X" on the cows that kick.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)
  • From mark lewis@1:3634/12.73 to Ben Ritchey on Sun Aug 12 13:21:28 2018

    On 2018 Aug 07 14:07:58, you wrote to Ib Joe:

    I'd rather work through the upgrade process, if I can... just ideas

    Ok, here ya go, backup A35 stuff, install A39 to a temp directory then:

    "install [version] to a temp directory" is THE absolute key part...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Cat Toy: Anything not nailed down
    ---
    * Origin: (1:3634/12.73)