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.

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

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

JavaScript-C (SpiderMonkey).