From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 13-FEB-1991 10:01:04.42
To:	ARISIA::EVERHART
CC:	
Subj:	Re: LAT V5.4-1

From:	RELAY-INFO-VAX@CRVAX.SRI.COM@SMTP@CRDGW2
To:	Everhart@Arisia@MRGATE

Received:  by crdgw1.ge.com (5.57/GE 1.83)
	 id AA21374; Wed, 13 Feb 91 08:15:33 EST
Received: From UCBVAX.BERKELEY.EDU by CRVAX.SRI.COM with TCP; Tue, 12 FEB 91 20:11:08 PST
Received: by ucbvax.Berkeley.EDU (5.63/1.42)
	id AA15644; Tue, 12 Feb 91 19:59:08 -0800
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 12 Feb 91 14:02:59 GMT
From: ubc-cs!news-server.csri.toronto.edu!bonnie.concordia.ca!IRO.UMontreal.CA!matrox!uvm-gen!idx!jrb@beaver.cs.washington.edu
Organization: IDX Corporation, S. Burlington, VT
Subject: Re: LAT V5.4-1
Message-Id: <2233.27b7f593@idx.com>
References: <1991Feb5.060012.26993@mprgate.mpr.ca>, <2294@inews.intel.com>, <1023@TALOS.UUCP>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com

In article <1023@TALOS.UUCP>, greg_a@TALOS.UUCP (Greg Askew) writes:
> wsanders@inews.intel.com (Wiley Sanders) writes:
> 
>>Could someone summarize and repost some info about this subject? I have
>>heard all kinds of rumors about the new LAT stuff causing problems
>>(well, mostly, that is crashes some large systems), and our company has
>>held off on installing it, but, is there a valid reason for doing so?
>>  I've installed 5.4-1 without the new LAT stuff and it works just fine.
> 
> I discovered that a serial print queue on a MUXServer 300 /DECMux 300 will
> not work.  The queue will pause if anything is printed, and the if you 
> attempt to copy a file to the (unspooled) device name, you will receive a
> data set hangup.
> 
> Digital says this problem will be fixed with the next release of the 
> MUXServer s/w (version 1.2), which is coming out "real soon now".
> Until then, the only resolution is to revert to pre 5.4-1 LAT.
------------------------
I had the same bug, but I was able to work around it by doing the following:

mc latcp
latcp>set node /connection=both

I don't know why this made the problem go away, but it did!
Jim Bresee
JRB@idx.com

> -- 
> /-----------------------------------------------------------------------------\
> |Greg Askew        uunet!uupsi!pbs!npri6!talos!greg_a                         |
> |NPRI -  Alexandria,  VA  22314  703.683.9090 *  VMS 5.4-1                    | 
> \-----------------------------------------------------------------------------/