• Problems upgrading to a47

    From Michael Batts@1:227/114 to All on Sun Oct 18 12:14:44 2020
    I updated to and have been running a46 perfectly since it was made available. After a request to upgrade to a47 from a friend who runs one of my MPLs I
    find that I'm experiencing a pretty significant problem.

    My bbs is highly customized from INI's to prompts, menues and ansi displays. Pretty much anything display related has been customized. The bbs was built with a focus on ANSI displays so only a very few ASCII displays were ever created (clear screen, pause, etc). I did intend to eventually create the ASCII versions where needed.

    In every case where a display filename was entered I only entered the prefix of the filename and left out the extension. So for example, a display file named MAINMENU.ANS was entered in the main.mnu config as MAINMENU. I took this
    queue from instructional videos and examples in Mystics INI files when I
    first began my retrobbs journey a few years ago believing (with good
    evidence) that Mystic would determine the extension based upon the users display emulation. Leaving off the extension for a display file has been working since my original install in 2018, until my attempt to upgrade to
    a47. For some reason, a47 will not display an ANSI file unless the complete filename is used.

    Initially thinking that it was doable to go back and change each of the names
    I just gave up after more than 12 hours of changes only to find another area that would not function properly. MNUs, INIs, File and Message area imports, MPLs, EVERYWHERE that I had left out the extension of a displayfile name
    Mystic would simply not display the file.

    I worked for awhile with my friend who had originally requested the upgrade and found that on his bbs, under a47, he did not appear to be experiencing the same problem. Soooooo, somewhere, somehow, when I try to upgrade to a47, Mystic
    just decides that it wants file extensions before it will display the files I have created. My default emulation settings have not changed and everything else appears to function properly.

    I have restored a46 on my system until I can determine where the switch is
    that tells mystic to use the same display logic in a47 that it did on a46 ;-)

    Any thoughts or assistance with this problem would be very helpful.

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From g00r00@1:129/215 to Michael Batts on Sun Oct 18 13:18:17 2020
    I updated to and have been running a46 perfectly since it was made available.After a request to upgrade to a47 from a friend who runs one
    of my MPLs Ifind that I'm experiencing a pretty significant problem.

    Remember there is no A47 yet, its still in development. Were you using the Oct 17 version?

    --- Mystic BBS v1.12 A47 2020/10/17 (Windows/32)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Michael Batts@1:227/114 to g00r00 on Sun Oct 18 15:06:25 2020
    On |1518 Oct 2020|08, |15g00r00 |08said the following...

    I updated to and have been running a46 perfectly since it was made available.After a request to upgrade to a47 from a friend who runs on of my MPLs Ifind that I'm experiencing a pretty significant problem.

    Remember there is no A47 yet, its still in development. Were you using the Oct 17 version?


    Yes sir, I do understand and thank you for your hard work. The mystic.exe version I am having issue with was compiled on 10/13/20 at 10:34.

    I appreciate your attention and assistance!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From g00r00@1:129/215 to Michael Batts on Sun Oct 18 18:00:47 2020
    Yes sir, I do understand and thank you for your hard work. The mystic.exeversion I am having issue with was compiled on 10/13/20 at 10:34.

    I would say that if you want to upgrade then you should try a later version.

    --- Mystic BBS v1.12 A47 2020/10/18 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Michael Batts@1:227/114 to g00r00 on Sun Oct 18 21:16:20 2020
    On |1518 Oct 2020|08, |15g00r00 |08said the following...

    Yes sir, I do understand and thank you for your hard work. The mystic.exeversion I am having issue with was compiled on 10/13/20 at 10:34.

    I would say that if you want to upgrade then you should try a later version.

    Can do easy! I'll give it a shot and get back to you.

    Thanks!!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From Michael Batts@1:227/114 to g00r00 on Sun Oct 18 21:58:55 2020
    I would say that if you want to upgrade then you should try a later version.

    I installed a47 containing the mystic.exe compiled 10/18/20 at 9:30pm and the problem persists. I briefly read a message here which seemed to indicate that someone else was seeing a problem displaying ANSI files.

    For me, it looks as though mystic is not appending the .ANS file extension
    when displaying files from the configuration if that extension is missing.

    Thanks again!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From g00r00@1:129/215 to Michael Batts on Sun Oct 18 23:17:13 2020
    I installed a47 containing the mystic.exe compiled 10/18/20 at 9:30pm
    and theproblem persists. I briefly read a message here which seemed to indicate thatsomeone else was seeing a problem displaying ANSI files.

    For me, it looks as though mystic is not appending the .ANS file extensionwhen displaying files from the configuration if that extension
    is missing.

    Hmm okay. There has to be a piece of the puzzle I'm missing here. I have a modded BBS too and its not experiencing any issues. There are plenty of |DF used in menus and prompts, including headers in menus. The default install also uses |DF headers in menus and those are displaying fine on all 5 systems I have it installed on (Windows, Linux x 2, macOS, Pi).

    Maybe I can add in some logging that will give us an idea of what its finding when it tries to display.

    What version of Widows are you using? I wonder if that could have something to do with it. I am running on Windows 10.

    --- Mystic BBS v1.12 A47 2020/10/18 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From g00r00@1:129/215 to Michael Batts on Mon Oct 19 00:19:42 2020
    I installed a47 containing the mystic.exe compiled 10/18/20 at 9:30pm
    and theproblem persists. I briefly read a message here which seemed to indicate thatsomeone else was seeing a problem displaying ANSI files.

    I just created a "w32test.rar" in the "prealpha" download folder which is an A47 with a bunch of extra logging in the "nodeX.log" file that shows what its doing for display files. If you could please try to install that and let me know what the log shows when it fails to display, I would appreciate it.

    Thanks!

    --- Mystic BBS v1.12 A47 2020/10/18 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Michael Batts@1:227/114 to g00r00 on Mon Oct 19 07:21:51 2020
    Hmm okay. There has to be a piece of the puzzle I'm missing here. I
    have a modded BBS too and its not experiencing any issues. There are plenty of |DF used in menus and prompts, including headers in menus.
    The default install also uses |DF headers in menus and those are displaying fine on all 5 systems I have it installed on (Windows, Linux x
    2, macOS, Pi).

    Yeap! Isn't that the way it always is with product development? Good thing
    we all love this hobby! ;)

    Maybe I can add in some logging that will give us an idea of what its finding when it tries to display.

    Happy to assist in any way I can.

    What version of Widows are you using? I wonder if that could have something to do with it. I am running on Windows 10.

    Running my system on a Dell Optiplex 745 under Windows Server 2003 x32-bit.

    Thank you, sir!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From Michael Batts@1:227/114 to g00r00 on Mon Oct 19 07:22:52 2020
    I just created a "w32test.rar" in the "prealpha" download folder which
    is an A47 with a bunch of extra logging in the "nodeX.log" file that
    shows what its doing for display files. If you could please try to install that and let me know what the log shows when it fails to
    display, I would appreciate it.

    Ill get that installed, tested and back to you today.

    Thanks again!!!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From Michael Batts@1:227/114 to g00r00 on Mon Oct 19 09:06:48 2020
    is an A47 with a bunch of extra logging in the "nodeX.log" file that
    shows what its doing for display files. If you could please try to install that and let me know what the log shows when it fails to
    display, I would appreciate it.

    Here ya go! I installed the test program and logged in.

    I am including what looks to be the relevant log entries below.
    If you want the entire log please let me know and Ill post it.
    As I'm reviewing the log I can confirm that Mystic displays the headers but not my custom ANSIs.

    --- LOG START ---
    2020.10.19 08:45:37 DEBUG Display file: c:\mystic\themes\default\text\rockmain. a* (Graphics=1)
    2020.10.19 08:45:37 DEBUG Candidate: ROCKMAIN.ANS
    2020.10.19 08:45:37 DEBUG Result:
    2020.10.19 08:45:37 DEBUG Display file: c:\mystic\themes\default\text\mainhdr.* * (Graphics=1)
    2020.10.19 08:45:37 DEBUG Candidate: MAINHDR.ANS
    2020.10.19 08:45:37 DEBUG Candidate: mainhdr.asc
    2020.10.19 08:45:37 DEBUG Result: c:\mystic\themes\default\text\mainhdr.asc 2020.10.19 08:45:39 DEBUG Display file: c:\mystic\themes\default\text\rockmsgs. a* (Graphics=1)
    2020.10.19 08:45:39 DEBUG Candidate: ROCKMSGS.ANS
    2020.10.19 08:45:39 DEBUG Result:
    2020.10.19 08:45:39 DEBUG Display file: c:\mystic\themes\default\text\msghdr.*a
    (Graphics=1)
    2020.10.19 08:45:39 DEBUG Candidate: MSGHDR.ANS
    2020.10.19 08:45:39 DEBUG Candidate: msghdr.asc
    --- LOG END ---

    Thanks again!!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
  • From Sam Penwright@1:123/120 to g00r00 on Mon Oct 19 16:37:04 2020
    Missing something it orgin line
    Sam


    Bye for now...
    Sam
    1:123/120.0@fidonet
    Ezycom BBS Support

    --- Ezycom V3.00 01FB064B
    * Origin: Deep Space Gateway BBS Running EZYCOM V3.0 (1:123/120)
  • From g00r00@1:129/215 to Michael Batts on Mon Oct 19 08:39:10 2020
    I just created a "w32test.rar" in the "prealpha" download folder whic is an A47 with a bunch of extra logging in the "nodeX.log" file that shows what its doing for display files. If you could please try to install that and let me know what the log shows when it fails to display, I would appreciate it.

    Ill get that installed, tested and back to you today.

    Thank you! I hope this will provide me with some direction. We'll get it figured out one way or another.

    I did end up trying the A47 install on a WinXP machine that that seems to be working okay too for me.

    --- Mystic BBS v1.12 A47 2020/10/18 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From g00r00@1:129/215 to Michael Batts on Mon Oct 19 17:37:20 2020
    I am including what looks to be the relevant log entries below.
    If you want the entire log please let me know and Ill post it.
    As I'm reviewing the log I can confirm that Mystic displays the headers but notmy custom ANSIs.

    Thanks very much for the help!

    I think I've fixed the problem and I have just uploaded a new build that has the fix into the prealpha area!

    --- Mystic BBS v1.12 A47 2020/10/18 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Michael Batts@1:227/114 to g00r00 on Mon Oct 19 21:29:01 2020
    Thanks very much for the help!

    Thank YOU! I am very happy to assist!

    I think I've fixed the problem and I have just uploaded a new build that has the fix into the prealpha area!

    I'll get it loaded and report back.

    Thanks again!

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From Michael Batts@1:227/114 to g00r00 on Mon Oct 19 21:59:04 2020
    I think I've fixed the problem and I have just uploaded a new build that hasthe fix into the prealpha area!

    You did indeed! Everything works according to Hoyle!

    Thanks again for taking the time to address this. I can sleep at night now ;)

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A47 2020/10/19 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From RUBEN FIGUEROA@1:124/5013 to Michael Batts on Mon Oct 19 17:48:46 2020
    I installed a47 containing the mystic.exe compiled 10/18/20 at 9:30pm and the
    problem persists. I briefly read a message here which seemed to indicate that
    someone else was seeing a problem displaying ANSI files.

    For me, it looks as though mystic is not appending the .ANS file extension when displaying files from the configuration if that extension is missing.

    in my case, the hdr info for top of menu is not being displayed.
    Default file is mainhdr.asc which displays either in ascii or ansi. I
    have a mainhdr.ans file in there and it is not displayed. I renamed it mainans.ans and that displays. So what comes with Mystic is mainhdr.asc
    and I wanted my own ansi and I created mainhdr.ans and that has been
    woking til A47.

    Not sure if that relates to your issue.

    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: WildCat Prison BBS, Mesquite Tx (1:124/5013)
  • From RUBEN FIGUEROA@1:124/5013 to g00r00 on Mon Oct 19 17:53:00 2020
    Hmm okay. There has to be a piece of the puzzle I'm missing here. I have a modded BBS too and its not experiencing any issues. There are plenty of |DF used in menus and prompts, including headers in menus. The default install also uses |DF headers in menus and those are displaying fine on all 5 systems I
    have it installed on (Windows, Linux x 2, macOS, Pi).

    Maybe I can add in some logging that will give us an idea of what its finding
    when it tries to display.

    What version of Widows are you using? I wonder if that could have something to
    do with it. I am running on Windows 10.

    In my case I am using windows 10 ver 1909 OS Build 38363, 1139

    Hope this helps.
    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: WildCat Prison BBS, Mesquite Tx (1:124/5013)
  • From g00r00@1:129/215 to Michael Batts on Mon Oct 19 22:52:30 2020
    I think I've fixed the problem and I have just uploaded a new build t hasthe fix into the prealpha area!

    You did indeed! Everything works according to Hoyle!

    Thanks again for taking the time to address this. I can sleep at night now ;)

    Anytime! Thanks for your report and help figuring it all out!

    This was obviously a major issue that might have otherwise slipped through the cracks because it wasn't happening on my BBS!

    --- Mystic BBS v1.12 A47 2020/10/19 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Michael Batts@1:227/114 to RUBEN FIGUEROA on Tue Oct 20 09:54:57 2020
    Default file is mainhdr.asc which displays either in ascii or ansi. I have a mainhdr.ans file in there and it is not displayed. I renamed it mainans.ans and that displays. So what comes with Mystic is mainhdr.asc and I wanted my own ansi and I created mainhdr.ans and that has been woking til A47.

    Not sure if that relates to your issue.

    Try the latest pre-alpha. It should fix your problem.

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A47 2020/10/19 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From Doug Cooper@1:227/702 to Michael Batts on Wed Oct 21 02:08:38 2020
    Default file is mainhdr.asc which displays either in ascii or ansi. have a mainhdr.ans file in there and it is not displayed. I renamed mainans.ans and that displays. So what comes with Mystic is mainhdr. and I wanted my own ansi and I created mainhdr.ans and that has been woking til A47.
    Not sure if that relates to your issue.
    Try the latest pre-alpha. It should fix your problem.

    And the latest alpha is kick butt!

    I'm on it and love it! Now I'm watching daily for g00r00 updates as it seems g00r00's creative mind is working some art :)

    Glad you got your problems fixed Michael!

    -tG

    --- Mystic BBS v1.12 A47 2020/10/20 (Windows/32)
    * Origin: The Underground [@] theunderground.us:10023 <-port (1:227/702)
  • From RUBEN FIGUEROA@1:124/5013 to Michael Batts on Wed Oct 21 17:44:02 2020
    Default file is mainhdr.asc which displays either in ascii or ansi. I have a mainhdr.ans file in there and it is not displayed. I renamed it mainans.ans and that displays. So what comes with Mystic is mainhdr.asc
    and I wanted my own ansi and I created mainhdr.ans and that has been woking til A47.

    Not sure if that relates to your issue.

    Try the latest pre-alpha. It should fix your problem.

    I downloaded his latest and all is well.
    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: WildCat Prison BBS, Mesquite Tx (1:124/5013)
  • From Michael Batts@1:227/114 to RUBEN FIGUEROA on Thu Oct 22 10:45:21 2020
    Try the latest pre-alpha. It should fix your problem.

    I downloaded his latest and all is well.

    AWESOME!!!

    How is your Spitfire board going?

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A47 2020/10/19 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)
  • From RUBEN FIGUEROA@1:124/5013 to Michael Batts on Thu Oct 22 15:21:18 2020
    On 10/22/2020 10:49 AM, Michael Batts wrote to RUBEN FIGUEROA:

    @TID: Mystic BBS 1.12 A47
    @MSGID: 1:227/114 d7ab00a3
    @REPLY: 1:124/5013 05fd8099
    @TZUTC: -0400
    Try the latest pre-alpha. It should fix your problem.

    I downloaded his latest and all is well.

    AWESOME!!!

    How is your Spitfire board going?

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)

    Spitfire is working. No new users. It does have problem from time to time and I have to close it down and restart.

    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A47 2020/10/19 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (1:227/114)

    --- Platinum Xpress/Win/WINServer v7.0
    * Origin: WildCat Prison BBS, Mesquite Tx (1:124/5013)