Suggestions about OS/2 1.00 packages
Hi,
Seems to me that Microsoft OS2 SDK 1.02 (3.5-1.44mb)
https://winworldpc.com/download/3CFD516 ... 54D21A8599
is not clear what really is. I think, woud be better to explain that is Microsoft
OS/2 1.00 added with MS OS/2 SDK 1.02
Names of files in the package are confused too. Would be better to use the real
names of the volumes:
MSOS2INS.IMA to OS2INSTALL.IMA
MSOS2PGM.IMA to OS2PROGRAM.IMA
MSOS2SUP.IMA to OS2SUPP.IMA
MSOS2TK1.IMA to OS2TOOLKIT1.IMA
MSOS2TK2.IMA to OS2TOOLKIT2.IMA
MSOS2UT1.IMA to OS2UTILITY1.IMA
MSOS2UT2.IMA to OS2UTILITY2.IMA
MSOS2EX1.IMA to OS2EXAMPLE1.IMA
MSOS2EX2.IMA to OS2EXAMPLE2.IMA
MSOS2C1.IMA to OS2CBIN1.IMA
MSOS2C2.IMA to OS2CBIN2.IMA
MSOS2C3.IMA to OS2CLIB1.IMA
MSOS2C4.IMA to OS2CLIB2.IMA
MSOS2ASM.IMA to OS2MASM.IMA
A 15º disk named NETWORK is missing. Is possible to instal the SDK whithout
it, but is necessary to create an empty floppy disk with this volume name for
the conclusion of installation as INSTDSK.CMD look for it.
There are some good tips about in http://www.pcjs.org/disks/pcx86/tools/m ... /sdk/1.02/
Another suggestion is to complete the information that exists, besides applying the patch (may be easy with the python script patchos2.py from http://www.os2museum.com/files/patchos2.py), that is necessary, as a general rule, partition and format the virtual disk created with VirtualBox. IBM version 1.00 can create a partition with your fdisk but can not format. Microsoft version 1.00 can not even create the partition (fdisk). So, as a genaral rule, boot from any DOS floppy with fdisk and format and prepare the virtual disk before installation.
Another tip refers to the mouse. Microsoft version 1.0 works with a PS/2 mouse in VirtualBox with the MOUSEA05.SYS driver dated 02-20-89, 17462 bytes, from MS OS/2 1.10. IBM version 1.0 mouse works only with MOUSEA05.SYS, dated 8-08-88, 16,950 bytes from MS OS/2 1.05 SDK.
Seems to me that Microsoft OS2 SDK 1.02 (3.5-1.44mb)
https://winworldpc.com/download/3CFD516 ... 54D21A8599
is not clear what really is. I think, woud be better to explain that is Microsoft
OS/2 1.00 added with MS OS/2 SDK 1.02
Names of files in the package are confused too. Would be better to use the real
names of the volumes:
MSOS2INS.IMA to OS2INSTALL.IMA
MSOS2PGM.IMA to OS2PROGRAM.IMA
MSOS2SUP.IMA to OS2SUPP.IMA
MSOS2TK1.IMA to OS2TOOLKIT1.IMA
MSOS2TK2.IMA to OS2TOOLKIT2.IMA
MSOS2UT1.IMA to OS2UTILITY1.IMA
MSOS2UT2.IMA to OS2UTILITY2.IMA
MSOS2EX1.IMA to OS2EXAMPLE1.IMA
MSOS2EX2.IMA to OS2EXAMPLE2.IMA
MSOS2C1.IMA to OS2CBIN1.IMA
MSOS2C2.IMA to OS2CBIN2.IMA
MSOS2C3.IMA to OS2CLIB1.IMA
MSOS2C4.IMA to OS2CLIB2.IMA
MSOS2ASM.IMA to OS2MASM.IMA
A 15º disk named NETWORK is missing. Is possible to instal the SDK whithout
it, but is necessary to create an empty floppy disk with this volume name for
the conclusion of installation as INSTDSK.CMD look for it.
There are some good tips about in http://www.pcjs.org/disks/pcx86/tools/m ... /sdk/1.02/
Another suggestion is to complete the information that exists, besides applying the patch (may be easy with the python script patchos2.py from http://www.os2museum.com/files/patchos2.py), that is necessary, as a general rule, partition and format the virtual disk created with VirtualBox. IBM version 1.00 can create a partition with your fdisk but can not format. Microsoft version 1.00 can not even create the partition (fdisk). So, as a genaral rule, boot from any DOS floppy with fdisk and format and prepare the virtual disk before installation.
Another tip refers to the mouse. Microsoft version 1.0 works with a PS/2 mouse in VirtualBox with the MOUSEA05.SYS driver dated 02-20-89, 17462 bytes, from MS OS/2 1.10. IBM version 1.0 mouse works only with MOUSEA05.SYS, dated 8-08-88, 16,950 bytes from MS OS/2 1.05 SDK.
Comments