Misplaced Pages

#150849

70-530: VINES is an acronym for Virtual Integrated NEtwork Service . Like Novell NetWare , VINES's network services are based on the Xerox XNS stack . James Allchin , who later worked as Group Vice President for Platforms at Microsoft until his retirement on January 30, 2007, was the chief architect of Banyan VINES. VINES ran on a low-level protocol known as VIP —the VINES Internetwork Protocol —that

140-450: A CP/M disk 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 –

210-737: 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

280-593: A DOS or Windows driver allowing companies to consolidate modems and analog phone lines. Promised as early as 1988, when the Microsoft-IBM collaboration was still ongoing and OS/2  1. x was still a 16-bit product, the product didn't become commercially available until after IBM and Microsoft had parted ways and OS/2 2.0 had become a 32-bit, pre-emptive multitasking and multithreading OS. By August 1993, Novell released its first version of "NetWare for OS/2". This first release supported OS/2 2.1 (1993) as

350-553: 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

420-466: A Support Pack for NetWare 6.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. A decision by

490-506: A client first boots up, it broadcast a request on the subnet asking for servers, which responds with suggested addresses. The client used the first to respond, although the servers could hand off "better" routing instructions to the client if the network changed. The overall concept resembled AppleTalk 's AARP system, with the exception that VINES required at least one server, whereas AARP functioned as peer-to-peer . Like AARP, VINES required an inherently "chatty" network, sending updates about

560-459: 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, DOS 3.3 or higher remains in memory, and the processor time-slices between the DOS and NetWare programs, allowing

630-454: A differentiator, eventually porting it to NT as a stand-alone product and offering it as an interface to LDAP systems. Banyan continued to operate a closed OS. This required hardware manufacturers to submit hardware and driver requirements so that Banyan could write drivers for each peripheral. When more open systems with published APIs began to appear, Banyan did not alter their model. This made it difficult for client-side support to handle

700-453: A flat server or domain-based network model—came to realize the strategic value of directory services. With little warning, Novell went from playing down the value of directory services to announcing its own: NetWare Directory Services (NDS). Eventually, Novell changed NDS to mean Novell Directory Services, and then renamed that to eDirectory. For Windows 2000 however, Microsoft included Active Directory , an LDAP directory service based on

770-426: A higher 16 MiB RAM limit, 80286 processor feature utilization, and 256 MB NetWare volume size limit (compared to the 32 MB that DOS allowed at that time) allowed the building of reliable, cost-effective server-based local area networks for the first time. The 16 MiB RAM limit was especially important, since it makes enough RAM available for disk caching to significantly improve performance. This became

SECTION 10

#1732869433151

840-550: A license model giving them essentially unlimited per-server users if they let Novell audit their total user count.) Version 4 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

910-523: 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 100 Mbit/s) inter-server link. Because of its non-preemptive nature,

980-418: 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 NetWare 2. x

1050-582: 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. Initially limited to

1120-582: 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". Advanced NetWare version 2. x , launched in 1986,

1190-403: 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 . First called ShareNet or S-Net , this network operating system (NOS)

1260-552: A third-party client. 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 the work by the SuperSet team. The team was originally assigned to create

1330-450: 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. In 1991, Novell introduced cheaper peer-to-peer networking products for DOS and Windows , unrelated to their server-centric NetWare. These are NetWare Lite 1.0 (NWL), and later Personal NetWare 1.0 (PNW) in 1993. In 1993,

1400-529: A wider range of network devices and systems, increasing its compatibility and appeal to a broader audience. 3Com's contribution to Microsoft's network and server software capabilities is closely tied to their collaboration on the development of LAN Manager . LAN Manager was Microsoft's networking software that aimed to provide file and print services for PCs connected in a network. In the late 1980s, Microsoft partnered with 3Com to integrate 3+Open's networking capabilities into LAN Manager. This collaboration led to

1470-399: Is NetWare File System 286, or NWFS 286, supporting volumes of up to 256 MB. NetWare 286 recognizes 80286 protected mode , extending NetWare's support of RAM from 1 MiB to the full 16 MiB addressable by the 80286. A minimum of 2 MiB is required to start up the operating system; any additional RAM is used for FAT , DET and file caching. Since 16-bit protected mode

SECTION 20

#1732869433151

1540-708: Is a discontinued computer network operating system developed by Novell, Inc. It initially used cooperative multitasking to run various services on a personal computer, using the IPX network protocol. 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

1610-467: 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 NetWare 286 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

1680-460: Is implemented in the 80286 and every subsequent Intel x86 processor, NetWare 286 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

1750-538: 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 NetWare ;5. During this time Novell also began to leverage its directory service, NDS, by tying their other products into

1820-568: 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

1890-627: The Marine Corps was ready for its first big test of VINES: the 1990-1991 Gulf War . Units were able to seamlessly coordinate ground, naval, and air strikes across military boundaries by using the chat function to pass target lists and adjust naval gun fire on the fly. Ground fire support coordination agencies used VINES up and down command channels—from Battalion-to-Regiment through Division-to-Corps and Squadron-to-Group to Aircraft Wing-to-Corps, as well as in peer-to-peer unit communication. 3Com 's journey into network operating system development began in

