The original NetWare product in 1983 supported clients running both CP/M and MS-DOS, ran over a proprietary star network topology and was based on a Novell-built file server using the Motorola 68000 processor. The company soon moved away from building its own hardware, and NetWare became hardware-independent, running on any suitable Intel-based IBM PC compatible system, and able to utilize a wide range of network cards. From the beginning NetWare implemented a number of features inspired by mainframe and minicomputer systems that were not available in its competitors' products.
By 2000, however, Microsoft was taking more of Novell's customer base and Novell increasingly looked to a future based on a Linux kernel. The successor to NetWare, Open Enterprise Server (OES), released in March 2005, offers all the services previously hosted by NetWare 6.5, but on a SUSE Linux Enterprise Server; the NetWare kernel remained an option until OES 11 in late 2011. NetWare 6.5SP8 General Support ended in 2010; Extended Support was available until the end of 2015, and Self Support until the end of 2017.
History
A networking card with a sticker indicating certification with NetWare
NetWare evolved from a very simple concept: file sharing instead of disk sharing. By controlling access at the level of individual files, instead of entire disks, files could be locked and better access control implemented. In 1983 when the first versions of NetWare originated, all other competing products were based on the concept of providing shared direct disk access. Novell's alternative approach was validated by IBM in 1984, which helped promote the NetWare product.
Novell NetWare shares disk space in the form of NetWare volumes, comparable to logical volumes. Client workstations running DOS run a special terminate and stay resident (TSR) program that allows them to map a local drive letter to a NetWare volume. Clients log into a server in order to be allowed to map volumes, and access can be restricted according to the login name. Similarly, they can connect to shared printers on the dedicated print server, and print as if the printer is connected locally.
At the end of the 1990s, with Internet connectivity booming, the Internet's TCP/IP protocol became dominant on LANs. Novell had introduced limited TCP/IP support in NetWare 3.x (c.1992) and 4.x (c.1995), consisting mainly of FTP services and UNIX-style LPR/LPD printing (available in NetWare 3.x), and a Novell-developed webserver (in NetWare 4.x). Native TCP/IP support for the client file and print services normally associated with NetWare was introduced in NetWare 5.0 (released in 1998). There was also a short-lived product, NWIP, that encapsulated IPX in TCP/IP, intended to ease transition of an existing NetWare environment from IPX to IP.
During the early to mid-1980s Microsoft introduced their own LAN system in LAN Manager, based on the competing NBF protocol. Early attempts to compete with NetWare failed, but this changed with the inclusion of improved networking support in Windows for Workgroups, and then the successful Windows NT and Windows 95. NT, in particular, offered a sub-set of NetWare's services, but on a system that could also be used on a desktop, and due to the vertical integration there was no need for a third-party client.
Early years
NetWare originated from consulting work by SuperSet Software, a group founded by the friends Drew Major, Dale Neibaur, Kyle Powell and later Mark Hurst. This work stemmed from their classwork at Brigham Young University in Provo, Utah, starting in October 1981.
In 1981, Raymond Noorda engaged[clarification needed] the work by the SuperSet team. The team was originally assigned to create a CP/Mdisk sharing system to help network the Motorola 68000-based hardware that Novell sold at the time. The first S-Net is CP/M-68K-based and shares a hard disk. In 1983, the team was privately convinced that CP/M was a doomed platform and instead came up with a successful file-sharing system for the newly introduced IBM-compatible PC. They also wrote an application called Snipes – a text-mode game – and used it to test the new network and demonstrate its capabilities. Snipes [aka 'NSnipes' for 'Network Snipes'] is the first network application ever written for a commercial personal computer, and it is recognized as one of the precursors of many popular multiplayer games such as Doom and Quake.[5]
First called ShareNet or S-Net, this network operating system (NOS) was later called Novell NetWare. NetWare is based on the NetWare Core Protocol (NCP), which is a packet-based protocol that enables a client to send requests to and receive replies from a NetWare server. Initially, NCP was directly tied to the IPX/SPX protocol, and NetWare communicated natively using only IPX/SPX.
The first product to bear the NetWare name was released in 1983. The original product, NetWare 68 (AKA S-Net), ran on Novell's proprietary 68000-based file server hardware, and used a star network topology. This was later joined by NetWare 86, which could use conventional Intel 8086-based PCs for the server. This was replaced in 1985 with Advanced NetWare 86, which allowed more than one server on the same network. In 1986, after the Intel 80286 processor became available, Novell released Advanced NetWare 286. Two versions were offered for sale; the basic version was sold as ELS I, plus an enhanced version, ELS II. *ELS* stood for "Entry Level System".
NetWare 286 2.x
Floppy disks for NetWare 2.2
Advanced NetWare version 2.x, launched in 1986, was written for the then-new 80286 CPU. The 80286 CPU features a new 16-bit protected mode that provides access to up to 16MiB RAM as well as new mechanisms to aid multi-tasking. (Prior to the 80286, PC CPU servers used the Intel 8088/8086 8-/16-bit processors, which are limited to an address space of 1MiB with not more than 640KiB of directly addressable RAM.) The combination of a higher 16MiB RAM limit, 80286 processor feature utilization, and 256MB NetWare volume size limit (compared to the 32MB that DOS allowed at that time) allowed the building of reliable, cost-effective server-based local area networks for the first time. The 16MiB RAM limit was especially important, since it makes enough RAM available for disk caching to significantly improve performance. This became the key to Novell's performance while also allowing larger networks to be built.
In a significant innovation, NetWare 286 is also hardware-independent, unlike competing network server systems. Novell servers can be assembled using any brand system with an Intel 80286 CPU, any MFM, RLL, ESDI, or SCSI hard drive and any 8- or 16-bit network adapter for which NetWare drivers are available – and 18 different manufacturer's network cards were supported at launch.[6]
The server could support up to four network cards,[6] and these can be a mixture of technologies such as ARCNET, Token Ring and Ethernet. The operating system is provided as a set of compiled object modules that required configuration and linking. Any change to the operating system requires a re-linking of the kernel. Installation also requires the use of a proprietary low-level format program for MFM hard drives called COMPSURF.
The file system used by NetWare2.x is NetWare File System 286, or NWFS286, supporting volumes of up to 256MB. NetWare286 recognizes 80286 protected mode, extending NetWare's support of RAM from 1MiB to the full 16MiB addressable by the 80286. A minimum of 2MiB is required to start up the operating system; any additional RAM is used for FAT, DET and file caching. Since 16-bit protected mode is implemented in the 80286 and every subsequent Intel x86 processor, NetWare286 version 2.x will run on any 80286 or later compatible processor.
NetWare 2.x implements a number of features inspired by mainframe and minicomputer systems that were not available in other operating systems of the day. The System Fault Tolerance (SFT) features includes standard read-after-write verification (SFT-I) with on-the-fly bad block re-mapping (at the time, disks did not have that feature built in) and software RAID1 (disk mirroring, SFT-II). The Transaction Tracking System (TTS) optionally protects files against incomplete updates. For single files, this requires only a file attribute to be set. Transactions over multiple files and controlled roll-backs are possible by programming to the TTS API.
NetWare2862.x normally requires a dedicated PC to act as the server, where the server uses DOS only as a boot loader to execute the operating system file NET$OS.EXE. All memory is allocated to NetWare; no DOS ran on the server. However, a "non-dedicated" version was also available for price-conscious customers. In this, DOS3.3 or higher remains in memory, and the processor time-slices between the DOS and NetWare programs, allowing the server computer to be used simultaneously as a network file server and as a user workstation. Because all extended memory (RAM above 1MiB) is allocated to NetWare, DOS is limited to only 640KiB; expanded memory managers that used the MMU of 80386 and higher processors, such as EMM386, do not work; 8086-style expanded memory on dedicated plug-in cards is possible however. Time slicing is accomplished using the keyboard interrupt, which requires strict compliance with the IBM PC design model, otherwise performance is affected.
Server licensing on early versions of NetWare286 is accomplished by using a key card. The key card was designed for an 8-bit ISA bus, and has a serial number encoded on a ROM chip. The serial number has to match the serial number of the NetWare software running on the server. To broaden the hardware base, particularly to machines using the IBM MCA bus, later versions of NetWare2.x do not require the key card; serialised license floppy disks are used in place of the key cards.
Licensing is normally for 100 users, but two ELS versions were also available. First a 5-user ELS in 1987, and followed by the 8-user ELS2.12II in 1988.[7]
NetWare 3.x
NetWare's 3.x range was a major step forward. It began with version 3.0 in 1990, followed quickly by version 3.10 and 3.11 in 1991.
A key feature was support for 32-bitprotected mode, eliminating the 16MiB memory limit of NetWare286 and therefore allowing larger hard drives to be supported (since NetWare3.x cached the entire file allocation table and directory entry table into memory for improved performance).
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.
A new file system was introduced by NetWare3.x– "NetWare File System 386", or NWFS386, which significantly extended volume capacity (1TB, 4GB files), and could handle up to 16 volume segments spanning multiple physical disk drives. Volume segments could be added while the server was in use and the volume was mounted, allowing a server to be expanded without interruption.
In NetWare3863.x all NLMs ran on the server at the same level of processor memory protection, known as "ring 0". This provided the best possible performance, it sacrificed reliability because there was no memory protection, and furthermore NetWare 3.x used a co-operative multitasking model, meaning that an NLM was required to yield to the kernel regularly. For either of these reasons a badly behaved NLM could result in a fatal (ABEND) error.
NetWare continued to be administered using console-based utilities.
Beginning in 1992, Novell's third-party vendors received license to use the above logo to market their NetWare-compatible products, for a fee.
With version 3.x, Novell increased the rigors of compatibility testing with their third-party vendors, revamping their certification program in October 1992 and unveiling a two-tier cooperating marketing program. The first tier provided Novell's vendors a package containing a compatibility guideline book, engineering support lines, self-testing tools, and limited marketing resources, the latter including a license to promote products with a logo stating "Yes, it runs with NetWare"– all free of charge and followed at the vendors' discretion. The second tier required a one-time application fee of $7,000 but replaced the logo's byline with a more confident-sounding "Yes, it's NetWare tested and approved" and accorded partners with more extensive support, including on-location testing by Novell Labs.[8][9] Initially limited to the United States, this program was rolled out in the United Kingdom in the following year.[10][11]
For a while, Novell also marketed an OEM version of NetWare3, called Portable NetWare. Originally announced in 1989 by Prime Computer as a product for its Prime EXL range, along with a distinct product for Unix System V,[12] Novell attracted support from a number of other OEMs including Data General, Hewlett-Packard, NCR Corporation, Sun Microsystems and Unisys.[13] An implementation provided by Altos was described in one review as "NetWare 386 for PC Unix systems", running in the standard Unix environment, utilising the native filesystem and network interfaces.[14] Portable NetWare's primary purpose was to offer file and print sharing facilities, but a "native" port of Netware to other platforms was considered necessary to offer the broader feature set of Novell's traditional NetWare products.[15] Alongside Hewlett-Packard, IBM collaborated with Novell to offer Portable NetWare and more comprehensive "native" ports of NetWare for its platforms.[16] Portable NetWare was later known as NetWare for UNIX. As a version of NetWare written in the C programming language, Novell would port functionality from its traditional product to a reference platform, leaving OEMs to port the Novell source code to run on top of their own, typically Unix, operating systems.[17]
While NetWare3.x was current, Novell introduced its first high-availability clustering system, named NetWare SFT-III, which allowed a logical server to be completely mirrored to a separate physical machine. Implemented as a shared-nothing cluster, under SFT-III the OS was logically split into an interrupt-driven I/O engine and the event-driven OS core. The I/O engines serialized their interrupts (disk, network etc.) into a combined event stream that was fed to two identical copies of the system engine through a fast (typically 100Mbit/s) inter-server link. Because of its non-preemptive nature, the OS core, stripped of non-deterministic I/O, behaves deterministically, like a large finite state machine. The outputs of the two system engines were compared to ensure proper operation, and two copies fed back to the I/O engines. Using the existing SFT-II software RAID functionality present in the core, disks could be mirrored between the two machines without special hardware. The two machines could be separated as far as the server-to-server link would permit. In case of a server or disk failure, the surviving server could take over client sessions transparently after a short pause since it had full state information. SFT-III was the first NetWare version able to make use of SMP hardware– the I/O engine could optionally be run on its own CPU. NetWare SFT-III, ahead of its time in several ways, was a mixed success.
NetWare4 and NDS were the subjects of many technical sessions at the Novell BrainShare conference, here seen during a break in 1995.Packages of NetWare 4.x
Version4 in 1993 introduced NetWare Directory Services, later re-branded as Novell Directory Services (NDS), based on X.500, which replaced the Bindery with a global directory service, in which the infrastructure was described and managed in a single place. Additionally, NDS provided an extensible schema, allowing the introduction of new object types. This allowed a single user authentication to NDS to govern access to any server in the directory tree structure. Users could therefore access network resources no matter on which server they resided, although user license counts were still tied to individual servers. (Large enterprises could opt for a license model giving them essentially unlimited per-server users if they let Novell audit their total user count.)
Version4 also introduced a number of useful tools and features, such as transparent compression at file system level and RSA public/private encryption.
Another new feature was the NetWare Asynchronous Services Interface (NASI). It allowed network sharing of multiple serial devices, such as modems. Client port redirection occurred via a DOS or Windows driver allowing companies to consolidate modems and analog phone lines.[18]
NetWare for OS/2
Promised as early as 1988, when the Microsoft-IBM collaboration was still ongoing and OS/21.x was still a 16-bit product,[19] the product didn't become commercially available until after IBM and Microsoft had parted ways and OS/22.0 had become a 32-bit, pre-emptive multitasking and multithreading OS.
By August 1993,[20] Novell released its first version of "NetWare for OS/2". This first release supported OS/22.1 (1993) as the base OS, and required that users first buy and install IBM OS/2, then purchase NetWare4.01, and then install the NetWare for OS/2 product. It retailed for $200.[20]
By around 1995, and coincidental with IBM's renewed marketing push for its 32-bit OS/2 Warp OS, both as a desktop client and as a LAN server (OS/2 Warp Server), NetWare for OS/2 began receiving some good press coverage. "NetWare 4.1 for OS/2" allowed to run Novell's network stack and server modules on top of IBM's 32-bit kernel and network stack. It was basically NetWare 4.x running as a service on top of OS/2. It was compatible with third party client and server utilities and NetWare Loadable Modules.[21]
Since IBM's 32-bit OS/2 included Netbios, IPX/SPX and TCP/IP support, this means that sysadmins could run all three most popular network stacks on a single box, and use the OS/2 box as a workstation too. NetWare for OS/2 shared memory on the system with OS/2 seamlessly. The book "Client Server survival Guide with OS/2" described it as "glue code that lets the unmodified NetWare4.x server program think it owns all resources on a OS/2 system". It also claimed that a NetWare server running on top of OS/2 only suffered a 5% to 10% overhead over NetWare running over the bare metal hardware, while gaining OS/2's pre-emptive multitasking and object oriented GUI.[22]
Novell continued releasing bugfixes and updates to NetWare for OS/2 up to 1998.[23]
Strategic mistakes
Novell's strategy with NetWare2862.x and 3.x proved very successful; before the arrival of Windows NT Server, Novell claimed 90% of the market for PC based servers.
However, the design of NetWare3.x and later involved a DOS partition to load NetWare server files. While of little technical import,[a] this feature became a liability due to the system administration it required. Compounding this, the NetWare console remained text-based at a time the Windows graphical interface gained widespread acceptance. Especially new users preferred the Windows graphical interface to learning DOS commands necessary to build and control a NetWare server. Novell could have eliminated at least the separately bootable DOS partition requirement at the outset, by retaining the design of NetWare286, 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 NetWare6.5.
As Novell initially used IPX/SPX instead of TCP/IP, they were poorly positioned to take advantage of the Internet in 1995. This resulted in Novell servers being bypassed for routing and Internet access in favor of hardware routers, Unix-based operating systems such as FreeBSD, and SOCKS and HTTP Proxy Servers on Windows and other operating systems.[citation needed]
A decision by the management of Novell also took away the ability of independent resellers and engineers to recommend and sell the product. The reduction of their effective sales force created this downward spiral in sales.
NetWare 4.1x and NetWare for Small Business
A book on NetWare published in Thai
Novell priced NetWare4.10 similarly to NetWare3.12, allowing customers who resisted NDS (typically small businesses) to try it at no cost.
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.
Novell packaged NetWare4.11 with its Web server, TCP/IP support and the Netscape browser into a bundle dubbed IntranetWare (also written as intraNetWare). A version designed for networks of 25 or fewer users was named IntranetWare for Small Business and contained a limited version of NDS and tried to simplify NDS administration. The intranetWare name was dropped in NetWare5.
During this time Novell also began to leverage its directory service, NDS, by tying their other products into the directory. Their e-mail system, GroupWise, was integrated with NDS, and Novell released many other directory-enabled products such as ZENworks and BorderManager.
NetWare still required IPX/SPX as NCP used it, but Novell started to acknowledge the demand for TCP/IP with NetWare4.11 by including tools and utilities that made it easier to create intranets and link networks to the Internet. Novell bundled tools, such as the IPX/IP gateway, to ease the connection between IPX workstations and IP networks. It also began integrating Internet technologies and support through features such as a natively hosted web server.
NetWare 5.x
With the release of NetWare5 in October 1998 Novell switched its primary NCP interface from the IPX/SPX network protocol to TCP/IP to meet market demand.[24] Products continued to support IPX/SPX, but the emphasis shifted to TCP/IP. New features included:
The Cluster Services improved on SFT-III, as NCS did not require specialized hardware or identical server configurations.
Novell released NetWare5 during a time when NetWare's market share had started dropping precipitously; many companies and organizations replaced their NetWare servers with servers running Microsoft's Windows NT operating system.
Around this time Novell also released their last upgrade to the NetWare4 operating system, NetWare4.2.
NetWare5 and above supported Novell NetStorage for Internet-based access to files stored within NetWare.[26][27] Novell released NetWare5.1 in January 2000. It introduced a number of tools, such as:
NetWare6 was released in October 2001, shortly after its predecessor. This version has a simplified licensing scheme based on users, not server connections. This allows unlimited connections per user to any number of NetWare servers in the network.[28] Novell Cluster Services was also improved to support 32-node clusters;[29] the base NetWare6.0 product included a two-node clustering license.
NetWare 6.5
NetWare6.5 was released in August 2003. Some of the new features in this version included:
In 2003, Novell announced the successor product to NetWare: Open Enterprise Server (OES). First released in March 2005, OES completes the separation of the services traditionally associated with NetWare (such as Directory Services, and file-and-print) from the platform underlying the delivery of those services. OES is essentially a set of applications (eDirectory, NetWare Core Protocol services, iPrint, etc.) that can run atop either a Linux or a NetWare kernel platform. Clustered OES implementations can even migrate services from Linux to NetWare and back again, making Novell one of the very few vendors to offer a multi-platform clustering solution.
Consequent to Novell's acquisitions of Ximian and the German Linux distributor SuSE, Novell moved away from NetWare and shifted its focus towards Linux. Marketing was focused on getting faithful NetWare users to move to the Linux platform for future releases.[30] The clearest indication of this direction was Novell's controversial decision to release Open Enterprise Server on Linux only, not NetWare. Novell later watered down this decision and stated that NetWare's 90 million users would be supported until at least 2015.[31] Meanwhile, many former NetWare customers rejected the confusing mix of licensed software running on an open-source Linux operating system in favor of moving to complete Open Source solutions such as those offered by Red Hat.[32]
2.0
OES 2 was released on 8 October 2007. It includes NetWare6.5 SP7, which supports running as a paravirtualized guest inside the Xen hypervisor and new Linux based version using SLES10.
Dynamic Storage Technology, which provide Shadow Volumes
Domain services for Windows (provided in OES2 service pack 1)
From the 1990s
As of 2010[update] some organizations still used Novell NetWare, but it had started to lose popularity from the mid-1990s, when NetWare was the de facto standard for file- and printer-sharing software for the Intel x86 server platform.[33]
Microsoft successfully took market share from NetWare products from the late-1990s.[34][35] Microsoft's more aggressive marketing was aimed directly at non-technical management through major magazines, while Novell NetWare's was through more technical magazines read by IT personnel.[citation needed]
Novell did not adapt their pricing structure to current market conditions, and NetWare sales suffered.[36]
The success of NetWare as a product is what allowed Novell to have sales-related offices around the world, as the back side of this mid-1990s Novell presentation folder shows.
NetWare dominated the network operating system (NOS) market from the mid-1980s through the mid- to late-1990s due to its extremely high performance relative to other NOS technologies. Most benchmarks during this period demonstrated a 5:1 to 10:1 performance advantage over products from Microsoft, Banyan, and others. One noteworthy benchmark pitted NetWare 3.x running NFS services over TCP/IP (not NetWare's native IPX protocol) against a dedicated Auspex NFS server and an SCO Unix server running NFS service. NetWare NFS outperformed both 'native' NFS systems and claimed a 2:1 performance advantage over SCO Unix NFS on the same hardware.[citation needed]
The reasons for NetWare's performance advantage are given below.
File service instead of disk service
When first developed, nearly all LAN storage was based on the disk server model. This meant that if a client computer wanted to read a particular block from a particular file it would have to issue the following requests across the relatively slow LAN:
Read first block of directory
Continue reading subsequent directory blocks until the directory block containing the information on the desired file was found, could be many directory blocks
Read through multiple file entry blocks until the block containing the location of the desired file block was found, could be many directory blocks
Read the desired data block
NetWare, since it was based on a file service model, interacted with the client at the file API level:
Send file open request (if this hadn't already been done)
Send a request for the desired data from the file
All of the work of searching the directory to figure out where the desired data was physically located on the disk was performed at high speed locally on the server. By the mid-1980s, most NOS products had shifted from the disk service to the file service model. Today, the disk service model is making a comeback, see SAN.
Aggressive caching
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.
The default dirty cache delay time was fixed at 2.2 seconds in NetWare286 versions 2.x. Starting with NetWare3863.x, the dirty disk cache delay time and dirty directory cache delay time settings controlled the amount of time the server would cache changed ("dirty") data before saving (flushing) the data to a hard drive. The default setting of 3.3seconds could be decreased to 0.5seconds but not reduced to zero, while the maximum delay was 10seconds. The option to increase the cache delay to 10seconds provided a significant performance boost. Windows2000 and 2003 server do not allow adjustment to the cache delay time. Instead, they use an algorithm that adjusts cache delay.
Efficiency of NetWare Core Protocol (NCP)
Most network protocols in use at the time NetWare was developed didn't trust the network to deliver messages. A typical client file read would work something like this:
Client sends read request to server
Server acknowledges request
Client acknowledges acknowledgement
Server sends requested data to client
Client acknowledges data
Server acknowledges acknowledgement
In contrast, NCP was based on the idea that networks worked perfectly most of the time, so the reply to a request served as the acknowledgement. Here is an example of a client read request using this model:
Client sends read request to server
Server sends requested data to client
All requests contained a sequence number, so if the client didn't receive a response within an appropriate amount of time it would re-send the request with the same sequence number. If the server had already processed the request it would resend the cached response, if it had not yet had time to process the request it would only send a "positive acknowledgement". The bottom line to this 'trust the network' approach was a 2/3 reduction in network transactions and the associated latency.
Non-preemptive OS designed for network services
One of the raging debates of the 1990s was whether it was more appropriate for network file service to be performed by a software layer running on top of a general purpose operating system, or by a special purpose operating system. NetWare was a special purpose operating system, not a timesharing OS. It was written from the ground up as a platform for client-server processing services. Initially it focused on file and print services, but later demonstrated its flexibility by running database, email, web and other services as well. It also performed efficiently as a router, supporting IPX, TCP/IP, and Appletalk, though it never offered the flexibility of a 'hardware' router.
In 4.x and earlier versions, NetWare did not support preemption, virtual memory,[37]graphical user interfaces, etc. Processes and services running under the NetWare OS were expected to be cooperative, that is to process a request and return control to the OS in a timely fashion. On the down side, this trust of application processes to manage themselves could lead to a misbehaving application bringing down the server.
↑ DOS merely loaded NetWare into memory and turned execution over to it. In later versions, DOS could be unloaded from RAM.
Related Research Articles
Internetwork Packet Exchange (IPX) is the network-layer protocol in the IPX/SPX protocol suite. IPX is derived from Xerox Network Systems' IDP. It also has the ability to act as a transport layer protocol.
Samba is a free software re-implementation of the SMB networking protocol, and was originally developed by Andrew Tridgell. Samba provides file and print services for various Microsoft Windows clients and can integrate with a Microsoft Windows Server domain, either as a Domain Controller (DC) or as a domain member. As of version 4, it supports Active Directory and Microsoft Windows NT domains.
A network operating system (NOS) is a specialized operating system for a network device such as a router, switch or firewall.
Network File System (NFS) is a distributed file system protocol originally developed by Sun Microsystems (Sun) in 1984, allowing a user on a client computer to access files over a computer network much like local storage is accessed. NFS, like many other protocols, builds on the Open Network Computing Remote Procedure Call system. NFS is an open IETF standard defined in a Request for Comments (RFC), allowing anyone to implement the protocol.
Novell, Inc. was an American software and services company headquartered in Provo, Utah, that existed from 1980 until 2014. Its most significant product was the multi-platform network operating system known as Novell NetWare. Novell technology contributed to the emergence of local area networks, which displaced the dominant mainframe computing model and changed computing worldwide.
In computing, the Windows Sockets API (WSA), later shortened to Winsock, is an application programming interface (API) that defines how Windows network application software should access network services, especially TCP/IP. It defines a standard interface between a Windows TCP/IP client application and the underlying TCP/IP protocol stack. The nomenclature is based on the Berkeley sockets API used in BSD for communications between programs.
Banyan VINES is a discontinued network operating system developed by Banyan Systems for computers running AT&T's UNIX System V.
IPX/SPX stands for Internetwork Packet Exchange/Sequenced Packet Exchange. IPX and SPX are networking protocols used initially on networks using the Novell NetWare operating systems. They also became widely used on networks deploying Microsoft Windows LANs, as they replaced NetWare LANs, but are no longer widely used. IPX/SPX was also widely used prior to and up to Windows XP, which supported the protocols, while later Windows versions do not, and TCP/IP took over for networking.
Btrieve is a transactional database software product. It is based on Indexed Sequential Access Method (ISAM), which is a way of storing data for fast retrieval. There have been several versions of the product for DOS, Linux, older versions of Microsoft Windows, 32-bit IBM OS/2 and for Novell NetWare.
The Apple Filing Protocol (AFP), formerly AppleTalk Filing Protocol, is a proprietary network protocol, and part of the Apple File Service (AFS), that offers file services for macOS, classic Mac OS, and Apple II computers. In OS X 10.8 Mountain Lion and earlier, AFP was the primary protocol for file services. Starting with OS X 10.9 Mavericks, Server Message Block (SMB) was made the primary file sharing protocol, with the ability to run an AFP server removed later in macOS 11 Big Sur. AFP supports Unicode file names, POSIX and access-control list permissions, resource forks, named extended attributes, and advanced file locking.
UnixWare is a Unix operating system. It was originally released by Univel, a jointly owned venture of AT&T's Unix System Laboratories (USL) and Novell. It was then taken over by Novell. Via Santa Cruz Operation (SCO), it went on to Caldera Systems, Caldera International, and The SCO Group before it was sold to UnXis. UnixWare is typically deployed as a server rather than a desktop. Binary distributions of UnixWare are available for x86 architecture computers. UnixWare is primarily marketed as a server operating system.
AppleShare is a discontinued product from Apple Computer which implements various network services. Its main purpose is to act as a file server, using the AFP protocol. Other network services implemented in later versions of AppleShare included a print server using the Printer Access Protocol (PAP), web server, electronic mail server, and SMB / CIFS server to support file sharing to Microsoft Windows clients.
In computing, the NetWare File System (NWFS) was a file system based on a heavily optimized, journal-based FAT file system. It was used in the Novell NetWare network operating system. It was the only file system for all volumes in NetWare versions 2.x, 3.x and 4.x, and the default and only file system for the SYS: volume continuing through version 5.x. Novell developed two varieties of NWFS:
16-bit NWFS 286, used in NetWare 2.x
32-bit NWFS 386, used in NetWare 3.x through NetWare 6.x.
The NetWare Core Protocol (NCP) is a network protocol used in some products from Novell, Inc. It is usually associated with the client-server operating system Novell NetWare which originally supported primarily MS-DOS client stations, but later support for other platforms such as Microsoft Windows, the classic Mac OS, Linux, Windows NT, Mac OS X, and various flavors of Unix was added.
Univel, Inc. was a joint venture of Novell and AT&T's Unix System Laboratories (USL) that was formed in December 1991 to develop and market the Destiny desktop Unix operating system, which was released in 1992 as UnixWare 1.0. Univel existed only briefly in the period between AT&T initially divesting parts of USL in 1991, and its eventual outright purchase by Novell, which completed in June 1993, thereby acquiring rights to the Unix operating system. Novell merged USL and Univel into their new Unix Systems Group (USG).
cc:Mail is a discontinued store-and-forward LAN-based email system originally developed on Microsoft's MS-DOS platform by Concentric Systems, Inc. in the 1980s. The company, founded by Robert Plummer, Hubert Lipinski, and Michael Palmer, later changed its name to PCC Systems, Inc., and then to cc:Mail, Inc. At the height of its popularity, cc:Mail had about 14 million users, and won various awards for being the top email software package of the mid-1990s.
Novell Embedded Systems Technology (NEST) was a series of APIs, data formats and network protocol stacks written in a highly portable fashion intended to be used in embedded systems. The idea was to allow various small devices to access Novell NetWare services, provide such services, or use NetWare's IPX protocol as a communications system. Novell referred to this concept as "Extended Networks", and when the effort was launched they boasted that they wanted to see one billion devices connected to NetWare networks by year 2000. NEST was launched in mid-1994 countering Microsoft's similar Microsoft at Work efforts, which had been launched in 1993.
NetWare Lite and Personal NetWare are a series of discontinued peer-to-peer local area networks developed by Novell for DOS- and Windows-based personal computers aimed at personal users and small businesses in the 1990s.
GroupWise is a messaging and collaboration platform from OpenText that supports email, calendaring, personal information management, instant messaging, and document management. The GroupWise platform consists of desktop client software, which is available for Windows,, and the server software, which is supported on Windows Server and Linux.
↑ Janah, Monua (1998-03-16). "Netware's Window Of Opportunity". InformationWeek News - Connects The Business Technology Community. Archived from the original on 2000-12-05. Retrieved 2014-05-23. 'The market has spoken, and TCP/IP has won,' says Novell CEO Eric Schmidt of the move to IP, a decision that was bitterly contested inside the company.
↑ Johnson, David; Gaskin, James E.; Cheung, Daniel; Tittel, Ed (2003). Novell NetWare 5.x to 6 upgrade. Exam cram 2. Que Publishing. pp.177, 426. ISBN978-0-7897-2788-6. Retrieved 2010-05-25. NetStorage is a bridge between a company's private, internal Novell network and the public Internet. Users can use NetStorage to securely access files from any location that has Internet access, without having to download or install additional software on the workstation.
↑ "How does User Access Licensing differ from earlier versions of NetWare?"(PDF). Novell NetWare 6.0 - NetWare Licensing Frequently Asked Questions. Novell. March 2002. p.7. Retrieved 2012-08-20. In previous versions of NetWare, a Server Connection License model is used, where users are granted access to network services on a per-server basis. This means each time a user accesses services on a different server, the user consumes a license unit on that server. Printer connections also consume a connection license. In the NetWare 6 User Access License model, users consume a single User license (per tree) regardless of the number of NetWare 6 servers they log on to. Printers that connect to a NetWare 6 server do not consume a User license. The same is true for all other non-User connections.
↑ "Overview-Product Features"(PDF). Novell NetWare 6.0 - Novell Cluster Services Overview and Installation. Provo, UT, USA: Novell. February 2002. p.9. Archived from the original(PDF) on 2006-11-25. Retrieved 2012-08-20. Multinode all-active cluster (up to 32 nodes). Any NetWare server in the cluster can restart resources (applications, services, IP addresses, and volumes) from a failed server in the cluster
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
