[log in to unmask] (Ron Burnett ) wrote:
 
>Date: Sun, 9 Apr 1995 11:22:45 EST
>From: Ron Burnett <[log in to unmask]>
>Subject: 5.0 Upgrade Gotchas
>
[snipped...]
 
>Just to make matters worse--we dropped NS/3000 off our
>contract  (as well as some other things), and the
>plain-vanilla 5.0 LAN  LINK software wouldn't let me
>restart our network.  Had the  perfectly *AWFUL*
>feeling that HP had left something off our  SUBSYS
>tape--but it turned out to be some old files left over
>from the full NS/3000 product.
 
[snipped...]
 
>Ron
>[log in to unmask]
 
I would like to take this opportunity to share a similar
experience regarding this very same issue. We had a 3.1 system
that had *every* hp network product installed on it (well,
except stuff for ibm connectivity). Then we converted to 4.0
and left everything off except those products we wanted to
continue using (sound familiar?). We had the same problem. The
jconfjob found all these *older* files in the net.sys group and
built a net config that didn't fit with the installed software.
Could not get nscontrol start to work. RC helped us get it
sorta kludged, but I did not get a *positive this will solve
it* response from them. I got a *lets try this, I think it
might fix it* type of response. After this hassle I asked for a
listing of the files that belonged to the net products we
didn't update so I could purge all the files just to make sure.
Well it took over 6 months to get this list. And it was like
pulling teeth.
 
So if someone from HP is listening I would suggest you figure
out a better way to get net products removed or inactivated so
they don't interfere with future updates and jconfjob.
 
-- Duane Percox (Quintessential School Systems)
   [log in to unmask]