Article View: comp.sys.next.sysadmin
Article #1406Re: Printer in 3.0? SIMPLE FIX!!!!!
From: Michael Haker
Date: Sat, 10 Oct 1992 06:26
Date: Sat, 10 Oct 1992 06:26
57 lines
3038 bytes
3038 bytes
In article <1992Sep28.205102.1675@mcshub.dcss.mcmaster.ca> pascal@nextasy.physics.mcmaster.ca (Pascal Gaudette) writes: > > In article <1992Sep25.184124.4242@mcshub.dcss.mcmaster.ca> I wrote: > > In article <}$#@byu.edu> yackd@oregon.et.byu.edu (Don Yacktman) writes: > > > In article <1992Sep22.163029.5016@ornl.gov>, > > > woo@ornl.gov(John W. Wooten) writes: > > > > > > > >What happened to my Printer? > > > > > > I don't know, but it happened to me, too. > > > > First of all, thanks to the many people that sent me their > printcap info. But it didn't work. I got the Local_Printer in > > I finally had to nidump all my user, group, nfs, hosts, etc., > info; copy the template netinfo database from > /usr/template/etc/netinfo; and niload everything back. > > MAJOR hassle. And it's going to be even worse for people who > have a lab of machines... > > Anyhow, I can finally print to my NeXT printer. > -- > Pascal "The Rascal" Gaudette pascal@nextasy.physics.mcmaster.ca > MacNUG president | *NeXTmail encouraged* > graduate student, McMaster university | Je ne suis pas infaillible. > Physics and astronomy dep. | Vive le Quebec LIBRE! I just discovered a semi-simple way to get the printer back. The problem is in the .NeXT/.NextDefaults.L file that each user has. If you delete this file for each user, the system will create a new one when each user logs back in. They can then print. IT IS NOT IN THE NETWORK. I discovered this because a new user I added after the 3.0 conversion had no problem printing. If you replace all the old . files of an old user with the new ones created for any-post-conversion users it also work. I played around comapring the . files and finally narrowed it down to the NeXT/.NextDefaults.L file. The catch with this fix is that each user losses their defaults (dock, preferences....) so its a bit of work for each of them to get things back, but it does work and it is not much work for the administrator. (Note, we thought it was in our netinfo so we completely reinstalled the system from the CD with hard disk initialization and rebuilt our net from scratch except for the user accounts and LocalApps, LocalLibrary stuff which were on another non-system disk). Hope this prevents a lot of you from doing an unneccessary amount of work like we did. Mike Haker Department of Chemistry, University of Wisconsin - Madison. haker@whitewater.chem.wisc.edu
Technical Details
Message-ID:
<1992Oct10.062644.26663@pslu1.psl.wisc.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!zazen!psl.wisc.edu!newsReferences:
<1992Sep28.205102.1675@mcshub.dcss.mcmaster.ca>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.sysadmin Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!zazen!psl.wisc.edu!news From: haker@whitewater.chem.wisc.edu (Michael Haker) Subject: Re: Printer in 3.0? SIMPLE FIX!!!!! Message-ID: <1992Oct10.062644.26663@pslu1.psl.wisc.edu> Sender: news@pslu1.psl.wisc.edu (USENET News System) Organization: Physical Sciences Lab, UW-Madison References: <1992Sep28.205102.1675@mcshub.dcss.mcmaster.ca> Date: Sat, 10 Oct 92 06:26:44 GMT Lines: 57