Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!crdgw1!uunet!comp.vuw.ac.nz!newbery From: newbery@rata.vuw.ac.nz (Michael Newbery) Newsgroups: comp.sys.mac.misc Subject: Re: LaserWriter Password Message-ID: <1990Jul22.214730.11026@comp.vuw.ac.nz> Date: 22 Jul 90 21:47:30 GMT References: <1216@surf.sics.bu.oz> <10557@batcomputer.tn.cornell.edu> Sender: news@comp.vuw.ac.nz (News Admin) Organization: Computing Serv. Ctr, Victoria Uni., Wellington, New Zealand Lines: 24 In article <10557@batcomputer.tn.cornell.edu> mha@tcgould.tn.cornell.edu (Mark H. Anbinder) writes: >I believe in order to use a LaserWriter that has had its password changed >from 0 to something else, you have to patch your Laser Prep file to tell >it to send the new password. I don't know how to do this... I don't You patch the Laserwriter cdev, not the LaserPrep file. The strings to do this are in the POST resources -8192 and -8161 (at least on my version), POST resources are like STR# resources (at least in this case), use the STR# template in ResEdit. Of course this means that you have to provide patched versions of the laserwriter driver to everyone, and Pagemaker does not work (unless you explicitly load the AldusPrep file down using a program that knows the new password.) Strangely enough, we do this, even though it causes some hassels. The upside is that we don't have to worry about the LW being restarted ten times a day by people loading different (non-current) versions of the LaserPrep, incidentally trashing the downloaded fonts. (This is on our public LW.) Not to mention some extremly badly behaved MSDOS WPs that know 0 about networking/sharing and attempt to reconfigure the EEPROM (to pretty antisocial settings) every time they are run. Rumor hath it that the problems with LaserPrep go away with Sys7, for which I am very thankful. -- Michael Newbery Distrust aphorisms