>>> Part 2 of 2...
throughput.
I used L0 and M0 to disable the speaker (I hate that screechy noise)
although you may deem it useable.
By using the entry ATZ1, I forced ProComm to load its settings from
the Profile 1 in NVRAM, leaving the Profile 0 alone.
Your modem may not support 115200, but most likely will. If not,
configure the baudrate setting to the highest your modem will support.
Once you've custom-tailored the file, you'll need to reconfigure
ProComm. Go to the directory where it resides, and type PCINSTAL at
the prompt. Run through the options, and bingo, your modem will be
listed in the selectable modems. Select it, and permit it overwrite
the modem's defaults (meaning set the settings/registers the way the
MODEMS.DAT entry tells it to), and to update your dialing directories
(meaning set the max baudrate to 115200).
Once you've installed everything correctly, there are still a few
things to consider. ProComm does not have integrated FIFO buffer
support for the 16550 chip in your modem. This is not particularly
troublesome unless you start to experience data overruns or errors on
file transfers. There are two things you can do. The first is to
obtain a DOS-based FIFO utility (lots of BBS's have these) and build
it into a batch file, or run ProComm under Windows and use its FIFO
support. Personally, I do both. Here's the batch file named PCPLUS.BAT
I've created with some notations to help you understand how it works:
@echo off     <---turn off any messages reported by DOS
cls           <---clear the screen
cd\pcplus     <---change to the ProComm directory
16550 1 on    <---activate 16550 FIFO support on COM1
pcplus        <---load ProComm
16550 1 off   <---turn off 16550 FIFO support after exiting program
cd\           <---change back to the root directory
cls           <---clear the screen (get a clean C:\ on the screen)
Getting FIFO support under Windows is a bit trickier. It depends on
which version you're using. Here's what you'll have to do to get it:
Windows 3.1 FIFO support
Make sure the following line is present in the [boot] section of the
SYSTEM.INI file:
COMM.DRV=COMM.DRV
Add the following lines to the [386Enh] section of the SYSTEM.INI
file (substituting your COM number (1, 2, etc.) for the 'x' in the
lines:
COMMdrv30=FALSE
COMxFIFO=2
COMxBUFFER=1024
COMxAUTOASSIGN=1
COMxTXSIZE=14
COMxRXSIZE=8
COMBOOSTTIME=30
Windows 3.11 FIFO support
Windows 3.11 uses a different internal architecture for COM port
support called "VCOMM architecture" that 3.1 does not have. It will
support 16550 FIFO support with addition of the following lines:
In the [boot] section:
COMM.DRV=COMM.DRV
In the [386Enh] section:
COMxFIFO=1
COMxTXFIFO=1
COMxRXTRIGGER=8
Windows 3.1 and 3.11- Set the port speed to 115200 by going under
Control Panel, then Ports, and set the baud rate to 115200, even
though it is not listed as an option. It will work nicely (or has for
me for the past 3 years).
When you do run ProComm, go into Setup (Alt-S) and make sure the
selection for auto baud rate adjustment is OFF. Also, change the
connection messages from CONNECT to CARRIER so that your modem will
report all messages fully.
If you need more help, let me know.
Stu
... I saw Elvis...I sat between him and Bigfoot on the UFO...
--- TAG 2.7c + FastEcho 1.45a
---------------