pcjs/disks/pc/tools/microsoft/os2/sdk/1.02

layout	title	permalink
page	Microsoft OS/2 SDK v1.02	/disks/pc/tools/microsoft/os2/sdk/1.02/

Microsoft OS/2 SDK v1.02

This copy of the Microsoft OS/2 SDK (v1.02) was obtained from the WinWorld website. The copy is incomplete -- 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, in the OS2DOC folder, you'll find a READ.ME!, which includes some very useful information about the installation process:

The installation guide is confusing, can you give me three easy steps to
installing the SDK?

	Sure.  First, put the program diskette into your machine and reboot it.
	Follow the instructions.  If you have a new machine, first format the
	hard drive, then reboot with the program diskette.

	Second: copy the files \OS2DOC\INPUT.EXE and \OS2DOC\INSTSDK.CMD from the
	TOOLKIT diskette to the root of your hard drive.  Run the program INSTSDK
	and answer its questions.

	Thats, all.

One of the first questions that the INSTSDK.CMD script asks is:

Are you installing MS OS/2 SDK on a PS/2 machine?

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 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 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.

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:

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 be found.

Fix the PATH in OS2INIT.CMD, then run the following command manually:

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; specifically:

IPCCALLS.DLL
IPCCALLS.LIB
IPCTEST.C
LANMAN.INI
MAILSLOT.H
MAKEFILE
NAMPIPE.SYS
NMPIPE.H
README.DOC

but you aren't likely to need those.