Misplaced Pages

#730269

94-648: The NBF protocol is broadly, but incorrectly, referred to as NetBEUI . This originates from the confusion with NetBIOS Extended User Interface, an extension to the NetBIOS API that was originally developed in conjunction with the NBF protocol; both the protocol and the NetBEUI emulator were originally developed to allow NetBIOS programs to run over IBM 's new Token Ring network. Microsoft caused this confusion by labelling its NBF protocol implementation NetBEUI . NBF

188-483: A local area network (LAN). The API was created in 1983 by Sytek Inc . for software communication over IBM PC Network LAN technology. On IBM PC Network , as an API alone, NetBIOS relied on proprietary Sytek networking protocols for communication over the wire. In 1985, IBM went forward with the Token Ring network scheme and produced an emulator of Sytek's NetBIOS API to allow NetBIOS-aware applications from

282-547: A virtual DOS machine (VDM). Originally, a nearly complete version of Windows code was included with OS/2 itself: Windows 3.0 in OS/2 2.0, and Windows 3.1 in OS/2 2.1. Later, IBM developed versions of OS/2 that would use whatever Windows version the user had installed previously, patching it on the fly, and sparing the cost of an additional Windows license. It could either run full-screen, using its own set of video drivers, or "seamlessly," where Windows programs would appear directly on

376-535: A "Session End" request. NBF protocol – apart from DOS, OS/2 and Unix implementations – was officially supported by Microsoft on almost every version of Windows up to Windows 2000 , but its use has decreased quickly since the development of NBT . Microsoft officially dropped support starting with Windows XP , but it is included on the Windows XP CD-ROM and can be installed manually. Windows Vista does not include NetBEUI (means NBF) support at all, but

470-488: A DNS server. (It is also possible to operate many TCP/IP-based applications, including the three listed above, using only IP addresses, but this is not the norm.) Under Windows, the node type of a networked computer relates to the way it resolves NetBIOS names to IP addresses . This assumes that there are any IP addresses for the NetBIOS nodes, which is assured only when NetBIOS operates over NBT; thus, node types are not

