                             B O O T S E T 
                       --------------------------

                    Version 0.059 - March 9, 1996


                       (c) Copyright  1996-1996
                         Software Technologies
===============================================================================
THESE PROGRAMS ARE SHAREWARE AND AS SUCH YOU ARE PERMITED TO DISTRIBUTE THEM
WITHOUT CHARGE PROVIDED THAT ALL FILES (EXCLUDING KEY FILES) ARE UNMODIFIED
AND DISTRIBUTED TOGETHER. DUE COPYRIGHT MUST BE OBSERVED. THESE PROGRAMS ARE
PROVIDED AS IS WITHOUT ANY WARRANTY, EXPRESSED OR IMPLIED, INCLUDING BUT NOT
LIMITED TO FITNESS FOR A PARTICULAR PURPOSE.

ALL TRADEMARKS AND SERVICE MARKS ARE THE PROPERTY OF THEIR RESPECTIVE OWNERS.
===============================================================================

------ NOTE: This is beta Software. It is NOT thoroughly tested! ------


What is BootSet ?
------------------
BootSet allow you to run batchfiles (batchcommands) during the OS/2 boot- 
sequence. BootSet is normally run before the graphic part of OS/2 (PM/WPS) is
loaded and therefore allows you to perform taskt that is not possible when
PM/WPS is loaded, for example replace system .DLL's and drivers.

Optionally you may use BootSet to select between different sets of startup
files using the reboot featur of BootSet.


How does BootSet compare with the Alt-F1 feature of Warp ?
-----------------------------------------------------------
BootSet is similar to the Alt-F1 feature of OS/2 Warp but is not restricted
to Warp. BootSet should (but is not tested to) run with both OS/2 2.0 and
OS/2 2.1 (and Warp).

I believe that the Alt-F1 feature of Warp has its ups and its down:

+:    -Its run before CONFIG.SYS is loaded and that makes it possible to
       switch CONFIG files without rebooting.
      -Its availible on all Warp systems without any extra installation.
      -There is no extra cost involved!

-:    -Its default setting requires you to press a specific key (Alt-F1) to
       activate the function.
      -Since the Alt-F1 feature starts early in boot you cannot use REXX in
       your batch files.
      -Your batch files must have strange names (ALFTF1A.CMD) and you must
       handle a lot of files in the OS2 directory.


Requirements:
--------------
BootSet should require IBM OS/2 2.0 or later although it has not been tested 
with anything else than OS/2 Warp Connect.
To be able to reboot BootSet its also required that the DOS.SYS device driver 
is loaded. This is normally done when installing the DOS support in OS/2.


Installation:
--------------
Install BootSet in a directory of your choice. You may install BootSet in any
directory that you wish. The only files that is needed is the .EXE file 
(BOOTSET.EXE) and its .INI file normally called BOOTSET.INI (but it may have
any name and any extention). You must also add the following line in your
CONFIG.SYS file:

CALL=C:\BOOTSET\BOOTSET.EXE C:\BOOTSET\BOOTSET.INI

Though you should change to a directory of your choice and the name
of your .INI file.

Please note that you must include the full path for both the .EXE file and for
the .INI file.

The position of this line in your CONFIG.SYS file i arbitary since OS/2 does
not load the lines in order but runs them in its own specific order. Note that
the lines starting with CALL are among the last to run.


Settings file:
----------------
The settings file is build in a specific order. There is a example included in
this package (BOOTSET.INI). Please refer to it when reading this text.

The settings file contains of a fixed header and after that the menu items are
listed. Following here is a description of the example .INI file (BOOTSET.INI).
Please note that all lines in the header must be present even if you do not use
them or they are not implemented in this version.

Line	Text		Explanation
====    ====            =============================================
01	0		Waitscreen (0=off, 1=on), not in this version
02	0		Foreground color (0-15), not in this version
03	0		Background color (0-15), not in this version
04	5		Timeout in seconds, Time Bootset will wait for keypress
05	0		For future enhancement
06	0		For future enhancement
07	0		For future enhancement
08	0		For future enhancement
09	0		For future enhancement
10	4		Number of menu items (a maximum of 255)

