README updates

disks/pc/README.md

@@ -96,6 +96,7 @@ The rest of our disk archive is available directly from the various [Machines](/
 * [Microsoft C 4.00](/disks/pc/tools/microsoft/c/4.00/)
 * Microsoft MASM 4.00
 * Microsoft Mouse 5.00
+* [Microsoft OS/2 SDK 1.02](/disks/pc/tools/microsoft/os2/sdk/1.02/)
 * Microsoft Windows SDK 1.01
 * Microsoft Windows SDK 1.03
 * Microsoft Windows SDK 1.04

disks/pc/tools/microsoft/os2/sdk/1.02/README.md

@@ -8,12 +8,18 @@ Microsoft OS/2 SDK v1.02
 ---
 
 This copy of the Microsoft OS/2 SDK (v1.02) was obtained from the [WinWorld](https://winworldpc.com/product/os-2-1x/10)
-website.  The copy is incomplete -- it's missing the **NETWORK** disk -- so we've included an empty **NETWORK** disk
+website.  Unfortunately, it's missing the **NETWORK** disk, so we've included an empty **NETWORK** disk
 that allows the SDK installation script to finish.
 
-We don't have any SDK documentation, other than what's included on these disks.  If you look at the **TOOLKIT1** disk,
+This SDK was released around December 1987 and included a copy of Microsoft OS/2 1.0.  We do not have any of the
-in the **OS2DOC** folder, you'll find a **READ.ME!**, which includes some very useful information about the
+printed documentation that came with the SDK, such as the *Installation Guide*, but we do have the
-installation process:
+[Microsoft® Operating System/2 Programmer’s Toolkit](/docs/os2/microsoft/ptk/1.0/) from March 1988, thanks to the
+[OS/2 Museum](http://www.os2museum.com/).
+
+### Installation
+
+If you look at the **TOOLKIT1** disk, in the **OS2DOC** folder, you'll find **READ.ME!**, which includes some very
+useful information about the SDK installation process:
 
 	The installation guide is confusing, can you give me three easy steps to
 	installing the SDK?
@@ -26,7 +32,7 @@ installation process:
 		TOOLKIT diskette to the root of your hard drive.  Run the program INSTSDK
 		and answer its questions.
 	
-		Thats, all.
+		Thats, all. [sic]
 
 One of the first questions that the INSTSDK.CMD script asks is:
 
@@ -34,30 +40,28 @@ One of the first questions that the INSTSDK.CMD script asks is:
 
 PCjs currently only simulates PC, XT and AT-class machines, not PS/2 machines, so you might be inclined to answer
 **NO** to that question, but in fact, the correct answer is **YES**, because the SDK doesn't actually care what kind
-of machine you're using.  It's asking that question only to determine whether you're using 3.5-inch or 5.25-inch SDK
+of machine you're using.  It's asking that question simply to determine whether you're using 3.5-inch or 5.25-inch SDK
 distribution diskettes.  These disks happen to be the 3.5-inch versions, so you must pretend you're using a PS/2.
 
-This SDK must have only been tested with the MS OS/2 installation disks included with the SDK, because if you install
+This SDK must have only been tested with the copy of MS OS/2 1.0 included with the SDK, because if you install
 it on IBM OS/2 1.0, the script will fail at the end, when it attempts to run LIBBUILD to build all the C runtime
-libraries.
+libraries.  Apparently, this is because IBM OS/2 1.0 creates an OS2INIT.CMD with PATH set to:
-
-The reason: IBM OS/2 1.0 creates an OS2INIT.CMD that sets PATH to:
 
 	C:\;C:\OS2;C:\OS2\INSTALL;
 
-so when INSTSDK.CMD updates PATH, it appends its own directories, resulting in:
+so when INSTSDK.CMD updates the PATH, it appends its own directories with a leading semi-colon, resulting in:
 
 	C:\;C:\OS2;C:\OS2\INSTALL;;C:\OS2SDK\TOOLS\BIN;C:\OS2SDK\TOOLS\PBIN
 
-and the "double semi-colon" apparently causes the PATH search to terminate prematurely, so the LIBBUILD program cannot
+and the "double semi-colon" apparently causes PATH searches to terminate prematurely, so the LIBBUILD program will
-be found.
+not be found.
 
-Fix the PATH in OS2INIT.CMD, then run the following command manually:
+To complete SDK installation, fix the PATH in OS2INIT.CMD, then type the following command:
 
 	for %i in (s m c l) do libbuild %i em %LIB%
 
-and *now* your MS OS/2 SDK will be properly installed.  You won't have the files from the missing **NETWORK** disk;
+and *now* your MS OS/2 SDK should be fully installed.  Well, not *quite* fully, because you won't have the files from
-specifically:
+the missing **NETWORK** disk; specifically:
 
 	IPCCALLS.DLL
 	IPCCALLS.LIB
@@ -69,4 +73,4 @@ specifically:
 	NMPIPE.H
 	README.DOC
 
-but you aren't likely to need those.
+but you aren't likely to need them.

docs/os2/README.md

@@ -11,4 +11,9 @@ For OS/2 1.0:
 
 * [Microsoft® Operating System/2 Programmer’s Toolkit](/docs/os2/microsoft/ptk/1.0/), March 1988
 
-Note that the above guide is a work-in-progress (converting the PDF text to Markdown).
+Note: the above guides are a work-in-progress (we're converting the PDFs to Markdown).
+
+OS/2 SDKs
+---
+
+* [Microsoft OS/2 SDK 1.02](/disks/pc/tools/microsoft/os2/sdk/1.02/)

docs/os2/microsoft/ptk/1.0/README.md

@@ -1,6 +1,6 @@
 ---
 layout: page
-title: "Microsoft OS/2: Welcome"
+title: "Microsoft OS/2 Programmer's Toolkit: Welcome"
 permalink: /docs/os2/microsoft/ptk/1.0/
 ---
 
@@ -36,3 +36,7 @@ the A: prompt:
 
 After running **setup**, make sure that you modify your PATH, INCLUDE, and LIB environment variables as directed by
 the program.
+
+---
+
+Note: the above guides are a work-in-progress (we're converting the PDFs to Markdown).