Novell Embedded Systems Technology

Last updated

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 (and later also TCP/IP). Novell referred to this concept as "Extended Networks", [1] and when the effort was launched they boasted that they wanted to see one billion devices connected to NetWare networks by year 2000. [2] NEST was launched in mid-1994 countering Microsoft's similar Microsoft at Work efforts, [2] which had been launched in 1993.

Contents

Neither technology saw much third-party support, although some of NEST's code was apparently re-used in Novell Distributed Print Services (NDPS), and thus iPrint.

Architecture

NEST consisted primarily of a Novell protocol driver stack implemented in ANSI C. [3] The stack included drivers for then-popular networking hardware, including Ethernet, Token Ring, AppleTalk (actually referring to LocalTalk, a common confusion) and ISDN, as well as higher-level modules for protocols such as Novell's own IPX, and AppleTalk, and later TCP/IP. [3]

The NetWare Services Layer added support for application protocols, notably NetWare client services such as file servers and network time synchronization, and the NEST Requester which acted as a pipe-like endpoint for lightweight communications. [3]

Orthogonal to these services, NEST also included basic implementations of Novell's PSERVER and NPRINTER servers. [3]

Finally, NEST also defined an operating system interface known as POSE (Portable Operating System Extension), which was a thin translation module defining all of the calls NEST needed to support its own functionality, things like memory management and process creation (as POSIX 1003.1, 1003.4, and 1003.4A subsets), which the developer ported to the particular platform of interest. [3] NEST was deliberately written to be able to run from ROM without secondary storage (i.e., it had no long-term state it needed to store). [3]

Whereas the Digital Research-inherited modular real-time multi-user multi-tasking operating system FlexOS was used by Novell as a primary test platform during development, [4] NEST did not include an operating system of its own, and instead was intended to be used on existing platforms and OSs. One such third-party OS to support NEST in 1995 was pSOS+ by Integrated Systems (ISI) [4] a company who had bought FlexOS from Novell for US$3,000,000 in July 1994. [5] The deal comprised a direct payment of half this sum as well as shares representing 2% of the company.

The NEST code was deliberately modular, in order to allow developers to use as much or as little of the overall package as they needed. It was expected that developers would pick and choose the components they needed, for instance, a device reporting status over the network might choose only the NEST Requester, IPX and an Ethernet driver, removing the rest from their assembly. In contrast, Microsoft at Work could be used in a similar fashion, but it seemed that it was generally expected that end users would use the complete system as the basis of their devices in a fashion similar to the later Windows CE.

Impact

Like at Work, however, NEST appears to have seen little real-world use. After the initial release in 1994, there appears to be little news on NEST, followed by another flurry in early 1996 [6] when TCP/IP support was added, at which point Novell claimed there were over 80 companies using NEST, including major office machinery firms like Canon, Hewlett-Packard, Ricoh, and Xerox. [6] However, NEST then went the way of at Work, and was abandoned within Novell in January 1997. [7] [8] [9]

See also

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.

A network operating system (NOS) is a specialized operating system for a network device such as a router, switch or firewall.

pSOS is a real-time operating system (RTOS), created in about 1982 by Alfred Chao, and developed and marketed for the first part of its life by his company Software Components Group (SCG). In the 1980s, pSOS rapidly became the RTOS of choice for all embedded systems based on the Motorola 68000 series family architecture, because it was written in 68000 assembly language and was highly optimised from the start. It was also modularised, with early support for OS-aware debugging, plug-in device drivers, Internet protocol suite (TCP/IP) stacks, language libraries, and disk subsystems. Later came source code level debugging, multiprocessing support, and further computer networking extensions.

<span class="mw-page-title-main">Novell</span> 1980–2014 American multinational software and services company

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.

NetBIOS is an acronym for Network Basic Input/Output System. It provides services related to the session layer of the OSI model allowing applications on separate computers to communicate over a local area network. As strictly an API, NetBIOS is not a networking protocol. Operating systems of the 1980s ran NetBIOS over IEEE 802.2 and IPX/SPX using the NetBIOS Frames (NBF) and NetBIOS over IPX/SPX (NBX) protocols, respectively. In modern networks, NetBIOS normally runs over TCP/IP via the NetBIOS over TCP/IP (NBT) protocol. NetBIOS is also used for identifying system names in TCP/IP (Windows).

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.

NetBIOS Frames (NBF) is a non-routable network- and transport-level data protocol most commonly used as one of the layers of Microsoft Windows networking in the 1990s. NBF or NetBIOS over IEEE 802.2 LLC is used by a number of network operating systems released in the 1990s, such as LAN Manager, LAN Server, Windows for Workgroups, Windows 95 and Windows NT. Other protocols, such as NBT, and NBX (NetBIOS-over-IPX/SPX) also implement the NetBIOS/NetBEUI services over other protocol suites.