The rest of the file contains of the sections (one for each menu item). The number
of sections shall be that same as the number of menu items specified above.
Each section contains of the menu text (shown in bootset menu), the number of lines
in the batchfile that is to be run when this menu item is selected, a reboot flag
and the lines of the batch file. 

Line	Text			Explanation
====    ====            	=============================================
11	Start cmd-line		Menu text
12	0			Reboot after this menuitem is run. 0=no reboot, 1=reboot
13	1			Number of lines i "batch file", (a maximum of 100)
14	CMD.EXE			"Batch file", linelength maximum 255 characters
15	Start with network      Menu text
16	1			Here we reboot after menu item is run
17	5			Five lines in this batchfile
18	COPY C:\SAVE\CONFIG.NET	C:\CONFIG.SYS
19	COPY C:\SAVE\AUTOEXEC.NET C:\AUTOEXEC.BAT
20	COPY C:\SAVE\STARTUP.NET C:\STARTUP.CMD
21	COPY C:\SAVE\PROTOCOL.SAV C:\IBMCOM\PROTOCOL.INI
22	COPY C:\SAVE\IBMLAN.SAV C:\IBMLAN\PROTOCOL.INI
23	Start standalone        Menu text
24	1			Here we reboot after menu item is run
25	3			Five lines in this batchfile
26	COPY C:\SAVE\CONFIG.STD	C:\CONFIG.SYS
27	COPY C:\SAVE\AUTOEXEC.STD C:\AUTOEXEC.BAT
28	DEL C:\STARTUP.CMD
29	Backup .INI & desktop   Menu text
30	0			No reboot
31	11			Eleven lines in this batchfile
32	ATTRIB -r -s C:\OS2\OS2*.INI
33	XCOPY C:\CONFIG.SYS C:\CFG\DESKTOP /V
34	XCOPY C:\AUTOEXEC.BAT C:\CFG\DESKTOP /V
35	XCOPY C:\OS2\*.INI C:\CFG\DESKTOP\OS2 /V
36	XCOPY C:\OS2\MDOS\WINOS2\*.INI C:\CFG\DESKTOP\WINOS2 /V
37	XCOPY C:\IBMCOM\PROTOCOL.INI C:\CFG\DESKTOP\NET /V
38	XCOPY C:\IBMLAN\IBMLAN.INI C:\CFG\DESKTOP\NET /V
39	XCOPY C:\Desktop C:\CFG\DESKTOP\Desktop /V /S /E
40	XCOPY "C:\Maintenance Desktop" "C:\CFG\DESKTOP\Maintenance Desktop" /V /S /E
41	XCOPY C:\Nowhere C:\CFG\DESKTOP\Nowhere /V /S /E
42	XCOPY C:\Nowhere1 C:\CFG\DESKTOP\Nowhere1 /V /S /E


Future enhancement:
-------------------

+ Installation program
  Command line for machines without PM
  PM version for "normal" use

+ PM program to create and edit the .INI file

+ Reboot without the need for DOS.SYS

+ A mode where BootSet just shows a small notice to press B if you want
  to load BootSet instead of showing all at ones.


If you look for other features dont hesitate to contact us via email
	mail@jmast.se

--------------------------------------------------------------------------------

License information:

This copy of BootSet is provided with a limited evaluation license not 
exceeding 21 days in duration from first use. Unregistered use beyond this 
evaluation period is in violation of this license, as is use for any 
commercial purpose prior to registration.

If you find BootSet useful and would like to register this software, a 
license fee is payable. Registration of this software will entitle you 
(or your corporation) to unlimited use of current and subsequent releases 
of the product(s).

Two license types are available: individual and corporate. An individual 
license is for the sole use of the named individual. A single corporate 
license entitles use by all employees/members of the named corporation/
institution.

Please indicate the license type required.


How to register BootSet:

   - Since this program is still in beta you must contact us to be able
     to register this program. Please contact us by email/mail or fax.

   - Our adress is:
     Software Technologies
     P.O Box 2345
     S-403 15  GOTHENBURG
     SWEDEN
     email.	mail@jmast.se
     Fax.	46-(0)31-195260


Pricing:

        Single user,                            $  25 
        Corporate                               $ 500 
        
        Please add $10 for handling and shipping.
--------------------------------------------------------------------------------
