GetBoot and PutBoot, v1.0

Copyright 1993, Matthew J. Palcic (Team OS/2)
All rights reserved.

You are free to copy this software and distribute it to other users as
long as the archive file is distributed in its entirety with this text
file included in the archive.
---------------------------------------------------------------------------

GetBoot and PutBoot were written to transfer boot sectors from disks to
files and from files to disks.  This is useful for users that inadvertently
ran the DOS 'SYS' command and wiped out OS/2 boot information, or for users
who installed MS-DOS 6.0 over their OS/2 installation.

Syntax is available by running the programs without any parameters on
the command line.

If you only ran the 'SYS' command, but previously had Dual Boot working,
and the AUTOEXEC.BAT and CONFIG.SYS files are still OS/2 versions,
follow steps 2 through 4 below.  OS/2 should now boot.

 ******

The process to restore an OS/2 boot drive after installing MS-DOS 6.0:

(Note: This does not work while running OS/2, from either floppy or hard
disk.)

  1. Run the GETSEC.EXE program to make a copy of the DOS boot sector
     currently on your hard drive (the one DOS 6.0 made):

       GETSEC C: C:\OS2\SYSTEM\boot.dos

  2. Insert the 'OS/2 Installation' diskette in drive A:.

  3. Run the GETSEC.EXE program to read the boot sector from drive A:.

       GETSEC A: boot.os2

  4. Run the PUTSEC.EXE program to place the OS/2 boot sector on your
     hard drive.

       PUTSEC boot.os2 C:

  5. Copy BOOT.DOS to the \OS2\SYSTEM directory if you didn't store the
     file there in step 1 above.

  6. Copy the DOS versions of AUTOEXEC.BAT and CONFIG.SYS to the
     \OS2\SYSTEM directory, but name them 'AUTOEXEC.DOS' and
     'CONFIG.DOS'.

  7. Make the OS/2 versions of AUTOEXEC.BAT and CONFIG.SYS the current
     files in the root, and be sure to name them 'AUTOEXEC.BAT' and
     'CONFIG.SYS'.  If not, you will not have a proper OS/2 CONFIG.SYS
     file and OS/2 will not boot.

     If your OS/2 CONFIG.SYS file is totally gone, you can at least get
     back to the one that was created during the OS/2 installation
     process by copying C:\OS2\INSTALL\CONFIG.SYS to the root directory.
     Any changes you made to CONFIG.SYS are, of course, gone but you can
     at least boot OS/2.  If your AUTOEXEC.BAT is gone, you're on your
     own for that one.

  8. Run 'C:\OS2\BOOT /DOS' to switch to DOS mode.  (YOU MUST PERFORM
     THIS STEP TO PLACE THE CORRECT FILES IN \OS2\SYSTEM.)

  9. Run 'C:\OS2\BOOT /OS2' to switch back to OS/2 mode.

  The above process makes OS/2 Dual Boot work even if Dual Boot didn't
  work before you installed DOS 6.0 (i.e., pre-installed OS/2 machines).

Note: Be sure you don't leave a DOS version of COMMAND.COM in the root
      of your boot drive. In your DOS CONFIG.SYS file you must have the
      line:

         SHELL=C:\DOS\COMMAND.COM C:\DOS /P

      and in DOS AUTOEXEC.BAT you should have the line:

         SET COMSPEC=C:\DOS\COMMAND.COM

      Adjust C:\DOS to wherever you put your DOS files and be sure
      COMMAND.COM is in that directory.  Then remove the COMMAND.COM
      from the root.  Otherwise you might get 'Incorrect DOS version'
      when you try to open a DOS box.


------------------------------------------------------------------------
The author claims no responsibility for a drive becoming unusable or for
loss of data.  The nature of this program is to modify an important part
of the disk structure, and should be used only by someone who knows why
they are using the program.  Back up data before using any utility that
performs low-level disk operations.  Attempts have been made to be sure
the program modifies the disk properly, but freak things do happen.

Matthew J. Palcic
PO Box 1571
Fairborn, OH  45324-1571