Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!gem.mps.ohio-state.edu!ctrsol!emory!cambridge.apple.com!bloom-beacon!eru!luth!sunic!maxim!prc From: prc@erbe.se (Robert Claeson) Newsgroups: comp.lang.postscript Subject: Re: Adobe PPD files Message-ID: <1036@maxim.erbe.se> Date: 5 Dec 89 10:53:59 GMT References: <1025@maxim.erbe.se> <17380@rpp386.cactus.org> Organization: ERBE DATA AB, Jarfalla, Sweden Lines: 24 In article , jtkohl@quicksilver.mit.edu (John T Kohl) writes: : I think a better solution is to lobby the application developers to add : an option to their programs that allow a user to specify the exitserver : password. This allows the shared environments to be carefully : controlled, while allowing people to get useful stuff printed (assuming : they either know the password or know how to find the SysOp who does). I believe that printer-specific information such as this is supposed to be retrieved from a PPD file. But since each printer on the system/network, even if they are of the same type, would need its own PPD file, I am tempting to use the Adobe-supplied PPD files (they can be retrieved from the archive-server@adobe.com) as templates and then copy the appropriate PPD file to a new file with the same name as the printer (ie, ps00, ps01 etc at our site) and use those. I believe that I would then be able to freely change the exitserver password in those files without breaking any conformance rules. Right or wrong? -- Robert Claeson E-mail: rclaeson@erbe.se ERBE DATA AB