* Crossposted in area LOCSYSOP, AUST_MODEM

I am now running an M34F with new (beta) ROMs and I am testing
to see what problems still exist.  So far I have had one old
problem apparently disappear, and one remain.  I have also 
basically finished the documentation of the Spirit Viper problems,
a serious one came up just near the end of my testing!  VIPER.ZIP
appears below.  NETCOMM.ZIP is updated as I rediscover bugs etc.
BFN.  Paul.

Modem usage on TML:

1993-04-12T22:24 Spirit II
1994-03-09T18:21 Spirit Thunder
1995-01-31T21:16 Spirit Viper
1995-02-02T09:23 Spirit Thunder
1996-01-20T23:25 Netcomm 1234SA
1996-01-21T18:58 USR Courier V34
1996-02-21T10:55 Netcomm M34F
1996-02-26T10:53 Spirit Viper
1996-02-28T09:40 Netcomm M34F
1996-03-02T00:30 USR Courier V34
1996-03-02T17:07 Netcomm M34F
1996-05-03T09:51 Spirit Viper
1996-06-11T13:30 Netcomm M34F with beta code


These are the problems I experienced with the Spirit Viper.
I had the modem on trial (for a second time!) for 2 days
on 1996-02-26.  On the whole, I don't have much to report
problemwise!  Third time trial started on 1996-05-03.

Problems with the Spirit Viper

1. A USR Sportster V34 is connecting to me at 28800 but without
EC.  Replacing the Viper with a Courier makes the problem go
away, which means the problem is fixable in the Viper.  Also
happens with a USR Courier V34.

2. A Netcomm M34F got a 26400 connect to me, whilst when I put
an M34F online, it connects at 28800 all the time.

3. ATW2 is documented in the manual as being the default.  It
isn't, ATW0 is.

4. ATW0 is documented in the manual as reporting only the DTE
speed.  It doesn't, it reports PROTOCOL etc.

5. S95 is documented in the manual as having a default value of 1.
It isn't, it's 46.

6. S2 says the range is "0-255 seconds".  It shouldn't have 
seconds.  It should possibly have instead that values >127 
disable the escape character.

7. S31 is documented as having a default value of 194.  This is
correct.  It is documented as having bit 2 = 1 as the default.
This is not correct with a value of 194.

8. Page 58 of the manual says that +FAA controls adaptive answer,
then shows AT+FA=1.  The list on the previous page shows +FAE
as controlling adaptive answer.

9. When I try to put either of these commands into binkley.cfg,
to answer the phone with adaptive answer...
Answer AT+FCLASS=2;+FAE=1;+FCR=1;A|
Answer AT+FCLASS=2;+FAA=1;+FCR=1;A|
it fails to recognize a data call.  In other words, adaptive answer
does not appear to work as "documented".  This may have just been
the one modem failing to connect though, I don't know.  Anyway, since
then, I have put in "AT+FAA=1;A|" and there is only the one modem
that I know about that fails to connect, which is a Banksia V34.  The
user says disabling NG tones his end fixes the problem, but says the
problem is my end.

10. Using AT+FAA=1;A as the answer string succeeds in adaptive 
answering to a variety of data calls, but failed on a Banksia.

11. Viper locked up after receiving a call, the lights:
OH, DSR, DTR, RI and PWR were on.  The call went like this:

# 10 Jun 02:04:59.69   RING
> 10 Jun 02:04:59.82   ATA
# 10 Jun 02:05:17.47   CARRIER 26400
> 10 Jun 02:09:36.82   dropping DTR
> 10 Jun 02:21:46.63   dropping DTR

Normally I get a "PROTOCOL xyz" after the "CARRIER 26400".
The prior connect was a 14400 connect, which worked fine.

12. A USR Sportster V32bis failed to get a connection with me,
his end reported BUSY...

> 09 Jun 08:23:55.38   dropping DTR
> 09 Jun 08:36:30.00   dropping DTR
# 09 Jun 08:38:20.91   RING
> 09 Jun 08:38:21.07   ATA
# 09 Jun 08:39:14.28   NO CARRIER
# 09 Jun 08:43:09.10   RING
> 09 Jun 08:43:09.25   ATA
# 09 Jun 08:43:19.38   CARRIER 14400
# 09 Jun 08:43:19.91   PROTOCOL: LAP-M
# 09 Jun 08:43:19.94   COMPRESSION: V.42BIS
# 09 Jun 08:43:19.97   CONNECT 14400/ARQ
@EOT:

---