When a sysop wants to chat, he wants to chat right now, damnit!

rather than just falling over and twitching like an injured slug

- JS system.operator_available property (read/writeable)
- SYSAVAIL @-code which expands to LiSysopAvailable or LiSysopNotAvailable
  (use the new SYSAVAIL @-code in the chat menu to show availabilty to chat)
- ;avail sysop command (in str_cmds.js) to toggle sysop availability
- Changed LiSysopIs text.dat string to be a format string (include %s) and
  the trailing \r\n, so that it can be used in str_cmds.js or anywhere else
  to report sysop availability to chat, or can be set to blank string to
  display nothing (this would not work previously).

Why isn't this fat cats bbs dot com? <shrugs>

Set survey=false in the [newuser] section of modopts.ini to disable the
"Where did you hear about this BBS?" new user question.

It's possible that isdir(temp_dir) will be false and then a mkpath()
call will fail because some other thread came in and crated the
directory at that very moment - so save errno if mkdir fails and
call isdir() again to double-check that the directory wasn't created
by someone else already.

into our revision-controlled text files. :-(

update frame.putmsg() "normal" ctrl-a code to use attributes from frame initialization (ansi "normal" is relative to the frame's settings). to emulate standard "normal" behaviour, initialize frames with BG_BLACK|LIGHTGRAY

Apparently, calling close(-1) on WinXP will cause a crash. Don't do that.
Make closeuserdat() resilient to an un-open file descriptor and use it
instead of close().

Hopefully The BRoKEN BUBBLe BBS stays "up". :-/

Also, added Starstocks. Stalk your favorite stars here!

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.

So don't bother linking to 00index*, just the ftp root dir should work
(for a while yet, anyway)

Previously, just the NodeNIsNotInUse message would be displayed.
Instead, display the NoNeedToSendMsgToSelf message.
Sysops are free to message themselves.

active_clients is destroyed in cleanup(), so it must be re-initialized inside
the server init/recycle loop.

bool (JSVAL_FALSE), not number (JS_FALSE).

Throw an exception if no filename is specified (rather than just abort the
script by returning JS_FALSE).

The return value is supposed to be a bool, not an int (JS_TRUE != JSVAL_TRUE).