default connect ANSI.  Copied this file from web/root/ftelnet/ftelnet-resources.

Not sure why there are two ftelnet copies... one likely doesn't belong.

(alphabetically) since pulling/merging from multiple lists (add'l echolists
and the areas.bbs) often creates a confusing mix of sorted and unsorted area
names.

Fix %LIST AreaFix response for ELIST_ONLY mode.
Fix %UNLINKED AreaFix response for non-ELIST_ONLY mode (include echolists).
Fix alter_areas() crash introduced in rev. 236 (j was not valid here).

Add help.
Add the COUNTRY commad which uses cty.dat for DXCC country prefix lookups.

rev 236 (this this one, access===D).

callsign was used in the match.

it resolves Joe's errors with areas.bbs modifications via AreaFix on Windows.

Yay!

Better/more log output when receiving AreaFix requests for echo/area lists.

ELIST_ONLY option: include unlinked echoes from "additional echolists" in the
response (rather than just "None.").
Created and used area_is_linked() function for the commonly copy/pasted code
for checking if a specific node address is already linked with a specific area.

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).