Differences

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

--- faq:misc [2020/09/15 16:30] – Added a SyncTERM bug report / feature request FAQ digital man
+++ faq:misc [2023/12/16 00:03] (current) – [Migration] Updated for Git *.cnf -> *.ini digital man
@@ Line 14: / Line 14: @@
   * [[#ftn_msgid|Why do my FidoNet MSGID's look different than someone else's]]?
   * [[#old_baja|Why won't an old Baja source file compile without errors]]?
+  * [[#sizeof_scfg|Why do I get this error about cfg->size != sizeof(scfg_t)]]?
   * [[#spell|How do I spell "Synchronet"]]?
   * [[#abbreviate|How do I abbreviate "Synchronet"]]?
   * [[#syncterm|How do I report a problem or request a feature for SyncTERM]]?
+  * [[#k:line|What is an AKILL on IRC and why was I K:Lined]]?
 ===== Deleted Msgs =====
@@ Line 40: / Line 42: @@
 :!: **Answer:**\\
-Many of the "New User" Questions can be disabled by setting various options in [[util:SCFG]]->System->New User Values->Question Toggles to "No":
+Many of the "New User" Questions can be disabled by setting various options in [[util:SCFG]]->System->New User Prompts... to "No":
 <code>
 ╔══════════════════════════════════╗
@@ Line 95: / Line 97: @@
 ║ │Text Directory             ..\text\                     ║
 ╚══════════════════════════════════════════════════════════╝
+</code>
+In Synchronet v3.20, this setting has moved to [[util:SCFG]]->System->Notifications->New User Feedback:
+<code>
+╔═════════════════════════════════╗
+║  System Operator Notifications  ║
+╠═════════════════════════════════╣
+->│New User Feedback      Nobody <-
+║ │Error Notifications    User #1 ║
+║ │Error Level            Error   ║
+╚═════════════════════════════════╝
 </code>
 ===== No Guest =====
@@ Line 102: / Line 115: @@
 :!: **Answer:**\\
-You don't have to have a Guest (G-[[access:restrictions|restricted]] user) account. If you don't create a Guest account to begin with, you won't have one. If you created a Guest account and you don't want it, then simply deleting the user account from the user base will work. However, without a Guest account, anonymous FTP access will not be available and some web UI elements may not function as is normally expected. To keep the Guest account but disallow logins to the Terminal Server (the traditional BBS user experience), set [[util:SCFG]]->Nodes->Node 1->Logon Requirements->Requirement String to:
+You don't have to have a Guest (G-[[access:restrictions|restricted]] user) account. If you don't create a Guest account to begin with, you won't have one. If you created a Guest account and you don't want it, then simply deleting the user account from the user base will work. However, without a Guest account, anonymous FTP access will not be available and some web UI elements may not function as is normally expected. To keep the Guest account but disallow logins to the Terminal Server (the traditional BBS user experience), set [[util:SCFG]]->Nodes->Node X->Logon Requirements->Requirement String to:
   NOT GUEST
 Doing this will cause terminal logons as "Guest" to be rejected with the following (configurable) message:
   You do not have sufficient access for this node.
-**Note:**\\
-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:**\\
@@ Line 141: / Line 151: @@
   - Shutdown the BBS
   - Fix your system date/time
-  - Run ''exec/[[util:dstsedit]]'' in your Synchronet ''[[dir:ctrl]]'' directory, change the "Date Stamp" to yesterday's date
+  - Edit ''[[dir:ctrl]]/dsts.ini'', change the "Date" value to yesterday's date
   - Restart the BBS
@@ Line 152: / Line 162: @@
 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 newly-installed files with your old/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, provided they are the same version of Synchronet. If the old computer was running a different (older) version of Synchronet than the version installed on the new computer, then it's likely best to upgrade the old version (if you can) on the old computer before migrating to the new one, though this is not strictly required.
 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.
@@ Line 158: / Line 168: @@
 If the source (old) computer was running Windows and you wish to preserve any changes you made to the [[:monitor:sbbsctrl|Synchronet Control Panel]] settings (stored in the Windows registry), you can export those settings to a ''sbbsctrl.ini'' file (using the File->Export Settings menu option) and then import them into the Synchronet Control Panel running on the new computer (using the File->Import Settings menu option). These settings include some changes made via the File->Properties menu. Settings made in most other menus in the Synchronet Control Panel are stored in your ''[[dir:ctrl]]/[[:config:sbbs.ini]]'' file.
-Configuration changes made via the ''[[:util:SCFG]]'' utility are stored in the ''*.cnf'' files in your ''[[dir:ctrl]]'' directory.
+If the source (old) and target (new) computers are both running a Unix-like operating system (e.g. Linux), be sure to rebuild *all* the native executable binaries (''e.g. libsbbs.so''), including 3rd party libraries (e.g. ''libcl.a'') on the new/target computer before trying to execute them. Failure to do so could result in "invalid opcode" errors.
+Configuration changes made via the ''[[:util:SCFG]]'' utility are stored in the ''*.ini'' (previously, ''*.cnf'') files in your ''[[dir:ctrl]]'' directory.
 If you wish to **only** migrate configuration and data files (e.g. over an new installation of Synchronet), copy (recursively) the following Synchronet sub-directories to the new computer:
   * ''[[dir:data]]''
   * ''[[dir:ctrl]]''
-  * ''[[dir:node]]1''
+  * ''[[dir:node]]*''
-If you customized any of your filter (''*.can'') or menu (e.g. ''*.asc'') files, you'll also want copy (recursively) the following directory:
+If you customized any of your filter (''*.can'') or menu (e.g. ''*.asc'', ''*.msg'') files, you'll also want copy (recursively) the following directory:
   * ''[[dir:text]]''
@@ Line 175: / Line 187: @@
   * ''[[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:Git]]) 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.
@@ Line 272: / Line 284: @@
 **Note:** To see a complete list of changes in Baja v2, see {{http://synchro.net/docs/baja2new.txt}}.
+===== sizeof scfg =====
+:?: **Question:**\\
+Why do I get the following error when running a Synchronet program: ''cfg->size(x) != sizeof(scfg_t) (y)''?
+:!: **Answer:**\\
+The program you're trying to run (e.g. ''sbbs'', ''sbbsctrl'', ''jsexec'') was built from a different version/revision of the Synchronet code base than the Synchronet library: ''sbbs.dll'' (on Windows) or ''libsbbs.so'' (on UNIX) it's loading from disk.
+Look for extra/additional Synchronet library files and executables on your file system (e.g. in your Synchronet ''[[dir:exec]]'' directory?) and remove or rebuild them.
 ===== Spell =====
@@ Line 298: / Line 319: @@
 :!: **Answer:**\\
 On sourceforge.net, [[https://sourceforge.net/p/syncterm/feature-requests/|feature requests]] and [[https://sourceforge.net/p/syncterm/tickets/|bug reports]].
+===== K:Line =====
+:?: ** Question:**\\
+What is an AKILL on IRC and why was I K:Lined?
+:!: **Answer:**\\
+AKILL is a feature of IRC services that will distribute a K:Line to all the other servers in the network. A K:Line is a server ban for your specific hostname or IP address. This means if you are AKILLed then you're banned from every other server. This is done to protect the network from spambots, flooders, and continually disruptive elements. AKILLs are done either manually by a Services Operator, or automatically by use of various methods employed by the IRCops.
+If you believe you have been accidentally or unfairly AKILLed from the Synchronet IRC network, contact sysop@endofthelinebbs.com with your IRC nickname, ip address, hostname (if you have one), date and time, including timezone, and any other relevant details.
 ===== See Also =====

Trace:

Differences

Navigation

Search

Toolbox