HST Setup
---------


John Souvestre & Jim King

June 5, 1988



This note describes how to set up the USRobotics Courier HST
(9600 baud) modem for use ProComm Plus, version 1.0, and
QModem, version 3.1A.

The RS-232C cable connecting the modem to the computer's serial
port should have at least the following pins connected: 1, 2,
3, 4, 5, 6, 7, 8, and 20.




Setup for USRobotics Courier HST
--------------------------------

First, check to make sure that you have a current Supervisor ROM.
Give the modem the I7 command. Check that the supervisor date
is 02/25/88, or later. If not - call USR and get a current
version.

The following assumes a fixed line rate (19.2K) between the
computer and the modem. This gives maximum performance. The
HST is set to factory defaults, except for:

S7=45[Optional - Increase carrier detect timer]
S11=50[Optional - Increase dialing speed]
S19=10[Optional - Set inactivity timer]
T[Optional - Touch-tone dialing]
X6 or X7[Necessary - Extended result codes]
&B1[Necessary - Fix DCE/DTE rate at 19.2k]
&H1[Necessary - Hardware flow control for transmit]
&K0[Optional - Disable compression, better for
ARC'ed files]
&R2[Necessary - Hardware flow control for receive]
&S1[Necessary - Modem controls DSR]

(Use the AT prefix to set the above then save with AT &W.)


DIP Switches:

1 - Up[Necessary - Data Terminal Ready follows pin 20]
6 - Up[Necessary - Carrier detect follows signal]




Setup for ProComm Plus, Version 1.0
-----------------------------------

Line/Port Setup:

15[19200,N,8,1]


Setup Facility - Modem Options - General Options:

Initialization command .. AT Z^M~~~AT S0=0 E1 M3 Q0 V1 X7^M
Dialing command ......... AT &M4 &N0 DT
Dialing command suffix .. ^M
Hangup command .......... ~~~+++~~~AT H0^M
Auto answer command ..... AT &M4 &N0 S0=1 S2=255^M
Wait for connection ..... 40 seconds
Pause between calls ..... 1 seconds
Auto baud detect ........ ON
Drop DTR to hangup ...... YES


Setup Facility - Modem Options - Result Messages:

300 baud connect message ......
1200 baud connect message .....
2400 baud connect message .....
4800 baud connect message .....
9600 baud connect message .....
19200 baud connect message .... CONN
No connect message 1 .......... NO DIALTONE
No connect message 2 .......... NO ANSWER
No connect message 3 .......... BUSY
No connect message 4 .......... NO CARRIER


Setup Facility - Terminal Options:

Duplex ............................ FULL
Software flow control (XON/XOFF) .. OFF
Hardware flow control (RTS/CTS) ... ON


Dialing Directory - Dialing Codes:

A- &M4[Enables ARQ - default]
B- &M0[Disables ARQ]
C- &N1[Force 300 baud]
D- &N2[Force 1200 baud]
E- &N3[Force 2400 baud]


Dialing Directory - Entries:

Set all entries to 19200.

The default is to call at 9600 baud with ARQ enabled. The
first time you call a new number (ex: 555-1212) wait till
you see the CONNECT message then look at the ARQ light on
the modem. If the light is on then suffix the phone number
with "-A" (ex: 555-1212-A). If the light is out then
suffix the phone number with "-B" (ex: 555-1212-B).
Disabling ARQ will speed up the connection by about 5
seconds. The "-A" suffix does nothing, functionally, but
lets you know that you have determined that this phone
number does have ARQ and makes your directory entries line
up. Note: To connect at 9600 baud ARQ must be enabled.

The "-C", "-D", and "-E" suffixes (use only 1 at a time)
will limit the modem to 300, 1200, or 2400 baud,
respectively. This is handy for testing and diagnosing
problems. Ex: 555-1212-BE.

Note: When connecting with ARQ the connect message will
include "/ARQ" (ex: CONNECT 2400/ARQ). ProComm ignores the
"/ARQ" but the software at the other end may not. The
result may be that you can connect to the other modem, but
the other CPU will not recognize its modem's connect
message. By disabling ARQ ("-B") and calling back you
should be able to get through. When you do, tell the other
person that he either needs to change his software to
recognize his ARQ connect message, or he needs to disable
the ARQ part of the connect message. If he has an HST, the
"&A0" command will do this.




Setup for QModem, Version 3.1A
------------------------------

Run QINSTALL (either from the DOS command line or by typing
Alt-N from within Qmodem). From the main menu, select _2)
Hardware_, and then _1) Modem Setup #1_. Change the initial
baud rate to 19200.

Go back to the main menu. Select _4) RunTime Setup_, then _1)
Defaults #1_. Say YES for "Do you want CTS signal checking?"
(so that Qmodem will do CTS/RTS hardware flow control), and NO
for "Do you want Redial to set baud rate?" (so that the baud
rate will be fixed at whatever you have in the dialing
directory [usually 19200]).

Change the dialing directory entries for all HST-equipped
boards to 19200 baud. You should also change the baud rate to
19200 for all low-speed MNP connections (in case the other
modem has MNP level 5, then you can take advantage of the
modems' data compression feature). You may want to go ahead
and change all entries to 19200 baud, although this is not
necessary. To force a connection at a lower baud rate, set the
dialing directory appropriately (rather than using dialing
suffixes).

Since Qmodem doesn't allow a dial suffix character as part of
the phone number, put the &M4 (enable MNP) and &M0 (disable
MNP) directly in the phone number. For example, a number for an
HST or MNP-equipped board would look like "555-1212 &M4", while
a non-MNP board would have a number like "555-1212 &M0".




General Notes on 19200 Baud
---------------------------

Some computers (particularly 4.77 MHz, 8088 machines) will not
support 19200 baud. If you have this type of computer, use
9600 baud instead.

If you are running a program that makes heavy use of extended
memory (like VDISK) during communications, you may lose
characters. With VDISK, you can fix this by reducing the size
of the extended memory transfer buffer.

Under DesqView, always run the communications program in window
#1.

Under OS/2, running a communications program in the DOS
compatibility box at 19200 baud, you will lose characters. Get
an OS/2 communications program.