OS/2 Versions And History - Revision history

Dr. Shuppet: /* Fixed wording */

2023-02-02T14:17:50Z

Fixed wording

← Older revision		Revision as of 14:17, 2 February 2023
Line 114:		Line 114:
	=== ADOS 5.0, PIGSKIN internal revision 7.68.17 ===		=== ADOS 5.0, PIGSKIN internal revision 7.68.17 ===

	Despite the confusing version number, this build of internal revision 7.68 is dated February 1987, three months after SIZZLE. It is a part of a development branch called Football, which was dedicated to shoehorning the 386's virtual 8086 mode for running multiple DOS programs into the main SIZZLE development branch. Since SIZZLE is a 16-bit operating system, Football barely runs on a pile of magic and a myriad of ~~cheap tricks~~, see the references for more details<ref>https://www.pcjs.org/software/pcx86/sys/os2/misc/87058/#football-design-document</ref><ref>https://www.os2museum.com/wp/playing-football/</ref>.		Despite the confusing version number, this build of internal revision 7.68 is dated February 1987, three months after SIZZLE. It is a part of a development branch called Football, which was dedicated to shoehorning the 386's virtual 8086 mode for running multiple DOS programs into the main SIZZLE development branch. Since SIZZLE is a 16-bit operating system, Football barely runs on a pile of magic and a myriad of ugly hacks, see the references for more details<ref>https://www.pcjs.org/software/pcx86/sys/os2/misc/87058/#football-design-document</ref><ref>https://www.os2museum.com/wp/playing-football/</ref>.

	<gallery>		<gallery>

Dr. Shuppet: /* Added section about PIGSKIN and corrected a few mistakes */

2023-02-02T14:15:57Z

Added section about PIGSKIN and corrected a few mistakes

← Older revision		Revision as of 14:15, 2 February 2023
Line 75:		Line 75:
	=== ADOS 5.0, internal revision 7.68 ===		=== ADOS 5.0, internal revision 7.68 ===

	The first known version of protected-mode DOS ~~(called 286DOS in some internal materials)~~ is from October 1986, which is quite late compared to both the release of the PC AT and the development of Windows 1.0 and DOS 4.0. Using the same internal revision format as DOS 4.0, it identifies itself as internal revision 7.68, which is consistent with the known internal revision of DOS 4.0 being 6.7. There is no clear name; boot screen identifies the system as '''CP-DOS 1.0''', while the command interpreter identifies the system as '''ADOS 5.00'''.		The first known version of protected-mode DOS is from October 1986, which is quite late compared to both the release of the PC AT and the development of Windows 1.0 and DOS 4.0. Using the same internal revision format as DOS 4.0, it identifies itself as internal revision 7.68, which is consistent with the known internal revision of DOS 4.0 being 6.7. There is no clear name; boot screen identifies the system as '''CP-DOS 1.0''', while the command interpreter identifies the system as '''ADOS 5.00'''.

	<gallery>		<gallery>
Line 105:		Line 105:
	Later in December 1986, internal revision 7.68 got another build with a version number 7.68.18, codenamed SIZZLE. It is said to improve overall performance<ref>https://betawiki.net/wiki/IBM_OS/2_1.0_revision_7.68.18</ref>, and contains an updated version of the real mode shell, which fixes the prompt glitch from 7.68 and now identifies itself as The IBM Personal Computer DOS Version 5.00.		Later in December 1986, internal revision 7.68 got another build with a version number 7.68.18, codenamed SIZZLE. It is said to improve overall performance<ref>https://betawiki.net/wiki/IBM_OS/2_1.0_revision_7.68.18</ref>, and contains an updated version of the real mode shell, which fixes the prompt glitch from 7.68 and now identifies itself as The IBM Personal Computer DOS Version 5.00.

	The build no longer relies on files on the hard drive, running fully from a diskette. Microsoft C Compiler 3.00.17 is bundled with the build in the DOS3TOOL directory.		The build no longer relies on files on the hard drive, running fully from a diskette. Microsoft C Compiler 3.00.17 is bundled with the build in the DOS3TOOL directory in the release build; MASM, LINK4, MAKE, LIB, SED, and a few other tools are bundled instead in the debug build<ref>https://www.pcjs.org/software/pcx86/sys/os2/misc/87007/</ref>.

	<gallery>		<gallery>