1960-477: 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

2030-579: The State Department, Treasury Department , Department of Agriculture , Department of Health and Human Services , and Department of Defense . The U.S. State Department was an early adopter of the VINES technology. Able to take advantage of the then high-speed 56k modems for telephonic connectivity of the developed world to the limited telephone modem speeds of 300 baud over bad analog telephone systems in developing countries, VINES linked embassies around

2100-631: The United States, this program was rolled out in the United Kingdom in the following year. For a while, Novell also marketed an OEM version of NetWare 3, 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, Novell attracted support from a number of other OEMs including Data General , Hewlett-Packard , NCR Corporation , Sun Microsystems and Unisys . An implementation provided by Altos

2170-500: 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 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

Banyan VINES - Misplaced Pages Continue

2240-511: The XNS (Xerox Network Systems) protocol suite. Over the years, 3Com continued to refine and improve its network operating systems. In 1985, they introduced 3+Open, which added support for third-party hardware. 3+Open was a significant advancement in 3Com's network operating system lineup. Introduced in 1985, it expanded on the capabilities of their previous offerings by providing support for third-party hardware and software. This allowed 3+Open to work with

2310-478: The arrival of Windows NT Server, Novell claimed 90% of the market for PC based servers. However, the design of NetWare 3. x and later involved a DOS partition to load NetWare server files. While of little technical import, 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

2380-525: 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. 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

2450-448: 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

2520-595: The creation of LAN Manager 2.0, which was released in 1989. This version of LAN Manager incorporated technologies from both Microsoft and 3Com, resulting in improved networking capabilities and compatibility. It enabled Microsoft to strengthen its networking offerings, making it a more competitive player in the network operating system space. Microsoft's experience with LAN Manager laid the foundation for their subsequent development of Windows NT and Windows Server operating systems. The knowledge and technologies gained from working with 3Com's networking solutions contributed to

2590-485: The directory from its Exchange mail server . While VINES is limited to a three-part name, user.company.org, like Novell's NDS structure, Active Directory is not bound by such a naming convention. Active Directory features an additional capability that both NDS and VINES lack, its "forest and trees" organizational model. The combination of better architecture and with marketing from a company the size of Microsoft doomed StreetTalk, VINES as an OS, and finally Banyan itself. By

2660-459: The directory took the form item @ group @ organization (similar to the naming format used in the XNS Clearinghouse directory service: item : group : organization ). This applied to user accounts as well as to resources like printers and file servers . VINES client software ran on most earlier PC-based operating systems, including MS-DOS and earlier versions of Microsoft Windows . It

2730-437: 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 NetWare 4.11 by including tools and utilities that made it easier to create intranets and link networks to the Internet. Novell bundled tools, such as

2800-439: The evolution of Microsoft's network and server software capabilities, helping them become a dominant force in the networking and server industry. For a decade, Banyan's OS competitors, Novell and Microsoft, dismissed the utility of directory services . Consequently, VINES dominated what came to be called the "directory services" space from 1985 to 1995. While seeming to ignore VINES, Novell and eventually Microsoft—companies with

2870-602: The explosive growth in, for example, printers. As competitors began to adopt some of VINES's outstanding wide area networking protocols and services, manufacturers were less inclined to send a unit to Banyan for VINES specific drivers when competitors allowed them to write their own. Dropping the Banyan brand for ePresence in 1999, as a general Internet services company, the firm sold its services division to Unisys in late 2003 and liquidated its remaining holdings in its Switchboard.com subsidiary. Novell NetWare NetWare

Banyan VINES - Misplaced Pages Continue

2940-458: 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

3010-544: 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. The server could support up to four network cards, and these can be

3080-527: The late 1970s. In 1979, they introduced their first network operating system, called 3+Share. It allowed multiple users to access files and resources on a shared server. However, it wasn't until 1982 that 3Com released 3Server, which was a significant step forward. 3Server was designed to work with 3Com's Ethernet hardware and was aimed at creating local area networks (LANs). It provided file and print sharing capabilities, enabling multiple computers to access common resources like printers and files. It operated on

3150-426: The late 1990s, VINES's once-touted StreetTalk Services's non-flat, non-domain model had lost ground to newer technology, despite its built-in messaging, efficiency and onetime performance edge. Banyan was unable to market its product far beyond its initial base of multi-national and government entities. The company lost ground in the networking market, and VINES sales dropped. Banyan increasingly turned to StreetTalk as

3220-434: The main NetWare product line took a dramatic turn when version 4 introduced NetWare Directory Services (NDS, later renamed eDirectory ), a global directory service based on ISO X.500 concepts (six years later, Microsoft released Active Directory ). The directory service, along with a new e-mail system ( GroupWise ), application configuration suite ( ZENworks ), and security product ( BorderManager ) were all targeted at

3290-458: 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. Novell priced NetWare 4.10 similarly to NetWare 3.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