564-599: A LAN. This limitation was generally overcome industry-wide through the transition from NBF to NBT, under which, for example, Microsoft was able to switch to Domain Name System (DNS) for resolution of NetBIOS hostnames , having formerly used the LAN segment-compartmentalized NBF protocol itself to resolve such names in Windows client-server networks . NetBIOS provides three distinct services: (Note: SMB , an upper layer,

658-435: A NetBIOS/NetBEUI packet might have to be transmitted as a sequence of "Data First Middle" packets and a "Data Only Last" packet; packets that do not need to be segmented in that fashion will be sent as a single "Data Only Last" packet. An acknowledgment will be sent for all "Data Only Last" packets that are successfully received; this will also acknowledge all preceding "Data First Middle" packets. Sessions are closed by sending

752-422: A Windows installation. As most computers were sold with Microsoft Windows pre-installed and the price was less, "Red Spine" was the more popular product. OS/2 Warp Connect—which has full LAN client support built-in—followed in mid-1995. Warp Connect was nicknamed "Grape". In OS/2 2.0, most performance-sensitive subsystems, including the graphics (Gre) and multimedia (MMPM/2) systems, were updated to 32-bit code in

846-452: A basic office application suite known as IBM Works . It was released in two versions: the less expensive "Red Spine" and the more expensive "Blue Spine" (named for the color of their boxes). "Red Spine" was designed to support Microsoft Windows applications by utilizing any existing installation of Windows on the computer's hard drive. "Blue Spine" includes Windows support in its own installation, and so can support Windows applications without

940-402: A complete product, nor was it ready to communicate on the network in the form it was distributed. It lacked any implementation of OSI Layers 1 to 4 ( Physical , Data link , Network and Transport Layers) and an OEM was expected to provide these implementations (in the form of a NetBIOS part) to make its version of MS-Net a complete and ready to use product. MS-Net accessed the network through

1034-630: A fixpack, and included as part of OS/2 2.1. Warp 3 brought about a fully 32-bit windowing system, while Warp 4 introduced the object-oriented 32-bit GRADD display driver model. In 1991, IBM started development on an intended replacement for OS/2 called Workplace OS . This was an entirely new product, brand new code, that borrowed only a few sections of code from both the existing OS/2 and AIX products. It used an entirely new microkernel code base, intended (eventually) to host several of IBM's operating systems (including OS/2) as microkernel "personalities". It also included major new architectural features including

SECTION 10

#1732780640731

1128-467: A full version of Warp 4 that required no activation and was essentially a free release. Special versions of OS/2 2.11 and Warp 4 also included symmetric multiprocessing (SMP) support. OS/2 sales were largely concentrated in networked computing used by corporate professionals; however, by the early 1990s, it was overtaken by Microsoft Windows NT. While OS/2 was arguably technically superior to Microsoft Windows 95 , OS/2 failed to develop much penetration in

1222-650: A hardware watchdog on selected machines (notably IBM machines) to break out of such a deadlock. Later, release 3.0 leveraged the enhancements of newer Intel 80486 and Intel Pentium processors—the Virtual Interrupt Flag (VIF), which was part of the Virtual Mode Extensions (VME)—to solve this problem. OS/2 2.1 was released in 1993. This version of OS/2 achieved compatibility with Windows 3.0 (and later Windows 3.1) by adapting Windows user-mode code components to run inside

1316-544: A property of NetBIOS per se but of interaction between NetBIOS and TCP/IP in the Windows OS environment. There are four node types. The node type in use is displayed by opening a command line and typing ipconfig /all . A Windows computer registry may also be configured in such a way as to display "unknown" for the node type. The NetBIOS Suffix, alternately called the NetBIOS End Character (endchar),

1410-499: A result of the dispute, IBM signed the license agreement 15 minutes before Microsoft's Windows 95 launch event, which was later than their competitors and this badly hurt sales of IBM PCs. IBM officials later conceded that OS/2 would not have been a viable operating system to keep them in the PC business. A project was launched internally by IBM to evaluate the looming competitive situation with Microsoft Windows 95. Primary concerns included

1504-477: A sequence of alphanumeric characters. The following characters are explicitly not permitted: \/:*?"<>| . Since Windows 2000, NetBIOS names also had to comply with restrictions on DNS names: they cannot consist entirely of digits, and the hyphen ("-") or full-stop (".") characters may not appear as the first or last character. Since Windows 2000, Microsoft has advised against including any full-stop (".") characters in NetBIOS names, such that applications can use

1598-509: A shared Windows session while isolating other applications in one or more separate Windows sessions. At the cost of additional hardware resources, this approach can protect each program in any given Windows session (and each instance of Windows itself) from every other program running in any separate Windows session (though not from other programs running in the same Windows session). Whether Windows applications are running in full-screen or windowed mode, and in one Windows session or several, it

1692-543: A single Windows session – multitasking cooperatively and without memory protection – just as they would under native Windows 3.x. However, to achieve true isolation between Windows 3.x programs, OS/2 can also run multiple copies of Windows in parallel, with each copy residing in a separate VDM. The user can then optionally place each program either in its own Windows session – with preemptive multitasking and full memory protection between sessions, though not within them – or allow some applications to run together cooperatively in

1786-442: A system registry, JFS, support for UNIX graphics libraries, and a new driver model. Workplace OS was developed solely for POWER platforms , and IBM intended to market a full line of PowerPCs in an effort to take over the market from Intel . A mission was formed to create prototypes of these machines and they were disclosed to several corporate customers, all of whom raised issues with the idea of dropping Intel. Advanced plans for

1880-809: A time, and did this in a way that allowed the DOS program to have total control over the computer. A problem in DOS mode could crash the entire computer. In contrast, OS/2 2.0 could leverage the virtual 8086 mode of the Intel 80386 processor to create a much safer virtual machine in which to run DOS programs. This included an extensive set of configuration options to optimize the performance and capabilities given to each DOS program. Any real-mode operating system (such as 8086 Xenix ) could also be made to run using OS/2's virtual machine capabilities, subject to certain direct hardware access limitations. Like most 32-bit environments, OS/2 could not run protected-mode DOS programs using

1974-417: Is 16 ASCII characters, however Microsoft limits the host name to 15 characters and reserves the 16th character as a NetBIOS Suffix. This suffix describes the service or name record type such as host record, master browser record, or domain controller record or other services. The host name (or short host name) is specified when Windows networking is installed/configured, the suffixes registered are determined by

SECTION 20

#1732780640731

2068-592: Is 4.52, which was released for both desktop and server systems in December 2001. IBM is still delivering defect support for a fee. IBM urges customers to migrate their often highly complex applications to e-business technologies such as Java in a platform-neutral manner. Once application migration is completed, IBM recommends migration to a different operating system, suggesting Linux as an alternative. After IBM discontinued development of OS/2, various third parties approached IBM to take over future development of

2162-541: Is a proprietary computer operating system for x86 and PowerPC based personal computers . It was initially created and developed jointly by IBM and Microsoft , under the leadership of IBM software designer Ed Iacobucci , intended as a replacement for DOS . The first version was released in 1987; a feud between the two companies beginning in 1990 resulted in Microsoft leaving development exclusively to IBM, who continued development on their own. OS/2 Warp 4 in 1996

2256-482: Is a protocol and the original NetBEUI was a NetBIOS application programming interface extension. NBF protocol uses 802.2 type 1 mode to provide the NetBIOS/NetBEUI name service and datagram service, and 802.2 type 2 mode to provide the NetBIOS/NetBEUI session service ( virtual circuit ). NBF protocol makes wide use of broadcast messages, which accounts for its reputation as a chatty interface. While

2350-588: Is a service that runs on top of the Session Service and the Datagram service, and is not to be confused as a necessary and integral part of NetBIOS itself. It can now run atop TCP with a small adaptation layer that adds a length field to each SMB message; this is necessary because TCP only provides a byte-stream service with no notion of message boundaries.) In order to start sessions or distribute datagrams, an application must register its NetBIOS name using

