Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site uw-beaver Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!laser-lovers From: laser-lovers@uw-beaver Newsgroups: fa.laser-lovers Subject: LaserWriter tech question re: setsccbatch Message-ID: <1302@uw-beaver> Date: Mon, 10-Jun-85 03:01:31 EDT Article-I.D.: uw-beave.1302 Posted: Mon Jun 10 03:01:31 1985 Date-Received: Tue, 11-Jun-85 04:57:20 EDT Sender: daemon@uw-beaver Organization: U of Washington Computer Science Lines: 40 From: Alan Crosswell We have a LaserWriter that for now is plugged into a Vax on the DB-25 connector and Appletalk on the DB-9 (No, we don't use both at the same time). Most of the time it's on the Vax, but occasionally it's switched to Appletalk. The problem is, that when on the Vax (rotary switch set to 9600), the DB-9 connector is active at 9600 baud and gets ioerrors anytime there is some Appletalk traffic. I figured I'd fix this by turning off the DB-9 port when in "batch" mode (that is, selector on 9600). So, I ran this program: 0 serverdict begin exitserver % exit server mode statusdict begin % open the status dictionary 9 0 0 setsccbatch % set port 9: 0 baud, 0 parity end This set the baud rate to 0 for the DB-9, which the Advanced Users Supplement of Inside LaserWriter claims is the proper method to turn off a port. At this point, the LaserWriter appeared to hang; no more jobs would print on it. Upon rebooting it, no startup page would come out. I was, however, able to connect to the DB-25 port with a terminal, enter executive mode and confirm that the sccbatch settings for port 9 had indeed been set to 0 baud, 0 parity and that the dostartpage boolean was still true. I was also able to get it to respond to a showpage command. I then set the baud rate back to 9600 for the DB-9 port and it rebooted fine: the startup page printed, and it accepted jobs just fine. Any thoughts on why this happened? My only conjecture is that the server is somehow getting goofed up because it normally polls both ports to select the next job and is getting wedged by one port being turned off. This doesn't explain why the startup page didn't print or why I was still able to have a conversation with the machine over the DB-25. Presumably, if I can talk to it, so can my spooler (TranScript's psif). Alan Crosswell Columbia University us.alan@cu20b.arpa -------