HP3000-L Archives

October 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Burke <[log in to unmask]>
Reply To:
John Burke <[log in to unmask]>
Date:
Mon, 11 Oct 1999 06:09:27 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
Bruce hits this one right on. We had the same problem going to 6.0 on one of
our machines. At one time we had X25 installed on this machine and while
MPE/iX 5.5 never protested about these old modules still laying around, 6.0
croaked. The solution is to rename everything showing up in NETCONTROL
VERSION that is not current and re-stream jconfjob.net.sys. Worked great for
us.

John Burke

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Guy Lachance
Sent: Friday, October 08, 1999 2:22 PM
To: [log in to unmask]
Subject: Network problem after upgrading 5.5 -> 6.0


Hello,

I upgraded ou 3000 to 6.0 and I cannot re-start the network with the
usual commands :

netcontrol start;net=lan1
netcontrol start;net=loop
nscontrol start

I get the following error message :

VERSION ERROR: BAD MODULE (S) NETXPORTERR 4044

Anybody has any idea ?

Thanks
 Guy

ATOM RSS1 RSS2