2444-549: Is answered by either a positive-acknowledgment (ACK) or negative-acknowledgment (NAK) response. A NAK will prompt retransmission of the data. Sessions are closed by the non-initiating computer by sending a close request. The computer that started the session will reply with a close response which prompts the final session closed packet. When NetBIOS is run in conjunction with Internet protocols (e.g., NBT), each computer may have multiple names: one or more NetBIOS name service names and one or more Internet host names. The NetBIOS name

2538-621: Is available," and to "allow NetBIOS interoperation in the Internet." After the PS/2 computer hit the market in 1987, IBM released the PC LAN Support Program, which included a driver offering the NetBIOS API. There is some confusion between the names NetBIOS and NetBEUI. NetBEUI originated strictly as the moniker for IBM's enhanced 1985 NetBIOS emulator for Token Ring. The name NetBEUI should have died there, considering that at

2632-409: Is being sent to all NetBIOS/NetBEUI names on the network. Session mode lets two computers establish a connection for a "conversation," allows larger messages to be handled, and provides error detection and recovery. Sessions are established by exchanging packets. The computer establishing the session sends a "Name Query" request, specifying that a session should be initialized. The computer with which

2726-481: Is possible to use DDE between OS/2 and Windows applications, and OLE between Windows applications only. IBM's OS/2 for Windows product (codename Ferengi), also known as "OS/2, Special Edition", was interpreted as a deliberate strategy "of cashing in on the pervasive success of the Microsoft platform" but risked confusing consumers with the notion that the product was a mere accessory or utility running on Windows such as Norton Desktop for Windows when, in fact, it

2820-534: Is similar in functionality to a non-networked version of X11 or the Windows GDI . On top of this lies the Workplace Shell (WPS) introduced in OS/2 2.0. WPS is an object-oriented shell allowing the user to perform traditional computing tasks such as accessing files, printers, launching legacy programs, and advanced object oriented tasks using built-in and third-party application objects that extended

2914-399: Is starting the session will then send a "Session Initialize" request which will prompt a "Session Confirm" response. Data is transmitted during an established session by data packets. IEEE 802.2 handles flow control and retransmission of data packets. Because NetBIOS/NetBEUI allows packets to be sent that are larger than the largest packet that could be transmitted on a particular MAC layer ,

NetBIOS Frames - Misplaced Pages Continue

3008-407: Is the 16th character of a NetBIOS name and indicates service type for the registered name. The number of record types is limited to 255; some commonly used values are: For unique names: For group names: The following table shows a brief history of NetBIOS and its related protocols. SMB was the main protocol that used NetBIOS. SMB enables Windows File and Printer Sharing. OS/2 OS/2

3102-767: Is unroutable it can only be used to communicate with devices in the same broadcast domain , but being bridgeable it can also be used to communicate with network segments connected to each other via bridges . The lack of support for routable networks means that NBF is only well-suited for small to medium-sized networks , where it has such an advantage over TCP/IP that requires little configuration. The NetBIOS/NetBEUI services must be implemented atop other protocols, such as IPX and TCP/IP (see above) in order to be of use in an internetwork. NetBIOS/NetBEUI provides three distinct services: NBF protocol implements all of these services. In order to start sessions or distribute datagrams, an application must register its NetBIOS/NetBEUI name using

3196-636: The BIOS or access hardware directly. Other development tools included a subset of the video and keyboard APIs as linkable libraries so that family mode programs are able to run under MS-DOS, and, in the OS/2 Extended Edition v1.0, a database engine called Database Manager or DBM (this was related to DB2 , and should not be confused with the DBM family of database engines for Unix and Unix-like operating systems). A task-switcher named Program Selector

3290-504: The HPFS filesystem . HPFS provided a number of improvements over the older FAT file system, including long filenames and a form of alternate data streams called Extended Attributes . In addition, extended attributes were also added to the FAT file system. The Extended Edition of 1.2 introduced TCP/IP and Ethernet support. OS/2- and Windows-related books of the late 1980s acknowledged

