Subj : Problems upgrading to a47
To   : All
From : Michael Batts
Date : Sun Oct 18 2020 12:14 pm

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)

.