home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
C!T ROM 2
/
ctrom_ii_b.zip
/
ctrom_ii_b
/
OS2
/
SYSTEEM
/
BOOT2X
/
BOOTOS2.DOC
< prev
next >
Wrap
Text File
|
1993-06-21
|
13KB
|
276 lines
OS/2 V2 BOOT System Create Utility
Copyright IBM Corp. (C) 1992,1993
Program Property of IBM
The BOOTOS2 program is a utility that allows you to build a BOOTable OS/2 V2
system using an existing OS/2 V2 system. The BOOT system can be installed on
either Floppy Disks or a Hard Disk Partition.
There are three types of BOOT systems you can install:
Minimal : This is a basic OS/2 V2 system that supports a single OS/2 Full
Screen screen session. All 16 and 32-bit OS/2 Full Screen
applications are supported. While multitasking is supported, the
ability to switch between different processes is not. This BOOT
system can be installed on a single 3.5" 1.44M Floppy Disk or on a
2M Hard Disk partition.
PM : This is an OS/2 V2 system that supports any 16 or 32-bit OS/2 Full
Screen or PM application. Multitasking is supported, as is the
ability to switch betwen different processes. The WPS is present
as a single OS/2 Window. This BOOT system requires a minimum of a
6M Hard Disk partition.
WPS : This is an OS/2 V2 system that supports any 16 or 32-bit OS/2 Full
Screen or PM application. Multitasking is supported, as is the
ability to switch betwen different processes. The OS/2 WPS is
fully active and starts up with a number of default Folders and
system objects. This BOOT system requires a minimum of a 7M Hard
Disk partition.
Syntax: BOOTOS2 <SOURCE=drive:\path\>
<TARGET=drive>
<TYPE=PM|WPS>
<NLS(Country,KBD,CodePage)>
<2DISK>
<ABIOS>
<REXX>
<SWAP=drive:\path\>
<TRACE>
SOURCE= Normally BOOTOS2 will prompt you for the first two
OS/2 V2 Install Disks (Disk 0 and Disk 1) so it can
copy over certain system files; KEYBOARD.DCP, CONFIG.SYS,
VTBL850.DCP and SYSINSTX.COM. If you installed OS/2 V2
from a LAN or equivalent redirected source, you can use
the SOURCE argument to point to the base directory of the
redirected directory structure. BOOTOS2 will then look
for the following directories:
drive:\path\DISK_0\
drive:\path\DISK_1\
NOTE: These directories contain the 'file contents' found
on each corresponding Install Disk; they do *not*
contain the Disk Image file. You can create the
files for each directory by using the OS/2 XCOPY
command for each Install Disk.
TARGET= By default, BOOTOS2 will install the BOOT system on a
floppy disk in your A: drive. You can use the TARGET=
argument to specify an alternate Drive to install the
BOOT system on. This alternate drive can be another
floppy or a Hard Disk Drive. The value for TARGET drive
is a single Drive letter; A .. Z
TYPE=PM BOOTOS2 will install a BOOT System that will support
PM Applications. The BOOT System will be accessed as
a single OS/2 Windowed Command Prompt.
TYPE=WPS BOOTOS2 will install a BOOT system that will support
PM Applications. The BOOT System will be accessed
using the OS/2 WorkPlace Shell (WPS).
NLS By Default, BOOTOS2 will get information regarding the
NLS environment from the following CONFIG.SYS statements:
DEVINFO=KBD,xx,KEYBOARD.DCP : Default xx = US
COUNTRY=xxx,COUNTRY.SYS : Default xxx = 001
CodePage=xxx : Default xxx = 850
If your environment requires different values for the
above statements, you specify them via the NLS argument.
Please note that you must specify all three values.
NOTE: The statement is only valid for a TYPE=PM or
TYPE=WPS install. For a minimal install (the
default) the 'stripped' versions of the NLS
modules, KEYBOARD.DCP and VTBL850.DCP, are
used which do not support alternate values.
2DISK - If creating a BOOT Disk on a 3.5" 1.44M Drive A:, this
allows a 2-disk BOOT System to be created using Drive
B: in conjunction with A:. Drive B: can be either a
second 3.5" 1.44M or a 5.25" 1.2M drive.
- If creating a BOOT disk on a 5.25" 1.2M Drive A:, the
2DISK option is assumed; i.e. it is required.
REXX If room allows, support for REXX will be installed.
SWAP= For a TYPE=PM or TYPE=WPS install, the default value for
the SWAPPATH is the ROOT directory of the target BOOT
system. You can use this option to place teh Swap File in
a different directory.
TRACE Use this option to create a Trace of the Install Process.
A file called BOOTOS2.LOG will be created that will
contain a complete record of the requested BOOT System
Install process.
You must run BOOTOS2 from an existing OS/2 V2 system. The BOOTOS2 program
will analyze your system and create a BOOT system that is specific for it. For
example it will determine if your system supports features such as HPFS or SCSI
and add the appropriate support for it. Because of this, a BOOT disk created
for a specific workstation will not necessarily work correctly on a different
workstation.
If you install the BOOT system on a Hard Disk Drive, you'll probably want to
also install the OS/2 BOOT Manager and add the BOOT system to it.
Please note that the BOOT system installed with this release of BOOTOS2 does
not support either DOS or Windows. A future release of the program might do so
if enough users want it (and I figure out how).
The file BOOT20.ZIP contains the following files:
BOOTOS2.EXE * The OS/2 BOOT System Create Utilty for OS/2 V2.0
BOOTOS2.ABS * Short Abstract descriping the Function of SE20BOOT
BOOTOS2.DOC * Documentation for SE20BOOT
BOS2U20.INI * User INI file needed for OS/2 2.0
BOS2S20.INI * System INI file needed for OS/2 2.0
BOS2U21.INI * User INI file needed for OS/2 2.0+SP and OS/2 2.1
BOS2S21.INI * System INI file needed for OS/2 2.0+SP and OS/2 2.1
BOS2REXX.EXE * Stub Module for REXX Support
LICENSE.TXT * IBM License Agreement
Author:
Kennneth A. Kahn, IBM Poughkeepsie N.Y.
CompuServe - 71333,2526
Internet - KENKAHN@VNET.IBM.COM
IBM Mail - USIB25P9 at IBMMAIL
History:
08/92 : (v1.00)
- Initial release
03/93 : (V2.00)
- Fixed a problem where SE20BOOT was not recognizing a Floppy Disk Drive as a
Removable medium if no Disk was in it when the program first started. This
would cause SE20BOOT to install the wrong BOOT System, resulting in various
errors.
- Fixed problem with FORMAT by making it run Synchronously so if it Fails, an
error code will be returned.
- Added support for NLS Statement
- When COPYing file, added more meaningful error messages
- Fixed problem running BOOTOS2 from a ROOT Directory
- The temporary directory where files from the install disks are copied is
changed from the directory where BOOTOS2.EXE is executed from to a new
subdirectory based off of it named BOS2TEMP This will prevent BOOTOS2 from
overwriting and deleting system files when it is located on the \OS2
directory of the BOOT Drive.
- The INI files can now be located on your DPATH
- If the Target Drive is already formatted and contains data, the option to
run the Install without formating is given.
- Added special support for the Image Adapter/A
- All DLLs will be located via LIBPATH instead of looking automatically for it
in \OS2\DLL
- Changed TARGET= to allow for X or X:
- For a minimal install, a check will be made to see if there is enough room
left on the target drive to copy over extra files like CHKDSK, UHPFS and
OSO001.MSG
- Fixed problem where HPFS support was not added if the Target drive was
formatted for HPFS but the active system did not have HPFS support.
- Added support for 2-Disk BOOT System via 2DISK argument
- Added NLS support for FORMAT by querying system for the response character
to use: US default is 'Y'
- Added support for a BOOT system when active system is OS/2 2.0 with Service
Pack or OS/2 2.1
- Added support for REXX invocation argument
- Added support for ABIOS argument. This allows a user to explicitly specify
that the workstation supports ABIOS. This will allow the user to circumvent
the problem where "RAM Loadable" MicroChannel machines were being diagnosed
as not supporting ABIOS; causing the wrong set of system files to be loaded.
- Changed external name to BOOTOS2
- Added support for the TRACE invocation option
- Added support for the SWAP= invocation argument
05/93 : (V3.00)
- Updated BOS2U21 and BOS2S21 files to 2.1 GA levels
- Fixed 2DISK option. It will no longer return RC=4 after trying
to format B.
- Added support for SVGA; Copy over \OS2\SVGADATA.PMI
- Added code to copy over BASEDEV= invocation arguments
- Added code to copy over HELPMGR.DLL if room allows
- Added 2.1 support for 8514 by updating BOS2U21.INI with the proper values
for PM_DISPLAYS. This updating of BOS2U21 will be done for all display
types if necessary.
- Added support for HPFS386
- For a Disk Install, install sequence changed so the files SYSINST1 and
HARDERR are only copied if there is room. This frees up room for BIO
files required by certain MicroChannel machines that could not fit
otherwise.
*NOTE* If SYSINST1/HARDERR are not installed, then CAD will not work
- Enhanced install of BASEDEV drivers. For a single 1.44M BOOT Disk, only
those BASEDEV drivers that are needed for accessing DASD (.ADD) are copied.
Otherwise, if room allows, all BASEDEV drivers will be copied.
- Removed copying of DTM.DLL for a TYPE=PM or TYPE=WPS install. It wasn't
needed for anything as far as I could tell and at least one user complained
it wasn't installed on his base OS/2 system
- Support for the IBM IA/A is not working in this release. I am trying to get
help with this from the IA/A development team, but it might take a while. If
you have IA/A support installed on your active system when you run BOOTOS2,
you can try the following:
* On the \OS2\DLL directory of your active OS/2 2.x system, look for a file
named DISPLAY.OLD; this is the DISPLAY.DLL that was active before you ran
the IA/A INSTALL program. Copy this 'over' the DISPLAY.DLL that BOOTOS2
installed on the \OS2\DLL directory of your 'target' system.
* In the CONFIG.SYS of your target system, look for the following statements:
DEVICE=\OS2\XGARING0.SYS
DEVICE=\OS2\IAOS2RFS.SYS
SET VIDEO_DEVICES=VIO_yyy,VIO_IBMIAA
SET VIO_IBMIAA=DEVICE(BVHVGA,BVHIAA)
SET VIO_yyy=DEVICE(BVHVGA,BVHyyy)
* Change these to:
rem DEVICE=\OS2\XGARING0.SYS
rem DEVICE=\OS2\IAOS2RFS.SYS
SET VIDEO_DEVICES=VIO_yyy
rem SET VIO_IBMIAA=DEVICE(BVHVGA,BVHIAA)
SET VIO_yyy=DEVICE(BVHyyy)
* Do this *BEFORE* you IPL your Target BOOTOS2 System