HOWTO - Installation of NetWare 5.1
Tobias Loecke
I have the very same problem installing NW51 as many others in here.
After install, the GUI loads and then vmware dies. After reboot, the
server is coming up, but it start abending every second. I the copied
the files onto the server, rebooted, but still tons of abends. The I did
step by step the network configuration, installed NDS, always rebooting,
still abending. I can't install the licenses, as I get the error "unable
to load cli.nlm". When I try to install the support pack, it cannot find
the product.dat file.
Seems to be a very weird server status, but I reinstalled it now
serveral time, but it always has the same effekt.
I am running vmware on a suse linux 7.1, kernel 2.2.18, current vmware
build. The NW51 install cd includes sp1.
I really appriciate any ideas.
Thanks,
Tobias
Jim Henderson wrote:
>
> Seem to be a few questions on how to do this, so I thought I'd repost my
> procedure for anyone interested, since my other post seems to not be
> being seen by the new people coming into the newsgroup.
>
> Host Configuration: 192 MB of RAM running Linux (RedHat 6.1 with 2.2.15
> kernel), VMware 2, rtl8139 ethernet adapter, CD-ROM, CD-RW, and an 8 GB
> hard drive (6 GB allocated to Linux). Processor is a Celeron 300A *not
> overclocked*. Diamond Viper V550 video card.
>
> Guest Configuration: 128 MB for NetWare 5.1, CD-ROM, Floppy, 2 GB
> virtual IDE drive for the NW51 installation. I use the IDE device
> drivers, haven't tried it with the SCSI emulation yet.
>
> Here are the steps I took:
>
> 1. Make sure the CD is mounted and VMware is set to boot from the CD.
> 2. Boot the VM
> 3. Run through the setup to the point of getting to the GUI install.
> Wait for Java to have its fit, then flip back to the system console.
> 4. Load NW5-IDLE (copied either to A: or C:)
> 5. NWCONFIG
> 6. Copy files
> 7. Create NCF files (AUTOEXEC.NCF and STARTUP.NCF)
> 8. Rediscover the network card stuff
> 9. Modify AUTOEXEC.NCF and name the server and set the server ID. Also
> add a LOAD CLIB and LOAD NW5-IDLE to the file. At some point, you'll
> want NW5-IDLE on the SYS volume (or the DOS partition if that's easier)
> 9. Reboot the server
> 10. Install NDS (NWCONFIG->Directory Options->Install
> 11. Install licenses
> 12. Remove STARTX.NCF from the AUTOEXEC.NCF
>
> That *should* do the trick, though it doesn't handle stuff that needs
> the GUI install like Certificate Services.
>
> After I finish the installation, I like to clean up the stuff I'm not
> going to use on the server, then use Petr's FILLZERO.NLM module to prep
> the virtual disk for shrinking, and then shrink the disk. The final
> disk file size is about 300 MB in size.
>
> What I then do is ZIP the machine nvram, cfg, and dsk files and put them
> on a real NW 4.11 server I have. Install once, copy as many times as
> needed for the testing.
>
> Jim
Carl Bretteville
See my post from March 5 entitled "NW 5.1 install, another approach".
It describes how I was able to install NW51 under VMWare.
Cheers,
Carl Bretteville
Member of the DeveloperNET SysOp team
Don't get (M)AD, get NDS!
Jim Henderson
installation consistent - I imaged an HP Vectra VL400 to get the image
installed, then restored it later. Just make sure you limit the size of
all volumes on the first disk to < 2 GB, as VMware can't use drives
larger than that apparently.
Jim
Tobias
is there a way to run the accelerate upgrade accupg.exe on a Linux host?
Dunno how.
But from your posting I understand it is easier to install NW5.0 in
vmware but NW5.1?
Jim, I am new to vmware, how can I get an image (i would have ghost
here) into vmware?
Thanks,
Tobias
Carl Bretteville
>Hi Carl,
>
>is there a way to run the accelerate upgrade accupg.exe on a Linux host?
>Dunno how.
It is a Java app compiled to an EXE, so you'll need a
Win9x/WinNT/Win2K box to run it. A VMWare guest with Client32 will
do... ;-)
>But from your posting I understand it is easier to install NW5.0 in
>vmware but NW5.1?
Yes, installing NW5 from the distribution CD was no problem. The
change that cuses VMWare to go leggs up was introduced in one of the
later versions of the Novell JVM. If I start X with support pack 6a
added to NW5 it blows up the same way NW51 does. I'm not quite sure
when this cahnge ocurred, but around the time NW51 was released is a
good bet.
The ACCUPG method was a last resort thing as even the NUT based
upgrade failed on my system. Anyway, I was happy to get it installed
one way or the other. X on the server isn't important for me at this
time, so I can live with it for now. Not sure if I can get eDir
installed though, but I'll give it a try eventually.
Best of luck!
Chuck Chopp
I did an eDir v8.5 installation on my NW v5.1 SP2a guest system. The
installation finished copying files and then when it went to start the X
server [and loaded JAVA.NLM] VMware died. However, whatever it wanted to do
with the X server was apparently not important because eDir was successfully
installed. I think that the part that failed was the installation of
ConsoleOne. I did a separate installation of ConsoleOne v1.2d from the NSEL
CDROMs and it installed OK via that method.
I now have my NW v5.1 SP2a system running a federated eDir tree and I've been
testing my various NDS-aware applications to verify that they work OK with a
federated tree. I'm also looking forward to testing some LDAP code against
this server.
Regards,
Chuck
--
Chuck Chopp
Chuck...@rtfmcsi.com http://www.rtfmcsi.com
ICQ # 22321532
RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651 800 774 0718 pager
80077...@skytel.com
Jim Henderson
store the image on a raw disk and set up VMWare to read that raw disk,
or you can burn the ghosted image to a CD and use the CD for restoring.
Jim
Carl Bretteville
Thanks for the input. That will come in handy.
Chuck Chopp
Carl,
You're welcome.
I should also add that the problems with starting the X server and
loading JAVA.NLM seem to only affect PIII systems. If I move my VMware
installation over to a desktop system that has a 400MHz Celeron
processor I don't get this problem. However, my VMware installation is
normallly on my 750MHz PIII laptop and that's where I encountered the
problem (VMware bug # 4090) with VMWare dying with a "memory could not
be read" error when the guest loads JAVA.NLM.
Casper Pedersen
> I should also add that the problems with starting the X server and
> loading JAVA.NLM seem to only affect PIII systems. If I move my VMware
> installation over to a desktop system that has a 400MHz Celeron
> processor I don't get this problem. However, my VMware installation is
> normallly on my 750MHz PIII laptop and that's where I encountered the
> problem (VMware bug # 4090) with VMWare dying with a "memory could not
> be read" error when the guest loads JAVA.NLM.
>
I actualy also get this problem on my Athlon 1Ghz, so it is not only on
PIII's...
Regards/Casper
Bon Thomassen
Installing NetWare 5.1 into a VMware Virtual Machine
1. In VMware, run the Configuration Wizard to create a new VM.
a. Select Other as the Guest Operating System.
b. Select the directory for the VM’s files.
c. Select Virtual Disk as the Disk Type.
d. Leave the default 2000 as the Virtual Disk Size.
e. Verify CD-ROM Enabled Using Drive "auto-detect" and Start with CD-ROM connected are
checked.
f. Verify Floppy Enabled "A:" and Start with floppy connected are checked.
g. Choose Bridged Networking (connected to the outside network) or Host-only Networking
(internal VMware network only) as appropriate for the configuration desired.
h. Select Finish at the Confirmation screen.
2. Before Powering On the VM, select Settings | Configuration Editor, and then select Memory. Give the
VM at least 96 MB of memory, which is the minimum for NetWare 5.1 to install.
3. Close the VMware window and select Yes to save changes to the other.vmx file.
4. Edit the other.vmx file with a text editor and add the line "cflags.set = 0x40"
5. Open the VMware window again by double clicking on the other.vmx file.
6. Make sure your NetWare 5.1 installation CD is in the CD-ROM drive, then select Power | Power On.
This CD is bootable, so the NetWare installation will begin automatically.
7. Accept the License Agreement and Create a New Boot Partition for DOS. When completed this will
require a reboot of the VM, which will then launch back into the install automatically.
8. Continue with the NetWare 5.1 install as normal, but be sure to change the Video setting to Standard
VGA instead of the default Super VGA. If you do not change this, the install will fail with an SVGA
error as soon as the graphics portion of the install starts. VMware uses IDE drives by default, so it will
autodetect as an IDE drive. The VMware virtual network card emulates an AMD Ethernet Pcnet-PCI
card, so choose the PCNTNW.LAN driver.
9. When you get to the file copy part of the installation, stay close and watch carefully. When it reaches
100%, begin moving the mouse. If the mouse is in motion when the graphical portion of the install
begins, it will detect the mouse. Otherwise, you will have to do the installation in mouseless mode.
---Added by Adam Bradley – start (abra...@novell.com)
10. As the GUI installation section begins and during a time where console entries are not being processed,
type the following set parameter:
?? set allow ip address duplicates = on
11. Add this statement to the autoexec.ncf file
---Added by Adam Bradley – end (abra...@novell.com)
12. After a few minutes, the installation will stop. If you toggle to the Server console you will see an error
for the Symantec JIT compiler. At the console prompt type "ENVSET java_compiler=none." Once
this variable is set, you can type "RUNSI" to restart the setup. (Note from Bon Thomassen: I had to use nwistart.ncf instead of runsi)
13. Installation should continue as normal from this point on, but may be slower.
14. To ensure that the Symantec JIT compiler is not enabled again after reboot, edit sys:\etc\java.cfg and
add the line "java_compiler=none"
---Added by Adam Bradley – start (abra...@novell.com)
15. On a Windows 2k Professional SP1 host, ensure the VMware process is running at a Normal priority
or below.
16. As the mouse will not work, to install application redirect the GUI to a remote X server.
17. NetWare doesn’t idle the CPU. To overcome this, copy NW5-IDLE.NLM to SYS:\SYSTEM and load
this NLM from the autoexec.ncf. Insert the entry at the beginning of the file.
---Added by Adam Bradley – end (abra...@novell.com)