Paul, at 22:10 on Mar 30 1996, you wrote to All...

PE> Note that 6 hours later, when I discovered the modem still off-hook,
PE> the Carrier Detect light was not on, but the "On hook" light was on.

Urk!  Good thing it wasn't an outbound ISD call then.  :)

PE> I dropped DTR several times and the modem refused to hang up.  
PE> I tried going "+++", but I was not expecting that to work, because I
PE> have that disabled.  I had to physically switch the modem off!!!

Bloody hell, this sounds like much the same problem that cursed many owners
of M7Fs, and occurred so frequently with Chris R that he pissed off the
NetComm and bought a Banksia instead (this was at his work though, not at
home).

PE> I NEED DTR to work properly, or at least I need the modem to HANG UP
PE> if it fails to connect.  An ISP that I know (Matra) has reported the
PE> same problem. 

Are they running M34Fs as well?

PE> Oh, I am running with AT\V6 now, as you can tell from
PE> the detailed stats.  The ISP says that when the problem happens for
PE> them, and someone tries to ring, the line appears as not-answering,
PE> as opposed to engaged. 

That's a serious problem, and it just ain't good enough in a $500 modem. 
In fact, it's bad enough that you might even qualify for your money back if
that's what you want.  Trouble is, what the fuck do you replace it with?  
Maybe Paul Markham will sell you his Courier quite cheaply, if you ask him
nicely.  :)

PE> 7. As you can see from the following log...
PE> > 30 Mar 11:14:14.00   AT%L
PE> # 30 Mar 11:14:14.03   050
PE> After receiving an incoming call, the receive level is being printed
PE> as -50db.  It is the same on EVERY incoming call.  As well as being
PE> what I believe to be a wildly inaccurate number, I do not expect that
PE> the levels would be exactly -50db on every single incoming call.

Hadn't you already determined that -50dBm to be a faulty reading?

Regards, Bill

--- Msgedsq/2 3.20