Line 111:		Line 111:
	File:ADOS 5.0 SIZZLE real mode.png\|thumb\|ADOS 5.0 internal revision 7.68.18 in real mode		File:ADOS 5.0 SIZZLE real mode.png\|thumb\|ADOS 5.0 internal revision 7.68.18 in real mode
	</gallery>		</gallery>

			=== ADOS 5.0, PIGSKIN internal revision 7.68.17 ===

			Despite the confusing version number, this build of internal revision 7.68 is dated February 1987, three months after SIZZLE. It is a part of a development branch called Football, which was dedicated to shoehorning the 386's virtual 8086 mode for running multiple DOS programs into the main SIZZLE development branch. Since SIZZLE is a 16-bit operating system, Football barely runs on a pile of magic and a myriad of cheap tricks, see the references for more details<ref>https://www.pcjs.org/software/pcx86/sys/os2/misc/87058/#football-design-document</ref><ref>https://www.os2museum.com/wp/playing-football/</ref>.

			<gallery>
			File:ADOS 5.0 PIGSKIN boot screen.png\|thumb\|ADOS 5.0 PIGSKIN booting in PCjs
			File:ADOS 5.0 PIGSKIN session manager.png\|thumb\|ADOS 5.0 PIGSKIN session manager
			File:ADOS 5.0 PIGSKIN real mode shell.png\|thumb\|"Real" (V86) mode shell of ADOS 5.0 PIGSKIN, with VT52 emulation
			File:ADOS 5.0 PIGSKIN protected mode shell.png\|thumb\|Protected mode shell of ADOS 5.0 PIGSKIN
			</gallery>

			The kernel relies on 386 specific internal registers that were removed in Pentium, as well as an EGA GPU with a purely byte IO interface. Combined with the fact this is a debug build and requires to be poked at the serial console, it makes this build especially hard to run in an emulator. COMPAQ DeskPro 386-16 is known to be supported and is emulated by PCjs, which features a VM with PIGSKIN.

			Just like internal revision 7.68, the build attempts to access the hard drive, in this case only to create a swap file at C:\TMP\SWAPPER.DAT. The protected mode part of the OS appears unchanged. Similarly to SIZZLE having SED.EXE, it also includes a Unix tool, CPGREP.EXE.

	== IBM OS/2 1.0 ==		== IBM OS/2 1.0 ==

Dr. Shuppet: /* Minor addition to MS OS/2 1.0 TODO */

2023-01-28T09:47:27Z

Minor addition to MS OS/2 1.0 TODO

← Older revision		Revision as of 09:47, 28 January 2023
Line 118:		Line 118:
	Things to do:		Things to do:
	* Document neozeed's and NCommander's exploration results		* Document neozeed's and NCommander's exploration results
	* Find out when OS/2 1.1-specific features (.DLL extension, OS name NE field, OS2KRNL) first appeared among MS OS/2 SDKs		* Find out when OS/2 1.1-specific features (.DLL extension, OS name NE field, OS2KRNL) first appeared among MS OS/2 SDKs, and compare them to the timeline of Windows if relevant

	== IBM OS/2 1.1 ==		== IBM OS/2 1.1 ==

Dr. Shuppet: /* Updated todo list for MS OS/2 1.0 */

2023-01-28T09:41:05Z

Updated todo list for MS OS/2 1.0

← Older revision		Revision as of 09:41, 28 January 2023
Line 116:		Line 116:
	== MS OS/2 1.0 ==		== MS OS/2 1.0 ==

	~~TODO~~: Document neozeed's and NCommander's ~~exporation~~ results		Things to do:
			* Document neozeed's and NCommander's exploration results
			* Find out when OS/2 1.1-specific features (.DLL extension, OS name NE field, OS2KRNL) first appeared among MS OS/2 SDKs

	== IBM OS/2 1.1 ==		== IBM OS/2 1.1 ==

Dr. Shuppet: /* Added list of topics to research */

2023-01-28T09:34:32Z

Added list of topics to research

← Older revision		Revision as of 09:34, 28 January 2023
Line 67:		Line 67:

	== OS/2 Pre-Betas ==		== OS/2 Pre-Betas ==

			Topics to research:
			* Compatibility of API and binaries between OS/2 Pre-Betas and later OS/2 versions
			* Compatibility of the early versions of the DOS box
			* The evolution of driver composition, i.e. what drivers are separate .SYS modules and what drivers are bundled in IBMBIO.COM and BASEDD*.SYS

	=== ADOS 5.0, internal revision 7.68 ===		=== ADOS 5.0, internal revision 7.68 ===

Dr. Shuppet: /* Added note about ADOS default prompt */

