Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!batcomputer!tedcrane From: tedcrane@batcomputer.tn.cornell.edu (Ted Crane) Newsgroups: comp.os.vms Subject: Re: Bi-directional non-LAT hosts Message-ID: <3122@batcomputer.tn.cornell.edu> Date: Tue, 8-Dec-87 17:59:57 EST Article-I.D.: batcompu.3122 Posted: Tue Dec 8 17:59:57 1987 Date-Received: Sun, 13-Dec-87 14:32:03 EST References: <8712042158.AA23634@ucbvax.Berkeley.EDU> <163@icus.UUCP> Reply-To: tedcrane@tcgould.tn.cornell.edu (Ted Crane) Organization: Tompkins County Computing, Ithaca, NY Lines: 23 Keywords: lat latserver In article <163@icus.UUCP> gil@icus.UUCP (Gil Kloepfer Jr.) writes: >that port when someone is using it locally. Secondly, the remote speed of >the line is fixed. You cannot say SET TERMINAL/SPEED=x LTAy: and expect >it to work. Unless someone has found the answer to this and didn't share >it with me on the net (I asked about this some time back), then it is >impossible. So far, DEC seems to agree with that statement. Anyhow, >this means that using a multi-speed modem on a DECserver port remotely >will be restricted to your favorite speed, or the one that the DECserver >port is defined as. The DECserver 200, at least, supports multispeed modems. You can indicate a port speed and an alternate port speed. The DECserver will monitor one of the data lines coming from the modem and fall back to the slower speed if requested. Now the bad news: as of the last time I tried it, the code to handle fallback speeds did not work correctly with a DF224 modem. Apparently the modem was not following its own spec as to signals and *even if it did* the software in the DECserver was making boo-boos of its own. It was necessary to issue privileged local commands to the DECserver to properly use a multi-speed modem. I'd appreciate an update on this situation if anyone knows of a fix or work- around.