3384-554: The HPFS filesystem , text mode OS/2 1.x applications, and OS/2 LAN Manager network support. Some early NT materials even included OS/2 copyright notices embedded in the software. One example of NT OS/2 1.x support is in the WIN2K resource kit. Windows NT could also support OS/2 1.x Presentation Manager and AVIO applications with the addition of the Windows NT Add-On Subsystem for Presentation Manager. OS/2 2.0

3478-557: The IEEE 802.2 Logical Link Control layer. In 1985, Microsoft created its own implementation of the NetBIOS API for its MS-Net networking technology. As in the case of IBM's Token Ring, the services of Microsoft's NetBIOS implementation were provided over the IEEE 802.2 Logical Link Control layer by the NBF protocol. However, the MS-Net was only delivered to OEMs , and it was actually not

3572-538: The Intel 80286 processor and DOS fundamentally does not. IBM insisted on supporting the 80286 processor, with its 16-bit segmented memory mode, because of commitments made to customers who had purchased many 80286-based PS/2s as a result of IBM's promises surrounding OS/2. Until release 2.0 in April 1992, OS/2 ran in 16-bit protected mode and therefore could not benefit from the Intel 80386 's much simpler 32-bit flat memory model and virtual 8086 mode features. This

3666-500: The MAC address of the host with a given NetBIOS/NetBEUI name; this is done by sending a "Name Query" packet, the response to which will have the MAC address of the host sending the response, i.e. the host with that name. Datagram mode is " connectionless ". A datagram is sent with a "Datagram" packet if it is being sent to a particular NetBIOS/NetBEUI name, or a "Datagram Broadcast" packet if it

3760-531: The "Joint Development Agreement" in August 1985. It was code-named "CP/DOS" and it took two years for the first product to be delivered. OS/2 1.0 was announced in April 1987 and released in December. The original release only ran in text mode , and a GUI was introduced with OS/2 1.1 about a year later. OS/2 features an API for controlling the video display (VIO) and handling keyboard and mouse events so that programmers writing for protected mode need not call

3854-640: The 1980s (DOS and Novell Netware primarily) 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). NetBIOS is an operating system-level API that allows applications on computers to communicate with one another over

NetBIOS Frames - Misplaced Pages Continue

3948-494: The Intel 80286 processor. Notably, basic system calls were modeled after MS-DOS calls; their names even started with "Dos" and it was possible to create "Family Mode" applications – text mode applications that could work on both systems. Because of this heritage, OS/2 shares similarities with Unix , Xenix , and Windows NT . OS/2 sales were largely concentrated in networked computing used by corporate professionals. OS/2 2.0

4042-475: The Microsoft's own variant of NetBIOS, which was split into two parts - the lower level part that OEMs had to provide implemented the NetBIOS calls that depended on layers 1-4, while the higher level part, provided by Microsoft, was hardware- and protocol-independent. This NetBIOS implementation supported the full NetBIOS API, but was called by invoking x86 interrupt 0x2A, instead of IBM's standard interrupt 0x5C. The reliance on OEMs to implement parts of NetBIOS had

4136-404: The NetBIOS name resolution protocol. Datagram mode is connectionless ; the application is responsible for error detection and recovery. In NBT , the datagram service runs on UDP port 138. The datagram service primitives offered by NetBIOS are: Session mode lets two computers establish a connection, allows messages to span multiple packets, and provides error detection and recovery. In NBT ,

4230-454: The OS/2 desktop. The process containing Windows was given fairly extensive access to hardware, especially video, and the result was that switching between a full-screen WinOS/2 session and the Workplace Shell could occasionally cause issues. Because OS/2 only runs the user-mode system components of Windows, it is incompatible with Windows device drivers ( VxDs ) and applications that require them. Multiple Windows applications run by default in

4324-503: The OS/2 team, as Cutler did not think much of the OS/2 technology and wanted to build on his work on the MICA project at Digital rather than creating a "DOS plus". His NT OS/2 was a completely new architecture. IBM grew concerned about the delays in development of OS/2 2.0. Initially, the companies agreed that IBM would take over maintenance of OS/2 1.0 and development of OS/2 2.0, while Microsoft would continue development of OS/2 3.0. In

4418-510: The PC-Network era to work over IBM's new Token Ring hardware. This IBM emulator, named NetBIOS Extended User Interface (NetBEUI), expanded the base NetBIOS API created by Sytek with, among other things, the ability to deal with the greater node capacity of Token Ring. A new networking protocol, NBF , was simultaneously produced by IBM to allow its NetBEUI API (their enhanced NetBIOS API) to provide its services over Token Ring – specifically, at

