"ser2.zip" is a zip file (pkzip 2.04g) containing three files:

ser2.exe - a new version of sersetup.exe with two bug fixes and several other
modifications to help improve things and keep stats during the connection.  The
first bug fix is the one from nuser.exe, by Dave Thomson, which keeps the head
and tail from becoming too large -- this prevents overflow and also keeps the
time to perform the mod operation at a minimum.  The mod problem caused many
people to see a huge slowdown after about 2 minutes.  Actually, I mention the
first bug only so you know that it's taken care of -- Michael Corrigan sent me
several modifications which actually remove the mod operation altogether, plus
take care of the second bug, which is the 'extratics' variable -- this fix
seems to get rid of the 1/4 second delay which occurs every couple of seconds,
especially on Gateway Telepath I's.  Michael also added a lot of statistical
counters, and made it possible to connect at baud rates up to 19200.  There are
other things too, but you can type 'ser2 -?' or 'ser2 -help' for the usage
lines.  You might try '-player1' on the slower computer if you have two
computers of drastically different speeds -- not sure, but the comments in the
code seem to imply that will help.

I posted 'ser_rg.zip', which contained 'ser.exe' a couple of days ago.  Some
people got it to work, others didn't -- the failure seemed to be that one or
both people went straight to the demo.  I did a lot of testing on this, and
found that ser.exe works great (for me) if I use Procomm to connect first,
then just type 'ser -com#'.  If I use 'setup.exe' or use the '-dial' or
'-answer' arguments to ser.exe, it goes straight to the demo for me too.  After
many hours, my final conclusion is that I don't have a clue as to why.  Which
brings me to the next two files.  For those of you that don't have comm
programs, use the following INSTEAD of setup.exe and -dial and -answer:

dial.bat - a small batch file that just echo's AT commands to the com port, and
prompts you to hit return a couple of times, then finally runs 'ser2.exe'.

answer.bat - similar, but for the answering computer.  Basically just does an
init string (like dial.bat), and then runs 'ser2.exe'.

You can easily edit these files, change the init strings or the arguments to
ser2.exe.  I put a "%1" after ser2.exe so you can type something like 'dial
-19200' to connect at 19200 (or 14400) baud.  You'll probably have to change it
for the init string, and also the com port if you don't use com1.  Take a look,
it's pretty simple.  Keep in mind that some modems won't process anything after
ATZ, so you might want to put two init lines in.  Or better yet, use AT&F to
reset to factory defaults, then another init string.  I'd suggest putting
'S0=1' somewhere in the answering init string so the modem automatically
answers, then you just listen for the modems to stop screaching, and hit
rerturn to start the game.  On many modems, to set the baud rate to 14400, you
might use one of the following:  If you use &N6, use &N8.  If you use S37=9,
use S37=11.

If you'd like the source code I used, write me.  Many thanks to Dave Thomson
and Michael Corrigan -- I say that so you can blame them too if it doesn't work
right :-) :-).

Ok, so here they are -- now go play Doom and write me and tell me that it
worked great. :-) :-)

Russell     (gilbert@esd.dl.nec.com)