client_socket_dup before activating the passthru_socket. This resolves the
issue of external programs receiving stale data from the previous passthru
session - data that was not sucessfully read by the last external program
invoked.

file named in the ZFILE frame, they will usually compute the local CRC
value and request the sender to compute and send its CRC of the file it
wants to send. If the CRCs match, the receiver will send a ZSKIP frame
next ("skip this file, I already have it"). However, when I implemented
the ZCRC frame support in zmodem_send_file(), I added the ZCRC frame
check *after* the check to see if its a ZSKIP frame, when in fact, they
will normally come in the other order (ZCRC, then ZSKIP). This would result
in multiple ZCRC request/response, then ZSKIP requests that were ignored
by the sender (who just send a ZFILE frame again). Simple fix: check for
ZCRC frame before ZSKIP frame.

upper-case character.

Provide upper-case wrapper for compatibility.

dependencies (scfglib*.c, scfglib*.c, etc.) for the single-threaded SBBS
that need to load the configuration (*.cnf) files from ctrl.
Rather than updating 8 projects every time the load_cfg.c dependencies change
and rebuilding 8 times, just use a lib.
Also fixed-up some linker warnings about EDITANDCONTINUE, blah, blah, blah.

lines in the QWK body (not '\xE3'), even if the message contains invalid
UTF-8 character sequences.
This likely fixes the recent issue with blank messages and QWK kludges being
imported into body text.

needs functions in str_util.c.

wrapper for utf8_normalize_str() and utf8_replace_chars with the proper
arguments.
This will fix *a* problem with UTF-8 message not being converted to CP437 in
QWK packets correctly (we were just normalizing, not fully converting).
Also got rid of the defunct DLLCALL usage str_util.c

as "Cancel" (i.e. overwrite and rename options did not work).

(with an ACK) - you skip right to the requested transfer mode byte ('G').

Purge any pending receive data before sending the YMODEM header block.
This helps to insure that the next byte received from the receiver
(ACK, NAK, 'C' or 'G') is an actual response to the header block we sent and
not some other pending receiver start-request.

The problem that was observed was upon YMODEM-G uploads to the BBS/sexyz, the
receiver (sexyz) would send a few 'G's before the sender (e.g. SyncTERM)
would get around to sending the YMODEM header block (while the user selects
the file path/name to upload, takes a few seconds). The sender would see
the first of these buffered 'G's received while selecting a file as an
acknowledgement of the header block and then immediatley start sending file
data. Meanwhile, the receiver sees incoming file data *before* he actually
acknowledges the header block and throws it out as unexpectd data, so we're
out-of-sync and with YMODEM-G there is no recovery/retry scheme.

Now, it assumes the CR is bare (not followed by LF or NUL), so that should
probably be fixed. But for now, just copied pretty much as is from telnet_io.c
so I can eliminate another version of this function.

queue input.

the baked-in one.
Log a nag message that sysop should get an API key of their own if
they don't done got one.
Removed unusable if() block.

This is a massive change, but is required if I'm going to make LORD JSLint
happy, which will help a lot with testing.

dorkit.

rely on type coersion.  *defs.js should be jslint clean.

set the "Networked via FidoNet" flag for the newly created subs.
Similarly, for QWKnet and importing a control.dat file.
Also fixed a cosmetic issue with the import/export file type window
disappearing before the file path/name intput box appears.