4512-584: The System Properties dialog box. There may also be connection-specific suffixes which can be viewed or changed on the DNS tab in Control Panel → Network → TCP/IP → Advanced Properties. Host names are used by applications such as telnet , ftp , web browsers , etc. To connect to a computer running the TCP/IP protocol using its name, the host name must be resolved into an IP address , typically by

4606-546: The Windows XP NetBEUI support drivers can be used. NetBIOS#NetBEUI NetBIOS ( / ˈ n ɛ t b aɪ ɒ s / ) 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

4700-670: The board in the Personal Systems Division as well as across IBM as a whole. This resulted in a decision being made at a level above the Division to cut over 95% of the overall budget for the entire product line, end all new development (including Workplace OS), eliminate the Boca Raton development lab, end all sales and marketing efforts of the product, and lay off over 1,300 development individuals (as well as sales and support personnel). $ 990 million had been spent in

4794-512: The case). Generally a computer running Internet protocols (whether it is a Windows machine or not) usually has a host name (also sometimes called a machine name). Originally these names were stored in and provided by a hosts file but today most such names are part of the hierarchical Domain Name System (DNS). Generally the host name of a Windows computer is based on the NetBIOS name plus the Primary DNS Suffix, which are both set in

SECTION 50

#1732780640731

4888-725: The consumer and stand-alone desktop PC segments; there were reports that it could not be installed properly on IBM's own Aptiva series of home PCs. Microsoft made an offer in 1994 where IBM would receive the same terms as Compaq (the largest PC manufacturer at the time) for a license of Windows 95, if IBM ended development of OS/2 completely. IBM refused and instead went with an "IBM First" strategy of promoting OS/2 Warp and disparaging Windows, as IBM aimed to drive sales of its own software as well as hardware. By 1995, Windows 95 negotiations between IBM and Microsoft, which were already difficult, stalled when IBM purchased Lotus SmartSuite , which would have directly competed with Microsoft Office . As

4982-545: The end, Microsoft decided to recast NT OS/2 3.0 as Windows NT, leaving all future OS/2 development to IBM. From a business perspective, it was logical to concentrate on a consumer line of operating systems based on DOS and Windows, and to prepare a new high-end system in such a way as to keep good compatibility with existing Windows applications. While it waited for this new high-end system to develop, Microsoft would still receive licensing money from Xenix and OS/2 sales. Windows NT's OS/2 heritage can be seen in its initial support for

5076-412: The existence of both systems and promoted OS/2 as the system of the future. The collaboration between IBM and Microsoft unravelled in 1990, between the releases of Windows 3.0 and OS/2 1.3. During this time, Windows 3.0 became a tremendous success, selling millions of copies in its first year. Much of its success was because Windows 3.0 (along with MS-DOS) was bundled with most new computers. OS/2, on

5170-427: The first version of their OS/2-based operating system in 2017 as ArcaOS. As of 2023, there have been multiple releases of ArcaOS, and it remains under active development. Many people hoped that IBM would release OS/2 or a significant part of it as open source . Petitions were held in 2005 and 2007, but IBM refused them, citing legal and technical reasons. It is unlikely that the entire OS will be open at any point in

5264-401: The fully-licensed MS-DOS 5.0, which had been patched and improved upon. For the first time, OS/2 was able to run more than one DOS application at a time. This was so effective that it allowed OS/2 to run a modified copy of Windows 3.0, itself a DOS extender , including Windows 3.0 applications. Because of the limitations of the Intel 80286 processor, OS/2 1.x could run only one DOS program at

5358-538: The future because it contains third-party code to which IBM does not have copyright, and much of this code is from Microsoft. IBM also once engaged in a technology transfer with Commodore , licensing Amiga technology for OS/2 2.0 and above, in exchange for the REXX scripting language. This means that OS/2 may have some code that was not written by IBM, which can therefore prevent the OS from being re-announced as open-sourced in

5452-550: The future. On the other hand, IBM donated Object REXX for Windows and OS/2 to the Open Object REXX project maintained by the REXX Language Association on SourceForge . There was a petition, arranged by OS2World, to open parts of the OS. Open source operating systems such as Linux have already profited from OS/2 indirectly through IBM's release of the improved JFS file system , which

5546-509: The individual services supplied by the host. In order to connect to a computer running TCP/IP via its NetBIOS name, the name must be resolved to a network address . Today this is usually an IP address (the NetBIOS name to IP address resolution is often done by either broadcasts or a WINS Server – NetBIOS Name Server). A computer's NetBIOS name is often the same as that computer's host name (see below), although truncated to 15 characters, but it may also be completely different. NetBIOS names are