3360-532: The middle layer level, VINES used fairly standard software. The unreliable datagram service and data-stream service operated essentially identically to UDP and TCP on top of IP . VINES added a reliable message service as well, a hybrid of the two that offered guaranteed delivery of single packets. Banyan offered customers TCP/IP as an extra cost option for owners of standard Vines servers. This extra charge for TCP/IP on VINES servers continued long after TCP/IP server availability had become commoditized. At

3430-496: The needs of large enterprises. 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. The final update release

3500-692: 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 NetWare 4.11 with its Web server, TCP/IP support and

3570-452: The server computer to be used simultaneously as a network file server and as a user workstation. Because all extended memory (RAM above 1 MiB) is allocated to NetWare, DOS is limited to only 640 KiB; 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

SECTION 50

#1732869433151

3640-440: The server was in use and the volume was mounted, allowing a server to be expanded without interruption. In NetWare 386 3. 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

3710-758: 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. With NetWare 3 an improved routing protocol, NetWare Link Services Protocol , has been introduced which scales better than Routing Information Protocol and allows building large networks. Version 4 in 1993 introduced NetWare Directory Services, later re-branded as Novell Directory Services (NDS), based on X.500 , which replaced

3780-465: The server. To broaden the hardware base, particularly to machines using the IBM MCA bus, later versions of NetWare 2. 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 ELS 2.12 II in 1988. NetWare's 3. x range

3850-629: The status of clients to other servers on the internetwork . Rounding out its lower-level system, VINES used RTP (the Routing Table Protocol ), a low-overhead message system for passing around information about changes to the routing, and ARP to determine the address of other nodes on the system. These closely resembled the similar systems used in other XNS-based protocols. VINES also included ICP (the Internet Control Protocol ), which it used to pass error-messages and metrics. At

3920-460: 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 . NetWare 286 2. x normally requires

3990-475: The topmost layer, VINES provided the standard file and print services, as well as the unique StreetTalk , a globally consistent name service . Banyan has a version of StreetTalk that ran natively on an NT server. Using a globally distributed, partially replicated database, StreetTalk could meld multiple widely separated networks into a single network that allowed seamless resource-sharing. It accomplished this through its rigidly hierarchical naming-scheme; entries in

4060-491: The unmodified NetWare 4. 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. Novell continued releasing bugfixes and updates to NetWare for OS/2 up to 1998. Novell's strategy with NetWare 286 2. x and 3. x proved very successful; before

4130-633: The world. VINES also features built-in point-to-point and group chat capability that was useful for basic communication over secure lines. By the late 1980s, the US Marine Corps was searching for simple, off-the-shelf worldwide network connectivity with rich built-in email, file, and print features. By 1988, the Marine Corps had standardized on VINES as both its garrison (base) and forward-deployed ground-based battlefield email-centric network operating system . Using both ground-based secure radio channels and satellite and military tactical phone switches,

4200-445: 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-bit protected mode , eliminating the 16 MiB memory limit of NetWare 286 and therefore allowing larger hard drives to be supported (since NetWare 3. x cached the entire file allocation table and directory entry table into memory for improved performance). NetWare version 3. x

4270-649: 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 NetWare 3. x  – " NetWare File System 386", or NWFS 386, which significantly extended volume capacity (1 TB, 4 GB files), and could handle up to 16 volume segments spanning multiple physical disk drives. Volume segments could be added while

SECTION 60

#1732869433151

4340-567: 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. 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

4410-570: 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. 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. Alongside Hewlett-Packard, IBM collaborated with Novell to offer Portable NetWare and more comprehensive "native" ports of NetWare for its platforms. Portable NetWare

4480-611: Was essentially identical to the lower layers of the Xerox Network Systems (XNS) protocols. Addresses consist of a 32-bit address and a 16-bit subnet that map to the 48-bit Ethernet address to route to machines. This means that, like other XNS-based systems, VINES can only support a two-level internet. A set of routing algorithms , however, set VINES apart from other XNS systems at this level. The key differentiator, ARP ( Address Resolution Protocol ), allowed VINES clients to automatically set up their own network addresses. When

4550-619: 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

4620-439: 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. While NetWare 3. x was current, Novell introduced its first high-availability clustering system, named NetWare SFT-III , which allowed

4690-616: Was lightweight on the client, and hence remained in use during the latter half of the 1990s on many older machines that could not run other networking stacks. This occurred on the server side as well, as VINES generally offered good performance, even from mediocre hardware. With StreetTalk's inherent low bandwidth requirements, global companies and governments that grasped the advantages of worldwide directory services seamlessly spanning multiple time zones recognized VINE's technological edge. Users included gas and oil companies, power companies, public utilities—and U.S. Government agencies including

4760-463: 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. 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

4830-506: Was version 6.5SP8 of May 2009; NetWare is no longer on Novell's product list. 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. The replacement is Open Enterprise Server. 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

4900-454: Was written for the then-new 80286 CPU. The 80286 CPU features a new 16-bit protected mode that provides access to up to 16 MiB 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 1 MiB with not more than 640 KiB of directly addressable RAM.) The combination of

#150849