Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!zephyr.ens.tek.com!orca.wv.tek.com!pogo!rickc
From: rickc@pogo.WV.TEK.COM (Rick Clements)
Newsgroups: comp.lang.postscript
Subject: Re: Help: Overriding DIPS on LaserWriter IINTX
Message-ID: <9586@pogo.WV.TEK.COM>
Date: 8 Aug 90 20:44:04 GMT
References: <1990Aug7.225900.22721@sun.soe.clarkson.edu> <5431@plains.UUCP>
Reply-To: rickc@pogo.WV.TEK.COM (Rick Clements)
Organization: Tektronix, Inc., Wilsonville,  OR.
Lines: 30

In article <5431@plains.UUCP> dall@plains.UUCP (Brian Dall) writes:
}I don't have my red book handy, but this can be set using the setsccbatch
}commands, if I recall correctly.  Darn, I wish I hadn't left it at work.
}Setting the port is a bit messy, because it requires an exitserver and
}after you set it, it "doesn't listen" to the port that was sending the
}program to change the port.  Usually you need to send an EOF (ctrl-D, from
}the serial port) from the new device.  It is similar to setting the speed
}from 9600 to 19200 bps and back again from the serial port.  Send the 
}program to change the speed, then change the speed of your comm program
}and ctrl-D to end the program.  If you send anything after the line of
}code that changes the speed, you get gibberish and the printer responds
}with an error and "ingnoring until end of file."

setsccbatch doesn't change the port you are using.  It will change the
parameters for a port you're not using.  (Ex. you can set the serial parameters
from the parallel port.)

It doesn't require any special handling of EOF.  The red book says the change
in parameters don't take effect until it sees an EOF.  I have played enough
with the LaserWriter to know it behaves this way.  I think it flushes its
transmit buffer before it changes the parameters also.

I don't know of any way to over ride the switch settings.  But, I don't
worry about it because the printer I use takes data from all three ports
simultaneously.



-- 
Rick Clements (RickC@pogo.WV.TEK.COM)