From: wlrc@uhura.neoucom.edu (William R. Cruce)
Subject: Gateway Telepath tests
Organization: Northeastern Ohio Universities College of Medicine
Date: Mon, 23 Nov 1992 06:33:43 GMT


I have had a Gateway modem for several months.  I have not noticed
some of the problems reported by others on the net.  That is I have
used kermit successfully with it and I have not noticed any unusual
disconnections during long sessions.  I have noticed problems
making successful connections with other modems and that is the
main subject of this report (see below).

Before I get to that, a few comments.  The biggest problem with
the Gateway modem is Gateway's service staff.  The first line of
people one encounters on the phone do not understand anything about
modems, but will insist that they do until you pummel them with
a lot of difficult questions.  To talk to a service person who
really understands the modems is a matter of chance encounters.
Once I was transferred to someone both polite and intelligent and
who understood modems (he claimed to have been involved in the
Telepath's design).  Another time I  spoke to a person who was the
rudest and most unpleasant service person I have ever encountered.
The guy did, at the end of a painful hour on the phone, supply
me with a modification to the MODEM INIT string which proved to
work well (see below).

The biggest problem I have had with the Gateway is that I could not
reliably reset it to a standard condition, especially after having
to 'force' it into a fixed baud rate.  There are enough variables in
the phone lines without needing a headache like this.  The modifi
cations to MODEM INIT seem to fix this.
-------------------------------------

THE RESULTS OF MY TESTS:

Using Gateway 2000 Telepath (G2T) and Crosstalk For Windows (CFW)
Success of connections to various modems, using Modem Init String:

          ^MATZ~AT&F&C1&D2&G0&K3\N3S95=5X4E0V1

Note this is made from the CFW default G2T string:
          ^M~AT&C1&D2&G0&K3\N3S95=5X4E0V1
With the addition of 'ATZ' after '^M' and '&F' after 'AT'

The advantage of these two additions is that:
     1) They appear to truly reset the modem to the default MODEM INIT
          condition after the string 'N0S37=n' is used as a 'Dial
          Modifier' in 'Setup' (where n=9 for 9600 baud, n=8 for 4800
          baud, n=6 for 2400 baud).  See below for more details.
     2) You always get complete reports of Error Correction and
          Compression protocols when a connection is made (otherwise
          these reports disappear after forcing the modem to a fixed
          baud rate).

[A] 14.4k modems which *usually* auto-connect at 14.4k (LAP-M
protocol, v.42bis compression).

US Robotics Dual Standard HST/v.32bis/v.42bis
     Ontrack BBS "B" 612-937-8567
     Mustang (Qmodem) BBS "B", nodes 7-12, 805-334-2243
Hayes Ultra v.32bis
     Mustang (Qmodem) BBS "A" nodes 1-4,  805-395-0250
Telebit T3000 v.32bis/Turbo PEP
     local mainframe (sometimes requires forced connection at 9.6k)
ZyXel v.32bis/v.42/v.42bis 16.4k
     Rusty & Edie's BBS "F" 216-726-3632

---------------------------
[B] 9.6k modems which *usually* auto-connect at 9.6k (LAP-M protocol,
v.42bis compression).

US Robotics Dual Standard HST/v.32/v.42/v.42bis
     Toshiba BBS "B" 714-837-2116
     Gateway BBS "B" 605-232-2224
Practical Peripherals 9600SA
     Toshiba BBS "A" 714-837-2722(Sometimes auto connects at 9.6k,
          otherwise will not work at forced 9.6k but will at forced
          4.8k or 2.4k)
Unknown "v.42/MNP5"
     Local mainframe
Unknown "9.6k" modems
     Symantec (Norton) BBS   408-973-9834
     Softklone (Mirror) BBS  904-878-9884 (Sometimes auto connects at
          9.6k, othertimes requires forced 9.6k)

--------------------------
[C] 14.4k or 9.6k modems which *always* require forced 9.6k connection
(N0S37=9) (LAP-M protocol, v.42bis compression).

Hayes v.42 V-Series 9.6k (There have been reports that the V-Series is
'non-standard')
     Rusty & Edie's BBS "D" 216-726-3619
US Robotics Dual Standard HST/v.32bis 14.4k
     Rusty & Edie's BBS "B" 216-726-3589
US Robotics Dual Standard HST/v.32bis 16.8k
     Rusty & Edie's BBS "C" 216-726-3636

--------------------------
[D] Modems which require forced 2.4k to work (N0S37=6)

CompuCom Speedmodem Star v.32bis/MNP2-5 (Supposedly these will only
connect at 9.6k to another CompuCom)
     Toshiba BBS "E" 714-837-4572
     Rusty & Edie's BBS "E" 216-726-3584
Hayes V-Series Smartmodem 9600 (There have been reports that the V-
Series is 'non-standard')
     Toshiba BBS "C" 714-837-4409

--------------------------
[E] Numerous 2.4k modems, all "Hayes Compatible" connect correctly at
2.4k.

---------------------------------------------------------------
-- 
'This Escalator Doesn't Stop at Your Station'       #24/37 for BRAZIL

    Bill Cruce, INTERNET: wlrc@uhura.neoucom.edu, VOICE: 216-325-2511
   N.E. Ohio Univ. Coll. of Medicine, Box 95, Rootstown OH 44272-0095
From: bourman@hpcc01.corp.hp.com (Bob Bourman)
Date: Fri, 20 Nov 1992 00:39:23 GMT
Subject: Re: AT&F command - does it truly reset?
Organization: the HP Corporate notes server