NetWare 4.x

edited July 2019 in Product Comments

NetWare 4.x

WinWorld is an online museum dedicated to providing free and open access to one of the largest archives of abandonware software and information on the web.

Read the full story here


Comments

  • Netware 4.2 seems to be broken; I'm trying to install it in VirtualBox, and it hangs after copying the installation files to the hard disk (this is the case whether I choose a simple or a custom installation).

  • Looks like 4.2 works in VMware (Netware 4 is not "officially" supported, but it does install, albeit I don't have a license disk).

  • @HeadsetGuy said:
    Netware 4.2 seems to be broken; I'm trying to install it in VirtualBox, and it hangs after copying the installation files to the hard disk (this is the case whether I choose a simple or a custom installation).

    I managed to get this version running in Qemu.

  • Novel Netware 4.11 CD isn't recognised as an ISO9660 image.

    I managed to fix/convert using the iat tool on Ubuntu:


    $ iat netware_4.11.iso netware_4.11_fixed.iso
    Iso9660 Analyzer Tool v0.1.3 by Salvatore Santagati
    Licensed under GPL v2 or later

    Detect Signature RAW at 2344
    Detect Signature RAW at 4696
    Detect Signature RAW at 7048
    Detect Signature RAW at 9400
    Detect Signature RAW at 11752
    Detect Signature RAW at 14104
    Detect Signature RAW at 16456
    Detect Signature RAW at 18808
    Detect Signature RAW at 21160
    Detect Signature RAW at 23512
    Detect Signature RAW at 25864
    Detect Signature RAW at 28216
    Detect Signature RAW at 30568
    Detect Signature RAW at 32920
    Detect Signature RAW at 35272
    Detect Signature RAW at 37624
    Detect Signature ISO9660 START at 37648
    Detect Signature RAW at 39976
    Detect Signature ISO9660 END at 40000

    Image offset start at 0
    Sector header 16 bit
    Sector ECC 288 bit
    Block 2352

    Done

    The new image ceated is now recognised by Qemu.

  • Not sure if relevant here but. Downloaded the Netware 4.11 iso from this site, extracted to installable cdrom. Under DOS 6.22 the install starts and then fails after approximately 60% through the file copy process to the \nwserver directory. Do I need to extract this image in some particular way? This is strictly through an MSDOS environment on an IBM 300 PL utilizing a Pentium 3 cpu. Thank you in advance.

  • Repackaged the 4.11 ISO, give it another try now.

  • There is a NetWare 4.2 100-user license ISO at https://archive.org/details/novell-net-ware-4.2.
  • Is there a link for the 4.11 license disk?
  • I'm not too familiar with these versions of Netware, is a license disk something that would have been provided alongside a CD-ROM? If there wasn't a floppy image in the 7z package, then I don't believe we ever had one.

    Were these disks copy protected?
  • CDs were all the same. The separate diskette containing the single encrypted file "SERVER.MLS" controlled number of users for a given license.

    I feel bad because once upon a time I had squirrelled away literally thousands of legit seats of 3.12 and 4.1 - and they are all gone now. :(
  • Ok, added a note about this in the product description.
  • edited June 2025
    4.2 does not install in Virtualbox 7 directly, first you have to intall in 86box.

    86box Config:
    Socket7-Dual Voltage - [i430TX] ASUS TX97 Pentium 100/66 128mb ram
    Display: [PCI} S3 Trio64 (Phoenix).
    Microsoft serial Mouse.
    No sound Card.
    Network [PCI} AMD PCnet FAST III
    Storage Controller: None FD Controller: None
    Hard Disk - This is important! - choose Raw Image - Ex: netware42.img. 1GB
    Use a DOS 6.2 boot disk, do fdisk, just create a 100mb primary partition, format c: /s and copy DOS files to c:\DOS
    Boot from HDD DOS boot, insert Netware 4.2 ISO and launch installation, partition the free space to SYS:\
    Skip the server license.
    After completion, convert within virtualbox path: "vboxmanage convertfromraw c:\temp\netware42.img c:\temp\netware.vdi --format vdi"
    Create Netware42 VM in Virtualbox without HDD
    copy the .vdi it in the Virtualbox VM folder. /Users/USERNAME/VirtualBoxVMs/Netware42/

    On Booting Virtualbox VM, run load install and Manage Network Drivers and Deselect network card Driver and Choose the same driver again, it will reconfigure autoexec.ncf automatically.
    Also you have to add load nw4-idle.nlm in autoexec.ncf manually and place it with toolbox.nlm in SYS:/System
    Startup.ncf you have also to add the line Load ideata.ham port=170 int=f for the cdrom to work, by then remove mscdex and config.sys device.
    You must also load the server licenses.

    To mount a cdrom:
    insert image in virtualbox
    On Netware prompt:
    load cdrom
    cd device list
    volume
    cd mount [volume] (the name that appears under volume)
    To change CD:
    dismount [volume]
    remove iso from virtualbox and add other
    unload cdrom
    load cdrom
    cd device list
    mount [volume]
  • FYI the process is similar for VMware Workstation Pro (now free). The advantage of using VMware Workstation is that its virtual disk format (VMDK) can be directly attached to a VirtualBox VM without conversion (and vice versa). (I am using VirtualBox v7.2.14 r174565 and VMware Workstation Pro v17.6.4 build-24832109).

    Proceed to install Netware 4.2 on VMWare Workstation first (because the installer will not succeed on VirtualBox) (specific instructions not provided):

    - Create a VMware Workstation VM with suitable hardware specifications for Netware 4.2 (ie. disk, ram, network)
    - MSDOS with appropriate CDROM driver
    - Netware 4.x from ISO

    After Netware is installed, proceed to migrate VMware Workstation to VirtualBox using below instructions.

    Shutdown Netware:

    Type "down".

    Type "exit".

    Power off the VMWare Guest.

    Note the VMware ".vmdk" (Virtual Machine Disk) file location.

    Create a new VM in VirtualBox with similar OS and hardware specifications. Additional attributes:

    - Attach the existing ".vmdk" file as the hard disk file

    - For Network settings:

    - Attached to = Bridged Adapter
    - Adapter Type = PCnet-PCI II (Am79C970A)

    Boot the Netware Server on VirtualBox VM:

    Type "cd c:\nwserver".

    Type "server.exe".

    For any prompts that appear (usually related to disk and network drivers), enter any value required to proceed (the values do not need to be correct at this time).

    Once the Netware Console prompt is reached,

    Load the Install module:

    Type "load install".

    Re-install storage drivers:

    Go to "Driver options -> Configure disk and storage device drivers".

    Remove existing disk drivers:

    Select "Deselect a selected driver".

    Repeat for all existing selected disk drivers.

    Autodetect storage drivers:

    Select "Discover and load additional drivers".

    Save changes.

    Exit back to Console.

    Mount system volume:

    Type "mount sys".

    Verify system volume is mounted:

    Type "volumes".

    Load the Install module (again):

    Type "load install".

    Re-install network drivers:

    Go to "Driver options -> Configure network drivers".

    Remove existing network drivers:

    Select "Deselect a selected driver".

    Repeat for all existing selected network drivers.

    Autodetect network drivers:

    Select "Discover and load additional drivers"

    Save changes.

    Exit back to Console.

    Re-initialise drivers:

    Type "reinitialize system".

    Reboot:

    Type "down".

    Type "exit".

    Type "cd c:\nwserver".

    Type "server.exe".

    Configure TCP (optional (ie. helpful for enabling TCPIP ping utility to test and/or troubleshoot VM network adapter settings)):

    Load the Internet Config module:

    Type "load inetcfg".

    Enable TCP/IP protocol:

    Go to "Protocols -> TCP/IP".

    Set TCP/IP Status = Enabled.

    Save changes.

    Return to module's top-level menu.

    Bind protocol to network interface:

    Go to "Bindings -> -> TCP/IP -> PCNTNW_1".

    - Local IP Address = eg. 192.168.1.47
    - Subnetwork Mask of Connected Network = FF.FF.FF.0

    Save changes.

    Exit back to Console.

    Re-initialise drivers:

    Type "reinitialize system".

    Test ping:

    Type "load ping".

    - Host name = eg. 192.168.1.1

    Press to start ping.

    Add more IPs to ping if desired.

    Observe that Sent and Received packets counter should be increasing.

    From another host with a TCPIP address, ping the Netware server's IP address:

    Type eg. "ping 192.168.1.47".

    Observe successful ping statistics.
Sign In or Register to comment.