faq
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
faq [2016/04/20 04:20] – Kludge lines and the V key avon | faq [2023/01/04 14:59] (current) – start menu question avon | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Frequently Asked Questions ====== | ====== Frequently Asked Questions ====== | ||
- | === Q: How can I view the kludge lines for messages posted | + | This page contains a mix of FAQ that will be added to over time. If you have information that you think would suit being listed here please drop a note to avon [at] bbs.nz |
- | < | + | ==== Start menu field is empty ==== |
- | A: When you are reading a message posted to a echomail message base press the V key. This toggles on/off the ability to view kludge lines such as PATH and SEEN-BY. If you reply to the message when the kludge lines are visible you can also quote them in your reply. | + | |
- | </ | + | |
- | === Q: I use Mystic | + | //Hmm. When I upgrade my users to a higher security level and then check their account. I find the 'Start Menu' field is empty. Should this be the case?// |
- | <code> | + | |
- | A: YES! You can easily switch platforms and retain your BBS! However, there are | + | From Mystic 1.12 A48 the "Start Menu" field in the Security Profile editor no longer copies onto the user's record when upgrading user access. |
- | some basic steps required, particularly | + | |
- | system with case sensitive file names: | + | Instead, Mystic checks the start menu for the user's security profile on login. |
+ | |||
+ | IF: User's record has a custom start menu defined, use it as start menu | ||
+ | ELSE: If User's security level profile has a start menu defined, use it | ||
+ | ELSE: Use default start menu from System Configuration> | ||
+ | |||
+ | Mystic will also now log which start menu is being loaded when a user logs in. " | ||
+ | |||
+ | It might be a good idea if upgrading to check your security profiles to make sure the start menu field is set to a blank or a value that you want for users with those settings otherwise users could get an error loading menu error when logging in. | ||
+ | |||
+ | ==== Fix time zone settings ==== | ||
+ | |||
+ | //Help! My time zone information is wrong and TZUTC shows a 0 value in Linux// | ||
+ | |||
+ | Most Linux distributions | ||
+ | |||
+ | Its also possible your distribution is minimal and does not include support for timezone at all, and in that case you must set it using its configuration tool or package manager. | ||
+ | |||
+ | It is also possible that you have changed some values and they are set improperly or that you are using a distribution that uses some format never seen before. | ||
+ | |||
+ | Since there are so many different distributions and possibilities, | ||
+ | |||
+ | The logic Mystic uses is based off of checking the TZ environment variable value and acting accordingly: | ||
+ | |||
+ | If TZ environment variable has a value then: | ||
+ | If TZ begins with / then use this value as timezone file location | ||
+ | If TZ is set such as ' | ||
+ | If no TZDIR value is set use / | ||
+ | If TZDIR is set use TZDIR + TZ | ||
+ | |||
+ | If TZ environment variable has NO value then: | ||
+ | |||
+ | Check / | ||
+ | If no file then check / | ||
+ | If no file then check / | ||
+ | If no file then check value of TZDIR + " | ||
+ | |||
+ | |||
+ | Troubleshooting an issue will largely depend on what the values are for your TZ and TZDIR environment variables which you can check by doing a "echo $TZ" and "echo $TZDIR" | ||
+ | |||
+ | ==== Change Mystic -cfg ANSI ==== | ||
+ | |||
+ | //How can I change the background ANSI that is displayed when I run Mystic -CFG ?// | ||
+ | |||
+ | The ANSI file you want is called " | ||
+ | |||
+ | Note you can also totally change the overall Mystic -CFG theme by heading to Configuration | ||
+ | |||
+ | Here you will find several themes you can apply that include: | ||
+ | |||
+ | * 3D ANSI | ||
+ | * Shareware | ||
+ | * Mono Pink | ||
+ | * Mono Blue | ||
+ | * Turbo Vision | ||
+ | |||
+ | |||
+ | |||
+ | ==== ANSI displays incorrectly ==== | ||
+ | |||
+ | //ANSI output and other screens that Mystic displays looks a bit strange / distorted | ||
+ | |||
+ | This is most likely caused by the Default CodePage setting you are using. Mystic can send client terminals either CP437 or UTF8 data output, converting relevant outbound data to UTF8 when selected. | ||
+ | |||
+ | There are two settings that control this. They can be found in the Mystic Configuration System by running Mystic -cfg from the command line. Head to the Configuration > Login/ | ||
| | ||
- | 1. When copying files, make sure all data, menu, and display files are lower | + | == Default Codepage == |
- | cased. | + | |
- | + | This sets the default codepage sent to the users console when connecting | |
- | 2. Once the files are copied, you must run " | + | |
- | new operating system, and change the paths to match your new Mystic | + | == Local CodePage == |
- | | + | |
- | 3. Now run " | + | |
- | menu, and scripts directory so go into the Themes editor and change those | + | |
- | | + | |
- | own message base path which needs to be updated. | + | |
- | once by using the Global Message Base Editor. | + | |
- | 4. You *MUST* run MUTIL's file base packer before you start using the BBS | + | Mystic has a Local CodePage option which is used as the default when the -L command is used (local login). |
- | again. Failure | + | |
- | file bases. | + | Note that Local Codepage defaults to UTF8 for OSX and Raspberry Pi. MUTIL and MIS honor the local codepage settings and runs in UTF8 in Linux/OSX. |
- | | + | |
- | | + | The documentation has this to say about the Mystic codepage settings... |
- | | + | |
- | | + | If you do not understand what these are, set Default to CP437 and |
- | that is not. | + | Ask CodePage to " |
- | automatically regenerate these indexes for the current | + | things like Putty to connect to your BBS, and everything should look and |
- | + | work as expected. | |
- | If you encounter problems after performing these steps, the error messages | + | |
- | | + | When Mystic starts up, by default a user will have the configured " |
- | | + | code page. |
- | | + | one of the following: |
- | | + | |
- | + | Detect : Mystic only changes codepage from default if it is able | |
- | The same holds true in other areas as well, such as in MUTIL' | + | to detect a terminal that is likely NOT the default, but the |
- | | + | user is never prompted. |
- | | + | Ask : Mystic |
- | | + | to use after detecting ANSI. |
- | | + | CP437 : Codepage will always be set to MS-DOS (CP437) |
- | + | UTF8 : Codepage will always be set to UTF8 | |
- | | + | |
- | </code> | + | In Linux, the Default code page will actually be what Mystic runs in |
+ | when you run mystic from the command line, too. In Windows, the Sysop | ||
+ | side will always execute in CP437, even when a user is logged in that | ||
+ | has UTF8 enabled (the user of course will still get sent UTF8). | ||
+ | |||
+ | One other consideration, | ||
+ | VT102 instead of ANSI-BBS, which means a few things are different - most | ||
+ | noticably are ANSI clear screen codes. | ||
+ | moves the cursor to 1,1, while in VT102 it does not. This means its best | ||
+ | to edit your ANSIs and add a |CL at the very top so Mystic clears the | ||
+ | screen in a compatible way. | ||
+ | |||
+ | Some other final tips. | ||
+ | |||
+ | For a session you can override the the default code page settings from the command line by using the following syntax: Mystic -CP< | ||
+ | |||
+ | When a user selects UTF8 encoding, Mystic will now assume their terminal sends VT102 DELETE/ | ||
+ | |||
+ | ==== Change ANSI login logo ==== | ||
+ | |||
+ | //How do I change the ANSI login logo that displays above the login prompt?// | ||
+ | |||
+ | * Run Mystic -CFG | ||
+ | * Head to editors > theme/ | ||
+ | * Look for the filename ' | ||
+ | * You can update the filename after the DF MCI code to any ANSI file you want to display. | ||
+ | * Save your ANSI file of choice to your text directory :) | ||
+ | * Another option is to edit the existing preuser file and you will find it in / | ||
+ | |||
+ | ==== How to view kludge lines ==== | ||
+ | |||
+ | //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. This toggles on/off the ability to view kludge lines such as PATH and SEEN-BY.If you then reply to the message while the kludge lines are visible you can also quote them in your reply. | ||
+ | |||
+ | ==== Migrate Mystic to different | ||
+ | |||
+ | //I use Mystic in Windows, but I want to move to Raspberry Pi. Can I move to a different | ||
+ | |||
+ | YES! You can easily switch platforms and retain your BBS! However, there are some basic steps required, particularly when switching to or from an operating system with case sensitive file names: | ||
+ | |||
+ | * When copying files, make sure all data, menu, and display files are lower cased. | ||
+ | |||
+ | * Once the files are copied, you must run " | ||
+ | |||
+ | * In Mystic' | ||
+ | |||
+ | * Note that one pain point is converting over file base directories, | ||
+ | | ||
+ | If you encounter problems after performing these steps, the error messages and logs should guide you towards fixing the problem. | ||
+ | |||
+ | The same holds true in other areas as well, such as in MUTIL' | ||
+ | |||
+ | ==== Limit door game access ==== | ||
+ | |||
+ | //Can Mystic limit a door game to being executed only on one node at a time without scripting or batch files?// | ||
+ | |||
+ | Yes, you can use Mystic' | ||
- | === Q: Can Mystic limit a door game to being executed only on one node at a time without scripting or batch files? === | ||
- | < | ||
- | Yes, you can use Mystic' | ||
- | an external program to only a single user. Review the following screen capture | ||
- | below for an example: | ||
- | </ | ||
{{ : | {{ : | ||
+ | |||
+ | ==== How to config max nodes ===== | ||
+ | |||
+ | //How do I configure the number of nodes Mystic will accept?// | ||
+ | |||
+ | The first step is to set the "Max BBS Nodes" in your System Configuration > Servers > General Options section in the configuration. | ||
+ | |||
+ | BBS Nodes can be spawned by any number of built in Mystic servers, or also from external sources for things such as dial-up modems, local logins from the console, etc. The max BBS nodes is a limit to the sum of all possible ways Mystic can accept BBS node connections. | ||
+ | |||
+ | In the Servers > Configure servers configuration you will see options to modify or create TELNET, RLogin, and SSH servers. | ||
+ | |||
+ | The settings do not have to add up to Max BBS nodes. | ||
+ | |||
+ | ==== Importing files into Mystic ==== | ||
+ | |||
+ | //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 want 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" | ||
+ | |||
+ | There are two ways to perform a Mass Upload in the Mystic ecosystem: | ||
+ | | ||
+ | The first way is to perform a mass upload by setting " | ||
+ | | ||
+ | The second way is to run the "Mass Upload" | ||
+ | |||
+ | Files that have already been imported into the BBS can be edited directly in the file listing but pressing " | ||
+ | |||
+ | 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). | ||
+ |
faq.1461144004.txt.gz · Last modified: 2016/04/20 04:20 by avon