5640-560: The last full year. Warp 4 became the last distributed version of OS/2. Although a small and dedicated community remains faithful to OS/2, OS/2 failed to catch on in the mass market and is little used outside certain niches where IBM traditionally had a stronghold. For example, many bank installations, especially automated teller machines , run OS/2 with a customized user interface; French SNCF national railways used OS/2 1.x in thousands of ticket selling machines. Telecom companies such as Nortel used OS/2 in some voicemail systems. Also, OS/2

5734-483: The major code quality issues in the existing OS/2 product (resulting in over 20 service packs, each requiring more diskettes than the original installation), and the ineffective and heavily matrixed development organization in Boca Raton (where the consultants reported that "basically, everybody reports to everybody") and Austin. That study, tightly classified as "Registered Confidential" and printed only in numbered copies, identified untenable weaknesses and failures across

SECTION 60

#1732780640731

5828-608: The marketplace, partly due to strategic business measures imposed by Microsoft in the industry that have been considered anti-competitive . Following the failure of IBM's Workplace OS project, OS/2 Warp 4 became the final major release in 1996; IBM discontinued its support for OS/2 on December 31, 2006. Since then, OS/2 has been developed, supported and sold by two different third-party vendors under license from IBM – first by Serenity Systems as eComStation from 2001 to 2011, and later by Arca Noae LLC as ArcaOS since 2017. The development of OS/2 began when IBM and Microsoft signed

5922-405: The name NetBIOS commonly used only in reference to file and printer sharing over TCP/IP . More accurately, the former is NetBIOS Frames (NBF), and the latter is NetBIOS over TCP/IP (NBT). Since its original publication in a technical reference book from IBM, the NetBIOS API specification has become a de facto standard in the industry despite originally supporting a maximum of only 80 PCs in

6016-555: The name service. NetBIOS names are 16 octets in length and vary based on the particular implementation. Frequently, the 16th octet, called the NetBIOS Suffix, designates the type of resource, and can be used to tell other applications what type of services the system offers. In NBT , the name service operates on UDP port 137 (TCP port 137 can also be used, but rarely is). The name service primitives offered by NetBIOS are: Internet Protocol Version 6 (IPv6) are not supported by

6110-413: The name service. To do so, an "Add Name Query" or "Add Group Name Query" packet is broadcast on the network. If the NetBIOS/NetBEUI name is already in use, the name service, running on the host that owns the name, broadcasts a "Node Conflict" message on the network. In addition, to start a session or to send a datagram to a particular host rather than to broadcast the datagram, NBF protocol has to determine

6204-481: The new code base would eventually include replacement of the OS/400 operating system by Workplace OS, as well as a microkernel product that would have been used in industries such as telecommunications and set-top television receivers. A partially functional pre-alpha version of Workplace OS was demonstrated at Comdex, where a bemused Bill Gates stopped by the booth. The second and last time it would be shown in public

6298-506: The number of OS/2 users, in the belief that this would increase sales and demand for third-party applications, and thus strengthen OS/2's desktop numbers. This suggestion was bolstered by the fact that this demo version had replaced another which was not so easily cracked, but which had been released with trial versions of various applications. In 2000, the July edition of Australian Personal Computer magazine bundled software CD-ROMs, included

6392-474: The older VCPI interface, unlike the Standard mode of Windows 3.1; it only supported programs written according to DPMI . (Microsoft discouraged the use of VCPI under Windows 3.1, however, due to performance degradation.) Unlike Windows NT, OS/2 always allowed DOS programs the possibility of masking real hardware interrupts, so any DOS program could deadlock the machine in this way. OS/2 could, however, use

6486-509: The open hardware system approach that contributed to its success on the PC. IBM sought to use OS/2 to drive sales of its own hardware, and urged Microsoft to drop features, such as fonts , that IBM's hardware did not support. Microsoft programmers also became frustrated with IBM's bureaucracy and its use of lines of code to measure programmer productivity . IBM developers complained about the terseness and lack of comments in Microsoft's code, while Microsoft developers complained that IBM's code

6580-421: The operating system installation. A personal version of Lotus Notes was also included, with a number of template databases for contact management, brainstorming, and so forth. The UK-distributed free demo CD-ROM of OS/2 Warp essentially contained the entire OS and was easily, even accidentally, cracked , meaning that even people who liked it did not have to buy it. This was seen as a backdoor tactic to increase

6674-456: The operating system. The OS/2 software vendor Stardock made such a proposal to IBM in 1999, but it was not followed through by the company. Serenity Systems succeeded in negotiating an agreement with IBM, and began reselling OS/2 as eComStation in 2001. eComStation is now sold by XEU.com, the most recent version (2.1) was released in 2011. In 2015, Arca Noae, LLC announced that they had secured an agreement with IBM to resell OS/2. They released

