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

Recompiling ver.cpp only now, so need link ver.obj/o with the various targets now. I'll need to update the objects.mk for the *nix builds, next.

Replace use-of/linking-with wsock32.lib with ws2_32.lib to fix issues such as this one coming-up with the HAProxy feature merge:
unresolved external symbol __imp__inet_pton@12 referenced in function _xpms_accept 

This fixes the stat() issue on Windows XP/2K3 by allowing sbbs to benefit
from the run-time library updates that Microsoft releases periodically
(like https://www.microsoft.com/en-us/download/details.aspx?id=53840).

For more info on the stat() issue which caused all kinds of sbbs errors
(e.g. creating directories initially, but a lot more):
https://stackoverflow.com/questions/32452777/visual-c-2015-express-stat-not-working-on-windows-xp

Since we are using cryptlib which requires the MSVC runtime DLL anyway
(it is the default build behavior of MSVC), we weren't really gaining
anything from statically linking the CRTL (LIBCMT.LIB). And for some reason,
an up-to-date MSVC2019 still has (links-in) a LIBCMT.LIB file that includes
this stat bug. All the online help resources I found just to seem to suggest
updating the CRTL DLLs (on the target system), with no mention of any fixes
available for the static CRTLs on the build system. But with the no gain
from static linking anyway, I figured it was time to switch to DLL CRTLs.

The debug builds are still statically linking the CRTL for no particular
reason.

Visual Studio 2017 - Windows XP (v141_xp) toolset

Removed v4upgrade from sbbs project.

You get a warning if a minimum version is specified and SubSystem is not.
WINDOWS is for "applications that don't require a console" (like the DLLs)
and apparently the only difference is in standard (main/WinMain/etc) entry
point handling... which shouldn't be an issue in the DLLs.

If DigitalMan uses the Edit and Continue feature, he can fix it.  :-)

defines XPDEV_THREAD_SAFE (not currently used in Windows builds) and
LINK_LIST_THREADSAFE (notice the inconsistent use of underscore :-)
Use of this property sheet fixes the problem with the terminal server global
variable 'uptime' getting corrupted when jsrt_GetNew() called listInit() from
js_rtpool.c which didn't #include sbbs.h and therefore had a different idea
about the size of link_list_t and thus corrupted the global data region
(zeroing out the 'uptime' variable, probably amonst other important things).

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.

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

(e.g. src/js/win32.release/*).

JavaScript-C (SpiderMonkey).