Xref: utzoo comp.unix.ultrix:2889 gnu.emacs:2382 Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!yale!mintaka!mit-eddie!uw-beaver!ubc-cs!alberta!atha!cbmvax!grr From: grr@cbmvax.commodore.com (George Robbins) Newsgroups: comp.unix.ultrix,gnu.emacs Subject: Re: ds3100/uws 2.x xon/xoff LAT problem Keywords: ds3100, ultrix, xon/xoff, LAT Message-ID: <9832@cbmvax.commodore.com> Date: 26 Feb 90 21:05:18 GMT References: <229@asihub.AUTOSYS.COM> Reply-To: grr@cbmvax.cbm.commodore.com (George Robbins) Organization: Commodore, West Chester, PA Lines: 31 In article todd@unix.ecs.rpi.edu (R. Lindsay Todd) writes: > In article <229@asihub.AUTOSYS.COM> dan@asihub.AUTOSYS.COM (Dan O'Neill) writes: > > > > When connecting to a DS3100 from a LAT (local area terminal > > server), xon and xoff are not handled correctly. > > This is also a problem with VAXen running Ultrix 3.1/UWS 2.[12]. I called > DEC just a couple weeks ago about this problem; the best they could do was > submit an SPR. Perhaps there is a patch for RISC machines only? > > Oh yes -- the DECperson I talked to (Atlanta CSC) had to submit a QAR for > Ultrix 4.0/RISC, since it was a problem there too; hopefully it will be fixed > before this is released! It may be that the patch hasn't reached official status yet. In any case, network problems including LAT, NFS, FTP and so on are really handled out of Colorado, so call there instead of wasting time with Atlanta... > flow control on you port, e.g., > SET PORT FLOW CONTROL DISABLED > will turn off all flow control for a port on a DECserver 200 until the port is > logged off. Or setting the port/session to PASSALL should work, but this is something the software is supposed to be doing for you on a dynamic basis. -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing: domain: grr@cbmvax.commodore.com Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)