OS/2 - Revision history

Jnc: /* 16 bit versions */ Avoid redir after move

2025-06-14T04:37:50Z

‎16 bit versions: Avoid redir after move

Ak120: /* 16 bit versions */

2025-06-13T12:01:06Z

‎16 bit versions

Jnc: /* See also */ +Inside OS/2

2024-01-13T02:39:23Z

‎See also: +Inside OS/2

Tor: Fixed a few typos (and possessive "its") and links.

2023-01-20T09:15:21Z

Fixed a few typos (and possessive "its") and links.

Jnc: add some links; avoid redirs; a few typos

2023-01-19T14:51:39Z

add some links; avoid redirs; a few typos

Show changes

Neozeed: add in space for all the newly shared betas

2023-01-19T08:32:02Z

add in space for all the newly shared betas

Neozeed: /* Build 605 */

2022-04-22T11:17:58Z

‎Build 605

Neozeed: It's 605 not 603.

2022-04-22T11:16:55Z

It's 605 not 603.

Neozeed: Update notes on 6.123

2022-04-22T11:02:03Z

Update notes on 6.123

Neozeed: Getting ready to add details into the known 2.00's

2022-04-22T07:02:06Z

Getting ready to add details into the known 2.00's

@@ Line 39: / Line 39: @@
 *1.0
 *:This version was all textmode, and had an interface that was inspired from [[TopView]].  Although it could multi-task, most people didn't realize it, as all programs ran full screen.  It ran in 286 protected mode, except for the single "DOS" mode session.  As a result all device drivers for OS/2 had to be able to run in [[real mode|real]] & [[protected mode]]. Until 1.3 all versions were released by OEM hardware vendors ([[Compaq]], [[Zenith]] etc, along with IBM), this was normal practice for Microsoft at the time.
