Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!ucbvax!ucbcad!ames!lll-tis!ptsfa!ihnp4!laidbak!guardian From: guardian@laidbak.UUCP (Harry Skelton) Newsgroups: comp.dcom.modems Subject: Re: Zenith Data Systems 2400 baud modem Message-ID: <1211@laidbak.UUCP> Date: Mon, 26-Oct-87 09:24:25 EST Article-I.D.: laidbak.1211 Posted: Mon Oct 26 09:24:25 1987 Date-Received: Wed, 28-Oct-87 19:44:08 EST References: <279@n8emr.UUCP> Reply-To: guardian@laidbak.UUCP Organization: Lachman Associates, Inc., Naperville, IL Lines: 62 Summary: logins and *nix In article <279@n8emr.UUCP> lwv@n8emr.UUCP (Larry W. Virden) writes: > > 1) I would like to find out what the MODEM thinks it is set at > internally; any ideas on how to find all the nifty little saved off values? You would issue a AT Sx? (with x being the S value "register". You'd have to do this for each of the S values you wanted to look at. ( you can put them on in a row but there is a buffer limit.) > 2) when I attempt to call out, I often find that my modem doesnt answer the > initial carrier sound, nor does the original carrier change bauds. Yet, > after fiddling (doing some order of AT commands no sequence of which seems > to work twice in a row) another call causes the proper notice. In your dialer program (most systems have source to the dialer program) you'd have to set the modem with an ATZ command (to clear it's mind), then issue the information needed for a connect. (ATDTE0V0Q0M1 (maybe an L3 for good measure - speaker volume if internal ) ###-####). Read below why I would set it this way. > 3) I find > that it is terribly touchy about characters transmitted WHILE it > is trying to echo the CONNECT message back to me. Yet, if I put a pause > of 2 seconds before continuing with my login, I find that I get garbage and > a NOT CONNECT as well, as if the other side gave up after not seeing > something soon enough. These and more are the types of things that I would > like to discuss with a knowledgable person out there... Thanks! The problem with a modem set for verbose and echo is that you have a byte fight with getty or login. Your modem will adjust to the baud rate the caller is calling at but the connect message is displayed at the old baud rate (the rate the modem was running at last. i.e. You init at 2400 baud, you get a call at 1200, modem says CONNECT at 2400 but carrier at 1200. From there the system thinks CONNECT is a login at 2400 and getty assumes such and sets the port at that speed. From there the out-of-sync modems cause garbage and the login gets a beating from the modem. Disable the echo and verbose. Set the modem to X1 (almost dumb mode) and set the S0=1 in order to answer on the first ring. Several rings could send 0's to getty. When you dial out, reprogram your dialer program to init the modem with ATZ and echo and verbose. An X4 could not hurt either (something other than X1 - see your manual). When you are done with your modem take and send a 'ATZ' to it to get it back for use with login. You can use DIR in your L.sys file and use the UUCP script language to handle the modem on a direct basis. This is what I would do since cu, uucico and other *nix comm programs are not up to speed with the latest in modems. Need more help just send me mail. This is as simple as I can put it. For Flames try the 'N' key. It works for me! .---------. Harry Skelton : .-. : --- other mail drops --- guardian@laidbak.UUCP : `-'o : ihnp4!laidbak!ugh!bear ihnp4!laidbak!guardian : O : ihnp4!laidbak!laipc!bear `---------' "You can bring any calculator you like to the midterm, as long as it doesn't dim the lights when you turn it on."