Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!GRINNELL.MAILNET!McGuire_Ed From: McGuire_Ed@GRINNELL.MAILNET Newsgroups: comp.os.vms Subject: (none) Message-ID: <8704281250.AA18147@ucbvax.Berkeley.EDU> Date: Mon, 27-Apr-87 13:19:00 EDT Article-I.D.: ucbvax.8704281250.AA18147 Posted: Mon Apr 27 13:19:00 1987 Date-Received: Wed, 29-Apr-87 07:13:05 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 25 > Date: Fri, 24 Apr 87 13:18:29 +0200 > From: Tore Haraldsen USE/UiO > Subject: Timeout errors on DMZ-32 > > In a letter, McGuire_Ed%GRINNELL.MailNet@MIT-MULTICS.arpa complains > about timeout errors when typing large bodies of text. (To remind others: driver for DMZ-32 on 8600 often returns timeout error if user suspends output for roughly a minute with Hold Screen, when there is still more text than can be buffered in the terminal.) > We have observed differences here between standard Dec terminal interfaces > and a 32-port card for Net/One from UngermannBass. > Try twiddling the /TTSync terminal parameter, and check the setting > of /Hostsync and /Readsync parameters. I bet your problem will disappear > with a $ SET TERM /TTSync/NoHostSync/NoReadSync setting ... Thanks for the tip. I checked my parameters, and I find that all lines are already set /TTSYNC/NOHOSTSYNC/NOREADSYNC. The tack I'm taking right now is very similar, however. I've set SYSGEN parameter TTY_DEFPORT to 1, which should force the driver to handle incoming XON/XOFF instead of the DMZ-32 firmware. If the problem disappears, that may point to an interface problem between the DMZ-32 and the driver. Ed