6768-597: The other hand, was available only as an additional stand-alone software package. In addition, OS/2 lacked device drivers for many common devices such as printers, particularly non-IBM hardware. Windows, on the other hand, supported a much larger variety of hardware. The increasing popularity of Windows prompted Microsoft to shift its development focus from cooperating on OS/2 with IBM to building its own business based on Windows. Several technical and practical reasons contributed to this breakup. The two companies had significant differences in culture and vision. Microsoft favored

6862-430: The presence of a full-stop to distinguish domain names from NetBIOS names. The Windows LMHOSTS file provides a NetBIOS name resolution method that can be used for small networks that do not use a WINS server. A Windows machine's NetBIOS name is not to be confused with the computer's Internet host name (assuming that the computer is also an Internet host in addition to being a NetBIOS node, which need not necessarily be

6956-525: The previous GUI. Rather than merely providing an environment for program windows (such as the Program Manager), the Workplace Shell provided an environment in which the user could manage programs, files and devices by manipulating objects on the screen. With the Workplace Shell, everything in the system is an "object" to be manipulated. OS/2 2.0 was touted by IBM as "a better DOS than DOS and a better Windows than Windows". It managed this by including

7050-481: The protocol consumes few network resources in a very small network, broadcasts begin to adversely impact performance and speed when the number of hosts present in a network grows. Sytek developed NetBIOS for IBM for the PC-Network program and was used by Microsoft for MS-NET in 1985. In 1987, Microsoft and Novell utilized it for their network operating systems LAN Manager and NetWare . Because NBF protocol

7144-598: The release: IBM claimed that it had used Star Trek terms as internal names for prior OS/2 releases, and that this one seemed appropriate for external use as well. At the launch of OS/2 Warp in 1994, Patrick Stewart was to be the Master of Ceremonies ; however Kate Mulgrew of the then-upcoming series Star Trek: Voyager substituted for him at the last minute. OS/2 Warp offers a host of benefits over OS/2 2.1, notably broader hardware support, greater multimedia capabilities, Internet -compatible networking, and it includes

7238-452: The session is to be established will respond with a "Name Recognized" response indicating either that no session can be established (either because that computer is not listening for sessions being established to that name or because no resources are available to establish a session to that name) or that a session can be established (in which case the response will include a local session number to be used in subsequent packets). The computer that

7332-493: The session service runs on TCP port 139. The session service primitives offered by NetBIOS are: In the original protocol used to implement NetBIOS services on PC-Network, to establish a session, the initiating computer sends an Open request which is answered by an Open acknowledgment. The computer that started the session will then send a Session Request packet which will prompt either a Session Accept or Session Reject packet. During an established session, each transmitted packet

7426-548: The shell in an integrated fashion not available on any other mainstream operating system. WPS follows IBM's Common User Access user interface standards. WPS represents objects such as disks, folders, files, program objects, and printers using the System Object Model (SOM), which allows code to be shared among applications, possibly written in different programming languages. A distributed version called DSOM allowed objects on different computers to communicate. DSOM

7520-583: The time, the NetBIOS implementations by other companies were known simply as NetBIOS regardless of whether they incorporated the API extensions found in Token Ring's emulator. For MS-Net, however, Microsoft elected to name its implementation of the NBF protocol "NetBEUI" – naming its implementation of the transport protocol after IBM's enhanced version of the API. Consequently Microsoft file and printer sharing over Ethernet often continues to be called NetBEUI, with

7614-574: The unfortunate side effect that different OEM versions of MS-Net and NetBIOS generally weren't able to communicate with one another. In 1986, Novell released Advanced Novell NetWare 2.0 featuring the company's own emulation of the NetBIOS API. Its services were encapsulated within NetWare's IPX/SPX protocol using the NetBIOS over IPX/SPX (NBX) protocol. In 1987, a method of encapsulating NetBIOS in TCP and UDP packets, NetBIOS over TCP/IP (NBT),

7708-662: Was bloated . The two products have significant differences in API. OS/2 was announced when Windows 2.0 was near completion, and the Windows API already defined. However, IBM requested that this API be significantly changed for OS/2. Therefore, issues surrounding application compatibility appeared immediately. OS/2 designers hoped for source code conversion tools, allowing complete migration of Windows application source code to OS/2 at some point. However, OS/2 1.x did not gain enough momentum to allow vendors to avoid developing for both OS/2 and Windows in parallel. OS/2 1.x targets

7802-545: Was "a complete, modern, multi-tasking, pre-emptive operating system", itself hosting Windows instead of running on it. Available on CD-ROM or 18 floppy disks, the product documentation reportedly suggested Windows as a prerequisite for installing the product, also being confined to its original FAT partition, whereas the product apparently supported the later installation of Windows running from an HPFS partition, particularly beneficial for users of larger hard drives. Windows compatibility, relying on patching specific memory locations,

7896-545: Was at an OS/2 user group in Phoenix, Arizona ; the pre-alpha code refused to boot. It was released in 1995. But with $ 990 million being spent per year on development of this as well as Workplace OS, and no possible profit or widespread adoption, the end of the entire Workplace OS and OS/2 product line was near. In 1996, Warp 4 added Java and speech recognition software. IBM also released server editions of Warp 3 and Warp 4 which bundled IBM's LAN Server product directly into

7990-463: Was available through the Ctrl-Esc hotkey combination, allowing the user to select among multitasked text-mode sessions (or screen groups; each can run multiple programs). Communications and database-oriented extensions were delivered in 1988, as part of OS/2 1.0 Extended Edition: SNA , X.25 / APPC /LU 6.2, LAN Manager , Query Manager , SQL. The promised user interface, Presentation Manager ,

8084-518: Was especially painful in providing support for DOS applications. While, in 1988, Windows/386 2.1 could run several cooperatively multitasked DOS applications, including expanded memory (EMS) emulation, OS/2 1.3, released in 1991, was still limited to one 640 kB "DOS box". Given these issues, Microsoft started to work in parallel on a version of Windows which was more future-oriented and more portable. The hiring of Dave Cutler , former VAX/VMS architect, in 1988 created an immediate competition with

8178-605: Was introduced with OS/2 1.1 in October 1988. It had a similar user interface to Windows 2.1 , which was released in May of that year. (The interface was replaced in versions 1.2 and 1.3 by a look closer in appearance to Windows 3.0 .) The Extended Edition of 1.1, sold only through IBM sales channels, introduced distributed database support to IBM database systems and SNA communications support to IBM mainframe networks. In 1989, Version 1.2 introduced Installable Filesystems and, notably,

8272-642: Was ported from the OS/2 code base. As IBM didn't release the source of the OS/2 JFS driver, developers ported the Linux driver back to eComStation and added the functionality to boot from a JFS partition. This new JFS driver has been integrated into eComStation v2.0, and later into ArcaOS 5.0. Release dates refer to the US English editions unless otherwise noted. The graphic system has a layer named Presentation Manager that manages windows, fonts, and icons. This

8366-457: Was published. It was described in RFC 1001 ("Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods") and RFC 1002 ("Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications"). The NBT protocol was developed in order to "allow an implementation [of NetBIOS applications] to be built on virtually any type of system where the TCP/IP protocol suite

8460-401: Was released in 1992 as the first 32-bit version as well as the first to be entirely developed by IBM, after Microsoft severed ties over a dispute over how to position OS/2 relative to Microsoft's new Windows 3.1 operating environment. With OS/2 Warp 3 in 1994, IBM attempted to also target home consumers through a multi-million dollar advertising campaign. However it continued to struggle in

8554-474: Was released in April 1992. At the time, the suggested retail price was US$ 195 , while Windows retailed for $ 150 . OS/2 2.0 provided a 32-bit API for native programs, though the OS itself still contained some 16-bit code and drivers. It also included a new OOUI (object-oriented user interface) called the Workplace Shell . This was a fully object-oriented interface that was a significant departure from

8648-400: Was reportedly broken by the release of Windows 3.11, prompting accusations of arbitrary changes to Windows in order to perpetrate "a deliberate act of Microsoft sabotage" against IBM's product. Released in 1994, OS/2 version 3.0 was labelled as OS/2 Warp to highlight the new performance benefits, and generally to freshen the product image. "Warp" had originally been the internal IBM name for

8742-444: Was the last major upgrade, after which IBM slowly halted the product as it failed to compete against Microsoft's Windows ; updated versions of OS/2 were released by IBM until 2001. The name stands for "Operating System/2", because it was introduced as part of the same generation change release as IBM's " Personal System/2 (PS/2)" line of second-generation PCs. OS/2 was intended as a protected-mode successor of PC DOS targeting

8836-549: Was used for the host PC used to control the Satellite Operations Support System equipment installed at NPR member stations from 1994 to 2007, and used to receive the network's programming via satellite. Although IBM began indicating shortly after the release of Warp 4 that OS/2 would eventually be withdrawn, the company did not end support until December 31, 2006, with sales of OS/2 stopping on December 23, 2005. The latest IBM OS/2 Warp version

#730269