Paul, at 23:36 on May 24 1996, you wrote to Bill Grimsley...

BG> Have a look at the following extract from the Binkley 2.60 docs, and tell 
BG> me if you had your Viper set up correctly, according to its fax class.  
BG> Unless it's a Class 2.0 (which it isn't), 

PE> It is Class 2, anyway.

I know.  Only USR bothered to follow the ITU recommendations correctly.  :)

BG> your bit rate was probably set too high (or did you use the FaxBaud 
BG> comment?).

PE> No, I didn't.

Bloody hell, so your Viper was trying to answer faxes at your locked bit
rate of 57600bps then?  Any wonder it didn't work properly.  The whole
point of ITU Class 2.0 is that it receives faxes at ANY serial port bit
rate, unlike Class 2's having to be locked at 19200 for faxes.

BG> If the Fossil is not locked then BinkleyTerm will set the bit rate
BG> to 19200 on a FAX connection unless you set `FaxBaud X', in which
BG> case your specified 'baud' rate will be used.

PE> If it sets the baud rate to 19200, that should be good enough, no?

That will solve the bit rate mismatch, but I can't comment on how it's
likely to affect the adaptive answer fiasco.  Might be worth a try though.

Regards, Bill
@EOT:

--- MsgedSQ/2 3.30