OS/2 Warp 4 desktop. This version was released on 25 September 1996.(1.0–1.2), andWorking stateHistorical, now developed asSource modelInitial releaseDecember 1987; 31 years ago ( 1987-12)4.52 / December 2001; 17 years ago ( 2001-12)Marketing targetProfessionals, servers,Platforms,typeDefaultOfficial websiteOS/2 is a series of computer, initially created by and under the leadership of IBM software designer. As a result of a feud between the two companies over how to position OS/2 relative to Microsoft's new operating environment, the two companies severed the relationship in 1992 and OS/2 development fell to IBM exclusively. The name stands for 'Operating System/2', because it was introduced as part of the same generation change release as IBM's ' (PS/2)' line of second-generation.

• Ecomstation 2.1 Deutsch Download Firefox
• Ecomstation Iso
• Ecomstation Dead

The first version of OS/2 was released in December 1987 and newer versions were released until December 2001.OS/2 was intended as a successor of. Notably, basic were modeled after calls; their names even started with 'Dos' and it was possible to create 'Family Mode' applications – applications that could work on both systems.

Because of this heritage, OS/2 shares similarities with, and.IBM discontinued its support for OS/2 on 31 December 2006. Since then, it has been updated, maintained and marketed under the name. In 2015 it was announced that a new OEM distribution of OS/2 would be released that was to be called. ArcaOS is available for purchase. Contents.Development history 1985–1989: Joint development The development of OS/2 began when IBM and Microsoft signed 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 is -only, and a GUI was introduced with OS/2 1.1 about a year later.

OS/2 features an for controlling the (VIO) and handling and mouse events so that programmers writing for need not call the 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, and should not be confused with the family of database engines for Unix and operating systems). A task-switcher named Program Selector was available through the Ctrl-Esc 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:, //LU 6.2, SQL.The promised user interface, was introduced with OS/2 1.1 in October 1988. It had a similar user interface to, 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 ).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, the. HPFS provided a number of improvements over the older file system, including long filenames and a form of called. In addition, extended attributes were also added to the FAT file system.

Installation Disk A of Microsoft OS/2 1.3 (3½-inch floppy disk)The Extended Edition of 1.2 introduced and support.OS/2- and Windows-related books of the late 1980s acknowledged the existence of both systems and promoted OS/2 as the system of the future. 1990: Breakup The collaboration between IBM and Microsoft unravelled in 1990, between the releases of 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 the other hand, was available only as an additional stand-alone software package. In addition, OS/2 lacked 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 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, including systems that could not support the features Microsoft wanted. Microsoft programmers also became frustrated with IBM's bureaucracy and its use of to measure. IBM developers complained about the terseness and lack of in Microsoft's code, while Microsoft developers complained that IBM's code was.The two products have significant differences in API. OS/2 was announced when was near completion, and the 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 the processor and DOS fundamentally doesn't. IBM insisted on supporting the 80286 processor, with its 16-bit 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 and therefore could not benefit from the 's much simpler and features.