<span class="mw-page-title-main">NetWare</span> Computer network operating system

NetWare 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.

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.

<span class="mw-page-title-main">UnixWare</span> Unix operating system

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.

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.

In computer networking, STREAMS is the native framework in Unix System V for implementing character device drivers, network protocols, and inter-process communication. In this framework, a stream is a chain of coroutines that pass messages between a program and a device driver. STREAMS originated in Version 8 Research Unix, as Streams.

NWLink is Microsoft's implementation of Novell's IPX/SPX protocols. NWLink includes an implementation of NetBIOS atop IPX/SPX.

lwIP is a widely used open-source TCP/IP stack designed for embedded systems. lwIP was originally developed by Adam Dunkels at the Swedish Institute of Computer Science and is now developed and maintained by a worldwide network of developers.

A Bluetooth stack is software that is an implementation of the Bluetooth protocol stack.

<span class="mw-page-title-main">Personal NetWare</span>

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.

FlexOS is a discontinued modular real-time multiuser multitasking operating system (RTOS) designed for computer-integrated manufacturing, laboratory, retail and financial markets. Developed by Digital Research's Flexible Automation Business Unit in Monterey, California, in 1985.

Ethernut is an open source hardware and software project for use as an embedded-Ethernet-system.

<span class="mw-page-title-main">DR-WebSpyder</span> Graphical web browser for DOS and Linux

DR-WebSpyder is a DOS web browser, mail client and operating system runtime environment that was developed by Caldera UK in 1997. It was based on the DR-DOS operating system and networking components from Novell as well as the Arachne web browser by Michal Polák of xChaos software. The system was designed to run on low-end desktop systems, but being able to boot and execute from disk as well as from ROM or network, it was also tailored for x86-based thin clients and embedded systems with or without disk drives. Using the web browser as its principal user interface, it could be also used for kiosk systems and set-top boxes. It was ported to Linux in 1999 under the name Embrowser and was renamed Embedix Browser in 2000.

References

  1. ↑ Hindley, Kelly; Raphel, Catherine; King, Melanie (1995-06-15). "Novell Forms New Systems Group To Develop Next Generation Network System Software" (Press release). Orem, UT, USA: Novell, Inc. Archived from the original on 2018-08-18. Retrieved 2018-08-18.
  2. 1 2 Salamone, Salvatore (August 1995). "Novell builds a NEST - Novell Embedded Systems Technology makes NetWare portable and embeddable". BYTE . Archived from the original on 2000-10-02. Retrieved 2006-09-13.
  3. 1 2 3 4 5 6 Hill, Mary (1994-11-01). "NEST Architectural Overview - Articles and Tips". Novell AppNotes. Extended Networks Division: Novell. Archived from the original on 2018-08-18. Retrieved 2018-08-18.
  4. 1 2 "Novell Announces RTOS Vendor Program Which Brings Integrated Networking Solutions to the Embedded Systems Marketplace" (Press Release). Orem, UT, USA: Novell, Inc. 1995-05-23. Archived from the original on 2018-08-18. Retrieved 2018-08-18. "Because Novell used Integrated Systems' FlexOS during the development and testing of NEST, we are in the unique position of supporting it through both our real-time product lines pSOSystem for deeply embedded markets, and FlexOS for point of sale," said Moses Joseph, vice president of marketing for Integrated Systems. "Developers using the FlexOS development kit and the expanded pSOSystem/NEST package for everything from home security and entertainment to office automation and global communications applications, now have quick and easy access to the widest variety of standard networking protocols.
  5. ↑ "pSOSystem and the NEST Development Environment - Designing Embedded Applications with NetWare Connectivity" (White paper). Integrated Systems, Inc. (ISI). 1998. Archived from the original on 1998-02-19.
  6. 1 2 Bell, Mark, ed. (1996-02-27). "Novell's NEST comes to the Internet". NETstuff / Newsbytes News Network. Archived from the original on 2000-10-15. Retrieved 2006-09-13.
  7. 1 2 Adams, Brooke (1997-01-22). "Novell Integrating Parts of NEST With Company's Other Divisions". Deseret News . Deseret News Publishing Company. Archived from the original on 2018-08-19. Retrieved 2018-08-19.
  8. ↑ Woollacott, Matthew (1997-02-03). "Empty NEST: Novell dumps universal operating system plan". InfoWorld . Vol. 19, no. 5. InfoWorld Publishing Co. p. 6. ISSN   0199-6649. Archived from the original on 2020-02-09. Retrieved 2018-08-19.
  9. ↑ Magee, Mike (1997). "Novell abandons Nest and prompts Sun to join embedded systems group (440)". Incisive Business Media Limited. Archived from the original on 2018-08-19. Retrieved 2018-08-19.
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.