faq
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
faq [2022/02/24 13:09] – g00r00 | faq [2023/01/04 14:59] (current) – start menu question avon | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Frequently Asked Questions ====== | ====== Frequently Asked Questions ====== | ||
- | === Q: Help! My time zone information | + | This page contains a mix of FAQ that will be added to over time. If you have information |
- | | + | ==== Start menu field is empty ==== |
- | | + | |
- | | + | //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?// |
+ | |||
+ | 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. | ||
+ | |||
+ | 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 use reasonable | ||
+ | |||
+ | 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, | ||
| | ||
- | Its also possible your distribution | + | The logic Mystic uses is based off of checking the TZ environment variable value and acting accordingly: |
- | 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 some many different distributions and possibilities, | ||
- | difficult to give a single set of instructions on how to resolve timezone | ||
- | issues. | ||
- | file on the disk, and Mystic has to be able to find it. | ||
- | | ||
- | 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 environment variable has a value then: | ||
If TZ begins with / then use this value as timezone file location | If TZ begins with / then use this value as timezone file location | ||
Line 29: | Line 38: | ||
If no TZDIR value is set use / | If no TZDIR value is set use / | ||
If TZDIR is set use TZDIR + TZ | 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 + " | ||
+ | | ||
- | If TZ environment | + | Troubleshooting an issue will largely depend on what the values are for your TZ and TZDIR environment |
- | Check / | + | ==== Change Mystic -cfg ANSI ==== |
- | 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 | + | //How can I change the background ANSI that is displayed when I run Mystic -CFG ?// |
- | TZ and TZDIR environment variables which you can check by doing a "echo $TZ" | + | |
- | and "echo $TZDIR" | + | |
- | </code> | + | |
- | === Q: How can I change the background | + | The ANSI file you want is called " |
- | The ANSI file you want is called " | + | Note you can also totally change |
- | directory. This serves as the " | + | |
- | === 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? === | + | Here you will find several themes you can apply that include: |
- | | + | * 3D ANSI |
+ | * Shareware BBS | ||
+ | * Mono Pink | ||
+ | * Mono Blue | ||
+ | * Turbo Vision | ||
+ | |||
+ | |||
+ | |||
+ | ==== ANSI displays incorrectly ==== | ||
+ | |||
+ | //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. 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/ | ||
| | ||
- | Mystic can send client terminals either CP437 or UTF8 data output, converting | + | == Default Codepage == |
- | 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. | + | |
| | ||
- | Then head to the Configuration > Login/ | + | This sets the default codepage sent to the users console when connecting to Mystic. |
- | Default Codepage and Local Codepage settings. | + | |
| | ||
- | Default Codepage | + | == Local CodePage == |
+ | |||
+ | Mystic has a Local CodePage option which is used as the default when the -L command is used (local login). | ||
| | ||
- | This sets the default | + | Note that Local Codepage defaults to UTF8 for OSX and Raspberry Pi. MUTIL and MIS honor the local codepage |
- | to Mystic. | + | |
| | ||
- | Local CodePage | + | The documentation has this to say about the Mystic codepage settings... |
- | + | ||
- | Mystic has a Local CodePage option which is used as the default when the -L | + | |
- | command is used (local login). | + | |
- | vs an incoming caller. | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | | + | |
- | + | ||
- | [SNIP] | + | |
| | ||
If you do not understand what these are, set Default to CP437 and | If you do not understand what these are, set Default to CP437 and | ||
Line 106: | Line 116: | ||
screen in a compatible way. | screen in a compatible way. | ||
| | ||
- | [snip] | + | 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< |
- | + | ||
- | For a session you can override the the default code page settings from the | + | When a user selects UTF8 encoding, Mystic will now assume their terminal sends VT102 DELETE/ |
- | | + | |
- | | + | ==== Change ANSI login logo ==== |
- | | + | |
- | | + | |
- | + | ||
- | When a user selects UTF8 encoding, Mystic will now assume their terminal sends | + | |
- | | + | |
- | + | ||
| | ||
+ | //How do I change the ANSI login logo that displays above the login prompt?// | ||
- | === Q: How do I change | + | * 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 / | ||
- | Run Mystic -CFG | + | ==== How to view kludge lines ==== |
- | 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 can I view the kludge lines for messages posted in a echomail message base?// | ||
- | === Q: How can I view the kludge lines for messages | + | When reading a message |
- | When reading a message posted | + | ==== Migrate Mystic |
- | 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. | + | |
- | ==== 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? ==== | + | //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?// |
- | < | + | |
- | | + | 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: |
- | some basic steps required, particularly when switching to or from an operating | + | |
- | system with case sensitive file names: | + | |
- | + | ||
- | | + | |
- | cased. | + | |
- | The only exception to this rule is DOS door drop files which are created in | + | |
- | upper-case on case-sensitive file systems. | + | |
- | | + | |
- | | + | |
- | new operating system, and change the paths in System Configuration to match | + | |
- | your new Mystic location. | + | |
- | | + | |
- | | + | |
- | directory that you will need to change via the Theme editor. | + | |
- | base also has its own message base path which needs to be updated. | + | |
- | be done all at once by using the Global Message Base Editor. | + | |
- | | + | |
- | | + | |
- | the actual directories where files are stored for each base. These often | + | |
- | have to be manually edited per file base, since those directories are | + | |
- | specific to each base. | + | |
- | | + | 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 ==== |
- | + | ||
- | The same holds true in other areas as well, such as in MUTIL' | + | //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' |
- | | + | |
- | | + | |
- | + | ||
- | | + | |
- | </code> | + | |
- | === 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: | ||
- | </ | ||
{{ : | {{ : | ||
- | === Q: How do I configure the number of nodes Mystic will accept? | + | ==== 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 | + | 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. | |
- | In the Servers > Configure servers configuration you will see options to | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | The settings do not have to add up to Max BBS nodes. | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | === Q: How do I get files into a File Base that I've created? | + | ==== 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: |
- | | + | |
- | | + | |
- | | + | |
| | ||
- | There are two ways to perform a Mass Upload | + | The first way is to perform a mass upload by setting " |
| | ||
- | The first way is to perform a mass upload by setting " | + | The second way is to run the "Mass Upload" |
- | your MUTIL .INI file so that any time you execute " | + | |
- | for new files and add them to your BBS automatically. | + | 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). |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | Files that have already been imported into the BBS can be edited directly in | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | NOTE: When performing a mass upload, Mystic will be unable to extract the | + | |
- | | + | |
- | | + |
faq.txt · Last modified: 2023/01/04 14:59 by avon