2023-01-28T09:34:12Z

Added note about ADOS default prompt

← Older revision		Revision as of 09:34, 28 January 2023
Line 79:		Line 79:
	</gallery>		</gallery>

	Feature-wise, ADOS 5.0 is a continuation of DOS 4.0, keeping e.g. New Executable, the DOSCALLS in-kernel module, Session Manager, and SCREEN$ device (KEYBD$ seems to be missing from internal revision 7.68). A significant difference is the absence of any interrupt-based API in protected mode, all of which was moved to DOSCALLS or several userspace modules<ref>http://www.edm2.com/index.php/OS/2_DLL_Entry_Points</ref>:		Feature-wise, ADOS 5.0 is a continuation of DOS 4.0, keeping e.g. New Executable, the DOSCALLS in-kernel module, Session Manager, and SCREEN$ device (KEYBD$ seems to be missing from internal revision 7.68). The default prompt is X], which is different from the standard X>, X:\>, and [4.0 X:\>] prompts used by DOS. A significant difference is the absence of any interrupt-based API in protected mode, all of which was moved to DOSCALLS or several userspace modules<ref>http://www.edm2.com/index.php/OS/2_DLL_Entry_Points</ref>:

	* BKSCALLS.EXE - Base Keyboard Subsystem		* BKSCALLS.EXE - Base Keyboard Subsystem

Dr. Shuppet: /* Added section about SIZZLE */

2023-01-25T20:47:57Z

Added section about SIZZLE

@@ Line 92: / Line 92: @@
 Session Manager (SM.EXE in DOS 4.0) was split into SESMGR.EXE and SHELL.EXE. SESMGR is a module linked by any program that wants to act as a session manager; internally it uses DOSCALLS, KBDCALLS, MOUCALLS, and VIOCALLS routines to handle that. This allows custom shells to be written; SHELL.EXE is the system-provided shell, in appearance very similar to SM.EXE.
-To provide binary compatibility with real-mode DOS, ADOS 5.0 introduces a separate, real mode environment, identifying itself as The IBM Personal Computer DOS Version 5.00. For this purpose, the protected mode command line interpreter was renamed to CMD.EXE, COMMAND.COM being used for the real mode interpreter. PROTMODE has to be set to yes in CONFIG.SYS in order for the DOS mode to be available; it then appears in the session manager menu as COMMAND.COM R.
+This build expects a hard drive with a C:\MTDOS directory to be present, throwing (non-fatal) errors if it isn't there. The name MTDOS might be an indication of the system still being called by the name of its predecessor, Multitasking DOS, internally by the developers.
 == IBM OS/2 1.0 ==

Dr. Shuppet: /* Added screenshot of ADOS 5.0 7.68 DOS mode */

2023-01-25T20:27:45Z

Added screenshot of ADOS 5.0 7.68 DOS mode

← Older revision		Revision as of 20:27, 25 January 2023
Line 76:		Line 76:
	File:ADOS 5.0 internal revision 7.68 command prompt.png\|thumb\|ADOS 5.0 internal revision 7.68 command prompt (CMD.EXE)		File:ADOS 5.0 internal revision 7.68 command prompt.png\|thumb\|ADOS 5.0 internal revision 7.68 command prompt (CMD.EXE)
	File:ADOS 5.0 internal revision 7.68 boot screen.png\|thumb\|ADOS 5.0 internal revision 7.68 booting in VirtualBox		File:ADOS 5.0 internal revision 7.68 boot screen.png\|thumb\|ADOS 5.0 internal revision 7.68 booting in VirtualBox
			File:ADOS 5.0 real mode.png\|thumb\|ADOS 5.0 real mode shell, an early version of the so-called penalty box
	</gallery>		</gallery>

