Install Novell Netware 5.1

[Janella Eldert]

sales.acmegraphics.marketing.acmemarketing.acmeNOTE: If User objects with the same name exist in different contexts, each user object attempts authentication in order until one succeeds with the corresponding password.The CIFSCTXS.CFG context search file can be edited manually after installation. For more information, see Specifying Contexts in the Context Search File.


You don't have to install Novell Client for NetWare, because Windows XP contains an embedded client for it. To install it, you'll need to open Properties for the network connection and click Install..., then select Client and click Add... You'll have only one choice there, if the client isn't already installed, Client Service for NetWare.



Install Novell Netware 5.1

DOWNLOAD https://pulctechpgeho.blogspot.com/?ma=2wRsOK






It supports only IPX, so if your server runs IP only, you'll have to install the client from Novell. Make sure you configure the same IPX number for both the server and the client. On the server, it is set up in SYS;\SYSTEM\AUTOEXEC.NCF file. You can access it from the server's console by either loading INSTALL or NWCONFIG, or by editing it directly with EDIT:


Your best bet here is to find a Windows XP machine (not Vista or Win7) and install the Novell Client to it. You can download it from Novell.com (link). Make sure the WinXP machine is on the same network subnet as your dumb terminal. During configuration, make sure you select "IP and IPX" as protocols, and make sure the "Server" field is the NW4.11 server. I assume you have login credentials. Login with those to the server.


Use the VMware ESX Server Configuration Editor to verify the virtual machine's devices are set up as you expect before starting the installation. For example, be sure that your virtual machine is configured for at least 48MB of memory (which the NetWare server installation requires). VMware also recommends that you disable the screen saver on the host system before starting the installation process.


VMware recommends that you install MS-DOS 5.0 or higher in a small (50MB FAT16) partition as described in these guidelines. The rest of the free space on the virtual disk is used for the NetWare partition. Even though the virtual machine should most likely run NetWare most of the time, it is a good idea to install the DOSIDLE.EXE program, which you can download from www.vmware.com/software/dosidle210.zip.


Note: Once the installation has been completed, you can load and bind the appropriate LAN driver. Selecting or loading a LAN driver during the NetWare 4.x installation may hang the installation process.


We are going to just accept the defaults (hit enter a few times) which will partition the first disk, and ready it for the MS-DOS install. After enough enters, qemu will reboot, and MS-DOS will format the first disk, and then prompt for disk two. We will want to change disks. This part of qemu can be a little scarry for the uninitated, however its quite simple. Click on the qemu window, then hit CTRL+ALT+2. This will bring you to a window like this:


It will prompt for the port & interrupt, just press enter to accept the defaults. With the disk in place, its time to install the Netware files so that we can then setup the networking. Type in the following:


Then perss enter. Netware will now start to copy the files. This can take a while. Once the copy is completed, press escape back to the main menu, then exit the installer. I know this seems counter intuitive, but its for a good reason.






i have an old pc that has a network drive by netware 3.12 in dos 6.22 . i backup hard disk by microsoft disk2vhd and now have an vhd file. i add vhd file in virtualbox and dos successfully boot. i can input server command, but when i input server command show this error:


NetWare version 3.x was also much simpler to install, with disk and network support provided by software modules called a NetWare Loadable Module (NLM) loaded either at start-up or when it was needed. NLMs could also add functionality such as anti-virus software, backup software, database and web servers. Support for long filenames was also provided by an NLM.


By August 1993,[14] Novell released its first version of "NetWare for OS/2". This first release supported OS/2 2.1 (1993) as the base OS, and required that users first buy and install IBM OS/2, then purchase NetWare 4.01, and then install the NetWare for OS/2 product. It retailed for $200.[14]


While the design of NetWare 3.x and later involved a DOS partition to load NetWare server files; while of little technical import (DOS merely loaded NetWare into memory and turned execution over to it; in later versions, DOS could be unloaded from RAM), this feature became a marketing liability. Additionally, the NetWare console remained text-based, when the Windows graphical interface gained widespread acceptance. Novell could have eliminated this technical liability by retaining the design of NetWare 286, which installed the server file into a Novell partition and allowed the server to boot from the Novell partition without creating a bootable DOS partition. Novell finally added support for this in a Support Pack for NetWare 6.5.


