Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!swlabs!jack
From: jack@swlabs.UUCP (Jack Bonn)
Newsgroups: comp.dcom.modems
Subject: Re: Zenith Data Systems 2400 baud modem
Message-ID: <895@swlabs.UUCP>
Date: Tue, 10-Nov-87 18:57:26 EST
Article-I.D.: swlabs.895
Posted: Tue Nov 10 18:57:26 1987
Date-Received: Fri, 13-Nov-87 06:02:02 EST
References: <279@n8emr.UUCP> <932@men2a.ORI-CAL.COM> <325@n8emr.UUCP>
Distribution: na
Organization: Software Labs, Ltd. Easton CT USA
Lines: 28
Keywords: Zenith Bizcomp

In article <325@n8emr.UUCP>, lwv@n8emr.UUCP (Larry W. Virden) writes:
> 
> When I type
> directly to the modem, things work relatively well.  The two problem sites 
> that I call recognize my modem, my modem recognizes them, I get a connect
> 2400, and I can proceed with login.  BUT, when in an auto-script/macro
> whatever you would like to call it mode of operation, and I get the connect
> 2400, the next character emitted to the modem causes about 5-6 garbage
> (like change of baud rate style) characters and a NO CONNECT message
> to occur.  

Larry-

I tried mailing you this with no success.

Is it possible that the problem modems have MNP error correction and you
don't?  Sometimes it is necessary to delay before starting to send any
characters to an MNP modem.  This lets the other modem know that you are 
not an MNP modem.  Hopefully there is a way to make the autodialer
script delay before starting to send.

This would not explain what the far end is sending to your modem to
get it jammed up.  But if the delay helps, your are on the right track.

I hope this helps.
-- 
Jack Bonn, <> Software Labs, Ltd, Box 451, Easton CT  06612
uunet!swlabs!jack