Line 91:		Line 92:
	Session Manager (SM.EXE in DOS 4.0) was split into SESMGR.EXE and SHELL.EXE. SESMGR is a module linked by any program that wants to act as a session manager; internally it uses DOSCALLS, KBDCALLS, MOUCALLS, and VIOCALLS routines to handle that. This allows custom shells to be written; SHELL.EXE is the system-provided shell, in appearance very similar to SM.EXE.		Session Manager (SM.EXE in DOS 4.0) was split into SESMGR.EXE and SHELL.EXE. SESMGR is a module linked by any program that wants to act as a session manager; internally it uses DOSCALLS, KBDCALLS, MOUCALLS, and VIOCALLS routines to handle that. This allows custom shells to be written; SHELL.EXE is the system-provided shell, in appearance very similar to SM.EXE.

	To provide binary compatibility with real-mode DOS, ADOS 5.0 introduces a separate, real mode environment, identifying itself as The IBM Personal Computer DOS Version 5.00. For this purpose, the protected mode command line interpreter was renamed to CMD.EXE, COMMAND.COM being used for the real mode interpreter.		To provide binary compatibility with real-mode DOS, ADOS 5.0 introduces a separate, real mode environment, identifying itself as The IBM Personal Computer DOS Version 5.00. For this purpose, the protected mode command line interpreter was renamed to CMD.EXE, COMMAND.COM being used for the real mode interpreter. PROTMODE has to be set to yes in CONFIG.SYS in order for the DOS mode to be available; it then appears in the session manager menu as COMMAND.COM R.

	== IBM OS/2 1.0 ==		== IBM OS/2 1.0 ==

Dr. Shuppet: /* Added real mode ADOS 5.0 */

2023-01-20T10:05:00Z

Added real mode ADOS 5.0

← Older revision		Revision as of 10:05, 20 January 2023
Line 70:		Line 70:
	=== ADOS 5.0, internal revision 7.68 ===		=== ADOS 5.0, internal revision 7.68 ===

	The first known version of protected-mode DOS is from October 1986, which is quite late compared to both the release of the PC AT and the development of Windows 1.0 and DOS 4.0. Using the same internal revision format as DOS 4.0, it identifies itself as internal revision 7.68, which is consistent with the known internal revision of DOS 4.0 being 6.7. There is no clear name; boot screen identifies the system as '''CP-DOS 1.0''', while the command interpreter identifies the system as '''ADOS 5.00'''.		The first known version of protected-mode DOS (called 286DOS in some internal materials) is from October 1986, which is quite late compared to both the release of the PC AT and the development of Windows 1.0 and DOS 4.0. Using the same internal revision format as DOS 4.0, it identifies itself as internal revision 7.68, which is consistent with the known internal revision of DOS 4.0 being 6.7. There is no clear name; boot screen identifies the system as '''CP-DOS 1.0''', while the command interpreter identifies the system as '''ADOS 5.00'''.

	<gallery>		<gallery>
Line 89:		Line 89:
	* VIOCALLS.EXE - Video Calls (VIO subsystem)		* VIOCALLS.EXE - Video Calls (VIO subsystem)

	Session Manager (SM.EXE in DOS 4.0) was split into SESMGR.EXE and SHELL.EXE. SESMGR is a module linked by any program that wants to act as a session manager; internally it uses DOSCALLS, KBDCALLS, MOUCALLS, and VIOCALLS routines to handle that. This allows custom shells to be written; SHELL.EXE is the system-provided shell, in appearance very similar to SM.EXE.		Session Manager (SM.EXE in DOS 4.0) was split into SESMGR.EXE and SHELL.EXE. SESMGR is a module linked by any program that wants to act as a session manager; internally it uses DOSCALLS, KBDCALLS, MOUCALLS, and VIOCALLS routines to handle that. This allows custom shells to be written; SHELL.EXE is the system-provided shell, in appearance very similar to SM.EXE.

			To provide binary compatibility with real-mode DOS, ADOS 5.0 introduces a separate, real mode environment, identifying itself as The IBM Personal Computer DOS Version 5.00. For this purpose, the protected mode command line interpreter was renamed to CMD.EXE, COMMAND.COM being used for the real mode interpreter.

	== IBM OS/2 1.0 ==		== IBM OS/2 1.0 ==

Dr. Shuppet: /* Added ADOS 5.0 Session Manager description */

2023-01-20T09:25:36Z

Added ADOS 5.0 Session Manager description

← Older revision		Revision as of 09:25, 20 January 2023
Line 88:		Line 88:
	* QUECALLS.EXE - Queue Calls		* QUECALLS.EXE - Queue Calls
	* VIOCALLS.EXE - Video Calls (VIO subsystem)		* VIOCALLS.EXE - Video Calls (VIO subsystem)

			Session Manager (SM.EXE in DOS 4.0) was split into SESMGR.EXE and SHELL.EXE. SESMGR is a module linked by any program that wants to act as a session manager; internally it uses DOSCALLS, KBDCALLS, MOUCALLS, and VIOCALLS routines to handle that. This allows custom shells to be written; SHELL.EXE is the system-provided shell, in appearance very similar to SM.EXE.

	== IBM OS/2 1.0 ==		== IBM OS/2 1.0 ==