Later Novell released NetWare version 4.11 in 1996 which included many enhancements that made the operating system easier to install, easier to operate, faster, and more stable. It also included the first full 32-bit client for Microsoft Windows-based workstations, SMP support and the NetWare Administrator (NWADMIN or NWADMN32), a GUI-based administration tool for NetWare. Previous administration tools used the Cworthy interface, the character-based GUI tools such as SYSCON and PCONSOLE with blue text-based background. Some of these tools survive to this day, for instance MONITOR.NLM.


From the start, the NetWare design focused on servers with copious amounts of RAM. The entire file allocation table (FAT) was read into RAM when a volume was mounted, thereby requiring a minimum amount of RAM proportional to online disk space; adding a disk to a server would often require a RAM upgrade as well. Unlike most competing network operating systems prior to Windows NT, NetWare automatically used all otherwise unused RAM for caching active files, employing delayed write-backs to facilitate re-ordering of disk requests (elevator seeks). An unexpected shutdown could therefore corrupt data, making an uninterruptible power supply practically a mandatory part of a server installation.


Once the agent is installed, you can update to a newer agent version using these same installation procedures. It is not necessary to remove the old agent. If an agent is already installed, you have the option to save any custom agent settings during installation.


I wrote lholling an email because he answerd another novell netware post and he told me i should upgrade to SP9 - but how can i fresh install with SP9? Can i integrate SP9 in the normal installation prozess? Is there anybody out there who get this scenario up an running, if yes please give me some infos about your configuration?!


Another curious thing what happend to me was that when i tried to format drive c: of my dos installation the VM rebootet without any errors or warnings... what i did in the end was: i created an running dos vm in vmware server and imported that into esx...


i've no license for Portlock Storage Manager and Server Magic, but it's not a requirement for me to migrate the Novell Server. To reinstall the System successfully would be good enough for me. But as i wrote in my first post - i can't load the drivers you posted...


If it is a Servicepack 9 issue - would it be possible to make a new install directly with SP9? The normal setup fails when the installer tries to create the sys volume. When i reboot at this point, i have a dos partition with nwserver folder. I was able to start server.exe but only without sys vol and i also was not able to load your scsi driver.


many thanks for your help - but i'm thinking about using windows server 2003 with IPX instead of Novell 4.11 - the main reason is that it is not supported by vmware esx. I've to replace my novell dos clients with ms dos clients what is not very nice for me but i think in the end it would be a more stable solution...


A network device driver must be installed before the Broadcom NetXtreme Gigabit Ethernet adapter can be used with your Novell NetWare system. Before you can successfully install the adapter driver for Novell NetWare, the adapter card must be physically installed in the system and, typically, NetWare operating system software must already be running on the system. Make sure that your system meets the hardware and operating system software requirements described in Installing the Hardware. To enable the Broadcom NetXtreme Gigabit Ethernet adapter to function correctly, you must install the latest Novell NetWare support pack files. The NetWare support pack or patch file(s) needed for the operating system running on your system are indicated below: Table 1. NetWare Support Files NetWare Version Support Pack Files to be Installed NetWare 4.2 Latest support pack The latest support pack can be found at:


NOTE: The following instructions are for installing Novell NetWare Server 4.2, 5.1, or 6.0 driver software. For instructions on installing Novell NetWare Server 6.5 driver software, see Installing NetWare Server 6.5 Driver Software.


Verify that the system has the latest support pack available installed. The latest support packs can be found at: You may want to create an archive disk (see Creating a Driver Disk)by copying all the files from the CDROM\NetWare\Driver directory onto a floppy disk. If you elect to use the CD directly, ensure that the CDROM.NLM file is loaded and that you know the NetWare volume name for the CD.


Example: The default maximum number of receive buffers for the system is 500, and the default minimum is 128. Edit the Startup.ncf file to have the following entries. The actual number of receive buffers is a function of the number of ports in the system. The following is an example for a system with 8 ports installed:

0aad45d008