Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
faq:misc [2019/01/29 02:36] – [SBBSList] Updated with links to dynamically generated HTML versions of the list digital man | faq:misc [2020/04/17 23:25] – [No Guest] Mention the login module's modopts.ini guest setting digital man |
---|
You do not have to configure the other nodes (Node 2, 3, etc.) in [[util:SCFG]] so long as they fall within the range of the ''FirstNode''/''LastNode'' key values from the [[config:sbbs.ini#BBS|[BBS]]] section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file. | You do not have to configure the other nodes (Node 2, 3, etc.) in [[util:SCFG]] so long as they fall within the range of the ''FirstNode''/''LastNode'' key values from the [[config:sbbs.ini#BBS|[BBS]]] section of your ''[[dir:ctrl]]/[[config:sbbs.ini]]'' file. |
| |
| **Note:**\\ |
| You can remove the ''or 'Guest''' text from the [[module:login]] module's ''Login:'' prompt, even if the Guest user account exists, by setting ''guest=false'' in the ''[login]'' section of the ''[[dir:ctrl]]/[[config:modopts.ini]]'' file. This login module setting does not impact a user's ability to login to the Terminal Server as //Guest//. |
===== SBBSList ===== | ===== SBBSList ===== |
:?: **Question:**\\ | :?: **Question:**\\ |
| |
:!: **Answer:**\\ | :!: **Answer:**\\ |
You can simply copy the Synchronet directory tree (e.g. ''C:\SBBS''), complete with all sub-directories, to the new computer. | You can simply copy the Synchronet directory tree (e.g. ''C:\SBBS''), complete with all sub-directories, to the new computer, even if the new computer is running a different operating system! |
| |
Synchronet doesn't **require** //installation// on a computer, but if you wish to, you can [[:install:]] Synchronet on the new computer and then simply over-write the installed files with your migrated files. | Synchronet doesn't **require** //installation// on a computer, but if you wish to, you can [[:install:]] Synchronet on the new computer and then simply over-write the newly-installed files with your old/migrated files. |
| |
If the target (new) computer is running Windows and you choose not to install, then you may want to create a shortcut to ''sbbsctrl.exe'' in your Windows ''Startup'' folder (so it will automatically run when you login) and/or install the [[:monitor:ntsvcs|Synchronet NT Services]] (which can run without logging-in as a user). If the target computer is running Windows //Vista// or later, then you'll also want to follow the solution to this [[:faq:win#sbbsexecdll|FAQ]] as well. For 16-bit DOS program support, the Synchronet Windows NT FOSSIL driver (''sbbsexec.dll'') must also be copied to the Windows ''System32'' folder. See [[/faq:win#sbbsexecdll|the sbbsexec.dll FAQ]] for details. | If the target (new) computer is running Windows and you choose not to install, then you may want to create a shortcut to ''sbbsctrl.exe'' in your Windows ''Startup'' folder (so it will automatically run when you login) and/or install the [[:monitor:ntsvcs|Synchronet NT Services]] (which can run without logging-in as a user). If the target computer is running Windows //Vista// or later, then you'll also want to follow the solution to this [[:faq:win#sbbsexecdll|FAQ]] as well. For 16-bit DOS program support, the Synchronet Windows NT FOSSIL driver (''sbbsexec.dll'') must also be copied to the Windows ''System32'' folder. See [[/faq:win#sbbsexecdll|the sbbsexec.dll FAQ]] for details. |
If you customized any of your executable modules (e.g. ''*.js''), you'll also want copy the following directory: | If you customized any of your executable modules (e.g. ''*.js''), you'll also want copy the following directory: |
* ''[[dir:mods]]'' | * ''[[dir:mods]]'' |
| |
| If you installed any new doors in the ''xtrn'' directory or your users used any of the stock-installed doors and you'd like to retain that data, you'll also want to copy the following directory: |
| |
| * ''[[dir:xtrn]]'' |
| |
**Note:** Sysop-installed (e.g. not from [[:dev:CVS]]) or modified modules should not normally be stored in your ''[[dir:exec]]'' directory, but if they were, then you'll want to copy those over as well. | **Note:** Sysop-installed (e.g. not from [[:dev:CVS]]) or modified modules should not normally be stored in your ''[[dir:exec]]'' directory, but if they were, then you'll want to copy those over as well. |