-*:The IBM OS/2 1.0 announcement can be read [[IBM OS2 1.0 announcement|here]].
+*:The IBM OS/2 1.0 announcement can be read [[IBM OS/2 SE 1.0 announcement|here]].
 *1.1
 *:OS/2 1.1 was released in 1988, and was the first version to include the [[Presentation Manager]].  It 'looked' identical to that of [[Windows 2.0]].  IBM OS/2 1.1 included the PM version of [[Borland Sidekick]] to fill in the gap of accessories for OS/2.  While there was some initial excitement over this version of OS/2, it quickly faded as you had to either buy a new computer with it installed, or jump through OEM channels to get OS/2.  Microsoft didn't sell OS'es to end users in the 1980s (This didn't change until OS/2 1.3, MS-DOS 5 & Windows NT 3.1). Version 1.1c was 386 aware, in that it could use the 80386's ability to quickly & easily transition from real & protected modes, bypassing the [[triple fault]] method of the 286.

@@ Line 31: / Line 31: @@
 === 16 bit versions ===
-All of these versions require an i286 [[Central Processing Unit|CPU]], and an IBM AT, or PS/2 compatible computer.  All of the 16-bit versions were limited to a SINGLE MS-DOS compatibility box, greatly reducing the overall usefulness of OS/2 with the ever increasing prevalence of MS-DOS based applications.  At the same time, the 16-bit version supported swapping, DLL's, threads and preemptive multi-tasking.  There was an excellent overview of the original OS/2's in the book [http://ebooks.znu.edu.ua/files/comp_books1/cd0/isos2.txt Inside OS/2].
+All of these versions require an i286 [[Central Processing Unit|CPU]], and an IBM AT, or PS/2 compatible computer.  All of the 16-bit versions were limited to a SINGLE MS-DOS compatibility box, greatly reducing the overall usefulness of OS/2 with the ever-increasing prevalence of MS-DOS based applications.  At the same time, the 16-bit version supported swapping, DLL's, threads and preemptive multi-tasking.  There was an excellent overview of the original OS/2's in the book [http://ebooks.znu.edu.ua/files/comp_books1/cd0/isos2.txt Inside OS/2].
 *1.0
-[[Image:Microsoft OS2 1.0 - Heathkit Zenith OEM.jpg|thumb|right|150px|OS/2 1.0]]
+*:This version was all textmode, and had an interface that was inspired from [[TopView]].  Although it could multi-task, most people didn't realize it, as all programs ran full screen.  It ran in 286 protected mode, except for the single "DOS" mode session.  As a result all device drivers for OS/2 had to be able to run in [[real mode|real]] & [[protected mode]]. Until 1.3 all versions were released by OEM hardware vendors ([[Compaq]], [[Zenith]] etc, along with IBM), this was normal practice for Microsoft at the time.
-This version was all textmode, and had an interface that was inspired from [[TopView]].  Although it could multi-task, most people didn't realize it, as all programs ran full screen.  It ran in 286 protected mode, except for the single "DOS" mode session.  As a result all device drivers for OS/2 had to be able to run in [[real mode|real]] & [[protected mode]]. Until 1.3 all versions were released by OEM hardware vendors ([[Compaq]], [[Zenith]] etc, along with IBM), this was normal practice for Microsoft at the time.
+*:The IBM OS/2 1.0 announcement can be read [[IBM OS2 1.0 announcement|here]].
 *1.1
-[[Image:IBM OS2 1.1 full package.jpg|thumb|right|150px|OS/2 1.1 full package]]
+*:OS/2 1.1 was released in 1988, and was the first version to include the [[Presentation Manager]].  It 'looked' identical to that of [[Windows 2.0]].  IBM OS/2 1.1 included the PM version of [[Borland Sidekick]] to fill in the gap of accessories for OS/2.  While there was some initial excitement over this version of OS/2, it quickly faded as you had to either buy a new computer with it installed, or jump through OEM channels to get OS/2.  Microsoft didn't sell OS'es to end users in the 1980s (This didn't change until OS/2 1.3, MS-DOS 5 & Windows NT 3.1). Version 1.1c was 386 aware, in that it could use the 80386's ability to quickly & easily transition from real & protected modes, bypassing the [[triple fault]] method of the 286.
 *1.2
-[[Image:IBM OS2 1.2 box cover.jpg|thumb|right|150px|OS/2 1.2 box]]
+*:This version released in September 1988 was significant with the inclusion of the [[HPFS]] [[file system]].  HPFS was significantly faster than the aging [[FAT]] file system as it placed its tables in the middle of the disk, and it allowed for larger file systems, long filenames and extended attributes.  A later [[service pack]] allowed for 386 and above CPUs to use the 386 method of switching between real & protected mode, allowing it to operate significantly faster (1.2c).  From what I understand this was the last version of OS/2 that included direct involvement from Microsoft.
-I think this version was released in September of 1988. This release was significant with the inclusion of the [[HPFS]] [[file system]].  HPFS was significantly faster then the aging [[FAT]] file system as it placed its tables in the middle of the disk, and it allowed for larger file systems, long filenames and extended attributes.  A later [[service pack]] allowed for 386 and above CPUs to use the 386 method of switching between real & protected mode, allowing it to operate significantly faster (1.2c).  From what I understand this was the last version of OS/2 that included direct involvement from Microsoft.
+*:OS/2 1.2 from IBM included the 'standard' edition, along with the EE or extended edition.  The EE edition included basic communications capability (x.25, rs232 terminal), and a SQL database.
+*:[[InfoWorld]] included an excellent review of OS/2 1.2 [http://books.google.com/books?id=1DsEAAAAMBAJ&lpg=PT79&dq=%22OS%2F2%201.2%22&pg=PT66#v=onepage&q=%22OS/2%201.2%22&f=false|here].
 *1.21
-I think this version was a Microsoft exclusive, and the final version that they were directly involved in.
+*:I think this version was a Microsoft exclusive, and the final version that they were directly involved in.
 *1.3
-[[Image:Microsoft OS2 front.JPG|thumb|right|150px|Microsoft OS/2 1.3]]
+*:This was the last version of the 16 bit OS/2 family. The 1.3 user interface resembled that of [[Windows 3.0]]. Microsoft did include a 32-bit HPFS driver in their [[Lan Manager]] package which allowed for the fastest HPFS implementation prior to OS/2 2.0 & Windows NT 3.1
-Around this time, Microsoft had released a beta of the WLO or Windows library for OS/2.  The beta included a copy of all of the applettes & games from Windows 3.0 that could run in the Presentation Manager of OS/2.  These libraries were also used to deliver the last versions of Microsoft Word & Excel for OS/2.  Microsoft had planned on releasing these libraries to allow people to easily port their Windows applications to OS/2, but the rift had happened right before that date, so the beta (which is easy to find) was the only thing released.  You can read more about it [http://pages.prodigy.net/michaln/history/pr/wlo.html here].
+Around this time, Microsoft had released a beta of the WLO or Windows library for OS/2.  The beta included a copy of all of the applets & games from Windows 3.0 that could run in the Presentation Manager of OS/2.  These libraries were also used to deliver the last versions of Microsoft Word & Excel for OS/2.  Microsoft had planned on releasing these libraries to allow people to easily port their Windows applications to OS/2, but the rift had happened right before that date, so the beta (which is easy to find) was the only thing released.  You can read more about it [http://pages.prodigy.net/michaln/history/pr/wlo.html here].
-Additionally, market penetration and OEM interest in OS/2 had dwindled so quickly by this point that Microsoft had decided to do a retail version of OS/2 (pictured to the right) to support its new [[Microsoft SQL Server]] product.  Windows NT on the i386 platform included support for 16-bit OS/2 applications, namely for the Microsoft Languages (Fortran/Assembler & C) and SQL Server.  Since they all were text mode, they would run un-modified up through Windows 2000.
+Additionally, market penetration and OEM interest in OS/2 had dwindled so quickly by this point that Microsoft had decided to do a retail version of OS/2 (pictured to the right) to support its new [[Microsoft SQL Server]] product.  Windows NT on the i386 platform included support for 16-bit OS/2 applications, namely for the Microsoft Languages (Fortran/Assembler & C) and SQL Server.  Since they all were text mode, they would run unmodified up through Windows 2000.
 === 32-bit versions ===

@@ Line 318: / Line 318: @@
 * Watcom Fortran 77
 * Watcom SQL
 [[Category: Microsoft Operating Systems]]

@@ Line 16: / Line 16: @@
 === Pre-Release version ===
-In the beginning there is several known pre-release versions, then followed up with the infamous $3,000 SDK package.  These include:
+In the beginning there are several known pre-release versions, then followed up with the infamous $3,000 SDK package.  These include:
 * A/DOS
@@ Line 100: / Line 100: @@
 [[Image:IBM OS2 Warp 3.0 blue spine cover.jpg|150px|thumb|right|OS/2 Warp 3.0 BlueSpine]]
 *3.0 (09/1994)
-This was the WARP release.  At the time this release preempted the [[Windows 95]] release.  IBM had done their best to tune OS/2 to run in 4MB of ram on a 386SX CPU.  Warp also included the 'bonus pack' which included SLIP/[[PPP]] [[TCP/IP]], a dialer application and a [[word processor]] & spreadsheet.  A simple [[Gopher]] [[client]] & [[Network News Transfer Protocol|NNTP]] client were also included.
+This was the WARP release.  At the time this release preempted the [[Windows 95]] release.  IBM had done their best to tune OS/2 to run in 4MB of [[Random Access Memory|RAM]] on a 386SX CPU.  Warp also included the 'bonus pack' which included SLIP/[[PPP]] [[TCP/IP]], a dialer application and a [[word processor]] & spreadsheet.  A simple [[Gopher]] [[client]] & [[Network News Transfer Protocol|NNTP]] client were also included.
 IMHO this is where IBM missed the boat, by making TCP/IP difficult to configure, and by not including [[local area network|LAN]] drivers (that was WARP CONNECT), while [[Windows 95]] & [[Windows_NT#Windows_NT_3.5|NT 3.5]] both included SLIP/PPP *AND* LAN drivers.
@@ Line 140: / Line 140: @@
 == PowerPC port ==
-It's a deep secret that the PowerPC version ended up sucking up so much time, effort and money from IBM's development of OS/2, that it ended up bleeding the group dry, and without a product to ship.  IMHO it's a shame, as partnered with the [[PowerPC 615]] CPU it could have revolutionalized the industry.. But then back then everyone expected Intel to hit a wall, IBM had the 615 in their pocket which was a PowerPC CPU which was pin compatible with a 486, and could run [[Intel x86|x86]] code (albeit slow..) and then switch to PPC mode.  The company [[NexGen]] opened up everyone's eyes that a specialized [[Reduced Instruction Set Computer|RISC]] CPU could in fact run x86 instructions much quicker then a real Intel CPU...  This opened the way to the Pentium CPUs and effectively killed the RISC revolution.
+It's a deep secret that the PowerPC version ended up sucking up so much time, effort and money from IBM's development of OS/2, that it ended up bleeding the group dry, and without a product to ship.  IMHO it's a shame, as partnered with the [[PowerPC 615]] CPU it could have revolutionized the industry.. But then back then everyone expected Intel to hit a wall, IBM had the 615 in their pocket which was a PowerPC CPU which was pin compatible with a 486, and could run [[Intel x86|x86]] code (albeit slow..) and then switch to PPC mode.  The company [[NexGen]] opened up everyone's eyes that a specialized [[Reduced Instruction Set Computer|RISC]] CPU could in fact run x86 instructions much quicker then a real Intel CPU...  This opened the way to the Pentium CPUs and effectively killed the RISC revolution.
 There is a most excellent review to be found [http://www.os2museum.com/wp/?page_id=30 here] that also includes screenshots.
@@ Line 147: / Line 147: @@
 === 16 bit versions ===
-The latest version of VirtualBOX from SUN is capable of installing & Running the 1.x version of OS/2 provided that they have had a [[Patching OS/2 for fast machines|timing patch]] in place.  I have found that the 'best' profile is to use the "Oracle Solaris 10 5/09 and earlier" profile.  Be sure to limit the VM to 16MB of ram, add both a floppy drive, and a serial port, otherwise you'll have difficulty booting.
+The latest version of VirtualBOX from SUN is capable of installing & Running the 1.x version of OS/2 provided that they have had a [[Patching OS/2 for fast machines|timing patch]] in place.  I have found that the 'best' profile is to use the "Oracle Solaris 10 5/09 and earlier" profile.  Be sure to limit the VM to 16MB of RAM, add both a floppy drive, and a serial port, otherwise you'll have difficulty booting.
 Right now the best solution is either [https://pcem-emulator.co.uk/ PCem] or [http://ci.86box.net/ 86Box].  With the appropriate [http://tinyurl.com/rs20170821 ROMS] it's possible to install onto an emulated 286/386 class based machine.
@@ Line 159: / Line 159: @@
 ==== OS/2 1.1 ====
 [[Image:OS2 1.1.jpg|thumb|200px|right|OS/2 1.1 under Bochs]]
-There are some hacks available to run OS/2 1.1 under [[VMWare]], and [[Bochs]]. There are some [[Patching OS/2 for fast machines|binary patches]] you can do to allow old 1.x OS/2 on fast machines.  Even without an emulator you'd need to do this on anything in pentium II speeds..  With the speed stuff in hand, you can now run 1.1 on VirtualBOX as it's floppy driver now works with OS/2 to detect speed/density correctly.
+There are some hacks available to run OS/2 1.1 under [[VMWare]], and [[Bochs]]. There are some [[Patching OS/2 for fast machines|binary patches]] you can do to allow old 1.x OS/2 on fast machines.  Even without an emulator you'd need to do this on anything in Pentium II speeds..  With the speed stuff in hand, you can now run 1.1 on VirtualBOX as its floppy driver now works with OS/2 to detect speed/density correctly.
 OS/2 1.1c is the first version that supports the 386's method of switching from protected mode to real mode.  Prior to level c of OS/2 1.1 the method was a 286 triple fault, which almost all emulators do not fully support, or it may simply be in the IBM versions.  I'm still not sure as early versions of OS/2 are hard to track down.
@@ Line 184: / Line 184: @@
 ==== OS/2 2.0 ====
-OS/2 2.00 ended up being a [[death march]] of a project, taking far too long, straining the joint agreement between Microsoft and IBM to the breaking point and leading to the infamous divorce.  As it'd come to light decades later Microsoft really had been trying to bring an 80386 version of OS/2 to market since inception, and version 2.00 was the chance to bring this to fruition in codename 'Cruiser'.  Sadly many of these betas did not survive.  There is 3 main branches of these early versions, the Microsoft versions where they were directly involved, the IBM transition to where IBM was now responsible for Cruiser, and finally the Workplace Shell versions, where IBM decided to add a new shell to OS/2 to make 2.00 more 'substantial' but also ended up delaying OS/2 2.00 further.
+OS/2 2.00 ended up being a [[death march]] of a project, taking far too long, straining the joint agreement between Microsoft and IBM to the breaking point and leading to the infamous divorce.  As it'd come to light decades later Microsoft really had been trying to bring an 80386 version of OS/2 to market since inception, and version 2.00 was the chance to bring this to fruition in codename 'Cruiser'.  Sadly many of these betas did not survive.  There are 3 main branches of these early versions, the Microsoft versions where they were directly involved, the IBM transition to where IBM was now responsible for Cruiser, and finally the Workplace Shell versions, where IBM decided to add a new shell to OS/2 to make 2.00 more 'substantial' but also ended up delaying OS/2 2.00 further.
 ===== Betas =====
@@ Line 194: / Line 194: @@
 ====== Build 123 ======
 [[Image:OS2 2.0 6.123.png|thumb|200px|right|OS/2 2.0 Build 123 on 86Box.]]
-The best way to install this is on 86Box/PCem using the AMI 486 clone with a Pentium Overdrive processor and use the inport busmouse adapter, along with the generic VGA adapter.
+The best way to install this is on 86Box/PCem using the AMI 486 clone with a Pentium Overdrive processor and use the [[Microsoft InPort|InPort]] [[Bus mouse]] adapter, along with the generic VGA adapter.
 This build is the 'divorce' edition when IBM started to ship the betas itself, this version uses the OS/2 1.2 Presentation Manager.  The MS-DOS is built around MS-DOS 4.0 and includes no DPMI support at all.
 You can read more about it [http://www.os2museum.com/wp/os-2-2-0-spring-91-edition/ on OS/2 Museum].  The disks can be downloaded from archive.org [[https://archive.org/details/os2-2.0-6.123 here]].
-To install I used [[86box]] i486 Socket 2, IBM PS/ValuePoint 433DX/Si, with a Pentium OverDrive 63Mhz processor, and a 'type 9' disk setup on IDE.  The mouse is set to PS/2 mode.
+To install I used [[86box]] i486 Socket 2, IBM PS/ValuePoint 433DX/Si, with a Pentium OverDrive 63 MHz processor, and a 'type 9' disk setup on IDE.  The mouse is set to PS/2 mode.
 The kernel has the following version string:
@@ Line 209: / Line 209: @@
 ====== Build 605 ======
-Not sure why it's build 605 as it way out of sequence. Perhaps they thought they were close to the end.  This is one of the last Presentation Manager based releases.  It can be downloaded from [[https://archive.org/details/os2-2.0-6.605 archive.org here]].
+Not sure why it's build 605 as it is way out of sequence. Perhaps they thought they were close to the end.  This is one of the last Presentation Manager based releases.  It can be downloaded from [[https://archive.org/details/os2-2.0-6.605 archive.org here]].
 The kernel string reports as:
@@ Line 215: / Line 215: @@
 	Internal revision 6.605, 91/09/11
-The accessories are more fleshed out than 6.123, and to me despite it not supporting DPMI it feels like something that could have shipped in 89.
+The accessories are more fleshed out than 6.123, and to me despite it not supporting DPMI it feels like something that could have shipped in '89.
 also introduced the minimal text setup spanning install disk 1-4, with the rest being setup under the Presentation Manager.
@@ Line 232: / Line 232: @@
 *DISK.NUM
-Then boot from GA's install, then use it's disk 1.  Then use LA's disk from that point onward, and it'll install.
+Then boot from GA's install, then use its disk 1.  Then use LA's disk from that point onward, and it'll install.
 ====== Build 304 ======
@@ Line 240: / Line 240: @@
 [[Image:Vpc5x os2v20 wps.png|thumb|200px|right|OS/2 2.0 running under Virtual PC 5 for OS/2]]
-I've run OS/2 2.0 & 4.0 under Virtual PC, and [[Qemu]]... I guess it really comes down to if you move disk images around between various hardware platforms.  Anything prior to version 3.0 should be run in an ISA emulation mode (-M isa) to let the peripherals work in a more compatible manner...  Virtual PC 2007 works fine as well, and includes extensions that allow the guest VM to use drives that are installed on the host pc.  I've heard that VMWare has given up the compatibility mode fixes.
+I've run OS/2 2.0 & 4.0 under Virtual PC, and [[Qemu]]... I guess it really comes down to if you move disk images around between various hardware platforms.  Anything prior to version 3.0 should be run in an ISA emulation mode (-M isa) to let the peripherals work in a more compatible manner...  Virtual PC 2007 works fine as well, and includes extensions that allow the guest VM to use drives that are installed on the host PC.  I've heard that VMWare has given up the compatibility mode fixes.
 I'm now running OS/2 2.0 under VMWare Player, and it seems to be running OK.  I've found one issue with networking, the Set PermaNet Server feature must be set to TRUE, under the LAPS configuration tool.
@@ Line 308: / Line 308: @@
 ** Microsoft Excel 2.2, 3.0
-All of these products are 16 bit only.  While there was two pre-releases of MS OS/2 2.0 that included CL386 & MASM386 none of these are fully out in the wild so I'm not sure if they could produce programs that would run on the IBM OS/2 2.0 GA and beyond.
+All of these products are 16 bit only.  While there were two pre-releases of MS OS/2 2.0 that included CL386 & MASM386 none of these are fully out in the wild so I'm not sure if they could produce programs that would run on the IBM OS/2 2.0 GA and beyond.
 === StarDivision ===

@@ Line 5: / Line 5: @@
 Microsoft, famous for hedging bets, started the [[Windows]] project around the same time, as a low cost entry interface with rudimentary (cooperative) [[multitasking]].
-Needless to say, Microsoft wanted to target the [[i386]] processor, and work on 32-bit software, while IBM wanted to deliver to the IBM AT customers it had sold to, and demanded the [[i286]] 16-bit version.  Someone at IBM even got the idea that the development tools should be a revenue stream, and needless to say, the $3,000 SDK was '''NOT''' a big seller.  Instead the industry worked around OS/2, and developed [[DOS Extender]] technology, and Microsoft practically gave away the Windows SDK, allowed for OEM customizations, and famously released the [[QuickC for Windows]] product.
+Needless to say, Microsoft wanted to target the [[i386]] processor, and work on 32-bit software, while IBM wanted to deliver to the IBM AT customers it had sold to, and the upcoming PS/2 model 60, hence the demand for the [[i286]] 16-bit version.  Someone at IBM even got the idea that the development tools should be a revenue stream, and needless to say, the $3,000 SDK was '''NOT''' a big seller.  Instead, the industry worked around OS/2, and developed [[DOS Extender]] technology, and Microsoft practically gave away the Windows SDK, allowed for OEM customizations, and famously released the [[QuickC for Windows]] product.
 Microsoft leapt at the chance to formalize DOS extenders into [[DPMI]], and use it in Windows, cementing OS/2's 1.x inability to run DPMI programs.  Microsoft was also upset that IBM locked them out of the graphical components of the OS, and that OS/2 worked BACKWARDS compared to Windows... the 0/0 in the screen coordinates is the bottom right, while everywhere else it's the top left..
 There is a great writeup on the divorce on google's [http://groups.google.com/group/comp.os.ms-windows.misc/msg/d710490b745d5e5e usenet archive], or locally here [[Gordon Letwin OS/2 usenet post]].  There is also a perspective from an Autodesk programmer available [http://www.sibbald.com/windows/windows01.html here].
 == Versions ==
 === 16 bit versions ===
@@ Line 284: / Line 301: @@
 ** Microsoft C 5.1, 6.0
 ** Microsoft COBOL PDS
 ** Microsoft Basic PDS 7.0, 7.1
 ** [[Microsoft Fortran]]

← Older revision		Revision as of 11:17, 22 April 2022
Line 200:		Line 200:

	The accessories are more fleshed out than 6.123, and to me despite it not supporting DPMI it feels like something that could have shipped in 89.		The accessories are more fleshed out than 6.123, and to me despite it not supporting DPMI it feels like something that could have shipped in 89.
		+
		+	605 also introduced the minimal text setup spanning install disk 1-4, with the rest being setup under the Presentation Manager.

	====== Build 177 ======		====== Build 177 ======

@@ Line 192: / Line 192: @@
 The Copyright dialog has this dated for 1990.
-====== Build 603 ======
+====== Build 605 ======
-Not sure why it's build 603 as it way out of sequence. Perhaps they thought they were close to the end.  This is one of the last Presentation Manager based releases.
+Not sure why it's build 605 as it way out of sequence. Perhaps they thought they were close to the end.  This is one of the last Presentation Manager based releases.  It can be downloaded from [[https://archive.org/details/os2-2.0-6.605 archive.org here]].
 ====== Build 177 ======