Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!VAX1.CC.UAKRON.EDU!mcs.kent.edu!usenet.ins.cwru.edu!eagle!mars.lerc.nasa.gov!edwill From: edwill@mars.lerc.nasa.gov (Glenn L. Williams) Newsgroups: comp.sys.apollo Subject: Re: sr 10.2 xon/xoff problem. Message-ID: <1991Mar29.205007.3012@eagle.lerc.nasa.gov> Date: 29 Mar 91 20:47:58 GMT References: <1991Mar25.152157.25840@ccs.carleton.ca> Sender: news@eagle.lerc.nasa.gov Reply-To: edwill@mars.lerc.nasa.gov Organization: NASA Lewis Research Center Lines: 34 News-Software: VAX/VMS VNEWS 1.3-4 In article <1991Mar25.152157.25840@ccs.carleton.ca>, ardavan@ccs.carleton.ca (Ardavan Tajbakhsh) writes... > > > We have a Laserwriter II NT connected to a network of Apollos running > sr 10.2 (patch level PSK5) and we are using aegis print services. Everything > is fine except when a large postscript file is sent to the printer. The > printer acknowledges that it is receiving something, but doesn't generate > any output. > > I suspected that because of the size of the file (150355 bytes), the printer > tried to XOFF the line but failed. I put a terminal in place of the Laserwriter, > verified that I was talking to it, sent the file and saw the output scrolling on > the screen. Typing on the terminal had no effect. > > I know that I can probably get around the problem by using the Unix print > daemon and associated software, but I'd like to understand what is happening > rather than using a workaround. Incidentally, here are the characteristics > of the line connected to the Laserwriter: > ,stuff deleted here, With the Mentor Graphics Postscript server, we had to set up the server config file correctly to get rid of illegal control characters in the first and last lines of the file. However, a line in the text somewhere that says letter 0 timeout resulted in a problem like yours. If this line was commented out (preceded with % or simply removed) then the printer printed fine. > Ardavan