Differences

This shows you the differences between two versions of the page.

--- faq [2019/03/23 02:57] – content updates avon
+++ faq [2021/04/29 11:47] – [Q: I use Mystic in Windows, but I want to move to Raspberry Pi. Can I move to a different operating system without losing my BBS data?] g00r00
@@ Line 1: / Line 1: @@
 ====== Frequently Asked Questions ======
-==== Q: How can I change the background ANSI that is displayed when I run Mystic -CFG ? ====
+=== Q: How can I change the background ANSI that is displayed when I run Mystic -CFG ? ===
     The ANSI file you want is called "cfgroot.ans" and resides in the DATA
     directory. This serves as the "wallpaper" for the System Configuration.
-==== Q: ANSI output and other screens that Mystic displays looks a bit strange / distorted when I connect to the BBS or run a configuration change. Why is this and how can I fix it? ====
+=== Q: ANSI output and other screens that Mystic displays looks a bit strange / distorted when I connect to the BBS or run a configuration change. Why is this and how can I fix it? ===
     This is most likely caused by the Default CodePage setting you are using.
@@ Line 80: / Line 80: @@
-==== Q: How do I change the ANSI login logo that displays above the login prompt? ====
+=== Q: How do I change the ANSI login logo that displays above the login prompt? ===
   Run Mystic -CFG
@@ Line 91: / Line 91: @@
-==== Q: How can I view the kludge lines for messages posted in a echomail message base? ====
+=== Q: How can I view the kludge lines for messages posted in a echomail message base? ===
   When reading a message posted to a echomail message base press the V key.
@@ Line 147: / Line 147: @@
 {{ :singlenodedoor.jpg?400 |}}
-==== Q: How do I configure the number of nodes Mystic will accept? ====
+=== Q: How do I configure the number of nodes Mystic will accept? ===
     A: The first step is to set the "Max BBS Nodes" in your System Configuration >
     Servers > General Options section in the configuration.  This defines the
@@ Line 173: / Line 173: @@
     the BBS nodes.
+=== Q: How do I get files into a File Base that I've created? ===
+    When you create a file base using the File Base Editor, you will specify a
+    directory that will contain the files you wanted listed in the file base
+    you are creating.
+    Once that is done you will need to copy the files you want listed into that
+    directory, and perform what is called a "Mass Upload".  The "Mass Upload"
+    scans all of the File Base directories and identifies new files that have
+    not been imported into Mystic yet.  For each new file it finds, it will
+    scan it for a FILE_ID file to get the description and create an entry in
+    the file listing for the file.
+    There are two ways to perform a Mass Upload in the Mystic ecosystem:
+    The first way is to perform a mass upload by setting "MassUpload=true" in
+    your MUTIL .INI file so that any time you execute "mutil" it will search
+    for new files and add them to your BBS automatically.
+    The second way is to run the "Mass Upload" SysOp function while logged into
+    the BBS.  If you have SysOp access this is a more interactive way to perform
+    the mass upload.  For each new file found, Mystic will ask you if you want
+    to import it into the file listing.  If a description is not found for a
+    file Mystic will give you the opportunity to provide the description.
+    Files that have already been imported into the BBS can be edited directly in
+    the file listing but pressing "E" when you have SysOp access.  This will open
+    up the editor for that file where you can perform many functions including
+    editing the file description using Mystic's message editor.  You can also use
+    the online file listing editor SysOp command (/E by default with SysOp access)
+    to open the editor from anywhere in the BBS.
+    NOTE: When performing a mass upload, Mystic will be unable to extract the
+    descriptions if the configured archive utilities are not available for Mystic
+    to use (unzip, zip, rar, etc).