application" error message (when run on XP) and reportedly will allow target
executables to run on non-SEE (pre-Pentium III) CPUs. Seriously, anyone really
running Windows XP on a Pentium II today? I guess it's possible <shrug> and we
really get little benefit from SSE in Synchronet.

I couldn't get Windows 2000 running in Hyper-V, so I guess Windows 2000 is
now officially unsupported by Synchronet (and long unsupported by Microsoft).

Thanks to Android8675 for the bug report and Rushfan for the solution tip.

(don't assume SSE support in target CPU).

number of hash sets (don't let these files grow indefinitely).

build error) - conflict with definition form vadefs.h.

loop immediately upon socket receive error (e.g. 54, ECONNRESET).

better and has a higher alchohol content.

Use a linked list to track runtimes, thereby allowing an unlimited number
of them.

These functions are still needed since Spidermonkey crashes if more than
one runtime is created simultaneously.

initialization due to no service sockets being successfully bound. The crash
was in cleanup(), while checking the 'theads_pending_start' protected-int,
which had not been created/initialized yet. The fix is to create/init the
threads_pending_start protected-int before any possible call to cleanup().

The system.inet_addr property is for Internet email and not necessarily the
correct host name for this instance (these nodse) of the BBS.
The "2nd rlogin name" is now *always* used as the login name for RLogin.

The system.inet_addr property is for Internet email and not necessarily the
correct host name for this instance (these nodse) of the BBS.

also clear the associated counts (sizes) for these arrays, eliminating some
potential crashes while dereferencing these arrays after freeing (e.g. during
shutdown or recycle of sbbs).

so the runtime "pool" concept might need to go away. For now, we'll just change
the RT_TYPE to RT_UNIQUE (no sharing of runtimes, using more memory) and
double the size of the RT pool from 128 to 256. Without sharing, the pool may
not make sense unless there is a significant time penalty when first creating
RTs (in which case reusing RTs will be faster).

of these files for now (if you don't want to upgrade just yet).

Don't use the WIN_SAV mode for the question toggles (causes unnecessary
screen flash).
Save/restore the current lightbar offset for the new user "default toggles"
and "new user questions" lists.
Refer to the "chat handle" field as "/ call sign" here as well.

of the new user process - could be used to display a file or execute a script
via @-code.
Introduced the "Color Terminal" new user question toggle (defaults to off).

- MaxMsgSize
- MaxMsgsWaiting
- ConnectTimeout
Added NO_DOS comment to [bbs]->Options section

for 20 megabytes).

of these files for now (if you don't want to upgrade just yet).

for that instance of SBBS (e.g. when running SBBS-Win32 on Windows-x64).

has been configured to 0 (unlimited).

Windows 8.0, a.k.a. NT v6.2 instead of Windows 8.1, a.k.a. NT v6.3) by using
a LAN manager API function. Ugh.

a linked list which had previously been freed, it would try to destroy the
mutex (Win32 critical section) which had already been destroyed and cause a
crash. Clear the LIST_MUTEX (and LIST_SEMAPHORE) flags after freeing those
resources to prevent this double-free issue.
This bug was apparently triggered by the web server (listFree(&log_list) in
cleanup()) because cleanup() can be called in some recycle failure cases
(e.g. ports cannot rebind) *before* listInit() is called. Some *other* error
following a recycle must preced this bug/crash.

Thanks to Noel for helping with the debugging (capturing callstack with MSVC).

specified as enumerations in the spec but relying on more than one outside
entity for a definition of the values (ie: County and State values)

These types aren't validated.

- Max Msgs Waiting per user (does not apply to W-exempt users)
- Connect Timeout (for sendmail outbound connections)
Allow these parameters to be set to 0 (N/A):
- Max Recipients (0=unlimited)
- Lines Per Yield (0=no yielding)

sendmail thread was running.

not match database and beginning new user sing-up.

SSH), use that as the default login name.
Clear the bbs.rlogin_name value if the login fails.