This was especially painful in providing support for DOS applications. While, in 1988, could run several DOS applications, including (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, former architect, in 1988 created an immediate competition with the OS/2 team, as Cutler did not think much of the OS/2 technology and wanted to build on his work at rather than creating a 'DOS plus'. His 'NT OS/2' was a completely new architecture. The OS/2 2.0 upgrade boxIBM 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 the end, Microsoft decided to recast NT OS/2 3.0 as, 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 the, 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 and AVIO applications with the addition of the Windows NT Add-On Subsystem for Presentation Manager. 1992: 32-bit era OS/2 2.0 was released in April 1992.

It 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. This was a fully object-oriented interface that was a significant departure from 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.DOS compatibility 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 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, including Windows 3.0 applications.Because of the limitations of the processor, OS/2 1.x could run only one DOS program at 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 of the processor to create a much safer 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 ) 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 the older interface, unlike the Standard mode of Windows 3.1; it only supported programs written according to. (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 the machine in this way. OS/2 could, however, use a hardware on selected machines (notably IBM machines) to break out of such a deadlock.

Later, release 3.0 leveraged the enhancements of newer and processors—the (VIF), which was part of the (VME)—to solve this problem. Further information: Windows 3.x compatibility Compatibility with Windows 3.0 (and later Windows 3.1) was achieved by adapting Windows user-mode code components to run inside a (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 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 and applications that require them.Multiple Windows applications run by default in 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 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 is possible to use between OS/2 and Windows applications, and between Windows applications only. 1994–1996: The 'Warp' years. OS/2 Warp 4 desktop after installationReleased 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 the release: IBM claimed that it had used 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, was to be the; however of the then-upcoming series was substituted at the last minute.: p. 108OS/2 Warp offers a host of benefits over OS/2 2.1, notably broader hardware support, greater multimedia capabilities, -compatible networking, and it includes a basic office application suite known as. 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 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 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 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.

Firefox 3.5.4 for OS/2 Warp 4In 1996, Warp 4 added and software. IBM also released server editions of Warp 3 and Warp 4 which bundled IBM's LAN Server product directly into the operating system installation. A personal version of was also included, with a number of template databases for contact management, brainstorming, and so forth. The UK-distributed free demo of OS/2 Warp essentially contained the entire OS and was easily, even accidentally, meaning that even people who liked it did not have to buy it. This was seen as a backdoor tactic to increase 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 magazine bundled software CD-ROMs, included 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 (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. While OS/2 was arguably technically superior to Microsoft, OS/2 failed to develop much penetration in the consumer and stand-alone desktop PC segments; there were reports that it could not be installed properly on IBM's own series of home PCs. Microsoft made an offer in 1994 where IBM would receive the same terms as (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, which would have directly competed with. As 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. Workplace OS. Main article:In 1991 IBM started development on an intended replacement for OS/2 called.

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 a system registry, JFS, support for UNIX graphics libraries, and a new driver model.Workplace OS was developed solely for, and IBM intended to market a full line of PowerPCs in an effort to take over the market from. 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 the new code base would eventually include replacement of the 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 stopped by the booth. The second and last time it would be shown in public was at an OS/2 user group in Phoenix, Arizona; the pre-alpha code refused to boot.It was released in 1995.

Ecomstation 2.1 Deutsch Download Firefox

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.Downsizing. This section does not any. Unsourced material may be challenged. ( March 2013) A project was launched internally by IBM to evaluate the looming competitive situation with Microsoft Windows 95. Primary concerns included 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 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 the last full year.

Warp 4 became the last distributed version of OS/2.2001: Fading out. A crashed in Australia running OS/2 WarpA small and dedicated community remained faithful to OS/2 for many years after its final mainstream release, but overall, 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, run OS/2 with a customized user interface; French national railways used OS/2 1.x in thousands of ticket selling machines. Telecom companies such as use OS/2 in some voicemail systems.

Also, OS/2 was used for the host PC used to control the equipment installed at 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. Sales of OS/2 stopped on December 23, 2005. The latest IBM version is 4.52, which was released for both desktop and server systems in December 2001. Serenity Systems has been reselling OS/2 since 2001, calling it.

Version 1.2 was released in 2004. After a series of preliminary 'release candidates,' version 2.0 GA (General Availability) was released on 15 May 2010. EComStation version 2.1 GA was released on May 20, 2011.IBM is still delivering defect support for a fee. IBM urges customers to migrate their often highly complex applications to technologies such as in a platform-neutral manner. Once application migration is completed, IBM recommends migration to a different operating system, suggesting as an alternative.

Virtualization. This section needs to be updated. Please update this article to reflect recent events or newly available information. ( March 2016)As of 2008, support for running OS/2 under appears to be improving in several third-party products.

OS/2 has historically been more difficult to run in a virtual machine than most other legacy operating systems because of its extensive reliance on the full set of features of the x86 CPU; in particular, OS/2's use of prevented it from running in. Emulators such as and don't suffer from this problem and can run OS/2.

A beta of VMware Workstation 2.0 released in January 2000 was the first that could run OS/2 at all. Later, the company decided to drop official OS/2 support.from (originally ) has been able to run OS/2 without hardware virtualization support for many years. It also provided 'additions' code which greatly improves host–guest OS interactions in OS/2.

The additions are not provided with the current version of VirtualPC, but the version last included with a release may still be used with current releases. At one point, OS/2 was a supported host for VirtualPC in addition to a guest. Note that OS/2 runs only as a guest on those versions of VirtualPC that use virtualization (x86 based hosts) and not those doing full emulation (VirtualPC for Mac).from (originally, later ) supports OS/2 Warp 3, 4 and 4.5 as well as eComStation as guests. However, attempting to run OS/2 and eComStation can still be difficult, if not impossible, because of the strict requirements of VT-x/AMD-V hardware-enabled virtualization and only ACP2/MCP2 is reported to work in a reliable manner.The difficulties in efficiently running OS/2 have, at least once, created an opportunity for a new company.

A large bank in needed a way to use OS/2 on newer hardware that OS/2 did not support. As virtualization software is an easy way around this, the company desired to run OS/2 under a. Once it was determined that VMware was not a possibility, it hired a group of Russian software developers to write a host-based hypervisor that would officially support OS/2. Thus, the company and their product was born. ATMs vendors and have both adopted as their migration path from OS/2.

initially shipped XP Embedded Edition exclusively, but following extensive pressure from customer banks to support a common OS, switched to XP Professional to match their primary competitor. Security niche OS/2 has few native; while it is not invulnerable by design, its reduced market share appears to have. There are, however, OS/2-based antivirus programs, dealing with DOS viruses and Windows viruses that could pass through an OS/2 server.

Petitions for open source Many people hoped that IBM would release OS/2 or a significant part of it as. 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 the future because it contains third-party code to which IBM does not have copyright, and much of this code is from. IBM also once engaged in a technology transfer with, licensing technology for OS/2 2.0 and above, in exchange for the 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 the future. On the other hand, donated for Windows and OS/2 to the Open Object REXX project maintained by the REXX Language Association on.There was a petition, arranged by, to open parts of the OS. Open source operating systems such as have already profited from OS/2 indirectly through IBM's release of the improved, which 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 and added the functionality to boot from a JFS partition. This new JFS driver has been integrated into eComStation v2.0, the successor of OS/2.Summary of releases Release dates refer to the US English editions unless otherwise noted. This section needs expansion. You can help. ( April 2019)The is based on the stack as visible with compatible tools.Drivers Hardware vendors were reluctant to support device drivers for alternative operating systems including OS/2 and Linux, leaving users with few choices from a select few vendors. To relieve this issue for video cards, IBM licensed a reduced version of the, allowing users to choose from a wide selection of cards supported through Scitech's modular driver design. Problems Some problems were classic subjects of comparison with other operating systems:.

Synchronous input queue (SIQ): if a GUI application was not servicing its window messages, the entire GUI system could get stuck and a reboot was required. This problem was considerably reduced with later Warp 3 fixpacks and refined by Warp 4, by taking control over the application after it had not responded for several seconds. No unified object handles (OS/2 v2.11 and earlier): The availability of threads probably led system designers to overlook mechanisms which allow a single thread to wait for different types of asynchronous events at the same time, for example the keyboard and the mouse in a 'console' program. Even though select was added later, it only worked on network sockets. In case of a console program, dedicating a separate thread for waiting on each source of events made it difficult to properly release all the input devices before starting other programs in the same 'session'. As a result, console programs usually polled the keyboard and the mouse alternately, which resulted in wasted CPU and a characteristic 'jerky' reactivity to user input.

In OS/2 3.0 IBM introduced a new call for this specific problem.Historical uses. This section needs additional citations for. Unsourced material may be challenged and removed.Find sources: – ( June 2011) OS/2 has been widely used in Iran Export Bank (Bank Saderat Iran) in their teller machines, ATMs and local servers (over 30,000 working stations). As of 2011, the bank moved to virtualize and renew their infrastructure by moving OS/2 to Virtual Machines running over Windows.OS/2 was widely used in banks.

Had a peak 10,000 machines running OS/2 Warp in the 1990s. OS/2 was used in until 2006. The workstations and and attendant computers have been migrated to.OS/2 has been used in the banking industry. Bank in still ran its network on OS/2 as late as 2002. In used OS/2 as late as 2009, and even the turn of the decade.OS/2 was widely adopted by professionals and companies. In mid-1990s native 32-bit accounting software were well developed and serving corporate markets.OS/2 ran the faulty at. The OS was eventually scrapped, but the software written for the system led to massive delays in the opening of the new airport.

The OS itself was not at fault, but the software written to run on the OS was. The baggage handling system was eventually removed.OS/2 was used by radio personality. He once had a 10-minute on-air rant about OS/2 versus and recommended OS/2.

He also used OS/2 on his laptop.OS/2 was used as part of the Satellite Operations Support System (SOSS) for 's. SOSS was a computer-controlled system using OS/2 that NPR member stations used to receive programming feeds via satellite. SOSS was introduced in 1994 using OS/2 3.0, and was retired in 2007, when NPR switched over to its successor, the.OS/2 was used to control the automated light rail system in, British Columbia, Canada until the late 2000s when it was replaced by.OS/2 was used in the Signals Control System (JLESCS) in London, UK. This control system delivered by Alcatel was in use from 1999 to 2011 i.e. Between abandonment before opening of the line's unimplemented original automatic train control system and the present system. JLESCS did not provide automatic train operation only manual train supervision.

Six OS/2 local site computers were distributed along the railway between Stratford and Westminster, the shunting tower at Stratford depot, and several formed the central equipment located at Neasden. Matthew Nawrocki (26 February 2013). Retrieved 22 September 2013. Nuska, Andrew (June 21, 2013). Retrieved 20 May 2017. McCracken, Harry (April 2, 2012).

Time Magazine. Retrieved 20 May 2017. Markoff, John (June 28, 1992).

Retrieved 20 May 2017. Michal Necasek (2001-09-08).

The History of OS/2. Archived from on 2007-10-12. IBM (12 July 2005). Archived from on 27 April 2006.

James Sanders (2015). Cite journal requires journal=. James Sanders (2016).

Cite journal requires journal=. Sharwood, Simon (19 May 2017). The Register. IBM and Microsoft (1985).

Retrieved March 25, 2013. Cite journal requires journal=. Michal Necasek (April 2, 1987).

The History of OS/2 (Press release). Archived from on April 10, 2010. Retrieved March 25, 2013. (PDF). Retrieved 2 April 2019. Michal Necasek (2001-07-16).

The History of OS/2. Archived from on 2010-08-11. ^ David Both (May 2, 2012) originally published December 19, 1996. DataBook for OS/2 Warp. Archived from on February 18, 2013. Retrieved April 9, 2013. H.

Gilbert (1995). PC Lube and Tune.

Archived from on 2006-07-14. Bob Eager (28 October 2000). Tavi Systems.; foreword by (1988). OS/2 Programmer's Guide. I believe OS/2 is destined to be the most important operating system, and possibly program, of all time. As the successor to DOS, which has over 10,000,000 systems in use, it creates incredible opportunities for everyone involved with PCs. Bellis, Mary.

Dotdash. Thomas Hormby (25 May 2005). Archived from on March 12, 2006.

Retrieved April 9, 2013. Michal Necasek (2001-10-29). The History of OS/2. Archived from on 2006-06-13. Paul Thurrott (24 January 2003). Archived from on 4 June 2010.;;.

Michael Lee Vasu; Debra W. David Garson (1998-03-03). P. 268. Gordon Letwin.

Google Groups. Computer History Collection (transcript of a Video History interview). Interviewed by David Allison. National Museum of American History, Smithsonian Institution. Retrieved April 10, 2013.

Microsoft (2000). Inside Out, Microsoft—In Our Own Words.

Warner Business Books. Microsoft. Microsoft TechNet. Retrieved April 9, 2013. Robert X. Cringely (27 April 2006). Pbs.org.

Microsoft (6 November 1999). Archived from on March 9, 2013. Christian Alice Scarborough (15 September 1998).

Game Zero magazine. 6 March 1995. Timothy F. Sipples (20 February 1995). Internet Movie Database.

In 1996, was contracted by IBM to help promote the latest release of OS/2 Warp, version 4 (previously codenamed Merlin), due to associations with Star Trek. Archived from on January 27, 2013. Retrieved April 9, 2013.

Chapman, Merrill R. (paperback) (2nd ed.). Berkeley, California: Apress.

They rented a hall in New York City and invited hundreds to see Patrick Stewart, the then current captain of the Starship Enterprise to help roll out the product in a gala event. (Stewart was a no-show.). Lewis, Peter H. (8 August 1995).

The New York Times. Wasserman, Elizabeth (June 8, 1999). Retrieved 2013-03-20.

Fleisch, Brett D; Allan, Mark (September 23, 1997). John Wiley & Sons, Ltd. Archived from on August 24, 2007. Retrieved March 25, 2013. Cite journal requires journal=. Retrieved 2013-03-20.

^ IBM. Retrieved 2013-03-20. Retrieved 2013-03-20.

Retrieved April 9, 2013. Archived from on May 13, 2010. Retrieved April 9, 2013. Archived from on 2014-02-01.

Retrieved 2013-03-20. (PDF). Retrieved 2013-03-20.

The VMware Team. Archived from on 2006-04-20. VirtualBox. Timothy Prickett Morgan.

Ecomstation Iso

Archived from on 2007-04-03. John F. Morar, David M. Archived from on 2011-06-04. January 2011. Archived from on 2010-10-03.

Retrieved 2012-08-17. Archived from on January 27, 2013. Retrieved April 9, 2013. The Art of Unix Programming p. Retrieved 2011-07-05.

Retrieved 2016-12-19. (PDF). Retrieved 2016-12-19. (PDF). Archived from (PDF) on 2011-11-24.

Retrieved 2011-07-05. see IBM Developer Connection for OS/2, Internal Fixpack 12J. KbdGetConsole and DosWaitMuxWaitSem, see Control Program Programming Guide and Reference, IBM OS/2 Toolkit. Archived from on 2012-07-28. (fee).

January 24, 2002. Retrieved 2010-01-24. ^ McCracken, Harry (April 2, 2012). Retrieved April 9, 2013., Jun 13, 2019, Tedium.

January 1989. 25 March 1996. P. 420. (PDF). Retrieved 30 December 2011. Retrieved 30 December 2011.

Archived from on 2014-03-05. Retrieved 30 December 2011. Retrieved 19 June 2014.Further reading.

Harvey M. Deitel and Michael S. Kogan (1992). (1988). (1994).

Ecomstation Dead

Peter Moylan (2004-07-23). Michal Necasek (2005-12-03).

The History of OS/2. Archived from on August 12, 2010.

Retrieved April 10, 2013. —Necasek discusses an aborted port to machines. Reimer, Jeremy. Retrieved 12 December 2013.External links.