RD> the Courier I think), the Banksia MyFastModem 33.6k is a nice unit (more 
RD> like $400 for the Banksia).

PE> It has problems connecting to Spirit Viper's and Lightspeed (and
PE> presumably most other Rockwell modems, although not the Netcomm
PE> M34F) when they (the Rockwell's) are set to adaptive answer. BFN. 
PE> Paul.

RD> In all the time I've been using a Banksia MyFastModem I havn't had a single 
RD> problem connecting to any other modem... Maybe I was just lucky that the 10 
RD> or so places I've called have not used modems with the Rockwell chipset...

Yep.  Here's a man who wasn't so fortunate...

Problems with Banksia modem, documented by John Tserkezis, 3:712/610
==============================================================================
==============================================================================
Outgoing poll to 436-1785, (Spirit Viper)

My logs:
----------  Mon 10 Jun 96, FD 2.12.SW
+  1:37:06  Event 0-{at}
+  2:05:01  Event 2-C
+  2:05:04  Calling Ten Minute Limit, 3:711/934, 436-1785
=  2:05:25  CONNECT 26400/NONE
?  2:05:39  No response from remote system
?  2:05:59  Unable to initiate transfer
?  2:06:05  Unable to complete mail transfer
$  2:06:05  To 3:711/934,  0:40, 44.
+  2:10:36  Calling Ten Minute Limit, 3:711/934, 436-1785
=  2:10:41  BUSY
 (Modem was busy for the next 12 hours until manually reset)

 His logs:
 # 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

"Viper locked up after receiving a call, the lights:
 OH, DSR, DTR, RI and PWR were on.  The call went as above.
 Normally I get a "PROTOCOL xyz" after the "CARRIER 26400".
 The prior connect was a 14400 connect, which worked fine."

Outgoing and incoming calls (on this site) directly before and after this poll
worked fine.  On this host, calls up to my poll worked fine, after my poll,
his modem was locked up he until manually reset it.  Note that I normally get
error correction and compression when calling.




==============================================================================
Outgoing poll to 387-2380 (Spirit Viper)

My logs:
----------  Tue 11 Jun 96, FD 2.12.SW
+  6:00:04  Calling Phantom Connection BBS, 3:712/311, 387-2380
=  6:00:27  CONNECT 26400/NONE
?  6:01:10  Session handshake failure
+  6:04:48  Calling Phantom Connection BBS, 3:712/311, 387-2380
=  6:05:12  CONNECT 28800/NONE
?  6:05:55  Session handshake failure
+  6:09:41  Calling Phantom Connection BBS, 3:712/311, 387-2380
=  6:10:05  CONNECT 26400/NONE
?  6:10:48  Session handshake failure
+  6:14:26  Event 0-{at}

His logs:
----------  Tue 11 Jun 96, FD 2.20c.mL; Task=2
=  6:00:26  RING
=  6:00:39  CONNECT 26400/NONE
?  6:00:55  Timeout waiting for handshake packet
?  6:01:05  Timeout waiting for handshake packet
?  6:01:15  Timeout waiting for handshake packet
?  6:01:25  Timeout waiting for handshake packet
?  6:01:28  Session handshake failure
   6:01:28  Terminating call
=  6:05:10  RING
=  6:05:24  CONNECT 28800/NONE
?  6:05:40  Timeout waiting for handshake packet
?  6:05:50  Timeout waiting for handshake packet
?  6:06:00  Timeout waiting for handshake packet
?  6:06:12  Session handshake failure
   6:06:12  Terminating call
=  6:10:04  RING
=  6:10:17  CONNECT 26400/NONE
?  6:10:33  Timeout waiting for handshake packet
?  6:10:43  Timeout waiting for handshake packet
?  6:10:53  Timeout waiting for handshake packet
?  6:11:03  Timeout waiting for handshake packet
?  6:11:05  Session handshake failure
   6:11:06  Terminating call

Outgoing and incoming calls (on my site) directly before and after this poll
worked fine.  On this host, calls before 6:00am worked fine albeit at slower
cps rates (rain had been causing noisy lines).  For that night, calls to his
site were ALL with no error correction/data compression, but my call was the
only one that failed.

 Calls incoming outgoing from his site worked fine afterwards.

 In both cases, a LAPM & v42bis connect are usually normal.

                            ==================

 Failed calls from here to this site are actually common, but the next time
my system automatically calls (in another five minutes), it works.

 A typical failed call looks like this:

+  6:00:04  Calling Phantom Connection BBS, 3:712/311, 387-2380
=  6:01:10  NO CARRIER
+  6:05:31  Calling Phantom Connection BBS, 3:712/311, 387-2380
=  6:05:49  CONNECT 26400/ARQ/LAPM/V42BIS
+  6:05:51  Phantom Connection, 3:712/311
        Works fine from here

 This happens at least twice a month, up to about seven times a month.  March
1996 was a bad month. One "no carrier" message is the norm,
although sometimes
it occurs a couple of times before connecting.

==============================================================================
Outgoing poll to 436-1785, (Lightfax)

Fax adaptive answering was enabled, and was eventually disabled for the third
time I called (2:15am).  This site had received my call as a fax connect.
Other incoming calls for this site with the lightfax and adaptive answering
worked.

----------  Sun 28 Jul 96, FD 2.12.SW
+  1:33:45  Event 0-{at}
+  2:05:01  Event 2-C
+  2:05:04  Calling Ten Minute Limit, 3:711/934, 436-1785
=  2:05:54  NO CARRIER
+  2:10:22  Calling Ten Minute Limit, 3:711/934, 436-1785
=  2:11:13  NO CARRIER
+  2:15:34  Calling Ten Minute Limit, 3:711/934, 436-1785
=  2:15:50  CONNECT 26400/ARQ/LAPM/V42BIS
+  2:15:51  Ten Minute Limit, 3:711/934
~  2:15:51    AKA: 69:1171/213
~  2:15:51  SysOp: Paul Edwards
~  2:15:51  Using: BinkleyTerm PE 4.02
:  2:15:51  Tranx: 31FACD56 / 31FACD12
~  2:15:51   Site: Somewhere
~  2:15:51  Phone: -Unpublished-
*  2:15:57  Rcvd \\JT_1\SYS\BBS\FD\FILES\FFFF0144.SA0; 13868b, 3467 CPS
+  2:16:00  Mail transfer completed
$  2:16:00  To 3:711/934,  0:10, 44.

==============================================================================
==============================================================================
@EOT:

---