system: You are Nigel Murray, a caller on a 1990s BBS posting in the Telemate message echo. Write like a real BBS user of the era — plain, direct, in your own voice, no modern polish.

user: You are replying to Gordon Vanscheik about "TMW Hints & Tips".

They wrote:
GV>                   TELEMATE FOR WINDOWS 1.00 ... HINTS & TIPS
GV>
GV> This is just something I have decided to do ... mainly in
GV> response to some people who post problems and who obviously do
GV> not read help files :)  I am also concerned with several posts
GV> that state that TMW is not easy to use.  Nothing could be further
GV> from the truth. It is deep, rich, and very, VERY easy to set up
GV> and use (remember, people said the same thing about the DOS
GV> version!!  And now they swear by it).
GV>
GV> BUT, TMW is not necessarily intuitive right off the bat!  One MUST
GV> read the help file ... that is why Winfred has it open as the last
GV> step of the install process. Hint hint hint ...!
GV>
GV> Anyway, this is just the beginning ... this HINTS & TIPS file will
GV> grow as YOU ask questions and as I learn. But please people!
GV> READ THE HELP FILES THAT COME WITH TMW!!!!!!!!!!
GV>
GV>                   OPTIMAL WINDOWS SETTINGS FOR RUNNING TMW:
GV>
GV> 1) Make sure that you have a 16550a(fn) UART on either your modem
GV>    or on your I/O card.
GV>
GV> 2) Make sure that you are utilizing the proper communications
GV>    driver in Windows.  If you are still running Win 3.1, then you
GV>    MUST do the following: Replace COMM.DRV with a third party comm
GV>    driver such as CYBERCOM or WFXCOMM (WFXCOMM is highly recommended).
GV>    If you are running Window for Workgroups 3.11 then you do not need
GV>    to replace COMM.DRV.
GV>
GV>    NOTE:
GV>    If you are using Windows 95, just make sure your modem is installed
GV>    correctly (use CONTROL PANEL and follow the step-by-step
GV> procedure).
GV>    You may want to change the default MAXIMUM SPEED setting for 14.4
GV>    modems from 19200 to 38400.  This is all you need to do in Windows
GV> 95.
GV>    There is no need to do any of the following.
GV>
GV> 3)  Add the following lines to the [386Enh] section of your Window's
GV>     SYSTEM.INI file (Please note that the "x" in the Comx????
GV> statement is
GV>     a reference to the com port your modem is dedicated to.  For
GV> example,
GV>     if your modem is dedicated to com2 the the ComxBuffer= line would
GV> read,
GV>     Com2Buffer=):
GV>
GV>     ComxBuffer=10000  ;Windows com buff default is 256 bytes.
GV>     ComBoostTime=4    ;Windows default is 2.
GV>
GV> 3b) If you are utilizing WFXCOMM.DRV then add the following lines to
GV> the
GV>     [386Enh] section of  your SYSTEM.INI:
GV>
GV>     ComxRxSize=4  ;Defines the interupt threshold for the receive
GV> FIFO.
GV>                   ;Default value is 14, but a lower setting of 4
GV> increases
GV>                   ;receive reliability (8 may work well ... I
GV> recommend 4).
GV>                   ;NOTE: the "x" after the "R" in ComxRxSize= is NOT
GV>                   ;referring to your com port ... it is to remain an
GV> "x."
GV>
GV>     ComxTxSize=16 ;Defines the number of bytes loaded into the
GV> transmit FIFO
GV>                   ;on each interupt.  Default value is 8, but 16
GV> reduces
GV>                   ;interupt overhead without decreasing reliability.
GV>                   ;NOTE: the "x" after the "T" in ComxTxSize= is NOT
GV>                   ;referring to your com port ... it is to remain an
GV> "x."
GV>
GV> 3c) If you are using Windows for Workgroups 3.11 and are using its
GV>     default COMM.DRV, you may exercise the same control over COMM.DRV
GV> as
GV>     the above gives for WFXCOMM.DRV by adding the following lines to
GV> the
GV>     [386Enh] section of your SYSTEM.INI:
GV>
GV>     ComxRxTrigger=8  ;Valid values are 1,4,8, or 12 ... use 8 unless
GV>                      ;you receive CRC errors--then experiment.
GV>                      ;NOTE: the "x" after the "R" in ComxRxTrigger= is
GV> NOT
GV>                      ;referring to your com port ... it is to remain
GV> an "x."
GV>
GV>     ComxTxFifo=1     ;NOTE: the "x" after the "T" in ComxTxFifo= is
GV> NOT
GV>                      ;referring to your com port ... it is to remain
GV> an "x."
GV>
GV> 3d) Remove any lines that refer to "ComxFifo=" in the SYSTEM.INI. The
GV> FIFO
GV>     is enabled by default ... hence this line is redundant (If you are
GV>     utilizing WINFAX PRO, then having the entry ComxFifo=2 is a valid
GV>     but unnecessary setting).
GV>
GV> 4) If your modem is running on Com4 and you are not utilizing Com3
GV> then you
GV>    must disable Com3 while in Windows.  This is accomplished by
GV> editing your
GV>    Window's SYSTEM.INI file and altering the following lines found
GV> under the
GV>    [386Enh] section:
GV>
GV>     Com3Irq=4
GV>     Com3Base=03E8
GV>       to
GV>     Com3Irq=-1
GV>     Com3Base=-1
GV>
GV>   If you do not have the above lines in your SYSTEM.INI, then add them
GV> to
GV>   the [386Enh] section.  You should also add the following lines in
GV> the same
GV>   section stating the address of the Com Port and the IRQ it utilizes.
GV>
GV>     Com4Irq=3        ;Or whatever FREE irq you choose.
GV>     Com4Base=02E8
GV>
GV>   -=> Continued Next Message <=-
GV>
GV> --- FMail 0.96g
GV>  * Origin: The Other Side BBS - (403)346-5920 - (1:3417/2)

Write your reply.

assistant: On 08-31-95 Gordon Vanscheik wrote to All...
___
 * OFFLINE 1.56 * Unable to locate Coffee -- Operator Halted!