-=> JASEN BETTS wrote to JAMES BRADLEY <=-

 JB> Hello James.
How do, JB?

 JB> Do you see any other corruption of it input....extra or distorted
 JB> characters? the modem could be faulty...

Could be a cold solder joint to be sure. Flow control faults should show as bad
characters, right?

 JB>  A) Is there a better place to ask?

 JB> MODEMS, COMM, google

Not sure if those echos get here, but I know Google doesn't. I'll have as look
for Modems and Comm if it still needs work.

 JB>  C) Is there a loopback test for the HW handshake on the cable?

 JB> in your terminal program a key to do at&v^m
 JB> and hit it ten times quickly, if flow control (in the inbound stream)
 JB> is working you'll not detect any missing characters.

That's while connected to a remote host? 

 JB>  The UART is listed as 16550AN. Is this one of the buggered  ones
 JB> I've read so much about?

 JB> could be, I know NS-16550AFN is good.

It's of '99 vintage, and a part of the MB, so I think I'll not chase that
ghost.

 JB>  I do have a listing of the AT command set
 JB> I'm sure, but doubt I could find it in a day, let alone decypher

 JB> If you can find windows "drivers" (*.inf files) for it
they should give
 JB> a few hints. (they're basically text files with commands to do various
 JB> things listted in them)

Right-O... It didn't place an init string, but I'll search for theinf.

Thanks JB!


... The number you have dailed...Nine-one-one...has been changed.
--- MultiMail/MS-DOS v0.46

--- Mystic BBS v1.07.3 (DOS)