The "Events" log messages will now be logged to a disk file in
data/events*.log by default (unless this option is disabled).

If the "First node" is > 1, then the base filename will be
"events<first-node>", otherwise, it's just "events". This is because you
would not want multiple instances of sbbs writing to the same events.log
file - that would be chaos. These log files are subject the log
rotation/retention policy defined in SCFG.

This should resolve the FAQ for Windows sysops about what log file to
which their event log messages are being written.

There was a bug with reloading the configuration files in sbbsctrl where the sound button no longer reflected the truth and the sysop's previous click-state of the button was lost. Rather than going through writing the OPT_MUTE flag to the Options fields of all the sections of the sbbs.ini and then re-loading that file as a result, just do like we did with the sysop chat availability: use a semfile. So much simpler.

If anyone ever needs instance-specific muting, we can create/check instance/host-specific mute semfiles then. Doubt that'll happen though.

Also, removed the old sysavail control methods of ntsvcs too.

This won't impact Synchronet as it has a separate signal handling
thread, but we still need to behave properly for processes that
don't.  I'm also saying that ENOMEM does not indicate a disconnection,
though it may be better to pretend it was disconnected...

Don't return an error if the node#/node.cnf file can't be opened for all uses of load_cfg() except from the terminal server. This fixes #214 for Tracker1

The days of browsers rendering HTML served-up via FTP are over, so remove this feature. This also removes all JavaScript support from the FTP server and that is a bit odd as it was one of the first Synchronet components for which I added JS support.

Removing this feature was pretty painless; much easier than adding it was. The main motivation was less cruft to port to the file base in the works. There should be no more references to 00index.html anywhere at this point. Bye bye cool feature, we'll miss you.

The argument to JS_NewContext that we were allowing to be configured was not the contest stack size, but rather:
"The size, in bytes, of each "stack chunk". This is a memory management tuning parameter which most users should not adjust. 8192 is a good default value." - per Mozilla.

So we're just going to use the suggested default, hard-coded.

Read and write the Log fonts when importing/exporting sbbsctrl.ini.
Use sbbsctrl*.ini as the default Import Settings file mask.

I noticed on one particular system that Canceling or Completing
the configuration wizard on a fresh install, sbbsctrl.exe would
just shut down (no error dialog or anything, likely a crash of
some kind). Instrumenting StartupTimerTick() didn't reveal anything
useful (it ran to completion).

By changing the method of launching the Configuration Wizard,
I was able to eliminate this observed problem. Now, the StartupTimer
runs twice on a fresh install (just once for a normal startup),
and the second run of the StartupTimerTick starts the configuration
wizard.

I also reverted to the previous behavior of dynamically creating
and destroying the wizard for each use. There's just too much state
information to restore if the config wizard is run a second time.

Also, removed a bunch of old Registry settings readings (v3.10/11
upgrade support) and commented out code.

Fix naming of the "Run Other JavaScript module" menu item.

Allows sysop to select the .js file from the exec directory, but does not yet
allow them to specify/add any command-line options.

run by a point-and-click sysop. :-)
I have the beginnings of a run-any-JS-mod sub-menu item, but still need to work
on the prompt/selection of the filename to exec.
Native sbbs cmdline utils could be invoked via this menu option too (in the
future).
First COVID-19 deaths reported today in my home county. :-(

(executing echocfg.exe).

addresses configured in SCFG.
Added "Poll" sub-menu item to the Fidonet menu for convenient method of forcing
the BINKPOLL timed event to run.

- echocfg (executing)
- binkstats.ini (viewing)
- echostats.ini (viewing)
- sbbsecho.log (viewing)
- sbbsecho.ini (editing)
- badareas.lst (viewing)
- areas.bbs (editing)

I don't recall why I added this or what usefulness it has, but I'm gonna play
with it.

(ctrl/node.dab) is constantly closed and re-opened for every non-locking read.
This is really slow across network file systems and unnecessary, so use a
similar optimization as the C++ sbbs_t class where the file can (and normally
is) left open across multiple consecutive reads.

events when not in "appy-time".

alphabetized, so the indexes don't necessarily match the order (of timed
events) in SCFG.

Remember the last forced timed event setting.

reach the configured "max size", newly added log lines would not use the
configured color/font for the msg's log-level (they'd all use the default
color/font).

(interval) and display them on a single line with an " [x#]" suffix
which identifies the number of times the message was repeated during that
interval.
Also created a common log_msg() function and eliminated a lot of copy/pasta
in the various *_log_msg() functions.

Nov-28-2017 (don't save .ini files with every change of log-levels), it was
quite easy for the visible log level controls and the actual log level (in the
startup structures) to get out-of-sync.

I'm pondering saving the selected log-level when recycling or something else,
but for now at least the visible controls match the real log level.

chat, rather than the old startup options flag ([BBS]->SYSOP_AVAILABLE).
This will be much easier for other processes/programs to query and control.

controls. Since Nov-28-2016, this would trigger a recycle of all the servers,
which was really unecessary. So instead, just make sure we save the .ini file
when the program closes (in addition to the other times its saved).

for the Log Level controls calls SaveIniSettings).

- "Configure" menus (not working since the IPv6 commit) - both IPv4 and IPv6
   addresses may be specified (comma-separated), or multiple IPv4 addresses!
- Added new "Temp Ban" settings to Properites->Security tab.
- Added context (tab) sensitive "Help" button to Properties page
  (links to section on relevant wiki page).
- Every log window has a new right-click pop-up menu with 2 options:
  1. Copy Selected
  2. Copy All
  Hopefully it's obvious what these menu options do. :-)

By default, after 20 consecutive (unique) failed login attempts, *or*
a failed login attempt wtih a name from the name.can filter file.
The default temporary ban duration is 10 minutes.
The temporary ban thershold is configurable via LoginAttemptTempBanThreshold
in sbbs.ini and the ban duration is configurable via LoginAttemptTempBanDuration
(in seconds).