🚀 go-pugleaf

In article <1992Oct7.170405.18884@nwnexus.WA.COM> dean@thrall.com writes:
>
>Ok, guys I have a problem. I just upgraded to 3.0 last week. No problems until  
>now. I just attempted to run HostManager.app and it doesn't launch. It starts  
>to, but fails. Same goes for UserManager.
>
>The only thing that I can think of is taht my SLIP software is messing it up.  
>When you configure the SLIP you change to a Non-Netinfo network. It worked ok  
>under 2.1 , but 3.0 seems to be broken. Also launching NetInfoManager, it  
>brings up my SLIP connection befroe it reads the database.
>
>So if anyone has any ideas, please let me know.
>
I doubt it has anything to do with your SLIP software.  I've had the same
thing happen to two different NeXTstations I was upgrading, one of which did
not have any SLIP software installed at the time, the other has never had
SLIP software anywhere near it!

I've posted about this 3 times so far, and nobody has ever responded, not
even to say they've had the same problem (at least until now).  I'm relieved
to know it's not just me!

Any ideas anyone?  I solved the problem on my home machine by reinstalling
3.0 from scratch (booting from the CDROM, etc...), but there should be a
better way to solve or prevent this problem.

Timothy Buck   --   rri!tim@vtserf.cc.vt.edu OR timbuck@borg.lib.vt.edu
 Recognition Research, Inc. (703) 231-6500	++ NeXTmail accepted ++
------------------------------------------------------------------------
 Hate Blacksburg's weather? Wait an hour.  Hate the season? Wait a day.  

In article <1992Oct7.170405.18884@nwnexus.WA.COM> dean@thrall.com (Dean  
Johnson) writes:
> 
> Ok, guys I have a problem. I just upgraded to 3.0 last week. No problems  
until  
> now. I just attempted to run HostManager.app and it doesn't launch. It  
starts  
> to, but fails. Same goes for UserManager.
> 
> Dean Johnson

We had the same problem with our system upgrade and ended up completly  
reinstalling the system on our two machines.  At our NextUsers group  
meeting this week we were talking about this problem and so far the best  
hypothesis we have is that those systems where a netinfo client was  
upgraded before the netinfo server have these kind of problems, but those  
that upgraded the sever first did not.  

SO UPGRADE YOUR NETINFO SERVER FIRST.  

In response to your problem so far the only solution I'm aware of is to  
completely reinstall the system software.  To do a complete reinstall set  
the cd-rom so it has scsi address of 0 and reboot with the 3.0 cd in the  
drive, the system boots off the cd and goes through a complete upgrade  
with the option to initialize the hard drive (we didn't need to, but  
beware of links if you've moved system software onto external disk, the  
system can't write over the link since only sd1a is mounted).

Mike Haker
dept chem UW-madison
haker@whitewater.chem.wisc.edu