Path: utzoo!attcan!uunet!munnari!bruce!goanna!pnm
From: pnm@goanna.oz (Paul Menon)
Newsgroups: comp.protocols.appletalk
Subject: Re: lwsrv problem
Summary: Me too! Mee too!
Message-ID: <1981@goanna.oz>
Date: 13 Mar 89 00:09:28 GMT
References: <8903101809.AA00655@icarus.cns.syr.EDU>
Organization: Comp Sci, RMIT, Melbourne, Australia
Lines: 64



From article <8903101809.AA00655@icarus.cns.syr.EDU>, by jmvogtle@ICARUS.CNS.SYR.EDU (John M. Vogtle):
| Thanks for all those who responed to my original request.  So far the
| score stands as follows:
| 
|     lwsrv: 1
|     John:  0
	
	lwsrv:  2
	paul:	1 	(see workaround below)

...
| papif: accounting = yes, chargebanner yes, idlestuff yes, structured yes
| papif: reverse = none
| papif: pstext = /usr/local/lib/ps/pstext
| papif: banner file = .banner
| papif: cap.printers = /etc/cap.printers
| %%[ Error: invalidaccess; OffendingCommand: def ]%%
| %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
| papif: Finished job at Fri Mar 10 09:09:41 1989
|
	Exactly what I have experienced.

| I'm wondering what could cause the invalidaccess messages since "def"
| is legitimate PS.  I piped my current LaserPrep File into tlw and got
| the following:
| 
| Script started on Fri Mar 10 09:44:18 1989
| <icarus.root> tlw "Icarus LW ":LaserWriter@MACWEENIE-NET < FoundProcSet.605221731
| abInit: [ddp:  55.01, 49] starting
| Starting session with Icarus LW :LaserWriter@MACWEENIE-NET
| %no status
| status: idle
| 
| Okay
| 
| PostScript(r) Version 47.0
| Copyright (c) 1984, '85, '86, '87 Adobe Systems Inc.
| Copyright (c) 1981 Linotype     All Rights Reserved.
| PS>%%BeginProcSet: "(AppleDict md)" 68 0
| PS>currentfile statusdict begin serverdict begin product (LaserWriter II NT) eq revision 1 eq and {/setrealdevice {//setrealdevice exec 31 sendpcmd 4 eq tonerlight} bind def
| /execjob {31 sendpcmd 4 eq tonerlight //execjob exec} bind def end end eexec}{end end 722{currentfile read pop pop}repeat}ifelse 
| 
| %%[ Error: invalidaccess; OffendingCommand: def ]%%
| 
| script done on Fri Mar 10 09:45:49 1989

	Here too, the same has occurred.
It seems the LW doesn't want to speak the PostScript lingo.  We don't
have prepfix, but the conditions are identical to John's.  We are using
LWNTIIX's with ProcSet V 68.  We get around the problem by creating
an empty ProcSet (just the Begin and End lines) and hope someone has
initialiased the LW from a Mac.  Not good if the LWs have been switched
off.

  I have even tried getting into the EXECUTIVE "mode", with no success.

Any enlightenment will be appreciated.  I would like to even the score
with lwsrv too.  If anyone in oz has prepfix, please acknowledge.

Thankyou
	Paul Menon
	pnm@goanna.oz