OSOTBOOT - IMPROVING STARTUP PERFORMANCE FOR OS/2 WARP, OS/2 WARP
           CONNECT, AND OS/2 WARP FULLPACK
01/24/96

=======================================================================
    Improving Startup Performance for OS/2 Warp, OS/2 Warp Connect,
                      and OS/2 Warp Fullpack
=======================================================================

Please Read Entire Document for Full Explanation of Procedures
--------------------------------------------------------------

DESCRIPTION

This document provides ways to improve startup performance for OS/2 
Warp, OS/2 Warp Connect, and OS/2 Warp Fullpack.

RESOLUTION

1. Make sure the Windows Fast load option is disabled, especially if
   you have less than 6 MB of memory. This option loads a DOS and
   Windows session in the background during startup.

   a. Open OS/2 System.
   b. Open System Setup.
   c. Select WIN-OS/2 Setup.
   d. Deselect Fast load in WIN-OS/2 Window.

2. Do not archive your Desktop each time you restart your system.
   Archive only when you have completed customizing the Desktop.

   a. Point to an empty spot on the Desktop; then click mouse button 2.
      The Settings notebook appears.

   b. Click on the Archive tab.

   c. Click on the Create archive at each system restart button.

   Note: After restarting the system, repeat steps a through c,
         deselecting Create archive at each system restart.

3. Use multiple CONFIG.SYS files to load specific device drivers,
   depending on what you plan to do during a particular session.
   
   For example, the Internet Access Kit has several device drivers
   that, in low-memory systems, can use a lot of available free memory.
   This causes some swapping to occur. You can set up one CONFIG.SYS
   file with the device-driver statements remarked out, and another
   with the statements included. At startup, you can choose whether or
   not to load support for the Internet Access Kit.


Creating and Using Multiple CONFIG.SYS Files
--------------------------------------------
1. Copy the current CONFIG.SYS file to diskette.
   
   Note: You also can copy the file to the \OS2\BOOT subdirectory.
         If you do so, rename the file CONFIG.? (? can be any single
         alphabetic character except X, x, C, c, V, or v.) Be sure to
         make a note of the new name.

2. In the \OS2\BOOT subdirectory, create the new file, CONFIG.?, and
   customize it with the modifications you need. (If you copied to the
   subdirectory in step 1, you can modify the existing CONFIG.? file.)

3. Copy the CONFIG.? file to the current CONFIG.SYS file.

   Note: There are two ways to copy the CONFIG.? file. Read the next
         two topics and select the method that best suits your
         particular situation.


Replacing the CONFIG.SYS File Using the COPY Command
----------------------------------------------------
If you have only one CONFIG.? file, or if you don't plan to change
between CONFIG.? and CONFIG.SYS often, you might want to use the COPY 
command to replace the CONFIG.SYS file. The customized file then 
becomes the default CONFIG.SYS file. Type the following and press Enter 
(x is the directory where OS/2 is installed):

   COPY x:\OS2\BOOT\CONFIG.? x:\CONFIG.SYS

When you restart your system, the new CONFIG.SYS file will be used.


Replacing the CONFIG.SYS File Using a Batch File
------------------------------------------------
If you have several customized CONFIG.SYS files, using a batch file 
allows you to specify the customized file you want to use without 
entering multiple COPY commands. You simply change the ? character in 
the batch file, and then enter that character at the Recovery Choices 
screen. Here are the steps:

1. Create a batch file in the \OS2\BOOT subdirectory and name it
   ALTF1?.CMD, where ? is the character you used in the name of your
   CONFIG.? file.

2. Add the following command in the file (x is the directory where OS/2
   is installed):

      COPY x:\OS2\BOOT\CONFIG.? x:\CONFIG.SYS

3. Press Ctrl+Alt+Del to restart the system, and then Alt+F1 to display
   the Recovery Choices screen.

4. Press the ? character you used in the name of CONFIG.? file.

The system will continue the restart using the customized CONFIG.? file.

Note: If you enter a character at the Recovery Choices screen for which
      there is no corresponding ALTF1?.CMD batch file, the system will
      use the CONFIG.? file for the character you enter. If no such
      CONFIG.? file exists, the system will return to the Recovery
      Choices screen.

For more information, see your OS/2 documentation.

______________________________________________________________________
IBM disclaims all warranties, whether express or implied, including 
without limitation, warranties of fitness and merchantability with 
respect to the information in this document. By furnishing this 
document, IBM grants no licenses to any related patents or copyrights.  
Copyright (c) 1994, 1995 IBM Corporation. Any trademarks and product 
or brand names referenced in this document are the property of their 
respective owners. Consult your product manuals for complete trademark 
information.