.max 600
.. ............................................................................
.. ............................................................................
..
..  SCIN Installation Text - System/Partition Commander
..
..    Orange  - \003     Green Backgd/White   - \023   (BARTEXT)
..    White   - \004    Cyan Backgd/White    - \017  
..    Green   - \018     Red Backgd/White     - \005   (ATTENTION)
..    Cyan    - \002     Magenta Backgd/White - \020   (BARWARNING)
..    Magenta - \006  
..    Red     - \021   (BADHIGH)
..
..    Tabs set to 4, Right margin 74
..    To use shaded titles, surround title with \015 
..
..  General Commands
..    .anykey               Return after any key pressed
..    .clear                Clear display
..    .continue             Return after user presses any key
..    .errbell              Error tone
..    .max ###              Maximum message number allowed
..    .menu #1 #2 #3 " "    Menu selection, #1=line (-1=auto), #2=column,
..                            #3=msg # if selected (-1 = no msg connection)
..    .msg ###              Message number
..    .scroll               Scrollable message (can use colors above)
..    .scrollend            End of Scrollable message text
..    .select               Prompt user to select one menu item
..    .succbell             Sucess tone
..    .title att " "        Display Title with attribute.  If a shaded
..                            title is needed, surround the text with
..                            \015 characters (i.e. " test ")
..    .warnbell             Warning tone
..
..  Non-Scroll Block - This will auto-center each line of text
..    .bline att " "        Display text with attribute att at bottom line
..    .graphics att         Characters above 0x80 use this att
..    .line ## att          Next line starts at ## with attribute
..    .margin ##            Set left margin and skip auto-center function
..    .shade ## att " "     Make a shaded title at line ## with attribute
..
..  #define					used to store constant values 0-255 for #if
..                            (msgcomp handles up to 40)
..  #if						conditional based on command line variables
..  						  with the -Dxxx=y where xxx is the name and
..  						  y is the value 0-255.  (5 varibles max)
..  						  Parens are ignored, and does not support
..  						  nested parens. #if statements can be nested.
..  						  Conditions include ==, !=, >, <, >=, <=
..  #else					relates to #if
..  #endif					closure to #if
.. ..........................................................................
..
.. Defines
..
.. BUILD	(Build type)
#define BT_USA 				0	// US Normal                SC/SF
#define BT_JAPAN			1 	// Japan Normal             SJ
#define BT_NO_PASSWORD		2   // US Normal no Passwords   SX
#define BT_JAPAN_UP 		3 	// Japan Update only v3     SJ
#define BT_US_DEMO		    4   // US Demo only             SD
#define BT_UK				5   // U.K. version             HK
#define BT_FRENCH		    6	// French version           HF
#define BT_GERMAN			7   // German version           HD/ED
#define BT_LITE_NO_OS2		8   // Lite, no OS/2            SL
#define BT_PC				9   // Personal Edition         PC
#define BT_PC5      	    10  // PC v6    				PCV
#define BT_DW       	    13  // DriveWorks   			DW6
#define BT_LITE_PCA			16  // Lite, PC Answers         SP
#define BT_OEM_BE			17  // SC OEM, Be               BE
#define BT_SC98				31  // Windows 98 Edition       WC
#define BT_SECURITY			32  // Security Commander       SE
#define BT_SCDTRIAL			63	// Trial SCD (Time-bomb)	YX
#define BT_TRIAL			64  // Trial SC			        ST
#define BT_OEM_PHT			65  // SCD OEM, PHT				PH
#define BT_OEM_JPNLGT       66  // SCD OEM, JPN Logitech    LG
#define BT_OEM_L5			67  // SCD OEM, LASER5 Linux	LS
#define BT_OEM_MDK			68	// SCE OEM, Mandrake Linux	MK
#define BT_OEM_AL 			69	// SC OEM, ArcLinux         SCARC
#define BT_SC2000		    70  // SC2000					SC2K
#define BT_SC7			    71  // SC7						SC7
..
.. SERIES (Product category)
#define PC		 1		// Partition Commander v1
#define SC 		 2		// System Commander v3
#define SCW98    3		// System Commander Windows 98 edition
#define SCD 	 4		// System Commander Deluxe v4, most OEMs
#define SC2K 	 5		// System Commander 2000
#define PC5 	 6		// Partition Commander v6 & DriveWorks
#define SC7 	 7		// System Commander 7
..
.. LANG (Language)
#define ENGLISH				0
#define JAPAN				1
#define GERMAN				2
#define FRENCH				3
#define UK    				4
.. ............................................................................
.. ............................................................................
..
..  First Level Menus
..
.. ............................................................................
.. ............................................................................
.. UK version
.msg 10
.clear
.title BARTEXT " Troubleshooting "
.menu -1 -1 40 "START HERE FIRST"
.menu -1 -1 20 "Problems with a specific OS"
.menu -1 -1 21 "Boot time error messages and problems"
.menu -1 -1 22 "SCIN and Installation error messages"
#if SC_DELUXE == 1
.menu -1 -1 126 "OS Wizard startup problems"
#endif
.menu -1 -1 23 "Problems without error messages"
.menu -1 -1 24 "General Information"
.menu -1 -1 -1 "Return to previous menu"
.select
.. ............................................................................
.. All others version
.msg 11
.clear
.title BARTEXT " Troubleshooting "
.menu -1 -1 40 "START HERE FIRST"
.menu -1 -1 20 "Problems with a specific OS"
.menu -1 -1 21 "Boot time error messages and problems"
.menu -1 -1 22 "SCIN and Installation error messages"
.menu -1 -1 23 "Problems without error messages"
.menu -1 -1 25 "General Information"
.menu -1 -1 -1 "Return to previous menu"
.select
.. ............................................................................
.. ............................................................................
..
..  Second Level Menus
..
.. ............................................................................
.. ............................................................................
.msg 20
.clear
.title BARTEXT  " Problems with a Specific OS "
.menu -1 -1 30  "DOS Messages"
#if BUILD != BT_SC98
.menu -1 -1 31  "OS/2 Messages"
#endif
.menu -1 -1 32  "Windows 95/98/Me"
#if BUILD != BT_SC98
.menu -1 -1 33  "Windows NT/2000/XP"
.menu -1 -1 34  "Unix"
#endif
.menu -1 -1 -1  "Return to previous menu"
.select
.msg 21
.clear
.title BARTEXT  " Boot time error messages and problems "
.menu -1 -1 200 "Message 'BOOT ##' and hangs"
.menu -1 -1 201 "System fails to boot up"
#if BUILD != BT_SC98
.menu -1 -1 202 "Possible defective boot record"
#endif
.menu -1 -1 203 "Disk error"
.menu -1 -1 204 "Slow booting"
.menu -1 -1 205 "No Operating System Found"
.menu -1 -1 -1  "Return to previous menu"
.select
.. ............................................................................
.msg 22
.clear
.title BARTEXT  " SCIN/Installation error messages "
.menu -1 -1 210 "Partition Table Analysis Failed"
.menu -1 -1 211 "Partition Table Analysis Warning"
.menu -1 -1 212 "Unable to read Drive Parameters"
.menu -1 -1 213 "Unable to read Partition Table on Drive n"
.menu -1 -1 214 "DOS Boot Record Checks"
.menu -1 -1 215 "File Access Verification Failed"
.menu -1 -1 216 "Virus Warning"
.menu -1 -1 217 "Unable to Write MBR"
#if BUILD != BT_SC98  && BUILD != BT_LITE_PCA
.menu -1 -1 226 "System Transfer Error Messages"
#endif
.menu -1 -1 -1 "Return to previous menu"
.select
.. ............................................................................
.msg 23
.clear
.title BARTEXT " Problems without error messages "
#if BUILD != BT_SC98 && BUILD != BT_LITE_PCA
.menu -1 -1 220 "SC fails to detect a new OS installation"
#endif
.menu -1 -1 221 "OS selection menu does not appear after reboot"
.menu -1 -1 222 "OS selection menu appears again after selection"
.menu -1 -1 223 "Screen colors unreadable"
#if BUILD != BT_SC98
.menu -1 -1 224 "Disk compression software issues"
#endif
.menu -1 -1 225 "Unpredictable/flaky behavior"
.menu -1 -1 204 "Slow booting"
.menu -1 -1 -1  "Return to previous menu"
.select
.. ............................................................................
.msg 24
.clear
.title BARTEXT " General Information "
.menu -1 -1 35 "Common Questions and Answers"
.menu -1 -1 52 "Technical Support - Other Companies"
#if (BUILD != BT_OEM_PHT) && (BUILD != BT_OEM_L5) && (BUILD != BT_OEM_MDK) && (BUILD != BT_LITE_PCA) && (BUILD != BT_OEM_AL)
.menu -1 -1 51 "Upgrading to the Latest Version"
.menu -1 -1 50 "V Communications - Customer Support"

#else
.menu -1 -1 50 "Customer Support"
#endif
.menu -1 -1 -1 "Return to previous menu"
.select
.. ............................................................................
.msg 25
.clear
.title BARTEXT " General Information "
.menu -1 -1 35 "Common Questions and Answers"
.menu -1 -1 52 "Technical Support - Other Companies"
.menu -1 -1 51 "Upgrading to the Latest Version"
.menu -1 -1 49 "V Communications - Customer Service"
.menu -1 -1 -1 "Return to previous menu"
.select
.. ............................................................................
.. ............................................................................
..
..  Third Level Menus
..
.. ............................................................................
.. ............................................................................
.msg 30
.clear
.title BARTEXT  " DOS Messages "
.menu -1 -1 100 "Can't Access Drive"
.menu -1 -1 100 "Invalid Drive/Media Type"
.menu -1 -1 102 "COMMAND.COM missing/invalid/wrong version"
.menu -1 -1 103 "Incorrect DOS version"
.menu -1 -1 104 "Your current OS on drive C is not DOS"
.menu -1 -1 105 "Incorrect version of DBLSPACE.BIN"
.menu -1 -1 106 "MSDOS5.0 appears as the OEM name for MS-DOS 6"
.menu -1 -1 107 "DOS installation fails because of existing DOS"
.menu -1 -1 108 "SYS program fails with message"
.menu -1 -1 -1  "Return to previous menu"
.select
.. ............................................................................
.msg 31
.clear
.title BARTEXT " OS/2 Messages "
.menu -1 -1 110 "Drive Invalid"
.menu -1 -1 110 "Can't Find COUNTRY.SYS"
.menu -1 -1 112 "OS/2 fails to boot"
.menu -1 -1 111 "Installation Notes"
.menu -1 -1 -1  "Return to previous menu"
.select
.. ............................................................................
.msg 32
.clear
.title BARTEXT  " Windows 95/98/Me "
.menu -1 -1 125 "VFAT Device Initialization Failed"
#if BUILD != BT_SC98
.menu -1 -1 120 "Warning SU-0012 (OS/2 or NT will no longer work)"
.menu -1 -1 121 "Warning SU-0015 (NT will no longer work)"
.menu -1 -1 122 "Warning SU-0016 (OS/2 will no longer work)"
#endif
.menu -1 -1 123 "Windows 95/98 goes to DOS prompt (no graphics)"
.menu -1 -1 105 "Incorrect version of DBLSPACE.BIN"
#if BUILD != BT_SC98
.menu -1 -1 124 "Installation notes"
#endif
.menu -1 -1 -1  "Return to previous menu"
.select
.. ............................................................................
.msg 33
.clear
.title BARTEXT " Windows NT/2000/XP "
.menu -1 -1 130 "Fatal System Error"
.menu -1 -1 130 "Missing File <winnt root> \system32\ntoskrnl.exe"
#if BUILD != BT_LITE_PCA
.menu -1 -1 131 "Windows NT 4.0 with NT 3.x problems"
#endif
.menu -1 -1 132 "Installation Notes"
.menu -1 -1 -1 "Return to previous menu"
.select
.. ............................................................................
.msg 34
.clear
.title BARTEXT  " Unix Problems "
.menu -1 -1 140 "SCO Unix"
.menu -1 -1 140 "UnixWare"
.menu -1 -1 141 "Linux"
.menu -1 -1 -1  "Return to previous menu"
.select
.. ............................................................................
.msg 35
.clear
.title BARTEXT  " Common Questions and Answers "
.menu -1 -1 150 "How do DOS and Windows 95/98/Me assign drive letters?"
.menu -1 -1 151 "Why can't DOS or Windows 95/98/Me boot from a 2nd drive?"
#if BUILD != BT_SC98
.menu -1 -1 152 "What are the problems with changing drive positions?"
#endif
.menu -1 -1 153 "Will DEFRAG effect System Commander?"
.menu -1 -1 154 "What are the steps to back up System Commander?"
.menu -1 -1 155 "How can System Commander be removed?"
.menu -1 -1 156 "How do you make a Boot Diskette?"
.menu -1 -1 -1  "Return to previous menu"
.select
.. ............................................................................
.. ............................................................................
..
..  Help Blurbs
..
.. ............................................................................
.. ............................................................................
.msg 40
.clear
.scroll
.title Troubleshooting Basics

Use this help facility before you call for technical support. You will
find most problems can be quickly resolved using this information.

The information is organized along possible messages that come from
System Commander or appear from the selected operating system.  Problems
that have no messages appear in separate sections.

To view a complete index of all problems, press F2 at any time.  While
in the index menu, a letter A-Z will move you instantly to topics which
begin with that letter.  Press Enter to go see the topic, and
Esc to switch back to the point where you pressed F2.

To print a multi-page folder of information or send the information to a
file, press PrintScrn while viewing the information.  You will be
prompted for the desired action.

Some installation difficulties are caused by disk file system integrity
problems.   BEFORE YOU DO ANYTHING ELSE  You should perform the
following steps to insure the integrity of your hard disk:

   1) Run SCANDISK or CHKDSK.  If errors are found, correct the
      errors and see if the problems disappear.

   2) Scan for viruses. Recent experience has shown that the presence
      of many common viruses trigger strange problems, particularly when
      partitioning a disk.
#if BUILD == BT_LITE_PCA

Please note that some troubleshooting information may not apply to this
Lite Edition.  Lite edition only supports OSes installed in primary
partitions on the first drive.
#endif
.scrollend
.. ............................................................................
#if LANG == UK
.msg 49
.clear
.scroll
.title V Communications - Customer Service, UK

If you can not resolve your problem, please have the following infor-
mation available when calling for assistance:

        - Product version and serial number
        - Any error messages that appear

To help us get you an answer as quick as possible, please be at
your computer.  If you have a problem with a message on-screen,
be at the point where the message appears.

Please note that we can only help resolve problems that relate directly
to this product. We are unable to assist with other companies products,
Windows or DOS.

	 Web site: www.guildsoft.co.uk/vcom

     Tech Support email: support@guildsoft.co.uk
	 UK Tech Support phone: 0906 470 1707 (60p per minute charge)

	 Support phone (outside UK) +441752 895100

Calls may be monitored for training purposes.  Phone hours are from
9.00 am to 5.00 pm Monday to Friday, exlcuding Bank holidys.


.scrollend
#endif
.. ............................................................................
.msg 50
.clear
.scroll
#if (BUILD == BT_OEM_PHT) || (BUILD == BT_OEM_L5) || (BUILD == BT_OEM_MDK) || (BUILD == BT_OEM_AL)
.title Customer Support

If you are unable to resolve your issue, please have the following
information available when calling for assistance:

        - The product serial number from About
        - Any error messages that appear

To help us get you an answer as quickly as possible, please be at your
computer.  If you have a problem with a message on-screen, be at the
point where the message appears.

Please note that we can only help resolve problems that relate directly
to System Commander. We are unable to assist with other companies
products, DOS, or Windows issues.

For standard support included with this OEM version of System
Commander, please contact the Linux vendor's support desk or e-mail.

Paid support is also available from V Communications. The cost per
incident is currently $29.95. You can reach V Communications paid
support line at 408-965-4012. Please have your credit card ready.
We accept Visa, MasterCard and Amex.
#else

#if BUILD == BT_LITE_PCA
.title Paid Customer Support

This Lite edition does not offer any free technical support. Visit
our web site at WWW.V-COM.COM for free services such as FAQs and other
important information.

If you are unable to resolve your issue, we do offer paid phone support
from our US offices, from 9am to 5pm PST M-F.  Please have the following
information available when calling for assistance:

        - The product serial number from About
        - Any error messages that appear

To help us get you an answer as quickly as possible, please be at your
computer.  If you have a problem with a message on-screen, be at the
point where the message appears.

Please note that we can only help resolve problems that relate directly
to System Commander. We are unable to assist with other companies'
products, Windows, or other OSes.

Paid support cost per incident is currently $29.95. You can reach V
Communications paid support line at 408-965-4012. Please have your credit
card ready.  We accept Visa, MasterCard and Amex.

You can also purchase the full System Commander 2000 product, which
includes 90 days of free phone and email technical support.  SC2000 is
available at major retailers, or directly from the V Communications web
site at WWW.V-COM.COM.
#else
.title V Communications - Customer Support

If you are unable to resolve your issue, please have the following
information available when calling for assistance:

        - System Commander version and serial number
        - Any error messages that appear

To help us get you an answer as quick as possible, please be at
your computer.  If you have a problem with a message on-screen,
be at the point where the message appears.

Please note that we can only help resolve problems that relate directly
to System Commander. We are unable to assist with other companies
products, DOS, or Windows.

If you wish to contact us by mail, e-mail or FAX, please run SCOUT
and include the SCOUT.TXT file.  It has your serial number and version,
along with key information about System Commander.  Please include a
description of the problem you are having.  Also include an address and
telephone/Fax number where we can contact you.  We normally respond
within 2 business days by return fax or email.  For immediate response,
we recommend calling our technical support number.

Contact us at:

   V Communications, Inc.
   2290 North First St., Suite 101
   San Jose, CA  95131  USA

#if BUILD == BT_SC98
   Customer Support:    408-965-4012
#else
   Customer Support:    408-965-4018
#endif
   Fax:                 408-965-4014

   E-mail               support@v-com.com
   Web site             www.v-com.com
#endif
#endif
.scrollend
.. ............................................................................
#if (BUILD != BT_OEM_PHT) && (BUILD != BT_OEM_L5) && (BUILD != BT_OEM_MDK) && (BUILD != BT_LITE_PCA) && (BUILD != BT_OEM_AL)
.msg 51
.clear
.scroll
.title Upgrading to the Latest Version

Registered System Commander users may upgrade to the latest version for
a modest charge.  Registered users are normally notified about new
releases.

.scrollend
#endif
.. ............................................................................
.msg 52
.clear
.scroll
.title Technical Support - Other Companies

Product          Company           Telephone     E-Mail/Web Site

#if BUILD != BT_SC98
MS-DOS           Microsoft         206-646-5104  www.microsoft.com
Open Server      SCO               800-347-4381  support@sco.com
OpenStep         Apple (NeXT)      650-366-0900  www.next.com
OS/2             IBM               800-992-4777  askibm@info.ibm.com
PC-DOS           IBM               800-992-4777  askibm@info.ibm.com
Solaris          Sun Microsystems  310-348-6070  www.sun.com
TurboLinux       TurboLinux        650-244-7777  support@turbolinux.com
Windows 3.X      Microsoft         206-637-7038  www.microsoft.com
Windows NT/2K/XP Microsoft         206-635-7018  www.microsoft.com
Windows 95/98/Me Microsoft         206-635-7000  www.microsoft.com
UnixWare         SCO (Novell)      800-347-4381  support@sco.com
#else
MS-DOS           Microsoft         206-646-5104  www.microsoft.com
PC-DOS           IBM               800-992-4777  askibm@info.ibm.com
Windows 3.X      Microsoft         206-637-7038  www.microsoft.com
Windows NT/2K/XP Microsoft         206-635-7018  www.microsoft.com
Windows 95/98/Me Microsoft         206-635-7000  www.microsoft.com
#endif

   (Products are trademarks or registered trademarks of the respective
    companies)

.scrollend
.. ............................................................................
.msg 53
.anykey
.scroll
#if BUILD != BT_SC98
                           Ŀ
                            Installation 
                           
      What will happen:

                1  Installs all necessary files

                2  Retains any prior options

                3  Checks and warns you of any system problems

                4  Saves key information for the Uninstall option

#if BUILD == BT_PC || BUILD == BT_PC5
                5  Asks if you wish to install System Commander
#else
                5  Activates System Commander
#endif

  This installation will not affect your current partitions, OSes,
  nor will it change existing configuration files.

  It installs in less than 5 minutes and you can exit at any time by
  pressing Ctrl-C.
#else
   System Commander is ready to prepare your system for a safe Windows 98
   upgrade installation!  If you are not ready to install Windows 98 you
   should exit now (press Ctrl-C), and return when you are ready.

   IMPORTANT - You must use an Upgrade version of Windows 98.  Other
   versions will not work and may erase your existing Windows files.

   The installation of Windows 98 may take 30 minutes or more, and part
   of the System Commander installation may take a few minutes to save
   existing Windows files.  Please reserve enough time for this.

   Installation Overview
	 Step 1  Checks and warns you of any system problems, and saves
				key information for our uninstall option.

     Step 2  Makes a duplicate set of key Windows files.

     Step 3  Saves the system configuration files.

	 Step 4  Install your Windows 98 Upgrade!
#endif
.scrollend
.. ............................................................................
.msg 54
.clear
.shade 5 BARTEXT " License and Warranty "
.margin 6
.line 7 NORMAL
The License and Warranty appears in the user's manual and can also
be reviewed here.

This product is protected by both United States copyright law and
international treaty provisions. It is not shareware, and may not
#if (BUILD == BT_OEM_PHT) || (BUILD == BT_OEM_L5) || (BUILD == BT_OEM_MDK) || (BUILD == BT_LITE_PCA) ||  (BUILD == BT_OEM_AL)
be distributed in any form, other than directly from this authorized
vendor.
#else
be distributed in any form, other than by purchase directly from
V Communications, or an authorized reseller.
#endif

Copyright (C) 1993-2004  V Communications, Inc. All Rights Reserved.

.menu 18  12 -1 "Review License"
.menu 19  12 -1 "Yes, I agree to the license terms"
.menu 20  12 -1 "No, I'll exit now"
.select
.. ............................................................................
#if BUILD == BT_JAPAN
.msg 56
.clear
.scroll
.title V Communications/SoftBoat - Customer Service

If you can not resolve your problem, please have the following infor-
mation available when calling for assistance:

        - System Commander version and serial number
        - Any error messages that appear

To help us get you an answer as quick as possible, please be at
your computer.  If you have a problem with a message on-screen,
be at the point where the message appears.

Please note that we can only help resolve problems that relate directly
to System Commander. We are unable to assist with other companies
products, DOS, or Windows.

If you wish to contact us by mail, or FAX, please include your version
and serial number of System Commander along with a description of the
problem you are having.  Also include an address and telephone/Fax number
where we can contact you.

Contact us at:

   SoftBoat

   Customer Support:    03-3219-2868
   Fax:                 03-3293-4710

   Web site             www.bekkoame.or.jp/~lifeboat/product/sc/sc.html

.scrollend
#endif
.. ..........................................................................
.msg 57
.clear
.shade 10 BARTEXT " Installation Preparation "
.bline MESSAGE " "
.line 13 NORMAL
Please wait.
.. ............................................................................
.msg 60
.scroll
.title Partition Diagnostic

The Partition Diagnostic looks for problems in the partition table.
White and blue values are normal. Any abnormalities are shown in orange
magenta or red.

   Orange   Warning - The data is not correct, but it will not
                      cause any problems with System Commander.

   Magenta  Error -   The data is wrong, and may cause a problem
                      launching any OS installed in that partition.

   Red      Error -   The data is wrong, and may cause a problem
                      launching any OS installed in that partition.
                      It may also prevent System Commander from
                      operating.

   See "Warning and Errors" below for more information

 What is the Partition Table? 

The partition table defines different areas of a disk drive.  For
example, a system using DOS or Windows 95/98/Me with a single physical
drive could split the drive for a C drive and a D drive.  The location
and size of these "virtual" drives is specified by data in the partition
table.

Many operating systems have their own partition identifier.  For example,
Unix can reside in one partition, and DOS in another.  Since DOS does not
understand the Unix partition ID, it simply ignores the space on the disk
where Unix resides.


 What are the BIOS parameter limits? 

The drive (and often the BIOS) define the drive as a maximum set of
Heads, Sectors, and Cylinders.  These maximum limits are used by software
to access the disk and usually do not have a direct relationship to the
true drive design.

No entry in the partition table should reference a point on the drive
beyond these limits.


 What does the Partition data mean? 

The table shows specific data directly from your partition table(s).

Drive and Partition - This shows the drive number (1st drive = 0) and
   the partition number (1st partition is 0).  A value of 1-3
   indicates the second drive, and the fourth primary partition.

   An extended partition is followed by all of the extended partitions
   on the drive.  Each partition with an id value of 5, points to
   another group of partitions.

id - This defines the type of partition.  The FAT type partition used
   by DOS, Windows 95/98/Me and others use ID values 1, 4, or 6.  Windows
   NT and OS/2's HPFS or NTFS file systems use a value of 7.  Other
   operating systems use other values.  Hidden partitions add 10h to the
   value.  An ID of 16 indicate a hidden FAT ID 6 partition.

Starting Sector-Head-Cylinder - This identifies where the partition
   begins on the drive.

Ending Sector-Head-Cylinder - This identifies where the partition
   ends on the drive. This information can be wrong without affecting
   System Commander or an operating system, since neither use the
   information.

Starting Sector - This is an alternative value to the Starting head,
   sector and cylinder value.  It treats the disk as one long string of
   sectors, and points to where this partition begins. It should point
   to the same place on the disk as the starting head-sector-cylinder.

   Most standard operating systems do not use this value. In some
   systems, bad values may appear in this field.  These values are
   ignored by System Commander.

Total Sectors - This specifies how many sectors reside in a partition.
   If you multiply this value by the sector size (almost always 512),
   you will get the number of total bytes for the partition.

 Warnings and Errors 

It's unfortunate that some operating system utilities do not always
properly place correct values into the partition table.  This diagnostic
will show any errors in the partition table.

If your system is working fine, we recommend ignoring any warnings shown.
Warnings and errors are very difficult to fix, and most errors are not
serious.  In some cases, such as a bad ending head, sector, or cylinder
values, no one looks at this data anyway.

Some Unix variants are confused by IDE drives greater than 500 MB in
size.  To access the entire drive, the BIOS (or software such as
OnTrack's Disk Manager) uses a feature call Logical Block Addressing
(LBA). Some older operating Systems (including many current Unix
variants) bypass the BIOS and look at the drive as if LBA was not active.
This can make for a very strange partition entry that appears to have
many errors.  Again, if it works, don't fix it!

If you are having problems, such as a failure to see a drive after a
serious system crash, then the errors shown may help point out the
problem area.  The prior section explains in detail what each item is,
and the importance to the system.

Overlapping partition entries are common when using some Unix OSes which
do not see the disk in the same way that all other OSes see the disk.
While this looks weird, you can ignore the problem.  If the overlaps
occur with the same OS type (i.e. DOS or Windows 95/98/Me FAT), partition
software such as FDISK may have problems understanding the partition
layout.

System Commander does not change partition information nor can it
correct errors found in the partition.  The source of the problem
could be the operating system, a virus, a bug in an application
program, or simply shutting the computer off in the middle of a
critical disk write operation.


 Fixing a Defective Partition Entry 

If you determine a true problem exists with your partition table, we
strongly recommend using a utility such as Norton's Disk Doctor from
Symantec to attempt to automatically correct it.

In some cases, you could use the FDISK in your operating system to delete
a defective partition.  If you do this, keep in mind that all your
data in the one partition will be lost!  Other partitions are not
affected by the deletion of one partition (although drive letter
assignments might change).

Your operating system manuals and vendor should explain the use of FDISK
in detail. Also be sure you are deleting the right partition.  The
numbering used by many FDISK programs does not relate to the true order
of partitions shown by System Commander.

For very advanced users, you can go into the partition editor (F2). This
allows you to directly change values a partition.  Additional help is
available when you are in the Partition editor mode.
.scrollend
.. ............................................................................
.msg 61
.warnbell
.anykey
.scroll

.htitle  Windows is using FAT32 

#if SC_DELUXE == 1
Windows is using a FAT32 partition that cannot be seen or used by other
non-Windows operating systems.

You may prefer a FAT16 partition for Windows, which has no effect on
features, is more compatible with other OSes and is slightly faster.

FAT32's big advantage is its ability to have a partition larger than 2 GB
(the limit of FAT16).  FAT32 also provides more usable space for a given
size partition.

At any time, you can convert the FAT32 partition into a FAT16 partition
(or FAT16 to FAT32) by using the built in file system converter in System
Commander's OS Wizard, under Partitioning, Tools, Advanced.
#else
Windows is using a FAT32 partition that cannot be seen or used by any
other operating system.  This may occur if:

     your disk is larger than 8 GB

     a partition for Windows is greater than 2 GB

     your system was factory configured with OEM Windows 95

     you are using a small cluster size

You may prefer a FAT16 partition for Windows, which has no effect
on performance or features, but is limited to 2 GB per partition. To do
this, after first backing up all the data within the partition, delete
the partition using FDISK. A new FAT partition is then created using
Windows FDISK /X or using DOS FDISK.
#endif

.scrollend
.. ............................................................................
.msg 62
.warnbell
.anykey
.scroll

.htitle  Windows using Enhanced Partition Type 

Windows is using an enhanced partition type that cannot be seen or used
by a non-Windows operating system.  This occurs when:

    your disk is larger than 8 GB

    a partition for Windows is greater than 2 GB

    an enhanced int-13 (EBIOS) support was available during
     the Windows installation
.scrollend
.. ............................................................................
.msg 63
.warnbell
.anykey
.scroll
.htitle  Software disk manager detected 

Your system is currently using a software manager like Disk Manager
or EZ-Drive.  These products allow new large drives to work with
older systems.  System Commander is compatible with current releases
of these products.

Keep in mind disk managers work fine for DOS and Windows 95/98, but will
prevent most other OSes from running on your system.  If you plan to use
any other OSes, you might consider a hardware upgrade to support all
OSes.  These upgrades will also let the hard drive run in it's fastest
mode of operation, allow you to boot directly from a diskette, and gain
back additional main memory.

For more details and options, review the installation notes that are
available at the end of the installation.

.scrollend
.. ............................................................................
.msg 64
.warnbell
.anykey
.scroll


.htitle  MultiFAT Creation Error 

System Commander was unable to create the file needed for multiFAT
operation. It is likely there is not enough disk space or too many files
in the root directory.  We recommend you correct the problem before
continuing with the installation.

Press Ctrl-C to exit (recommended).

.scrollend
.. ............................................................................
.msg 65
.warnbell
.anykey
.scroll


.htitle  Old MultiFAT file corrupt 

The multiFAT file used to store multiple FAT OS information, such as
hidden files and boot records for DOS, Windows 95/98/Me, and NT/2000/XP,
is damaged and cannot be repaired.  The old multiFAT file will be erased
and a new multiFAT file will be created.

.scrollend
.. ............................................................................
.msg 66
.clear
.shade 5 BARTEXT " Boot Diskette "
.margin 7
.line 8 NORMAL
#if SERIES == SC2K || SERIES == PC5 || SERIES == SC7
Although it may never be necessary to use a bootable OS diskette,
it is important to have a bootable diskette in case of system
problems or should a new OS installation cause a problem.

Do you have a bootable diskette for the current running version
of DOS or Windows 95/98/Me? (remember that update versions of
Windows 95/98/Me and DOS do not come with a boot diskette!)

.menu 16  10 -1 "No boot diskette, create it now"
.menu 18  10 -1 "Yes, I have a boot diskette"
#else
Do you have a bootable diskette for the current running version
of DOS or Windows 95/98/Me? (remember that update versions of Windows
95/98/Me and DOS do not come with a boot diskette!)

.menu 13  10 -1 "No boot diskette"
.menu 15  10 -1 "Yes, I have a boot diskette"
#endif
.select
.. ............................................................................
.msg 67
.anykey
.scroll

Although it may never be necessary to use the bootable OS diskette, it is
important to have a bootable diskette in case of system problems or
should a new OS installation cause a problem.

Before you continue with the installation, we recommend you make a boot
diskette.  You can exit the installation now or you can make a boot
diskette after you complete this installation.

To make a boot diskette at a DOS or Windows 95/98 prompt after exiting,
insert a blank formatted diskette in drive A (do not use another drive).
At a minimum, use the following commands to create a system disk and
save a few key utilities.  You may wish to include additional files.

        SYS   A:          
        COPY  SYS.*  A:   
        COPY  FDISK.*  A: 
        COPY  FORMAT.*  A:

Press any key or Enter to continue the installation, or press
Ctrl-X to exit now.
.errbell
.scrollend
.. ............................................................................
.msg 68
.clear
.shade 6 BARTEXT " Disk Compression "
.margin 8
.line 8 NORMAL
Are you using any type of disk compression like DoubleSpace,
DoubleDisk, Xtra-Drive, Stacker or SuperStor?
.menu 13  12 -1 "No disk compression used"
.menu 15  12 -1 "Yes, compression in use"
.select
.. ............................................................................
.msg 69
.anykey
.warnbell
.scroll
.htitle  Disk Compression Detected 

#if BUILD != BT_SC98
System Commander is fully compatible with disk compression, but must be
installed in the non-compressed C drive.  Normally System Commander will
identify the non-compressed disk for you (in the next step).

One of System Commander's many features includes the ability to run
multiple OSes in different partitions or the same partition.  When using
disk compression, we strongly recommend always install each new OS in
a separate partition, rather than together with other OSes.

Disk compression is very specific to the OS and version you have
installed.  For example, PC-DOS 6 disk compression is quite different and
incompatible with MS-DOS 6's disk compression.  Many new OSes, such as
NT/2000/XP and OS/2 will be unable to see any compressed DOS or Windows
95/98/Me disks.

Technical support cannot assist you with problems of trying to run
multiple OSes inside a single compressed partition.  The best strategy,
when you must have disk compression software, is to always place new OSes
in their own isolated partition.
#else

SC98 is NOT compatible with disk compression.

To have both Windows 3.1/95 and Windows 98 you must either:

  1) Remove disk compression (refer to your OS manuals for instructions).

							  or

  2) Use System Commander (SC) to prepare to have each Windows in
     its own partition. SCD will handle these tasks for you automatically.

#endif
.scrollend
.. ............................................................................
.msg 71
.clear
.shade 8 BARTEXT " View notes on Installing Windows 95/98/Me/3.x ? "
.margin 6
.line 10 NORMAL
Review these important notes if you plan to install Windows 95, 98,
Me, or Windows 3.x/DOS soon.
.menu 14  10 -1 "Review Notes"
.menu 16  10 -1 "Skip notes"
.select
.. ............................................................................
.msg 72
.clear
.shade 8 BARTEXT " View notes on Windows NT/2000/XP ? "
.margin 6
.line 10 NORMAL
View these notes if you currently have NT/2000/XP or plan install
Windows NT/2000/XP sometime in the future.
.menu 14  10 -1 "Review Notes"
.menu 16  10 -1 "Skip notes"
.select
.. ............................................................................
.msg 73
.clear
.shade 8 BARTEXT " View notes on Installing OS/2 ? "
.margin 6
.line 10 NORMAL
If OS/2 is not installed and you plan to install it soon or sometime
in the future, review these important notes.
.menu 14  10 -1 "Review Notes"
.menu 16  10 -1 "Skip notes"
.select
.. ............................................................................
.msg 74
.anykey
.scroll


.htitle  Important Notes 

Even if you're an expert and never look at manuals, we strongly suggest
reading chapter 3, and following those instructions.

Almost all reported problems have resulted from not reading or following
the instructions in this critical Chapter.

.scrollend
.. ............................................................................
.msg 75
.anykey
.scroll



.htitle  File Installation 

#if BUILD == BT_SC98
   We recommend you install System Commander on your hard disk boot
   drive, typically C.
#else
   We recommend you install System Commander on your hard disk boot
   drive, typically C.  If you are using disk compression, specify the
   non-compressed boot drive letter (normally use the default shown
   unless you know otherwise).
#endif

   You can exit the installation at any time by pressing Ctrl-C.

.scrollend
.. ............................................................................
.msg 76
.clear
.shade 5 BARTEXT " Where to Install Files "
.margin 2
.line 8 NORMAL
 Enter the drive letter and path name where you wish to have program files
 installed on your hard disk (drive C: is recommended).  Press ENTER to
 use the default selection.



 Path:
.. ............................................................................
.msg 77
.anykey
.warnbell
.scroll



.htitle  Path Error 


              The path name you entered must consist of at
              least a drive letter and a directory.

			  Spaces are not allowed nor are long directory
			  names.  Please correct the entry.


.scrollend
.. ............................................................................
.msg 78
.anykey
.warnbell
.scroll

.htitle  Non-C Drive Warning 

You have selected a drive that is not your boot disk.  In some cases,
this product needs to be installed on the drive which your computer
will boot from, usually C:.  Installation on the boot drive is
required if you have a hard disk driver in your CONFIG.SYS file which
makes additional disk drives available to DOS.  Selecting C: now will
avoid having to move various program files later.

If you're sure that you don't have a hard disk driver in CONFIG.SYS,
then you can ignore this notice, and continue by pressing Enter.  To
return to the prior menu and change your drive letter press Esc.

#if BUILD != BT_SC98
With disk compression, C: is usually not the bootable drive and the drive
you specified may be correct.  See the manual for more details about
disk compression.

#endif
.scrollend
.. ............................................................................
.msg 79
.anykey
.warnbell
.scroll


.htitle  Invalid Pathname 

The path that you entered for file installation already exists on your
hard disk and is not a directory.  Please enter a different directory
name.  If you would rather abort the installation now, press Ctrl-C.

.scrollend
.. ............................................................................
.msg 80
.anykey
.warnbell
.scroll


.htitle  Pathname Error 

The installation was unable to create the directory that you specified.
Please enter a different path, or abort installation now by typing
Ctrl-C.

.scrollend
.. ............................................................................
.msg 81
.anykey
.warnbell
.scroll


.htitle  Access Error 

The installation was unable to access the drive and path you specified.
Please correct it or use a different one, or abort installation now by
typing Ctrl-C.

.scrollend
.. ............................................................................
.msg 82
.clear
.shade 11 BARTEXT " Getting Configuration Data "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 83
.clear
.shade 5 BARTEXT " File Installation "
.margin 10
.line 9 NORMAL

.. ............................................................................
.msg 84
.clear
.shade 11 BARTEXT " Saving original boot files for Uninstall option "
.bline MESSAGE " "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 85
.succbell
.line 13 MAGENTA
 Process complete.

.continue
.. ............................................................................
.msg 86
.clear
.shade 8 BARTEXT " Detected prior installation "
.margin 7
.line 10 NORMAL
Do you wish to transfer your prior settings from the old version
to the new version ?
.menu 14  10 -1 "Use prior settings"
.menu 16  10 -1 "Ignore all prior settings"
.select
.. ............................................................................
.msg 87
.clear
.shade 11 BARTEXT " Transferring Information "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 88
.clear
.shade 11 BARTEXT " Performing first-time initialization "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 89
.anykey
.warnbell
.scroll


.htitle  Invalid Name 


.center Please insert your correct name.

.scrollend
.. ............................................................................
.msg 90
.anykey
.warnbell
.scroll


.htitle  Invalid Company Field 


            Please insert your company name.  If the company name
            is not applicable, enter "self".

.scrollend
.. ............................................................................
.msg 91
.anykey
.warnbell
.scroll


#if SERIES == SC2K || SERIES == PC5 || SERIES == SC7





.htitle  Invalid Serial Number 


	  The serial number you entered was not correct.  The serial number
      is printed on the registration card and consists of four fields
#if SERIES == SC2K
      of letters and numbers.  For example: SC2K5-ENN-1234567-ABCD.
#else
#if SERIES == SC7
      of letters and numbers.  For example: SC7-ENN-1234567-ABCD.
#else
      of letters and numbers.  For example: PC6-ENN-1234567-ABCD.
#endif
#endif
#else
.htitle  Invalid Serial Number 


      The serial number you entered was not correct.  The serial number
#if (BUILD == BT_SC98) || (BUILD == BT_PC)
      is printed on the registration card and consists of 2 letters, 6
#else
      is printed on the diskette label and consists of two letters, six
#endif
#if SERIES == SCD
      numbers, a dash and four letters.  For example: YF123456-ABCD.
#else
      numbers, a dash and four letters.  For example: SC123456-ABCD.
#endif
#endif

.scrollend
.. ............................................................................
.msg 92
.anykey
.scroll
#if (BUILD == BT_OEM_PHT) || (BUILD == BT_OEM_L5) || (BUILD == BT_OEM_MDK) || (BUILD == BT_OEM_AL)
#if BUILD == BT_OEM_PHT
.htitle  TurboLinux Edition 
#else
#if BUILD == BT_OEM_L5
.htitle  LASER5 Linux Edition 
#else
#if BUILD == BT_OEM_AL
.htitle  ArcLinux Edition 
#else
.htitle  Mandrakesoft Edition 
#endif
#endif
#endif

This Special Linux edition of System Commander is designed to make it a
snap to install Linux onto a computer that is currently running Windows
98, Windows 95 or DOS, and allow you to easily switch between your
existing OS and Linux.

System Commander's exclusive OS Wizard is used to create a safe location
for Linux and the Linux Swap file, without the loss of your current OS.
This is accomplished by either locating enough free space on one of your
drives, or resizing an existing FAT or FAT32 partition to make more
free space available to install Linux.  It also creates the necessary
partitions for Linux.

Unlike our full System Commander, this edition is limited to two OSes on
your system, and does not include advanced features such as manual
partitioning, OS Wizard installation of other OSes and password control.
Also, there is no technical support provided with this edition.

You can purchase the full System Commander at any time, and it
will automatically detect and transfer all your current settings, so
no special extra work is required.

We know you will enjoy using System Commander!
#else
#if BUILD == BT_LITE_PCA
..htitle  Future Publishing Edition 
.htitle  Dennis Publishing Edition 

This special edition of System Commander is designed to easily select
from different OSes installed on your computer. This includes Windows
95/98/Me/NT/2000/XP, Linux, DOS, and any other OS that runs on the PC
platform.

Unlike our full System Commander, this edition is limited to four
OSes on your system, installed into primary partitions on the first
drive.  It does not include advanced features such as our OS Wizard to
automate the OS installation process, manual partitioning, or BackStep
Wizard to undo partitioning.  Also, there is no technical support
provided with this edition.

You can purchase the full System Commander at any time, and it will
automatically detect and transfer all your current settings, so no
special extra work is required.

This is not a trial version, and you are free to use it as long as you
like!  We know you will enjoy using System Commander.
#else


.htitle  Registration Card 

              Please fill out and return the registration card.

              Registered users will receive notification of new
              product releases and are eligible for technical
              support.

#endif
#endif
.scrollend
.. ............................................................................
.msg 93
.clear
.shade 8 BARTEXT " Serial Number "
.margin 7
.line 10 NORMAL
#if BUILD==BT_SC98 || BUILD==BT_PC || BUILD==BT_PC5 || SERIES==SC2K || SERIES==SC7
Please enter the product serial number from the registration
card.  #else
Please enter the product serial number from the diskette label.
#endif
#if SERIES == SC
For example: SC123456-ABCD
#endif
#if SERIES == SCD
For example: YF123456-ABCD
#endif
#if SERIES == SC2K
For example: SC2K5-ENN-1234567-ABCD
#endif
#if SERIES == SC7
For example: SC7-ENN-1234567-ABCD
#endif
#if SERIES == PC5
For example: PC6-ENN-1234567-ABCD
#endif
.line 14 HIGHLIGHT
                        S/N:
.. ............................................................................
.msg 94
.clear
.shade 8 BARTEXT " Non-Compressed Drive "
.margin 4
.line 10 NORMAL
Enter the drive letter of the non-compressed boot drive.  If you are
uncertain which drive letter is the non-compressed boot drive, you may
need to exit (Ctrl-C) and examine the root directory for each drive.
Usually, the drive will have only a few files in the root directory and
one huge file, for the compressed portion of the disk.

.line 16 REVERSE
  Enter boot drive letter (C to Z) and press Enter:
.. ............................................................................
.msg 95
.clear
.shade 11 BARTEXT " Copying Files "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 96
.clear
.succbell
.shade 11 BARTEXT " Copying Files "
.line 13 MAGENTA
Completed.
.continue
.. ............................................................................
.msg 97
.clear
.shade 8 BARTEXT " MultiFAT Option "
.margin 6
.line 10 NORMAL
If you want to use NT (all configurations), NetWare, or multiple
versions of DOS, Windows 95/98/Me, or OS/2 in a FAT partition,
this option must be selected.

.menu 14  10 -1 "Install MultiFAT option"
.menu 16  10 -1 "Skip MultiFAT support"
.select
.. ............................................................................
.msg 98
.clear
.shade 8 BARTEXT " MultiFAT Option "
.margin 7
.line 10 NORMAL
If you want to use DOS and Windows 95/98/Me in one partition, this
option must be selected.
.menu 14  10 -1 "Install MultiFAT option"
.menu 16  10 -1 "Skip MultiFAT support"
.select
.. ............................................................................
.msg 99
.clear
.errbell
.shade 8 ATTENTION " A MultiFAT Group Already Exists "
.margin 10
.line 10 NORMAL
System Commander has detected that a multiFAT group already
exists.  To turn off multiFAT feature, the multiFAT group
must be deleted.
.menu 14  16 -1 "Use existing group"
.menu 16  16 -1 "Delete current group"
.select
.. ............................................................................
.msg 100
.scroll
.title Invalid Drive/Media Type
.title Can't Access Drive

There are two very distinct problems depending on if you are attempting
to access drive C: or if you are attempting a later drive:

 Can't access drive C: or Invalid Drive/Media Type for drive C: 

Cause: When booting from a diskette, the C: drive has "disappeared"
   and/or is invalid with either of these messages.  Attempting to boot
   from the hard disk just generates the System Commander error message
   "Boot 1".  Proceed with this solution only if BOTH these conditions
   occur.

   The problem may be caused by CMOS memory loss or an incorrect drive
   type specified in setup.  This problem can also be caused by the DOS
   boot record being altered or erased, possibly due to a virus or
   application program defect.

Action: If you suspect CMOS loss or the wrong drive type was set in the
   BIOS setup program, attempt to correct this first and try rebooting
   from the hard disk.  Do not mess with the BIOS setup if you are
   unsure what you are doing!  You may need to contact service personnel
   for your computer if you are unfamiliar with using setup and/or the
   proper disk types for your system.

   If you conclude that the DOS boot sector has been damaged, System
   Commander has a built in feature to replace the DOS boot record.
   First boot the system from a DOS diskette.

   Now insert the System Commander installation disk used when
   installing System Commander.  As part of the installation, System
   Commander saved the DOS boot record.

    WARNING:  Do not proceed if the System Commander installation disk
   was used in another system!  The saved DOS boot record is rarely the
   same from system to system and replacement of the wrong DOS boot
   record will likely cause strange unrecoverable problems, and may even
   affect other non-DOS partitions.

   From the diskette, run SCIN, select Special options, and then select
   Restore DOS Boot record.

   Once the operation is complete, remove the diskette and reboot.
   Assuming no other damage occurred, System Commander's OS selection
   menu should appear.  In this special case, we recommend not selecting
   the default choice, but another DOS choice if available.  This will
   force System Commander to replace the boot record and hidden files in
   case these were also damaged.

 Invalid Drive/Media Type for drive D: or higher (not C:) 

Cause: The most common cause is a non-formatted partition.  This will
    usually occur after creating a new partition using a partitioning
    utility like FDISK.

    Another cause may be due to a bug in all versions of DOS and
    all versions of Windows 95/98/Me.  The problem appears when you have
    more than one primary FAT partition on any drive, AND you have
    logical partitions, where the last logical partition is not FAT.
    For example, you have two primary FAT partitions, and three logical
    partitions, where the last logical is not FAT, but is OS/2's HPFS,
    NT's NTFS, or Unix.

Action: If you are sure this is a new partition, you can just format
    the partition.

    Be sure you are not seeing the bug described above.  The bug above
    may show an invalid media type for the drive, but formatting the
	drive will usually trash data within an existing partition!

    If you have fallen into the DOS/Windows bug, you can instruct
    System Commander to hide the second primary partition (see Chapter 6,
    question 10 in the manual).  As an alternative, if you must see both
    primary partitions, then you must change the last logical partition
    to FAT.  This may require deleting the last logical partition (and
    losing all the data within the partition).

.scrollend
.. ............................................................................
.msg 102
.scroll
.title COMMAND.COM missing/invalid/wrong version

Cause: Most likely the copy of COMMAND.COM is the wrong version for the
   current DOS booted.  This will occur under several situations, as
   explained below.

Action: It is usually necessary to use your boot diskette at this point
   so the problem can be resolved.

   First, the CONFIG.SYS file for this version of DOS should have a
   SHELL statement that points to the COMMAND.COM for this version.  If
   you are unfamiliar with the SHELL statement, this critical line in
   CONFIG.SYS instructs where COMMAND.COM resides. For example, in DOS
   6, the default SHELL statement might appear as:

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

   Normally you would have created a unique sub-directory for each
   operating system, such as MSDOS6.2.  In this case, the SHELL
   statement must be changed when booting MS-DOS 6.2 to point to the
   directory where COMMAND.COM resides for MS-DOS version 6.2.  This new
   SHELL line might appear as:

         SHELL=C:\MSDOS6.2\COMMAND.COM  C:\MSDOS6.2 /P

   You might have other options or use a different subdirectory instead
   of "MSDOS6.2" shown.  In any case, the drive and path should always
   point to the subdirectory for COMMAND.COM related to the DOS version
   selected.

   Also check if the AUTOEXEC.BAT file has a COMSPEC statement, which
   must also point to the COMMAND.COM for this version.  You do not need
   COMSPEC if the CONFIG.SYS file has a SHELL statement.

   Verify that System Commander was properly set up to copy the unique
   version of COMMAND.COM into the root directory.  Some programs ignore
   the path and assume COMMAND.COM is in the root directory.

   To have System Commander automatically copy COMMAND.COM into the root
   directory, press Alt-S (Setup) from the OS selection menu, and select
   the File management menu.  Verify the files and subdirectories are
   correct.

   The files to copy will not be copied if the last boot was the same
   OS.  This means you may need to select another OS in the DOS
   partition, and then reboot and select the desired OS.

   These error messages will also appear if the wrong version of
   COMMAND.COM resides in the unique subdirectory you made for the DOS
   having the problem.  To correct this, copy the correct COMMAND.COM
   version for the selected DOS from the diskette into the unique
   subdirectory.

.scrollend
.. ............................................................................
.msg 103
.scroll
.title Incorrect DOS version

Cause: A device driver or TSR was run that does not match the
   current DOS version.   This is usually due to an incorrect directory
   specification or path statement.

Action: First you must determine which driver or TSR causes this
   message.  If it is occurring in the CONFIG.SYS file, check to see
   which drivers are loading before and after the message appears.
   Unfortunately, many device drivers do not display anything when they
   run.  Newer DOS versions allow a step by step confirmation of each
   CONFIG.SYS statement by pressing F8 when the phrase
   "Starting MS/PC-DOS..." appears on screen.

   You might also look in the CONFIG.SYS file for each DEVICE= line,
   verify the path for the device driver is correct, and it points to
   the subdirectory where the current OS files reside.  If the problem
   is occurring in AUTOEXEC.BAT, you can remove the statement ECHO OFF,
   and reboot to see which is the offending line.  Once the problem line
   is found, change the subdirectory to point to the current DOS
   directory.

   Additional notes about getting the CONFIG.SYS and AUTOEXEC.BAT files
   setup properly are reviewed in the section on Special DOS Issues
   in Chapter 4 of the manual.

.scrollend
.. ............................................................................
.msg 104
.scroll
.title Your current OS on drive C is not DOS

Cause: This message might appear while attempting to load a new
   operating system from a special update version of the DOS OS.  The
   update version of some older DOS versions does not correctly detect
   DOS or will not accept a system with a newer version of DOS than the
   one attempting to be loaded.

Action: There is no way around this limitation of the update version.
   You will need to load DOS from a non-update version of DOS.   If you
   have a bootable system diskette (which is not provided with the
   update version) you boot from it, create a unique directory, and copy
   all the desired files from the diskette to this directory.  In
   addition, you need to run the SYS program from the diskette.  At the
   DOS prompt, run:

         A:>  SYS  C:

   This will transfer the system to the C: drive.  Remember to update
   CONFIG.SYS and AUTOEXEC.BAT files.  Reboot to have System Commander
   save the new OS.

.scrollend
.. ............................................................................
.msg 105
.scroll
.title Incorrect version of DBLSPACE.BIN

Cause: If DOS 6.x was installed on top of Windows 95/98/Me, DOS will
   install an old version of DBLSPACE.BIN.

Action: If you are not using disk compression, we recommend renaming or
   removing DBLSPACE.BIN.  It is not needed nor used if disk compression
   is off.  The file appears in the C:\ root directory as a hidden
   system file.

.scrollend
.. ............................................................................
.msg 106
.scroll
.title MSDOS5.0 appears as OEM name for MS-DOS 6

Cause: Microsoft chose to leave the old DOS 5 name in the DOS boot
   record.  This is true for MS-DOS versions 6.00 through 6.22.

Action: None.  The OEM name is the name provided by the vendor.  System
   Commander, in most cases, will default to a selection name with the
   real version of DOS.

.scrollend
.. ............................................................................
.msg 107
.scroll
.title DOS installation fails because of existing DOS or Windows

Cause: The DOS setup program will not allow you to install an older
   version of DOS on top of a newer version or DOS or Windows 95/98/Me.

Action: First, be sure System Commander is installed in this partition
   and you have booted at least once.  This saves the files we are about
   to delete.  Next go to the C:\ root directory and unhide and delete the
   two files IO.SYS and MSDOS.SYS  (If using PC-DOS or Novell DOS, the
   files are IBMIO.COM and IBMDOS.COM).

        C:\ >  attrib  -h  -r  -s  msdos.sys
        C:\ >  del  msdos.sys
        C:\ >  attrib  -h  -r  -s  io.sys
        C:\ >  del  io.sys

   Now boot from your DOS installation diskette and proceed with the
   installation.  If DOS Setup suggests to format or "remove the files",
   DO NOT SELECT these options, as they will delete all files on the
   disk.

.scrollend
.. ............................................................................
.msg 108
.scroll
.title SYS program fails with message

The SYS program is used to install a partition boot record, and insert the
two hidden system files that run DOS.  Recent SYS programs also copy the
COMMAND.COM program.  Two undocumented errors can occur (in red):

 No room for System 

Cause: The SYS program wants to place the two hidden files as the first
   two directory entries.  In addition the SYS command wants to place
   the hidden files at the beginning of the partition.  Older versions
   (DOS 3 & 4) of the SYS command are more restrictive than newer
   versions.

Action: The best approach is to use System Commander to transfer the
   system from A: to C:.  This is accomplished through SCIN, under
   Special options.  The System Commander Transfer System function
   solves many limitations (and a few bugs) with the DOS/Windows SYS
   command.

   The following manual alternative method might also work to get
   around some of the standard SYS limitations.  Attempt the following
   actions with the drive that you want to load the system onto.  We'll
   assume drive C, but other drives are acceptable.  You need to unhide
   and delete the two system files IO.SYS and MSDOS.SYS  (If using
   PC-DOS or Novell DOS, the files are IBMIO.COM and IBMDOS.COM).

        C:\ >  attrib  -h  -r  -s  msdos.sys
        C:\ >  del  msdos.sys
        C:\ >  attrib  -h  -r  -s  io.sys
        C:\ >  del  io.sys

   If this fails to work, and you have installed Windows 95/98 previously
   into the same partition, delete the files with the .DOS extension:

        C:\ >  attrib  -h  -r  -s  msdos.dos
        C:\ >  del  msdos.dos
        C:\ >  attrib  -h  -r  -s  io.dos
        C:\ >  del  io.dos

   If this fails to work, it is necessary to use the System Commander
   "Transfer System" option.

 Write failure, diskette unusable 

Cause: The SYS program finds the target drive has not been formatted.
   (the error message is very inaccurate!).

Action: After confirming the drive has not been formatted (do a DIR
   C:), then format the drive.

.scrollend
.. ............................................................................
#if BUILD != BT_SC98
.msg 110
.scroll
.title Can't Find COUNTRY.SYS
.title Drive Invalid

Cause: If the operating system properly boots up using Boot Manager,
   but not directly from System Commander, this message usually
   indicates a non-standard drive lettering arrangement.  In rare cases,
   it might also mean the OS/2 CONFIG.SYS file is missing or built
   incorrectly.

Action: If your system is configured with more than one primary
   FAT/HPFS partition, and OS/2 is in a primary partition, it may be
   necessary to hide all but the one OS/2 primary partition.  To do
   this, reboot to System Commander's OS selection menu.  Highlight, but
   do not select the OS/2.   Press Alt-S (Setup) and select the Local
   special options menu.  The option Primary partitions accessible on
   drive 0 should be set to NONE (this will always keep the booted
   partition accessible, but hides all other primaries).

   If OS/2 is installed in a logical drive, in some configurations the
   drive letter may be set wrong by System Commander.  To correct this,
   reboot into System Commander.  Press Alt-S (Setup) and select the
   Local special options menu.  Change the option OS/2 boot drive letter
   from AUTO to the drive letter that matches what OS/2 normally boots
   to.  If you are not sure which drive letter this is, you can
   experiment by starting at C:, and trying the OS/2 selection.  If it
   fails, try the next drive letter.

   If you suspect the OS/2 CONFIG.SYS file, check the file to verify its
   existence and the COUNTRY= line is correct.  With OS/2 in the DOS
   partition, the config file will appear in the system directory as
   C:\OS2\SYSTEM\CONFIG.OS2.

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98
.msg 111
.scroll
.title OS/2 Installation Notes

   Contents
        Installing OS/2 - Disk Destruction!
        Planning where to install OS/2


   Installing OS/2 - Disk Destruction!
   
   Always use the Advanced install selection of OS/2.  The Easy (v4) and
   Express (v3) options in a number of configurations will either
   automatically format your drive without warning or may prompt you to
   format the drive.  If you are prompted to format the drive DO NOT
   SELECT the format option, or you will lose all other OSes in the FAT
   partition, such as NT/2000/XP, Windows 95/98/Me, and DOS. In addition,
   System Commander will no longer work, and the next reboot will show a
   "Boot 2>" error message.  OS/2 does not confirm your selection, so if
   you select the format option, the format begins immediately.


   Planning where to install OS/2
   
#if BUILD == BT_LITE_PCA
   For this Lite edition, OS/2 must be installed in a primary partition
   on the first drive. The full System Commander does support OS/2
   installed in logical partitions and/or OS/2 installed on other drives.
#else
   When installing OS/2, be aware that if you plan to install it into
   a logical partition or in a drive other than the first drive, OS/2
   requires that you install OS/2's Boot Manager (this is done as part
   of the OS/2 installation).  Once OS/2 installation completes, you can
   boot directly into the OS/2 partition without using Boot Manager.
#if BUILD != BT_PC && BUILD != BT_PC5
   The System Commander manual explains these issues in more detail.
#endif

   When Boot Manager is required, it must be installed on a primary
   partition on the first drive.  If you do not have unallocated space
   on the first drive, or do not have a free primary partition, OS/2
   cannot install Boot Manager, and OS/2 will not let you complete the
   OS/2 installation.

   Boot Manager is not required if you install OS/2 into any primary
   partition on the first drive.
#endif

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98
.msg 112
.scroll
.title OS/2 fails to boot

Cause: You may be attempting to boot the wrong partition, or more than
   one primary partition is accessible when trying to boot OS/2.

Action:
   Check if you are booting into the correct partition
   
   At boot time, on the main System Commander selection menu,
   press Alt-I (Info-disk).  This will show all the partitions, and
   which ones are currently marked as bootable.  Check that the correct
   OS/2 partition is bootable.  If you only have one OS/2 partition,
   then it should be obvious.  Most OS/2 partitions have an OEM name
   of "OS2..." or "IBM 20...".

   If you suspect the wrong partition is bootable, exit (press Escape)
   and press Alt-S (Setup).  Select the Order, add or removal menu,
   and then press Alt-A (Add).  Select P for partition.  Find the
   OS/2 partition you wish to make bootable (i.e. to make it appear on
   our menu), and press Alt-T (Toggle) to make the highlighted OS/2
   partition bootable. Try the new selection to see if OS/2 now works

   Two many primary partitions visible under OS/2
   
   If your system is configured with more than one primary FAT/HPFS
   partition, and OS/2 is in a primary partition, it may be necessary to
   hide all but the one OS/2 primary partition.  To do this, reboot to
   System Commander's OS selection menu.  Highlight, but do not select
   the OS/2.  Press Alt-S (Setup) and select the Local special
   options menu. The option Primary partitions accessible on drive 0
   should be set to NONE (this will always keep the booted partition
   accessible, but hides all other primaries).

   If OS/2 is installed in a logical drive, you need to verify that only
   one primary partition per drive is visible.  The System Commander
   default is to hide all but one primary partition when booting into
   OS/2 on a logical partition. At the main selection menu, highlight,
   but do not select the OS/2.  Press Alt-S (Setup) and select the
   Local special options menu.  Highlight the option Primary
   partitions accessible on drive 0 and press Enter.  Verify that only
   one primary partition option other than the extended partition is set
   to YES.

   Wrong drive letter
   
   In some configurations the drive letter may be set wrong by System
   Commander.  To correct this, reboot into System Commander.  Press
   Alt-S (Setup) and select the Local special options menu.  Change
   the option OS/2 boot drive letter from AUTO to the drive letter that
   matches what OS/2 normally boots to.  If you are not sure which drive
   letter this is, you can experiment by starting at C:, and trying the
   OS/2 selection.  If it fails, try the next drive letter.

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98
.msg 120
.scroll
.title Warning SU-0012 (OS/2 or NT will no longer work)

Cause: If an OS/2 or NT partition is present, this message will appear
   during the Windows 95/98/Me installation.

#if BUILD != BT_PC && BUILD != BT_PC5 && BUILD != BT_LITE_PCA
Action: No action is necessary.  System Commander protects both OS/2
   and NT from Windows 95/98/Me.
#else
Action: You should not install Windows in this partition. If you
   continue to do so, your OS/2 or NT/2000/XP will no longer work.  You
   can use System Commander to also support multiple OSes in a
   single partition.
#endif

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98
.msg 121
.scroll
.title Warning SU-0015 (NT/2000/XP will no longer work)

Cause: If NT/2000/XP was installed prior to Windows 95/98/Me, this
message may appear during the Windows 95/98/Me installation.

#if BUILD != BT_PC && BUILD != BT_PC5 && BUILD != BT_LITE_PCA
Action: No action is necessary.  System Commander protects NT/2000/XP
   from Windows 95/98/Me.
#else
Action: You should not install Windows in this partition. If you
   continue to do so, your Windows NT/2000/XP will no longer work.  You
   can use the full System Commander to support multiple OSes in a single
   partition.
#endif

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98
.msg 122
.scroll
.title Warning SU-0016 (OS/2 will no longer work)

Cause: If OS/2 was installed prior to Windows 95/98/Me, this message
will appear during the Windows 95/98/Me installation.

#if BUILD != BT_PC && BUILD != BT_PC5 && BUILD != BT_LITE_PCA
Action: No action is necessary.  System Commander protects OS/2 from
   Windows 95/98/Me.
#else
Action: You should not install Windows in this partition. If you
   continue to do so, your OS/2 will no longer work.  You can use
   the full System Commander to support multiple OSes in a single
   partition.
#endif

.scrollend
#endif
.. ............................................................................
.msg 123
.scroll
.title Windows 95/98 goes to DOS prompt (no graphics)

Cause: This occurs when Windows has some problem during the boot up
   process.

Action: Check the contents of the MSDOS.SYS text file.  When Windows
   DOS is active, this appears in the root directory as a hidden
   system file.  To list hidden files, at the Windows 95/98 DOS prompt,
   type:

        C:\ >  dir  /ah

   To access the file, change the attributes:

        C:\ >  attrib  -h  -s  -r  msdos.sys

   The MSDOS.SYS file is typically about 1500 bytes.  If the file is
   missing, set to zero length, or has been replaced with the older DOS
   MSDOS.SYS executable (10 KB or larger), Windows 95/98 will not come up.
   Correct the file if damaged or missing.  If the file is completely
   lost, we have included a generic MSDOS.SYS file for Windows 95/98 on
   the System Commander installation diskette.  It is under the filename
   MSDOS.BAK and is a hidden file.  Be sure to edit the entries in this
   file for the drives and path as appropriate for your system.

   If the MSDOS.SYS file is Windows 95/98 (i.e., about 1500 bytes), check
   that a line appears "BootGUI=1" under "[options]".  Without this
   line, or if the value is set to zero, Windows will go directly to
   a Windows DOS prompt without going into the graphical portion of
   Windows.

   You also might try pressing F8 immediately after you select Windows
   95/98 from System Commander.  This will issue a menu of options, such
   as safe mode, and a logging mode.  The Windows 95/98 manuals and
   on-line readme files should have other suggestions and
   recommendations, and explain the use of these options.

.scrollend
.. ............................................................................
.msg 124
.scroll
#if BUILD != BT_SC98
.title Windows 95/98/Me Installation Notes

#endif
   Contents

        A. Windows 95/98/Me not installed yet
        B. Windows Plus can Destroy other OSes!!!
        C. Installing Windows 95 Full-pack can destroy files and OSes
        D. Having Windows 95 and Windows 98 on the same system
#if BUILD != BT_PC && BUILD != BT_PC5 && BUILD != BT_LITE_PCA
        E. Installing DOS/Windows 3.x after Windows 95/98
#endif

   A. Windows 95/98/Me not installed yet
   
#if SC_DELUXE == 1
   The easiest and safest way to install Windows 95/98/Me is to use our
   OS Wizard feature at boot time.  This will automatically prepare
   your system for the installation.  If you prefer a manual method
   of Windows installation, be aware of the following issues:
#else
#if BUILD != BT_PC && BUILD != BT_PC5
   If you have not installed Windows 95/98/Me, it is very important that
   you review the notes in the System Commander manual.  The current
   release of Windows 95/98/Me will destroy some files and cause general
   havoc if you do not prepare for it.  Some of the specific issues
   include:
#else
   If you have not installed Windows 95/98/Me, it is very important that
   you review the notes in the Partition Commander manual.  The
   current release of Windows 95/98/Me will destroy some files and cause
   general havoc if you do not prepare for it.  Some of the specific
   issues include:
#endif
#endif

        The Windows 95 Installation will erase some or all of your
        current DOS files without warning or backup!

        The master boot record (MBR) will be replaced with a generic MBR
        during Windows 95/98/Me installation, temporarily preventing
		System Commander from running.

        The Windows 95/98/Me installations will look for older Windows
		versions and will always default to installing on top of any
		existing Windows installation.  To keep a prior version, you
		may need to install the new OS to another partition.


   B. Windows Plus can Destroy other OSes!!!
   
   Microsoft offers an separate package of utilities, icons, and
   wallpaper for Windows 95/98. It also includes disk compression. If you
   install disk compression it will compress your FAT partition and all
   OSes installed on that partition.  In most cases, these other OSes
   will no longer work.  A reboot may present a "Boot ##" error message
   and hang the system.

#if SC_DELUXE == 1
   If you get into this weird situation, boot from a DOS boot floppy.
   Change to the System Commander diskette and run SCIN.  Select
   Disable or Remove, and then Disable.  You may be able to run
   Windows 95/98, but the other OSes are not likely to be recoverable. A
   full installation of System Commander (run SETUP from the System
   Commander diskette) will get System Commander running again, but the
   other OSes must be loaded again.  Remember that System Commander MUST
   be installed onto the non-compressed drive, which will no longer be
   drive C:.
#else
#if BUILD != BT_PC && BUILD != BT_PC5
   If you get into this weird situation, boot from a DOS boot floppy.
   Change to the System Commander diskette and run SCIN.  Select
   Disable/Uninstall.  You may be able to run Windows 95/98, but the
   other OSes are not likely to be recoverable.  A full installation of
   System Commander (run INSTALL from the System Commander diskette) will
#if BUILD == BT_LITE_PCA
   get System Commander running again. Remember that System Commander
   MUST be installed onto the non-compressed drive, which will no longer
   be drive C:.
#else
   get System Commander running again, but the other OSes must be loaded
   again.  Remember that System Commander MUST be installed onto the
   non-compressed drive, which will no longer be drive C:.
#endif
#else
   If you get into this weird situation, boot from a DOS boot floppy.
   Change to the Partition Commander diskette and run SCIN.  Select
   Disable or Remove, and then Disable.  You may be able to run
   Windows 95, but System Commander will not run.  A full installation of
   System Commander (run SETUP from the Partition Commander diskette)
   will get System Commander running again.  Remember that System
   Commander MUST be installed onto the non-compressed drive, which will
   no longer be drive C:.
#endif
#endif

   In general, with Windows 95/98 Plus, we strongly recommend against
   installing disk compression (DriveSpace).

   C. Installing Windows 95 Full-pack can destroy files and OSes
   
   When installing the Windows 95 full-pack (i.e. you do not need DOS or
   Windows 3.x for installation), AND you already have an OS installed
   into another partition, Windows 95 setup will prompt you:

         Ŀ
           Microsoft Windows 95 Setup                        
                                   
               Setup has found non-MS-DOS operating system   
               files on your computer.                       
                                                             
                   Remove the files                          
                   Do not remove the files                   
                                                             
         

   DO NOT CHOOSE the default "Remove the files".  If you chose it,
   Windows 95 will delete all partitions on the disk, and recreate one
   large partition for the entire drive!  All programs and operating
   systems will be lost.  Windows 95 does not confirm this drastic
   action, so be very careful, and select the option Do not remove the
   files.

   D. Having Windows 95, 98 and/or Me on the same system
   
   We recommend installing each Windows version into it's own partition.
   If you place a new Windows installation on top of a prior installation
   (the default operation of the Windows installer) the prior
   installation will no longer be available.

#if BUILD != BT_PC && BUILD != BT_PC5 && BUILD != BT_LITE_PCA
   Although not currently recommended, you can install Windows 98 in the
   same partition as Windows 95 (this must be the partition where System
   Commander is installed).  To do this, and keep your Windows 95, you
   must first install Windows 95 again into a new directory.  Then you
   can install Windows 98 from the 2nd Windows 95 and have it install on
   top of the 2nd Windows 95.

   You cannot simply XCOPY the existing Windows 95 directory to a new
   directory.  This never works!  Also keep in mind that the "Program
   files" directory will be overwritten by Windows 98.  In our own
   testing of beta releases of Windows 98, this has not caused a problem
   with Windows 95, but this is not a sure thing.  Backups are always
   recommended before installing a new beta operating system.

   E. Installing DOS/Windows 3.x after Windows 95/98
   
   To install Windows 3.x, you must have DOS already installed.

   Some versions of DOS may refuse to install when Windows 95 or 98 are
   already installed in the same partition.  This problem can occur when
   the DOS install assumes you would not want to install an older DOS
   version on a system with a newer DOS (i.e. Windows 95/98)!

   This section assumes System Commander was already installed in this
   same partition, and the system has been booted once to have System
   Commander save the Windows 95/98 boot information.

   Step 1:  Boot from the DOS installation diskette, and when first
            prompted, press F3 twice to exit the installation program.

        2:  At the DOS prompt, type:
                c:
                cd \sc
                scin

        3:  From the SCIN menu, select 'Special options', then
            'Transfer system', and choose 'Automatic'.  When the
            transfer of DOS system files is complete, exit back
            to DOS (Tip: press Escape several times to exit).

        4:  At the DOS prompt, type:
                a:
                install

            The DOS installation should now proceed without any
            problems.

    If you are installing Windows 3.x after DOS is installed, do not
    choose the "Express install" when prompted, but choose "Custom
    install" so you can set the correct directory for installation.  When
    prompted, do not use the default directory "WINDOWS".  Choose an
    alternate name that is not currently used such as "WIN3" to avoid
    affecting your working Windows 95/98 directory.

#endif
.scrollend
.. ............................................................................
.msg 125
.scroll
.title VFAT Device Initialization Failed

Cause: The IFSHLP.SYS file is not accessible or is the wrong version,
   or an incomplete Windows 95/98 installation left the WINBOOT.INI file
   in the root directory.

Action: Depending on the cause, one of the following solutions will
   work.  This information is based on Microsoft's knowledgebase.
   Boot from a boot diskette (DOS or Windows 95/98) and check and
   correct the following:

   1) If the file WINBOOT.INI exists in the root directory on drive C,
        delete it.

   2) Edit the C:\CONFIG.SYS file, and verify the device line exists for
        IFSHLP.SYS.  A typical line (depending on where Windows 95/98 is
        installed) might appear as:

            DEVICE=C:\WINDOWS\IFSHLP.SYS

        If the line is missing or if the path is not pointing to where
        you installed Windows 95/98, correct it.  One common problem is
        having the path point to an old Windows 3.x installation.

   3) Check in the directory that you installed Windows 95/98 for the
        existence of the IFSHLP.SYS file, and that the date and time is
        the same as other Windows 95/98 system files (like TASKMAN.EXE).
        If missing or the wrong version, a copy must be loaded from
        another system or extracted from the Windows CD-ROM.  To extract
        the file from the CDROM, assuming it is in cabinet 12:

            C:\> g:\win95\extract  /L c:\win95  g:\win95\win95_12.cab

        Where "g:\win95" is the CD-ROM drive and location of the Windows
        compressed folders, and "c:\windows" is the hard disk location of
        your current Windows files.  Replace the drive and path that
        is appropriate for your system.

   4) The paths must be correct in the hidden system file MSDOS.SYS.
        You can access the file using the ATTRIB command (which might
        not be on your boot diskette).

            C:\> attrib  -s  -r  -h  c:\msdos.sys

        Next edit the MSDOS.SYS file and verify the paths are correct in
        the section that appears as:

            [Paths]
            WinDir=c:\windows         (should have your drive & path)
            WinBootDir=c:\windows     (should have your drive & path)
            HostWinBootDrv=c          (non-compressed boot drive)

        After any corrections have been made, re-hide the file by:

            C:\> attrib  +s  +r  +h  c:\msdos.sys
#if (BUILD != BT_SC98) && (BUILD != BT_PC) && (BUILD != BT_PC5)

    In many cases, you can edit files like CONFIG.SYS and MSDOS.SYS from
    System Commander at boot time.  To do this, at boot time, highlight
    the Windows 95/98 selection, and press Alt-S (Setup).  Select "File
    management menu" option.  Move to the file line you wish to edit and
    press Alt-E.
#endif

.scrollend
.. ............................................................................
#if SC_DELUXE == 1
.msg 126
.scroll
.title OS Wizard does not start
.title OS Wizard hangs during analysis

Cause: In some cases, the system analysis may be unable to complete
   in its normal way.  Nothing is written to the disk during this
   period.

Action: From the OS Selection menu, press Alt-S (setup) and select
   "Global special options menu".  Change "OS Wizard alternate start"
   to YES.

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98
.msg 130
.scroll
.title Fatal System Error
.title Missing File <winnt root> \system32\ntoskrnl.exe

Cause: If the NT partition is not accessible, the undocumented NT error
   message appears indicating "The Session Manager Initialization system
   process terminated" or with NT 3.5 "Windows NT could not start
   because of the following file is missing or corrupt".

   This can be caused by a new partition being created by another OS,
   such that it displaces the NT partition.

Action: This usually indicates the hidden file BOOT.INI has the wrong
   partition to find NT on.  This critical file resides in the DOS root
   directory.  To change or examine this file, first update the
   attributes:

        C:\ > attrib -r -h -s  c:\boot.ini

   One or more lines appear in BOOT.INI that have  \winnt  in them.  If
   only one NT is in the system, then all lines with \winnt should point
   to the same disk, rdisk, and partition.  For example, the following
   line indicates where the WINNT program will be found on one system.

        default=multi(0)disk(0)rdisk(0)partition(2)\winnt

   It may be the wrong disk number or partition is specified such that
   the NT loader can't find WINNT.  (It would be nice if NT simply
   explained this in English).  Make the corrections, and reboot.

   If you are at a complete loss, try changing the partition number by
   adding one or subtracting one.  In the above example, you might first
   try partition(3), and if that fails, try partition(1).

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98 && BUILD != BT_LITE_PCA
.msg 131
.scroll
.title Windows NT 4.0 with NT 3.x problems

Cause: NT 4.0 uses a different hidden file NTDETECT.COM than prior
   NT versions.  In addition, a few systems also contain a file
   NTBOOTDD.SYS which is different between versions.  These file(s)
   reside in the C: root directory as hidden system files.  To view
   these files, at a prompt in Windows 95/98/Me or DOS, enter:

        C:\ > dir /ah

   System Commander must be set up to copy these files from a save
   directory for each version of NT, into the root directory.

   If you installed one NT version under this release of System
   Commander, the files should be set up properly for the one NT
   version.  You will need to split the single NT choice into two
   choices as explained below.  If NT was set up under System Commander
   v2.26 or older the following instructions will create two choices on
   the menu and will specify the proper files to copy.

Action: If you only have one NT selection on the OS selection menu,
   Highlight the NT selection and press Alt-S (Setup). Select the
   Order, add, and removal menu and press Alt-A (Add).  Press "D"
   for duplicate.  This creates another choice for NT.

   For one of the NT choices, under the Setup menu, select the File
   management menu.  You must have the following files set to copy:

       Action  Update          Source                Target
     1  COPY   AUTO     C:\path\BOOT.INI        C:\
     2  COPY   PROMPT   C:\path\NTDETECT.COM    C:\
     3  COPY   IGNORE   C:\path\NTBOOTDD.SYS    C:\

   The "path" is left at the default. The NTBOOTDD.SYS is optional, but
   with the update set to "IGNORE" if the file does not exist, no error
   messages will appear.

   Press PgUp or PgDn in the File management menu to switch to the other
   NT selection.  Set the files to copy BOOT.INI, NTDETECT.COM, and
   NTBOOTDD.SYS the same as the prior NT selection, except for the
   different path.

   Lastly, boot into partition where System Commander is installed
   (DOS or Windows 95/98/Me), and get the correct files into the two
   different paths shown in the file management menu.  This will appear
   something like:

        C:\  C:\SC\WINNT35\  BOOT.INI
                                      NTDETECT.COM
                                      NTBOOTDD.SYS (optional)
                   
                C:\SC\WINNT40\  BOOT.INI
                                       NTDETECT.COM
                                       NTBOOTDD.SYS (optional)

   You will need to copy the NTDETECT.COM and NTBOOTDD.SYS files from
   the NT emergency repair diskette for each related NT version.  Edit
   the BOOT.INI file for each NT version (in paths WINNT35 & WINNT40),
   so that NT boots the correct partition for the version of NT.

   Remember that all these files are hidden system files, so you will
   need to use the ATTRIB command to unhide the file and allow editing.
   For example, to allow editing the BOOT.INI file:

        C:\ > attrib  -h  -r  -s  boot.ini

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98
.msg 132
.scroll
.title Windows NT/2000/XP Installation Notes

   Contents

        A. NT's Disk Administrator - OS corruption!
        B. Having NT 4.0 with older versions of NT
        C. Windows 2000/XP can prevent Windows NT boot

   A. NT's Disk Administrator - OS corruption!
   
   When first starting NT's Disk Administrator, Disk Administrator may
   find that no signatures were found on drive 0.  Its "Confirm" dialog
   box will indicate that the option will not affect other operating
   systems.  It then asks if you want to write a signature onto the
   drive.

   When writing the signature, a number of bytes are altered in the
   Master Boot Record.  System Commander is designed to tolerate these
   changes, and System Commander will not be affected.

   Some users of multiple OSes have reported that this NT option
   corrupted other OSes which reside in their own partition, such as
   OS/2 and Unix variants.  This problem is confirmed (and explained)
   in the Microsoft Knowledge database under "Disk Administrator
   Corrupts Partitions".  According to this article, the problem occurs
   with Windows NT 3.51 (and maybe other versions), when you have more
   than two logical partitions in an extended partition.

   When the problem occurs, the partition data is written to the wrong
   place on the disk drive, and may corrupt files or a file system.  In
   addition, the partition table itself may be corrupted.

   We recommend avoiding the use of NT's Disk Administrator in
   version 3.51.  Microsoft believes this bug is corrected in the latest
   v3 NT service pack and in version 4 of NT.


   B. Having NT 4.0 with older versions of NT
   
#if BUILD == BT_LITE_PCA
   We recommend each copy of Windows NT/2000/XP reside in its own
   partition.
#else
#if BUILD != BT_PC && BUILD != BT_PC5
   If you have an old 3.x version of NT, and wish to keep the old version
   and add NT version 4, a number of special steps must be taken IF you
   were using version 2 of System Commander when you installed NT.  If
   you are using version 3 or later of System Commander, no special
   actions are necessary, as System Commander manages the conflicts
   automatically.

   You may wish to print these notes, or later return to the SCIN
   program's installation notes on NT once the System Commander
   installation is complete.

   First we assume one NT version is installed in some partition, and
   appears as a selection on System Commander's menu (See Chapter 4
   for details).  These notes assume you have version 3.x and are adding
   NT version 4.  The notes also apply to systems with NT version 4.0
   where you wish to add NT version 3.x.

   1)   First, boot up to the OS selection menu, and highlight the NT
        choice.  Press Alt-S (Setup), and select the File management
        menu.  If the following files do not appear, add them.  We have
        assumed the files reside in the path \SC\WINNT (but any path
        you previously set is fine).

          Action  Update          Source                  Target
        1  COPY   AUTO     C:\SC\WINNT\BOOT.INI        C:\
        2  COPY   PROMPT   C:\SC\WINNT\NTDETECT.COM    C:\
        3  COPY   IGNORE   C:\SC\WINNT\NTBOOTDD.SYS    C:\

        If you made any changes, then to save the files, exit to the main
        OS selection menu, and  boot into NT once.  Shutdown NT and
        return to the System Commander selection menu.

   2)   Press Alt-S (Setup) and select the Order, add and removal
        menu.  The NT choice should still be highlighted.  Press
        Alt-A (Add) and select "D" for Duplicate.  Enter the
        appropriate name (like Windows NT 4.0) for the duplicate
        description.

   3)   When the duplicate is complete, exit and boot the new "Duplicate"
        NT choice.  At the moment, only the old NT will appear.  Now
        install the new NT version 4 into a new directory or drive.  If
        NT re-boots during the installation, be sure to pick the new
        "Duplicate" choice again, so the installation will complete.

        When Windows NT 4.0 completes its installation, you should have
        two choices on the System Commander selection menu for NT 3.x and
        NT 4.0.  The 4.0 choice will initially provide NT's OS Loader
        with choices for NT 3 and NT 4.  DO NOT pick NT v3 from the NT
        OS Loader menu as it will likely crash (although it should not
        harm anything).

        Identify the new NT save directory.  To do this, reboot to the OS
        selection menu, highlight (but do not select) the new NT choice.
        Press Alt-S, and select File management menu.  The full path
        name will appear (it is likely \SC\WINNT.A ). At a convenient
        time, edit the BOOT.INI file in the directory for the new NT.
        Remove the NT 3.5 choices from the BOOT.INI file, and only leave
        the NT 4.0 choice(s) you want.
#else
   We recommend each copy of Windows NT/2000/XP reside in its own
   partition.  You can use NT's boot loader if you wish to install
   multiple copies of Windows NT/2000/XP into logical partitions or
   primary partitions on a 2nd or later drive.
#endif
#endif

   C. Windows 2000/XP can prevent Windows NT boot
   
   If you install or run Windows 2000/XP on a system that has Windows NT
   SP3 or older in NTFS, the Windows NT partition will automatically be
   converted by Windows 2000/XP to an incompatible NTFS format, so that
   Windows NT will no longer boot.

#if BUILD != BT_PC && BUILD != BT_PC5
   Using OS Wizard will automatically hide NTFS partitions from Windows
   XP/2000 by default to prevent this issue, but in the event you unhide
   the partition and run Windows 2000/XP, the partition will be
   converted.

   In addition to keeping the NT partition always hidden from Windows
   2000/XP, our recommendation is to use Windows NT SP4 or later, or
   keep the Window NT partition in FAT rather than NTFS.

#endif
   Using Windows NT SP4 or later will allow booting after the conversion
   by Windows 2000/XP, but some Windows NT utilities will no longer work,
   such as NT's CHKDSK program.

   If you find you can no longer run your Windows NT, you can unhide
   the partition (if not already) and still access the data and files
   from Windows 2000/XP.
.scrollend
#endif
.. ............................................................................
.msg 135
.clear
.shade 7 BARTEXT " Internet Upgrade Installation "
.margin 2
.line 9 NORMAL
 Please enter the full path and file name of the System Commander upgrade
 file that you downloaded from the internet.



 Path:
.. ............................................................................
.msg 136
.clear
.shade 4 BARTEXT " Extracting Files for Installation "
.bline MESSAGE "Please wait."
.line 6 NORMAL
.. ............................................................................
#if BUILD != BT_SC98
.msg 140
.scroll
.title SCO Unix - Boot Problems
.title UnixWare - Boot Problems

Cause: If using SCO Unix System V or Novell UnixWare, depending on
   other partitions and how Unix was installed, it may be necessary to
   make the selected Unix partition the only accessible partition on
   drive 0.  System Commander defaults to making both the DOS and Unix
   partitions accessible.

Action: To make only the Unix partition accessible, on the System
   Commander OS selection menu, highlight Unix and press Alt-S (Setup).
   Select the Local special options menu, and move down to the selection
   Primary partitions accessible on drive 0:.  Select NO for all
   partitions except the UNIX partition.  You can also select NONE, as
   System Commander will never allow the selected boot partition (UNIX
   in this case) to be set to NO.  Press Escape three times to return to
   the OS selection menu and try the Unix selection again.

.scrollend
#endif
.. ............................................................................
#if BUILD != BT_SC98
.msg 141
.scroll
.title Linux - MBR Boot
.title Linux - Invalid Boot Record

Cause: Some Linux installations may default to booting through the
   Master Boot Record, although most will specifically ask you if LILO
   should use the Master Boot Record or a superblock.  The superblock
   is the desired approach.  This problem occurs if the LILO installation
   used the MBR method or you selected it by accident.

#if BUILD == BT_LITE_PCA
Action: Option A: Re-run LILO and set it to use the Superblock.
  Some versions of Linux have a bug that prevents a Linux MBR
  installation from switching to Superblock.

  Option B: Purchase the full System Commander, which has an automatic
  option for supporting the MBR method.
#else
Action: System Commander must be set up to launch the Linux MBR.  See
   the System Commander manual, at the end of Chapter 3 for "Special
   Case - Booting through the MBR".
#endif

.scrollend
#endif
.. ............................................................................
.msg 150
.clear
.scroll
.title Drive letter assignments for Windows 95/98/Me and DOS

Windows and DOS only recognize FAT type partitions.  All other partition
types, like OS/2's HPFS, NT's NTFS, Linux and other variants are ignored.
In addition, partitions hidden by System Commander are also invisible to
the OS.

Both Windows and DOS assign drive letters in the following order:

1) The primary partition on the first drive that the OS booted from
   is always assigned drive letter C.

2) If additional drives are installed that have primary FAT partitions,
   the first FAT primary partition is assigned the next letter.  This
   check continues looking for the first FAT primary partition on any
   remaining hard drives.  At this point only one primary FAT
   partition per drive is included.

3) Next the OS returns to the first drive, and checks for any logical FAT
   partitions.  These are assigned the next letters in the order found.
   All logical partitions are handled in this step.

4) All the remaining drives are checked for logical FAT partitions, and
   these are assigned drive letters.

5) Last the OS returns to the first drive, and checks for any remaining
   primary FAT partitions not assigned a drive letter yet.  This
   continues through any remaining drives.

6) The CONFIG.SYS file may specify other drive letters at this point.
   This includes the CD ROM and other devices that get assigned a drive
   letter through a device driver.

Complex Example

A system has two physical drives, and the first drive has two primary FAT
partitions and three logical partitions.  The second drive has one
primary partition, and four logical partitions.  The OS boots from
partition 1 on the first drive.  The drive letters are assigned as:


          Hard Drive 0
       Ŀ
    K:  Primary FAT  
        partition 0  
       Ĵ
    C:  Primary FAT  
        partition 1  
       Ĵ     Ŀ
        Extended       E:  Logical FAT  
        partition 2  Ĵ partition 2a 
       Ĵ     Ĵ
        Primary NTFS   F:  Logical FAT  
        partition 3        partition 2b 
            Ĵ
                         G:  Logical FAT  
                             partition 2c 
                            

          Hard Drive 1
       Ŀ
    D:  Primary FAT  
        partition 0  
       Ĵ     Ŀ
        Extended       H:  Logical FAT  
        partition 1  Ĵ partition 1a 
       Ĵ     Ĵ
        Primary Unix       Logical HPFS 
        partition 2        partition 1b 
       Ĵ     Ĵ
        Unused         I:  Logical FAT  
        partition 3        partition 1c 
            Ĵ
                         J:  Logical FAT  
                             partition 1d 
                             

If this system had a CD ROM drive, it would be assigned by the OS drive
letter L.


Bug in Windows 95/98/Me and DOS

Be aware of a rare but clear bug in all versions of DOS and all versions
of Windows 95/98/Me.  The problem appears when you have more than one
primary FAT partition on any drive, AND you have logical partitions,
where the last logical partition is not FAT.  In this one case, DOS and
Windows will not see the second primary partition, or may indicate the
drive has an invalid media byte.  There is nothing wrong with the
partition, but the OS will not let you use it.

For example, you have two primary FAT partitions, and three logical
partitions, where the last logical is not FAT, but is OS/2's HPFS, NT's
NTFS, or Linux.

.scrollend
.. ............................................................................
.msg 151
.clear
.scroll
.title DOS can't boot from a 2nd drive
.title Windows 95/98/Me can't boot from a 2nd drive

Although System Commander can attempt to boot an OS installed on any
drive, some OSes like DOS and Windows 95/98/Me have fixed internal code
which always assumes installation on one of the primary partitions on the
first physical drive.  The installation programs for DOS and Windows will
only allow installation when a primary FAT partition exists on the first
drive.

Do not confuse this requirement for the location of most of the utility
files.  For example, the Windows 95/98/Me installation program will ask
where you wish to install Windows.  You can specify any valid drive
letter.  Windows 95/98/Me (like DOS) will still install key system files
on the first physical drive's primary FAT partition.  In this case, if
you selected drive D (on a second disk), Windows 95/98/Me installs about
4 MB of files on C, and the remainder of Windows on D.

Some users try to outsmart Windows 95/98/Me or DOS by installing to the
first drive, and then changing the drive positions.  (For IDE drives,
this would involve changing the slave and master jumpers).  This will not
work.  When System Commander launches the DOS or Windows 95/98/Me from a
second drive, DOS/Windows will begin to read critical code and data from
the FIRST DRIVE, even if nothing exists on the first drive!  Of course it
usually hangs the system quickly thereafter.

If you have been considering trying to put the boot portion of DOS or
Windows 95/98/Me on a second or later drive FORGET IT!  System Commander
does allow you to install multiple FAT compatible OSes into the same
partition.  If you need complete isolation, then install each OS into a
separate primary partition on the first drive.  Both these approaches are
covered in detail in the manual.

.scrollend
.. ............................................................................
.msg 152
.clear
.scroll
.title Drive positions should not be changed

Occasionally we have users who have an OS installed on one or more drives,
and want to move the drives around.  A typical situation is a system
with a small first drive, and a new drive is added to the system.

The user wants to place the large drive in the first drive position and
move the old small drive into the second (or third) drive position.

It is very unlikely that you can boot any OS that was already installed on
that first drive now that it is moved to another location.  Almost every
OS, during its installation, will create a number of configuration files
that specify the hard disk number or location.  When the OS is moved to a
new location, these configuration files are no longer valid.  Attempting
to boot the OS will cause it to die, often with strange error messages.

If you are really intent on doing moving an OS to another drive, and the
OS allows installation on that drive, you could attempt to update the
configuration files to make it work.  We have not tried this, and cannot
provide any advice on which files or how to make such modifications.
Also see our note (use F2 index) on Why can't DOS or Windows 95/98/Me
boot from a 2nd drive?

BOOT 2> Error if System Commander is installed

#if SC_DELUXE == 1
If System Commander was not Disabled (from SCIN) prior to moving the
drives around, a reboot may leave you with a  BOOT 2>  error message.
To recover, boot from a Windows 95/98/Me or DOS diskette, and run SCIN.
Select Disable or Remove, and then Disable.
#else
If System Commander was not Uninstalled prior to moving the drives
around, a reboot may leave you with a  BOOT 2>  error message.  To
recover, boot from a DOS or Windows 95/98/Me diskette, and run SCIN.
Select Disable.
#endif

Moving System Commander to the first drive

System Commander is controlled by files that must be in the C root
directory (any primary FAT partition on the first physical drive).
Depending on what you are attempting, you can perform a full new install
of System Commander, or move the following System Commander files to the
C drive:

   SYSCMNDR.SYS
   SYSCMNDR.HLP
   SCDOS.SYS
   SCEDIT.SYS
   SYSIOMGR.SYS

The other files in the SC directory can reside on any drive, and are not
used in the boot up process.  If you have multiple FAT OSes in the same
partition, and wish to move these OSes as well, be sure to make the same
directories for each OS and copy the related files that System Commander
needs, such as CONFIG.SYS, AUTOEXEC.BAT, COMMAND.COM, BOOT.INI, etc. into
each subdirectory.

.scrollend
.. ............................................................................
.msg 153
.clear
.scroll
.title DEFRAG effects on System Commander

The exact location of key System Commander files is not critical and can
be moved by a DEFRAG operation without a problem.

If you have OS/2 and/or Windows 95/98/Me in the same partition as DOS, we
do not recommend using the DOS DEFRAG program, as it may destroy long
filenames used by OS/2 or Windows 95/98/Me.  It will never destroy the
file or file contents, only the long filename.

.scrollend
.. ............................................................................
.msg 154
.clear
.scroll
.title Backup steps for System Commander
.title Restoration of System Commander

Your backup software should backup (and allow restore) of the files
that make System Commander work.  These reside in the C drive's root
directory as hidden system files.  These include at a minimum:

   SYSCMNDR.SYS
   SYSCMNDR.HLP
   SCDOS.SYS
#if (BUILD != BT_SC98) && (BUILD != BT_PC) && (BUILD != BT_PC5)
   SCEDIT.SYS
   SYSIOMGR.SYS
#endif
#if SC_DELUXE == 1
   CHECKMBR.EXE
   SCOSW*.*
#endif

Restoration of these files will restore System Commander.  When
having multiple OSes in the same partition, the related directories and
files should be restored at the same time.

#if SERIES != SC
If you are restoring files after a drive is replaced, after the
restoration completes, run SCIN, and select Enable to complete
the System Commander restoration.  An enable will install System
Commander's master boot record, but does not affect any prior options,
partitions, or choices.
#else
If you are restoring files after a drive is replaced, after the
restoration completes, run SCIN, and select Reinstall to complete the
System Commander restoration.  A reinstall will install System
Commander's master boot record, but does not affect any prior options,
partitions, or choices.

#endif
.scrollend
.. ............................................................................
.msg 155
.clear
.scroll
.title Disabling System Commander
.title Removing System Commander
.title Uninstalling System Commander

#if SERIES != SC
To disable or uninstall System Commander, run SCIN from either the hard
disk or our installation diskette.  Select Disable or Remove.  You can
then select from two choices:

Temporarily Disable System Commander - Use this option to restore
  the original MBR and disable System Commander.  System Commander will
  not appear when you boot, and the last OS you had selected will boot up.

  At a later time, if you wish to enable System Commander, use the Enable
  System Commander (from SCIN) choice to reactivate System Commander.
  All your options and OS selections are restored.

Remove System Commander - This option restores the original MBR
  and deletes the System Commander files.  Once these files are
  deleted, a full installation of System Commander is required to
  activate System Commander again.

#if BUILD != BT_PC && BUILD != BT_PC5
   IMPORTANT  Multiple OSes installed in the MultiFAT (i.e. the
  partition we are installed in) will no longer work.  Even if you
  perform a full System Commander installation, the files that
  were saved to boot each OS are deleted!  You will need to install
  each OS again, except for the current running OS.

  Remove System Commander never affects OSes installed in other
  partitions, although without System Commander, it is often difficult to
  get access to those OSes.

#endif
These two options do not affect any partitions or partition changes you
have made since installing System Commander.

In rare cases, these options fail to remove the System Commander MBR.
This might occur if anti-virus software is running, or the BIOS is
preventing the master boot record from being updated.  Remove the
anti-virus software or turn off the BIOS virus check option.  As another
alternative, System Commander can be uninstalled by using the following
command available in DOS version 5 and later and Windows 95/98/Me:

   FDISK /MBR

Successful FDISK operation is indicated when it returns to the DOS prompt
without any messages.  This command does not alter the partition table.
#else
To uninstall System Commander, run SCIN from either the hard disk or
our installation diskette.  Select Disable/Uninstall and exit.  It is
not necessary to remove any other files.  The uninstall option does not
affect any partitions or partition changes you have made since installing
System Commander.

If at a later time you wish to reactivate System Commander, simply run
SCIN again and select Reinstall.  All your prior options and choices
will reappear.

In rare cases, the uninstall option fails to remove System Commander.
This might occur if anti-virus software is running, or the BIOS is
preventing the master boot record from being updated.  Remove the
anti-virus software or turn off the BIOS virus check option.  As another
alternative, System Commander can be uninstalled by using the following
command available in DOS version 5 and later and Windows 95/98/Me:

   FDISK /MBR

Successful operation is indicated when it returns to the DOS prompt
without any messages.  This command does not alter the partition table.


Removing System Commander files

If you wish to remove all System Commander files, first follow the
instructions above to uninstall.  Reboot once to be sure System Commander
is not in the boot up process.  Run SCIN again, and select Special
options.  Select Expose files for deletion.  Now you can easily
delete the files in the SC directory and the three files in the C root
directory:

   SYSCMNDR.SYS
   SYSCMNDR.HLP
   SCDOS.SYS
   SCEDIT.SYS
#endif
.scrollend
.. ............................................................................
.msg 156
.clear
.scroll
.title Boot Diskette Creation

 You may already have a boot diskette 

Windows 95/98/Me/NT and DOS will all offer to make a boot diskette
when you install those OSes.  The Full pack release of Windows 95 comes
with a Windows 95 boot diskette, and a full DOS installation diskette
can also be used as a boot diskette.  In this case, you boot from the
diskette, and exit the installation at first chance (usually by pressing
F3 when prompted).

 Creating a Windows 95/98/Me boot diskette (easy method) 

At the Windows desktop, select Start, Settings, Control Panel, then click
on the Add/Remove Programs icon.  Select the Startup Disk tab, and click
on Ok.  Windows will make the bootable disk and add all the important
files that would be useful to you.

 Creating a DOS or Windows 95/98 boot diskette (manual method) 

To create a boot diskette for DOS or Windows 95/98, you must have the OS
already installed on a system.  Boot into the OS, and go to a DOS prompt
(in Windows 95/98, open a DOS box).  Insert a blank diskette into the A:
drive.  If the diskette is not formatted yet, issue the format command:

   C:\ > format  a:

Load the system onto the diskette:

   C:\ > sys a:

Now copy key files to the diskette.  If creating a Windows 95/98 boot
diskette, the files normally reside in the \WINDOWS\COMMAND\ directory.
The files for DOS can be in a directory \DOS, or \BIN, or other name that
you specified during the original DOS installation.  Use the following
generic copy line where the path is where the file exists:

   C:\ > copy  \path\filename  a:

At a minimum, copy the following files to the new boot diskette:

   COMMAND.COM
   FORMAT.*
   FDISK.*
   SYS.*
   ATTRIB.*

You can copy additional programs to your boot diskette, such as your
editor files, if desired.  Remember there is a limited amount of room on
the diskette, so don't even attempt to copy Windows programs over to the
diskette.

Now try out your new boot diskette.  Shutdown Windows (or Ctrl-Alt-Del
if in DOS).  You should boot from the diskette and appear at a prompt.

.scrollend
.. ............................................................................
.msg 200
.clear
.scroll
.title Message 'Boot ##.' and hangs
.title Boot ##. message appears and then hangs

Cause: This indicates a problem in starting up the system or reading
   the disk drive.  With "Boot XY." the error code characters XY
   indicate the problem that occurred.  The first charter "X" indicates
   the basic type of error that occurred.  These problems include:

        "X" Character    Type of error
            
        0                Disk error reading the master boot record
        1                No FAT partition found on drive 0
        2/3/4/5          FAT found, but unable to locate SYSCMNDR.SYS
                           file in root directory, or a disk error
                           occurred reading the file, or the partition
                           is not 512 bytes per sector (the
                           DOS/Windows 95/98/Me standard).
        A                Disk error reading FAT
        B                Disk error reading SYSCMNDR.SYS
        C                Defective cluster encountered
        F                Could not find the SYSCMNDR.SYS file or a bad
                           cluster area was encountered (FAT32 only)
        G                Problem reading the SYSCMNDR.SYS file (FAT32
                           only)
        H                The contents of the SYSCMNDR.SYS file are bad
                           (FAT32 only)

   The second "Y" character indicates the error code returned from the
   hard disk BIOS.  It may indicate the hard disk or controller has some
   type of problem, or could indicate bad partition information on the
   disk.  BIOS error codes are:

        "Y" Character    Hard Disk BIOS error
            
        0                invalid or missing data (see note below)
        1                invalid drive or command
        2                missing address mark
        3                write protected
        4                sector not found
        8                DMA overrun (time-out)
        :                bad sector detected
        ;                bad track detected
        >                invalid or missing data (see note below)
        @                ECC error during read
        A                ECC error during read
        P                disk controller/drive problem
        p                seek operation failed
                        time-out - no response
        others           undocumented BIOS error

    Note: The second character errors "0" and ">" are not BIOS errors,
    but indicate the desired data was not found on the disk.

Action: The codes help identify the source of the problem.  Several
   combinations we've seen on occasion include:

   Boot 0x. (where x is any character)  This could indicate a bug
   in the BIOS of the hard disk controller or main system BIOS.
   System Commander has a special option to bypass the bug.  To set
   this up, boot from a DOS or Windows 95/98/Me diskette. Run SCIN MBR80
#if SERIES != SC
   from the hard disk or our diskette.  Select the Enable
   option.  Exit and reboot from the hard disk.
#else
   from the hard disk or our diskette.  Select the Reinstall option.
   Exit and reboot from the hard disk.
#endif

   Boot 2>. This indicates that the SYSCMNDR.SYS file could not be
   found in any primary partition on the first drive.  To fix this, boot
   from a DOS or Windows 95/98/Me diskette and perform a full install.

   Boot A@. This indicates that System commander was attempting to read
   the FAT, but the controller found an ECC error (which indicates a
   defective sector in the FAT data area).  At a minimum, run DOS's
   SCANDISK on the drive and have it correct any errors.  Be sure to
   perform the optional surface scan within SCANDISK.

   Boot Ax. (where x is any character)  If your system is using a
   Quantum Atlas SCSI drive, some older Atlas drives have a firmware
   bug that prevents System Commander from operating.  This bug will also
   prevent NT v4.0 from working as well (with a variety of possible error
   messages from NT).  You will need to update your Quantum drive
   firmware to XL915 or later.  We have confirmed this corrects the
   problem. As a temporary fix, boot from a DOS or Windows 9x/Me diskette,
#if SERIES != SC
   run SCIN (our diskette or hard disk) and select "Disable or
   Remove".  Then select "Temporarily Disable System Commander".
#else
   run SCIN (our diskette or hard disk) and select "Disable/Uninstall".
#endif

   To view the firmware version, when loading DOS or Windows 95/98/Me
   with the appropriate ASPI driver, the hard disk identification code
   will appear something like:  Quantum XP23150W L915.  The last four
   characters are the firmware version of the drive.  Additional notes
   relating to NT are available in the Microsoft Knowledgebase article
   Q158100.

   To fix other codes

   Assuming no physical drive problems, see the entry under DOS about
   "System Fails to boot up".  If the C: drive is inaccessible even from
   a DOS boot diskette, see the message "Can't access drive" under DOS.

   Disk compression often makes files inaccessible and can also cause
   some of these conditions.

   The SYSCMNDR.SYS file must reside in the root directory on the real
   (non-compressed) hard drive 0.  SYSCMNDR.SYS is installed as a hidden
   system file.  The SCIN uninstall option can switch these attributes
   to non-hidden, non-system so the file appears when viewing the
   directory contents.  The attributes of SYSCMNDR.SYS do not affect the
   operation of System Commander.

   System Commander does not care which partition on drive 0 is FAT, as
   it checks all four partitions, looking for a valid FAT partition
   that has SYSCMNDR.SYS.

   In some cases, the SCIN diagnostic can help locate the source of the
   problem.  Select Diagnostic checks, under Special options.

.scrollend
.. ............................................................................
.msg 201
.clear
.scroll
.title System fails to boot up

Cause: If you have some DOS partitions you have created on the first
   drive, but have not formatted them yet, this condition may occur.  It
   can also occur if your have added or are using disk compression and
   our files are not on the non-compressed drive.  The following
   instructions will restore the original master boot record.

Action: First boot the system from a DOS or Windows 95/98/Me diskette.
   If possible, switch to the directory on the hard disk where you
#if SERIES != SC
   installed System Commander.  Run SCIN and select "Disable or
   Remove".  Then select "Temporarily Disable System Commander".  Exit
   System Commander and reboot normally (without System Commander).

   If you could not locate the System Commander directory on the hard
   disk, Run SCIN from the System Commander diskette and select "Disable
   or Remove".  Then select "Temporarily Disable System Commander".
   System Commander restores the master boot record which was previously
   saved on the diskette during the original installation.
#else
   installed System Commander.  Run SCIN and select Disable/uninstall.
   Exit System Commander and reboot normally (without System Commander).

   If you could not locate the System Commander directory on the hard
   disk, Run SCIN from the System Commander diskette and select
   Disable/uninstall.  System Commander restores the master boot record
   which was previously saved on the diskette during the original
   installation.
#endif

   If this still does not correct the problem and you were using disk
   compression, it is likely the DOS bootable disk also has the disk
   compression software hidden on it, and the boot drive is being
   masked.  To fix the DOS boot diskette, you need to rename the hidden
   file DBLSPACE.BIN on the diskette.  To do this, you must first change
   the attributes.  Use the commands:

        A:\ > ATTRIB  -R -H -S  A:DBLSPACE.BIN

        A:\ > RENAME  A:DBLSPACE.BIN  DBLSPACE.TMP

   Now reboot off this diskette, and disable System Commander again.
   This will work for Stacker 3.1/4.0 and for DOS 6's
   DoubleSpace/DoubleDisk.  Other disk compression products may use other
   hidden files that need to be temporarily changed.
#if SERIES != SC
    NOTE:  Disable only replaces the master boot record.  It does not
   change the current partition information.  There is no problem
   performing a Disable, even if you had changed the partition
   information after System Commander was installed.  The original master
   boot record information is saved in a hidden read only file BOOT.DAT
   on both the hard disk and the System Commander diskette.

   If Disable fails to work, you can also attempt to use an undocumented
   (but safe) option in FDISK supplied in DOS 6 or later and Windows
   95/98/Me.  At the prompt enter:
#else
    NOTE:  Disable/Uninstall only replaces the master boot record.  It
   does not change the current partition information.  There is no
   problem performing an Uninstall, even if you had changed the partition
   information after System Commander was installed.  The original
   master boot record information is saved in a hidden read only file
   BOOT.DAT on both the hard disk and the System Commander diskette.

   If uninstall fails to work, you can also attempt to use an
   undocumented (but safe) option in FDISK supplied in DOS 6 or later and
   Windows 95/98/Me.  At the prompt enter:
#endif

        A:\ > FDISK  /MBR

   This inserts a new generic master boot record (which 99.99% systems
   have anyway).  It does not change the partition table contents.  If
   the option works correctly, FDISK will return to a DOS prompt without
   any messages.

.scrollend
.. ............................................................................
#if BUILD != BT_SC98
.msg 202
.clear
.scroll
.title Possible defective boot record

Cause: When this message appears after a non-DOS boot selection is
   made, the selected OS does not have a boot record, or uses a
   non-standard format.  If you selected (B) to boot anyway and the OS
   works, we would like to hear from you.  It appears the OS you are
   using does not follow any prior standard.

   If the OS fails to boot, it indicates the OS has not properly built
   the boot record or other critical files are missing from the
   partition.  It may also indicate the OS does not allow booting from
   the selected partition, and it should be removed from the OS
   selection menu.

Action: To remove a selection, select Setup (Alt-S) from the OS
   selection menu, and move to the Order, add and removal menu.
   Highlight the OS partition you wish to remove, and press Remove
   (Alt-R).

   Some operating systems may boot through the DOS partition, even
   though the OS is in a separate partition.  NT is a prime example of
   this.  NT does not normally boot directly into the NTFS partition
   until the NT bootup files in the DOS partition are run.  See chapter
   4 in the System Commander manual for more about NT operation.

.scrollend
#endif
.. ............................................................................
.msg 203
.clear
.scroll
.title Disk error

Cause: If you have non-standard hard drives which cannot be properly
   accessed without a special device driver, System Commander may not be
   able to update partition information on that drive.  IDE, EIDE, ESDI,
   MFM, and SCSI drives do not usually fall into this category.

   For example, some hardcards remain in a read-only mode until their
   device driver runs.  These types of drives are usually limited to
   DOS, since device drivers are rarely available for other operating
   systems.

Action: It is safe to select Ignore instead of the recommended Reboot
   from the disk error warning message.  To eliminate the problem
   (without replacing the drive), from the OS selection menu, press
   Alt-S (Setup), and select the Global special options menu.

   Select the choice Disk drives, above drive 0, ignored.  If the
   problem drive is the third drive, select > 1.  If you only need
   System Commander to look at the first drive, select > 0.  This
   option forces System Commander to ignore the specified drives.  Drive
   0 will always be accessible.

.scrollend
.. ............................................................................
.msg 204
.clear
.scroll
.title Slow Booting
.title Long delay before System Commander appears
.title Long delay after OS selection, before OS starts

Cause: A few system BIOSes incorrectly count the CD drive or other
   non-hard disk devices as a hard disk.  This count is used by System
   Commander to look at each hard disk on the system.  When a CD or
   other device "claims" to be a hard disk, the system typically waits a
   very long time (30 seconds to 5 minutes) before responding back to
   System Commander that an operation cannot be done.

Action: This is quite easy to correct.  A special option within System
   Commander instructs System Commander to ignore these phantom
   hard drives. You can set this option from DOS/Windows 95/98/Me or at
   boot time:
                   From DOS or Windows 95/98/Me 

   Run the SCDISK utility with the special command line option DLIMITn,
   where n the drive limit number.  For example, if your system has
   one hard disk, the DLIMIT value should be 1 (meaning that 1 drive is
   the limit, and the 2nd drive and above are ignored).  For the one
   hard drive case, the command line is:

        C:\ > scdisk  dlimit1

           	    From System Commander at boot time 

   Press Alt-S (Setup), and select the Global special options menu.
   Select the drive limit on the option "Disk drives, above drive 0
   ignored".  For a single hard disk system, the option should be > 0.
   For a two hard disk system, use the setting > 1.

.scrollend
.. ............................................................................
.msg 205
.clear
.scroll
.title No Operating System Found

Cause: Before System Commander appears, the message appears
   No Operating System Found and the system refuses to boot.

   This error message is not from System Commander, but a BIOS message
   or software running prior to System Commander.  The BIOS or software
   looks at the partition table.  When no primary partition is marked
   as active (bootable) it erroneously thinks that there is no operating
   system.  It may have been that System Commander booted an OS on a
   second or later drive, or a logical partition was booted, so no
   primary partition on the first drive would be active.

Action: To get out of this situation the first time, boot from a DOS
   or Windows 95/98/Me diskette and run FDISK. Make one of the partitions
   on the first drive active (it doesn't matter which partition is
   active).  Reboot from the hard disk, and the error message should
   disappear.  Then apply the appropriate fix below:

   Users of Buslogic SCSI adapters (and possibly other SCSI adapters)

   At boot time, go into the SCSI adapter setup program.  Select the
   "Advanced" menu, and change the option "Adapter BIOS controls
   booting" to NO.  Save and exit setup.   This option turns off the
   problem logic in the BIOS.

   Other users

   At the System Commander selection menu, press Alt-S (Setup) and go
   to Global special options menu.  Change the option "Force partition
   active on drive 0" to YES.  System Commander will ensure that one
   primary partition on the first drive will always be set active.  Be
   aware that in some rare cases, an operating system not installed on
   the first drive could become confused and not boot properly.

.scrollend
.. ............................................................................
.msg 210
.clear
.scroll
.title Partition Table Analysis Failed

Cause: Values in the partition table are not valid, such as a partition
   size of 32 GB or larger, a starting address larger than the drive
   parameters reported by the BIOS, or a starting or ending sector value
   of zero (invalid).

Action: The values in error are shown in red. It may be the
   partition does not exist and has bad values.  Use FDISK if you are
   sure this is the case to delete the invalid partition.

.scrollend
.. ............................................................................
.msg 211
.clear
.scroll
.title Partition Table Analysis Warnings

 First sector size mismatch 

Cause: Each partition table entry points to the start of a partition by
   the start head, sector and cylinder, and through an alternate way,
   the starting sector count.    The two methods should point to the
   same place on the disk, but they do not in this case.

Action: System Commander and many OSes only use the starting head,
   sector and cylinder values.  If these values are wrong, you will not
   be able to boot the partition.  If on the other hand, the first
   sector value is wrong, everything is likely to work fine.  There is
   no easy fix, other than deleting the partition and re-creating it
   (which of course, loses all the data in that partition).  There is
   not enough information available to identify which entry is wrong
   from the values.


 Ending address too large 

Cause: The ending head, sector, or cylinder numbers exceed the disk
   limits as specified by the BIOS.

Action: System Commander and many OSes ignore the ending values.  If
   your system is working fine, you might ignore the problem.  The only
   fix is to delete the partition, and re-create it (which will cause
   the loss of all data in the partition).


 Sector mismatch & Ending address 

The prior two warning conditions occurred on the drive.   See the prior
warnings for complete details.

.scrollend
.. ............................................................................
.msg 212
.clear
.scroll
.title Unable to read Drive Parameters

Cause: The BIOS returned an error while attempting to read the drive
   parameters.

Action: The BIOS is not working properly - try an another disk
   controller card or the CMOS has values for a drive that does not
   exist.

.scrollend
.. ............................................................................
.msg 213
.clear
.scroll
.title Unable to read Partition Table on Drive n

Cause: The BIOS returned an error when attempting to read the master
   boot record.

Action: There may be a serious problem with the drive or disk
   controller.  If this one sector is truly bad, the disk drive is
   unusable.

.scrollend
.. ............................................................................
.msg 214
.clear
.scroll
.title DOS Boot Record Checks

Serious errors are highlighted in red, which indicate source of
problem.  Minor warnings are highlighted in orange.

Serious errors will likely make OSes fail, and may make System Commander
unusable.  The specific values and limits are shown on each line of the
display. A new DOS boot record can be created using the SYS command from
a bootable DOS diskette.

.scrollend
.. ............................................................................
.msg 215
.clear
.scroll
.title File Access Verification Failed

 Error 1: Cannot open C:\SYSCMNDR.SYS 

Cause: The file SYSCMNDR.SYS could not be found

#if SERIES == SC2K || SERIES == SC7
Action: Perform a SETUP from the System Commander CD-ROM.  Be
   sure to install to the non-compressed drive if you are using
   disk compression.
#else
#if SERIES != SC
Action: Perform a SETUP from the System Commander diskette.  Be sure
   to install to the non-compressed drive if you are using disk
   compression.
#else
Action: Perform an INSTALL from the System Commander diskette.  Be sure
   to install to the non-compressed drive if you are using disk
   compression.
#endif
#endif

 Error 2: MBR BIOS read failure 

Cause: The BIOS returned an error reading the MBR (Master Boot Record).

Action: This might indicate a problem with the drive, the disk
   controller, or a TSR/driver that interferes with MBR access.


 Error 3: No DOS Partition or boot record found 

Cause: The test was unable to find any primary DOS partitions on the
   first drive, or if a DOS partition was found, it did not have a valid
   boot record.

Action: You must have a FAT primary partition on the first drive to
   install System Commander.  Use FDISK to create one, and then format
   and install DOS.


 Error 3a: BIOS Read drive parameters failed 

Cause: The BIOS returned an error when attempting to read the hard disk
   parameters.

Action: This may indicate a CMOS parameter error, or a drive or
   controller problem.


 Error 4: DOS read error 

Cause: While attempting to read a file from the disk, DOS returned an
   error.

Action: Run SCANDISK or CHKDSK /F to locate and fix any disk problems
   or bad sectors.


 Error 5: First sector comparison wrong 

Cause: This test reads the first sector of the file SYSCMNDR.SYS in the
   root directory through DOS and independently through the BIOS.  The
   byte for byte comparison failed, when it should be identical.

Action: If your system requires some type of unusual device driver for
   access to the hard disk, it may be impossible for System Commander to
   read the disk through the BIOS.  It is likely that other OSes will
   also have serious problems installing.  Consider a more standard
   drive, such as IDE, EIDE, or a current SCSI drive and controller.
   One product that might cause this is EZ-Boot.


 Error 7: BIOS read error, 1st sector 

Cause: When the BIOS attempts to read the first sector from the disk,
   the BIOS returns an error.

Action: See the action portion of the previous errors 3a, 4, and 5.


 Error 8: BIOS read error, dir read 

Cause: When the BIOS attempts to read the root directory portion of the
   disk, it returns an error.

Action: See the action portion of the previous errors 3a, 4, and 5.


 Error 9: BIOS read error, FAT 

Cause: When the BIOS attempts to read the File Allocation Table (FAT)
   portion of the disk, it returns an error.

Action: See the action portion of the previous errors 3a, 4, and 5.


 Error 10: BIOS read error, SYSCMNDR.SYS 

Cause: When the BIOS attempts to read the SYSCMNDR.SYS file, it returns
   an error.

Action: See the action portion of the previous errors 4  and 5.


 Error 11: Bad cluster in chain 

Cause: While attempting to read the SYSCMNDR.SYS file, a bad cluster
   was encountered, which should never occur.

Action: See the action portion of the previous errors 4 and 5.


 Error 12: DOS read error, SYSCMNDR.SYS 

Cause: DOS returned an error when attempting to read the SYSCMNDR.SYS
   file.

Action: Run SCANDISK or CHKDSK to locate and fix any disk problems or
   bad sectors.  Try reinstalling System Commander from the diskette.


 Error 13: BIOS-DOS sector comparison mismatch 

Cause: The byte for byte comparison failed when reading the file
   SYSCMNDR.SYS from DOS and from the BIOS.

Action: Run SCANDISK or CHKDSK to locate and fix any disk problems or
   bad sectors.  Try reinstalling System Commander from the diskette.


 Error 14: Cannot find SYSCMNDR.SYS dir entry 

Cause: The SYSCMNDR.SYS file does not appear in the non-compressed C:
   root.

#if SERIES == SC2K || SERIES == SC7
Action: Perform a SETUP from the System Commander CD-ROM.  Be
   sure to install to the non-compressed drive if you are using
   disk compression.
#else
#if SERIES != SC
Action: Perform a SETUP from the System Commander diskette.  Be sure
   to install to the non-compressed drive if you are using disk
   compression.
#else
Action: Perform an INSTALL from the System Commander diskette.  Be sure
   to install to the non-compressed drive if you are using disk
   compression.
#endif
#endif

.scrollend
.. ............................................................................
.msg 216
.clear
.scroll
.title Virus Warning - During Installation or from SCIN

System Commander looks to see if the full amount of DOS memory is
available.  On most systems, it should be 640 KB.  Lower numbers may
suggest that a virus exists in the system.

If this number is under 640 KB, a virus may be present, or it could be
caused by one or more of the following valid situations:

    Some system BIOSes use 1 KB for BIOS data.  This is common on IBM
     PS/2 machines and old EISA systems.

    A hard disk controller card's BIOS may take 1 to 4 KB of memory
     to improve disk performance.  A few of the known cards that do this
     include:
                GSI (1 KB)
                Promise 2300 (3 KB)
                Older HP SCSI adapters (4 KB)

    Software products that provide LBA support on IDE drive (i.e.
     makes drives greater than 504 MB usable).  This includes:
                On-Track's Disk Manager
                Micro-House's EZ-Drive
                SPExports

Viruses that affect the Master Boot Record are often badly written and
will cause weird problems when partitioning your disk.

Viruses can also affect System Commander, so we do not recommend
installing System Commander when a virus already exists in a system.


How Viruses operate out of the Master Boot Record

   Once the system is infected (typically through a COM or EXE file, or
   attempting to boot from an infected diskette), the boot virus
   will insert itself into the Master Boot Record (MBR) to ensure it
   will be run every time the system boots up.  When the infected MBR
   runs, it moves the virus code into RAM, and often changes the hard
   disk interrupt pointer to its code.  In addition, when the MBR was
   infected, the virus moves a copy of the original MBR to a different
   place on the disk.

   Since the virus is in control for every disk read and write, it can
   detect attempts to read and write the MBR, and redirect these
   accesses to the MBR copy instead of the real infected MBR.  This
   helps hide the virus and makes it difficult to remove.

Looking for signs of a virus

   One simple test can help identify if a virus might be infecting your
   system.  Boot from a DOS boot diskette (that has the write protect
   tab on and is known not to be infected) and run the DOS MEM command.
   The first number (typically 640 KB) should be the same value as when
   booting from the hard disk and running the MEM command from the hard
   disk.

   In any case, values less than 640 KB are suspicious and a good virus
   detection program should be run.

   The SCIN virus detection diagnostic provides an option (F8) to
   look into memory where the suspected virus may reside.  Any strings
   that appear in this area of memory will be displayed.  If strings
   do appear, they may indicate a legitimate user of this memory or
   strings used within the virus.

   For example, if you see a copyright message from software you have
   installed, it is not likely a virus.  On the other hand, the
   appearance of profanities, curses or other nonsense usually
   indicates a virus infection.

.scrollend
.. ............................................................................
.msg 217
.clear
.scroll
.title Unable to Write MBR

#if SERIES == SC2K || SERIES == SC7
System Commander must install a new master boot record to provide
different OS choices before any OS runs.  The Disable option
restores the original MBR. It is likely that the current OS, BIOS, or a
TSR interferes with the disk write.

Once the problem is solved, it is not necessary to fully install System
Commander again.  Simply run SCIN from the hard disk and select
Enable.  If the problem is solved, you will not get an error
message, and the System Commander installation will be complete!

 Possible Cause 1 - Anti-Virus Software 

A few anti-virus software packages prevent System Commander from updating
the MBR.  Temporarily remove the anti-virus software and reboot OR
simply boot from a Windows 95/98/Me or DOS boot diskette.  Run SCIN
from the hard disk, and select Enable.

 Possible Cause 2 - BIOS Anti-Virus option is Enabled 

Some PCs have an option in the BIOS to prevent the MBR from being written.
This option is stored in the system CMOS.  Since every vendor is
different, you will need to reboot into the BIOS setup program (typically
by holding down a key like "Del" or "Esc".  Once in the setup, look for
an option controlling the MBR or an option with the word "Virus" in it.
Make sure the option is Disabled.  Often this option is under a menu
called "Advanced".  Not all systems have an option to prevent MBR
writes, so if no option is found, this is not the problem.

If the option was found, and you switched it to "Disabled", save the CMOS
changes and exit.  Boot up the system, and run SCIN from the hard disk
and select Enable.

 Possible Cause 3 - OS is not DOS or Windows 95/98/Me 

If you attempted the installation from a DOS box in OS/2 or NT, these DOS
emulations fail to allow access to the MBR.  You must reboot from a real
DOS or Windows 95/98/Me boot diskette to complete the installation.  Once
booted from a diskette, run SCIN from the hard disk and select
Enable to finish the installation.

#else
#if SERIES != SC
System Commander must install a new master boot record to provide
different OS choices before any OS runs.  The Disable option
restores the original MBR. It is likely that the current OS, BIOS, or a
TSR interferes with the disk write.

Once the problem is solved, it is not necessary to fully install System
Commander again.  Simply run SCIN from the hard disk or our diskette,
and select Enable.  If the problem is solved, you will not get
an error message, and the System Commander installation will be complete!

 Possible Cause 1 - Anti-Virus Software 

A few anti-virus software packages prevent System Commander from updating
the MBR.  Temporarily remove the anti-virus software and reboot OR
simply boot from a Windows 95/98/Me or DOS boot diskette.  Run SCIN
from the hard disk (SC directory) or our diskette, and select
Enable.

 Possible Cause 2 - BIOS Anti-Virus option is Enabled 

Some PCs have an option in the BIOS to prevent the MBR from being written.
This option is stored in the system CMOS.  Since every vendor is
different, you will need to reboot into the BIOS setup program (typically
by holding down a key like "Del" or "Esc".  Once in the setup, look for
an option controlling the MBR or an option with the word "Virus" in it.
Make sure the option is Disabled.  Often this option is under a menu
called "Advanced".  Not all systems have an option to prevent MBR
writes, so if no option is found, this is not the problem.

If the option was found, and you switched it to "Disabled", save the CMOS
changes and exit.  Boot up the system, and run SCIN from the hard disk
(SC directory) or our diskette, and select Enable.

 Possible Cause 3 - OS is not DOS or Windows 95/98/Me 

If you attempted the installation from a DOS box in OS/2 or NT, these DOS
emulations fail to allow access to the MBR.  You must reboot from a real
DOS or Windows 95/98/Me boot diskette to complete the installation.  Once
booted from a diskette, run SCIN from the hard disk (SC directory) or
our diskette, and select Enable to finish the installation.
#else
System Commander must install a new master boot record to provide
different OS choices before any OS runs.  The Disable/uninstall option
restores the original MBR. It is likely that the current OS, BIOS, or a
TSR interferes with the disk write.

Once the problem is solved, it is not necessary to fully install System
Commander again.  Simply run SCIN from the hard disk or our diskette,
and select Reinstall.  If the problem is solved, you will not get an
error message, and the System Commander installation will be complete!

 Possible Cause 1 - Anti-Virus Software 

A few anti-virus software packages prevent System Commander from updating
the MBR.  Temporarily remove the anti-virus software and reboot OR
simply boot from a Windows 95/98/Me or DOS boot diskette.  Run SCIN
from the hard disk (SC directory) or our diskette, and select
ReInstall.

 Possible Cause 2 - BIOS Anti-Virus option is Enabled 

Some PCs have an option in the BIOS to prevent the MBR from being written.
This option is stored in the system CMOS.  Since every vendor is
different, you will need to reboot into the BIOS setup program (typically
by holding down a key like "Del" or "Esc".  Once in the setup, look for
an option controlling the MBR or an option with the word "Virus" in it.
Make sure the option is Disabled.  Often this option is under a menu
called "Advanced".  Not all systems have an option to prevent MBR
writes, so if no option is found, this is not the problem.

If the option was found, and you switched it to "Disabled", save the CMOS
changes and exit.  Boot up the system, and run SCIN from the hard disk
(SC directory) or our diskette, and select ReInstall.

 Possible Cause 3 - OS is not DOS or Windows 95/98/Me 

If you attempted the installation from a DOS box in OS/2 or NT, these DOS
emulations fail to allow access to the MBR.  You must reboot from a real
DOS or Windows 95/98/Me boot diskette to complete the installation.  Once
booted from a diskette, run SCIN from the hard disk (SC directory) or
our diskette, and select ReInstall to finish the installation.
#endif
#endif

 Possible Cause 4 - Software is used to support a drive > 504 MB 

Several software LBA (Logical Block Address) packages currently exist to
allow access to IDE drives that are greater than 504 MB.  These software
packages act like a TSR and replace the MBR with their own MBR, and
prevent anyone else from using the MBR.  The older versions of the Micro-
House Drive-Pro/EZ-Drive/EZ-BIOS product never allows MBR writes.  On
Track's Overlay Disk Manager does not allow MBR writes if the first drive
is less than 504 MB, and another drive in the system is greater than 504
MB.  On Track's disk manager normally allows MBR writes when the large
drive is the first drive.

A number of solutions are available, but they normally require deleting
partitions (and all the data on the drive), so be sure to have a good
backup of any key programs and data.

Solution 4A: Update your motherboard BIOS with a new one that supports
             large drives (typically the desired feature is called LBA).
             Set the BIOS's CMOS setup to use the LBA option (most
             BIOS's offer an auto-detect feature to do this).

             Use the LBA software vendor's uninstall instructions to
             remove the offending software OR boot directly from a DOS or
             Windows boot diskette and use the following instructions:
             At the prompt, run FDISK /MBR.  Then run FDISK to delete
             all partitions and use FDISK again to create the new
             partitions.  Remember to format the new partition and
             reinstall the OS.  Finally, restore your data from your
             backup.

Solution 4B: Install a true EIDE disk controller that supports IDE
             drives greater than 504 MB.  These adapters provide their
             own disk BIOS that has LBA support built in.  These products
             often improve your disk performance and use less memory than
             the software LBA approaches.  Once the new adapter is
             installed and setup, you need to remove the old LBA
             software.

             Use the LBA software vendor's uninstall instructions to
             remove the offending software OR boot directly from a DOS or
             Windows boot diskette and use the following instructions:
             At the prompt, run FDISK /MBR.  Then run FDISK to delete
             all partitions and use FDISK again to create the new
             partitions.  Remember to format the new partition and
             reinstall the OS.  Finally, restore your data from your
             backup.

Solution 4C: If using Micro House Drive-Pro/EZ-Drive/EZ-BIOS, upgrade
             to version 9 or later (On some systems, an EZ-Drive upgrade
             does not correct the problem. In these cases, a full backup
             is necessary, EZ-Drive must be completely removed, and the
             new version 9 EZ-Drive installed.  Then the backup can be
             restored.)


Solution 4D: If using On Track's Disk Manager, switch the drives so the
             large drive is the first drive.  You may need to re-install
             Disk Manager after swapping the drives.  Also keep in mind
             that it is very unlikely any OS will run after swapping the
             drives.  All OSes expect to remain on the drive letter they
             were installed on and get very confused when the drive is
             swapped.  It is likely a new installation of the OS will be
             required, or restore the OS from the old drive to the new
             drive from your backup.

 When all else fails 

#if SERIES == SC2K || SERIES == PC5 || SERIES == SC7
Simply boot from a Windows or DOS boot diskette.  Run SCIN from the
hard disk and select Enable. This will often deal with unknown
anti-virus software and other abnormalities.
#else
#if SERIES != SC
Simply boot from a Windows or DOS boot diskette.  Run SCIN from the
hard disk (SC directory) or our diskette, and select Enable.
This will often deal with unknown anti-virus software and other
abnormalities.
#else
Simply boot from a Windows or DOS boot diskette.  Run SCIN from the
hard disk (SC directory) or our diskette, and select ReInstall.  This
will often deal with unknown anti-virus software and other abnormalities.
#endif
#endif

.scrollend
.. ............................................................................
#if BUILD != BT_SC98
.msg 220
.clear
.scroll
.title SC fails to detect a new OS installation

Although rare, if the newly installed DOS has a boot record identical to
a prior installed DOS and the hidden system files have the same date and
time, System Commander may not offer the choice to save the new DOS.  In
this case, do not make a new selection from the System Commander menu,
but use the default  choice to avoid System Commander overwriting the new
DOS information.  At the DOS prompt, run SCIN from the System Commander
directory, and select Special options.  Then select Alter Current Boot
Record Serial Number.  Select YES, and then exit SCIN.  Reboot, and
System Commander should detect and save the new DOS.

.scrollend
#endif
.. ............................................................................
.msg 221
.clear
.scroll
.title OS selection menu does not appear after reboot

This might occur if a newly installed OS overwrites System Commander's
master boot record.  If this is the case, you need to first boot DOS or
Windows 95/98/Me from a diskette or the hard disk.  If you just installed
OS/2 or NT in the DOS partition, then boot from a DOS floppy.  Do not use
the DOS box from these OSes.  The DOS box of Windows 95/98/Me is
acceptable.

Once DOS or Windows 95/98/Me is running, switch to the System Commander
installation diskette or the subdirectory SC on the hard disk. Run SCIN
#if SERIES != SC
and select Enable.  This updates the master boot record without
changing any options you have set.  Exit SCIN, and reboot.
#else
and select Enable/Reinstall.  This updates the master boot record
without changing any options you have set.  Exit SCIN, and reboot.
#endif

If no new operating system was installed, it might mean that the hidden
system file SCDOS.SYS was deleted or destroyed.  This important file in
the C: root directory holds other hidden system files for each FAT
operating system.  If it is destroyed, you must restore it from a backup
or must re-install each operating system.  Assuming all other OS files
are intact, as an alternative, you can take these steps rather than
reinstalling each OS.

1) Boot from a floppy of the desired OS.

2) From the floppy, type  SYS C:  to transfer the hidden files onto
   the hard disk.

3) From the hard disk directory where the same OS has all of the system
   files, copy COMMAND.COM, CONFIG.SYS and AUTOEXEC.BAT to the C: root
   directory.

4) Reboot from the hard disk to make System Commander save the new OS.
   It will prompt for the new menu name and subdirectory where System
   Commander will save key files like CONFIG.SYS, AUTOEXEC.BAT and
   COMMAND.COM.

.scrollend
.. ............................................................................
.msg 222
.clear
.scroll
.title OS selection menu appears again after selection

Some versions of QEMM will force the system to reboot twice, or multiple
times when performing optimization.  Select the same choice until QEMM is
satisfied.  There may be options in QEMM to prevent this behavior.

.scrollend
.. ............................................................................
.msg 223
.clear
.scroll
.title Screen colors unreadable

If the installation program has difficulties displaying, or the color
combinations are hard to read, there are a number of options to control
this.  Refer to Chapter 5 under SCIN Command Line Options.  The -v
command line option will turn off the use of graphics, and may help with
video adapters that are not 100% VGA compatible.

If the screen is unreadable with the SCDISK utility, use the command line
option -v.

If the screen is hard to read or unreadable at boot time with System
Commander, two options are available:

    At boot time at the OS selection menu press Alt-S (Setup),
    and select the Global special options menu.  Then toggle the option
    Prevent the use of graphics to YES.

                           - or -

    At a DOS or Windows prompt, run:

        scdisk  no_font

    This will turn off graphics in both SCDISK and the System Commander
    boot time programs.

.scrollend
.. ............................................................................
#if BUILD != BT_SC98
.msg 224
.clear
.scroll
.title Disk compression software issues

Disk compression software such as DoubleSpace, Stacker and SuperStor
compress the disk and may change the drive lettering around.  System
Commander is fully compatible, but it must be installed in the
non-compressed portion of the disk.  This is necessary, since it is
impossible to read any files from the compressed portion until the
compression software driver is running.

Consult your compression software manual to find where the non-compressed
software resides.

Technical support cannot assist you with problems of trying to run
multiple OSes inside a single compressed partition.  The best strategy,
when you must have disk compression software, is to always place new OSes
in their own isolated partition.

When using any partitioning product, be VERY careful about assuming what
drive you are working on, as drive letters will usually appear
differently than what you see when the drive compression software alters
the true drive lettering!

.scrollend
#endif
.. ............................................................................
.msg 225
.clear
.scroll
.title Unpredictable/flaky behavior

If System Commander is erratic or partitioning the disk seems unstable,
suspect a possible virus has infected the Master Boot Record.  Run a
good, up to date virus detection program (the one included with DOS is a
bit weak for this).

Also be sure to run the SCANDISK or CHKDSK utilities to check for bad
disk sectors and ensure the file system has no errors.  Correct any
errors found.  If errors are detected in the two files that run System
Commander SYSCMNDR.SYS and SCDOS.SYS, a full System Commander
installation from the installation diskette is recommended.

With a new installation it may be necessary to skip the transfer the
data from the installed copy to the new copy.  First install the new copy
transferring the data.  If the system is still unstable, try a new
installation without transferring the data from the old copy.  Be aware
this will loose any OSes, except for the running OS, in the partition
System Commander is installed in.  (It will never affect OSes installed
in other partitions).

.scrollend
.. ............................................................................
#if BUILD != BT_SC98
.msg 226
.clear
.scroll

.title System Transfer Error Messages

While attempting to transfer the system files from a diskette to the hard
disk an error occurred that prevents the completion of the system
transfer.

 Error 22   DOS version 3 is not supported.  User a newer DOS version
for a boot diskette or attempt to use the standard SYS function from your
DOS boot diskette.

 Error 23   Unable to determine what OS resides on the diskette.  The
System transfer function is designed for MS-DOS 5 to 6.22, PC-DOS 4 to 7,
Novell DOS 7, Windows 95 (regular & OSR2), and Windows 98.  Other OSes
are not supported.  If you are using one of these listed diskettes, it
may indicate the diskette is not truly bootable, was made by some other
OS, or a virus has infected the diskette boot record.

 Error 24   The BIOS refuses to write to the new partition boot record
onto the hard disk.  This might indicate a virus, a running anti-virus
program, or invalid partition information.

 Error 25   After reading the existing hard disk partition boot record,
the data contained in it is invalid.  This might indicate a corrupted
partition.  If the partition is unaccessible or damaged, you might try
and correct the problem with a disk diagnostic utility such as Symantec's
Norton Disk Doctor.  You could also place a new valid boot record in the
partition by running the FORMAT command.  Remember that the FORMAT
command will erase any existing OSes and data that reside in the
partition.

 Error 26   Read error attempting to read the partition's boot record.
This usually indicates the partition table has invalid data.  Run the
SCIN Special options, diagnostics, partition table checks to identify
partition problems.  You may need to delete the corrupted partition using
FDISK.  Remember all the data in the partition is lost when you delete a
partition.

 Error 27   Unable to read the hard disk's master boot record.  The
hard drive may have a hardware problem.  No known software should
interfere with disk reads.

 Error 28   The SCBOOT.DAT file was found, but is damaged.  Copy the
SCBOOT.DAT file from the original master diskette of System Commander to
the location where you are running the SCIN.EXE program.

 Error 29   The SCBOOT.DAT file is missing. Copy the SCBOOT.DAT file
from the original master diskette of System Commander to the location
where you are running the SCIN.EXE program.

.scrollend
#endif
.. ............................................................................
.msg 300
.clear
.errbell
.shade 8 ATTENTION " A MultiFAT Group Already Exists "
.margin 10
.line 10 NORMAL
System Commander has detected that a multiFAT group already
exists. Do you wish to continue using the current group, or
do you prefer to delete the current group?
.menu 14  16 -1 "Use existing group"
.menu 16  16 -1 "Delete current group"
.select
.. ............................................................................
.msg 301
.clear
.errbell
.shade 8 ATTENTION " Confirm the current MultiFAT Group deletion "
.margin 10
.line 10 NORMAL
If you delete the current multiFAT group, only the currently
booted OS will be available.  Do you wish to delete the cur-
rent multiFAT group and create a new one?
.menu 14  16 -1 "No, use existing group"
.menu 16  16 -1 "Yes, delete current group"
.select
.. ............................................................................
.msg 302
.clear
.shade 11 BARTEXT " Converting old MultiFAT file to intermediate format "
.line 13 NORMAL
Conversion may take several minutes. Please wait.
.. ............................................................................
.msg 303
.clear
.shade 11 BARTEXT " Converting old MultiFAT file to intermediate format "
.line 13 MAGENTA
First conversion complete.
.. ............................................................................
.msg 304
.clear
.shade 11 BARTEXT " Converting old MultiFAT file to new format "
.line 13 NORMAL
Conversion may take several minutes. Please wait.
.. ............................................................................
.msg 305
.clear
.shade 11 BARTEXT " Final update of MultiFAT file to new format "
.line 13 NORMAL
Conversion may take several minutes. Please wait.
.. ............................................................................
.msg 306
.clear
.succbell
.shade 11 BARTEXT " Final update of MultiFAT file to new format "
.line 13 MAGENTA
Conversion complete.

.continue
.. ............................................................................
.msg 307
.clear
.shade 11 BARTEXT " Creating MultiFAT File "
.line 13 NORMAL
Please wait.
.. ............................................................................
.msg 308
.clear
.succbell
.shade 11 BARTEXT " Creating MultiFAT File "
.line 13 MAGENTA
Process complete.
.. ............................................................................
.msg 309
.clear
.errbell
.shade 4 ATTENTION " Program File is Missing! "
.bline MESSAGE "Press Esc key to exit."
.margin 9
.line 6 NORMAL
#if SERIES == SC2K || SERIES == PC5 || SERIES == SC7
The System Commander program file was missing from the
installation media.

    File:

This problem will occur if you did not install directly from
the CD-ROM and files are missing or deleted. Also verify that
disk compression does not mask the non-compressed drive.

Upon exit, switch to the drive used for the install and run
SETUP.  To attempt to finish the installation anyway, press
Alt-F9 now to skip the missing file (not recommended).
#else
The System Commander program file was missing from the root
directory of the boot disk.

    File:

This problem will occur if you did not install directly from
an installation diskette, or you deleted the file, or disk
compression masks the non-compressed drive.

#if SERIES != SC
Upon exit, switch to the diskette drive used for the install
(a: or b:) and run SETUP.  To attempt to finish the
installation anyway, press Alt-F9 now (not recommended).
#else
Upon exit, switch to the diskette drive used for the install
(a: or b:) and run INSTALL.  To attempt to finish the
installation anyway, press Alt-F9 now (not recommended).
#endif
#endif
.. ............................................................................
.msg 310
.clear
.errbell
.shade 4 ATTENTION " Program File is Missing! "
.bline MESSAGE "Press Enter to continue                                        Esc to Exit"

.margin 9
.line 6 NORMAL
#if SERIES == SC2K || SERIES == PC5 || SERIES == SC7
The System Commander program file was missing from the
installation media.

    File:

This problem will occur if you did not install directly from
the CD-ROM and files are missing or deleted. Also verify that
disk compression does not mask the non-compressed drive.

This is not a problem if your installation was made into a
different partition other than the currently active boot
partition.  For example, you just installed DOS or Windows
95/98/Me into a new partition, then ignore the warning and
continue.

If you deleted the partition where System Commander was
installed, do not continue, but exit now by pressing Esc.

#else
The System Commander program file was missing from the root
directory of the boot disk.

    File:

This problem will occur if you did not install directly from
an installation diskette, or you deleted the file, or disk
compression masks the non-compressed drive.

This is not a problem if your installation was made into a
different partition other than the currently active boot
partition.  For example, you just installed DOS or Windows
95/98/Me into a new partition, then ignore the warning and
continue.

If you deleted the partition where System Commander was
installed, do not continue, but exit now by pressing Esc.
#endif
.. ............................................................................
.msg 311
.clear
.errbell
.shade 4 ATTENTION " Program File is Missing! "
.bline MESSAGE "Press Enter to continue"
.margin 9
.line 6 NORMAL
#if SERIES == SC2K || SERIES == SC7
#else
The System Commander program file was missing from the
installation media.

    File:

This problem will occur if you did not install directly from
the CD-ROM and files are missing or deleted. Also verify that
disk compression does not mask the non-compressed drive.

This is not a problem if your installation was made into a
different partition other than the currently active boot
partition.  For example, you just installed DOS or Windows
95/98/Me into a new partition, then ignore the warning and
#endif
continue.
.. ............................................................................
.msg 312
.clear
.errbell
.shade 10 ATTENTION " No DOS Partition "
.bline MESSAGE " Press Esc key to exit. "
.margin 10
.line 13 NORMAL
Unable to locate DOS boot record on the first drive. System
Commander installation cannot continue.
.. ............................................................................
.msg 313
.clear
.errbell
.shade 5 ATTENTION " Problem with DOS Boot Record "
.margin 6
.line 7 NORMAL
A check of the DOS boot record found values that may prevent System
Commander from properly booting.
.. ............................................................................
.msg 314
.clear
.errbell
.shade 5 ATTENTION " Problem with DOS Boot Record "
.margin 6
.line 7 NORMAL
A check of the DOS boot record found values that may prevent System
Commander from properly booting.     The Installation should not be
completed.  Press Esc to attempt to continue (not recommended).
.. ............................................................................
.msg 315
.clear
.warnbell
.shade 5 BARWARNING " Minor Warning with DOS Boot Record "
.margin 6
.line 7 NORMAL
The first hard drive uses unusual drive parameters AND the partition
is greater than 1 GB.   Under very rare situations, this combination
may prevent proper booting.  If desired, press Ctrl-C to exit.
.. ............................................................................
.msg 316
.clear
.warnbell
.shade 5 BARWARNING " Minor Warning with DOS Boot Record "
.margin 6
.line 7 NORMAL
The first hard drive uses unusual drive parameters AND the partition
is greater than 1 GB.   Under very rare situations, this combination
may prevent proper booting.
.. ............................................................................
.msg 317
.clear
.warnbell
.shade 5 BARWARNING " Minor Warning with DOS Boot Record "
.margin 6
.line 7 NORMAL
The Total sectors from the partition entry is slightly different than
the value specified in the DOS boot record. This abnormality will not
effect installation or operation.
.. ............................................................................
.msg 318
.clear
.shade 7 BARTEXT " DOS Boot Record Information Valid "
.margin 10
.line 12 normal
              xxx
.. ............................................................................
.msg 319
.clear
.line 21 NORMAL
.margin 2
Reading partition table...
.. ............................................................................
.msg 320
.clear
.line 21 NORMAL
.margin 2
Partition table read. Getting BIOS parameters...
.. ............................................................................
.msg 321
.clear
.line 21 NORMAL
.margin 2
Partition table read. BIOS parameters read. Checking values...
.. ............................................................................
.msg 322
.clear
.shade 4 BARTEXT " Partition Table Validated "
.. ............................................................................
.msg 323
.clear
.shade 4 BARWARNING " Partition Table Analysis Warning - First sector size mismatch "
.. ............................................................................
.msg 324
.clear
.shade 4 BARWARNING " Partition Table Analysis Warning - Ending address too large "
.. ............................................................................
.msg 325
.clear
.shade 4 BARWARNING " Partition Table Analysis Warning - Sector mismatch & Ending address "
.. ............................................................................
.msg 326
.clear
.shade 4 ATTENTION " Partition Table Analysis Failed "
.. ............................................................................
.msg 327
.clear
.shade 6 ATTENTION " Partition Table Analysis Failed "
.line 9 BADHIGH
Unable to read drive parameters.
.. ............................................................................
.msg 328
.clear
.shade 6 ATTENTION " Partition Table Analysis Failed "
.margin 19
.line 9 BADHIGH
Unable to read partition table on drive
.. ............................................................................
.msg 329
#if BUILD == BT_SC2000 || BUILD == BT_DW || BUILD == BT_SC7
.bline MESSAGE "F1-Help  F2-Edit      Press Enter key for next drive             Esc to exit"
#else
#if (BUILD != BT_SC98) && (BUILD < 63) && (BUILD != BT_LITE_PCA)
.bline MESSAGE "F1-Help  F2-Edit      Press Enter key for next drive             Esc to exit"
.. Trial and all OEM versions - no edit
#else
.bline MESSAGE "F1-Help               Press Enter key for next drive             Esc to exit"
#endif
#endif
.. ............................................................................
.msg 330
.errbell
.bline MESSAGE "F1-Help about the problem    Ctrl-C to abort installation    Esc to continue"
.. ............................................................................
.msg 331
.clear
.shade 4 BARTEXT " Virus Analysis - None detected "
.line 7 NORMAL
.. ............................................................................
.msg 332
.clear
.shade 4 BARWARNING " Virus Analysis - Inconclusive "
.line 7 NORMAL
.. ............................................................................
.msg 333
.clear
.shade 4 ATTENTION " Virus Analysis Warning - Run a virus scanner "
.line 7 NORMAL
.. ............................................................................
.msg 334
.margin 5
.line 6 NORMAL
Likelihood of a MBR or boot virus:

  Total conventional memory (640 KB typical):
  Hard disk interrupt location:
  EIDE software (not in BIOS):


This test is not a substitute for a good virus scanner. It can help
identify viruses that typically attack the master boot record and
the partition boot record.  These viruses install themselves at the
top of memory, which reduces the normal 640 KB of conventional memory.

See help for more information and how false warnings may occur.
.. ............................................................................
.msg 335
.bline MESSAGE "F1-Help             F8 to view possible virus memory             Esc to exit"
.. ............................................................................
.msg 336
.bline MESSAGE "F1-Help    F8-view possible virus in memory    Ctrl-C to exit   Esc-continue"
.. ............................................................................
.msg 337
.bline MESSAGE "F1-Help                Press Enter key to continue                          "
.. ............................................................................
.msg 338
.bline MESSAGE "F1-Help                      Ctrl-C to exit                     Esc-continue"
.. ............................................................................
.msg 339
.clear
.shade 5 BARTEXT " View strings in memory where Virus may reside "
.line 7 NORMAL
.. ............................................................................
.msg 340
.bline MESSAGE "Press Enter key to scan further.                                Esc to exit."
.. ............................................................................
.msg 341
.clear
.errbell
.shade 5 ATTENTION " Problem with FAT Boot Record "
.margin 6
.line 7 NORMAL
A check of the FAT boot record found values that may prevent System
Commander from properly booting.
.. ............................................................................
.msg 342
.clear
.errbell
.shade 5 ATTENTION " Problem with FAT Boot Record "
.margin 6
.line 7 NORMAL
A check of the FAT boot record found values that may prevent System
Commander from properly booting.     The Installation should not be
completed.  Press Esc to attempt to continue (not recommended).
.. ............................................................................
.msg 343
.clear
.warnbell
.shade 5 BARWARNING " Minor Warning with FAT Boot Record "
.margin 6
.line 7 NORMAL
The first hard drive uses unusual drive parameters AND the partition
is greater than 1 GB.   Under very rare situations, this combination
may prevent proper booting.  If desired, press Ctrl-C to exit.
.. ............................................................................
.msg 344
.clear
.warnbell
.shade 5 BARWARNING " Minor Warning with FAT Boot Record "
.margin 6
.line 7 NORMAL
The first hard drive uses unusual drive parameters AND the partition
is greater than 1 GB.   Under very rare situations, this combination
may prevent proper booting.
.. ............................................................................
.msg 345
.clear
.warnbell
.shade 5 BARWARNING " Minor Warning with FAT Boot Record "
.margin 6
.line 7 NORMAL
The Total sectors from the partition entry is slightly different than
the value specified in the FAT boot record. This abnormality will not
effect installation or operation.
.. ............................................................................
.msg 346
.clear
.shade 7 BARTEXT " FAT Boot Record Information Valid "
.margin 10
.line 12 normal
              xxx
.. ............................................................................
.msg 347
.clear
.shade 8 BARTEXT " Installation "
.margin 12
.line 11 NORMAL
    Creation/Update of the MultiFAT file

    Saving disk information for uninstall

    Installation of new boot record
.bline MESSAGE "Please wait."
.. ............................................................................
.msg 348
.margin 12
.line 11 HIGHLIGHT
 >  Creation/Update of the MultiFAT file...
.. ............................................................................
.msg 349
.margin 12
.line 11 GREENTEXT
    Creation/Update of the MultiFAT file    Complete
.. ............................................................................
.msg 350
.margin 12
.line 13 HIGHLIGHT
 >  Saving disk information for uninstall...
.. ............................................................................
.msg 351
.margin 12
.line 13 GREENTEXT
    Saving disk information for uninstall   Complete
.. ............................................................................
.msg 352
.margin 12
.line 15 HIGHLIGHT
 >  Installation of new boot record...
.. ............................................................................
.msg 353
.succbell
.margin 12
.line 15 GREENTEXT
    Installation of new boot record         Complete
.. ............................................................................
.msg 354
.margin 10
.line 12 NORMAL
         Data from the FAT boot record, partition

Sectors per cluster (power of 2)
Bytes per sector (should be 512)
Number of FATs (always 2)
Number of root directory entries (= or > 512)
Media descriptor byte (never below F0h)
Sectors per track (1 to 63 valid)
Total sectors from partition entry
Total sectors from boot
.. ............................................................................
.msg 355
.margin 10
.line 12 NORMAL
      Data from the FAT32 boot record, partition

Sectors per cluster (power of 2)
Bytes per sector (should be 512)
Number of FATs (always 2)
Start of root directory
Media descriptor byte (never below F0h)
Sectors per track (1 to 63 valid)
Total sectors from partition entry
Total sectors from boot
.. ............................................................................
.msg 356
.bline MESSAGE "F1-Help                                                          Esc to exit"
.. ............................................................................
.msg 357
.bline MESSAGE "F1-Help          Press any key to exit installation          Esc to continue"
.. ............................................................................
.msg 358
.scroll
.title Boot Record Diagnostic

The Boot Record Diagnostic checks the values in the boot record for
validity.  Problems are highlighted in color.

   Orange   Warning - The data is not correct, but it will not
                      cause any problems with System Commander.

   Red      Error -   The data is wrong, and will likely prevent
                      System Commander from operating.

   See "Warning and Errors" below for more information

 What is the Boot Record? 

The boot record is a single sector of data and code installed by the
operating system's FORMAT utility.  It holds specific information about
the partition that the operating system uses to access the drive.

A few OSes, like DOS, will check for invalid values.  If any are found it
ignores all the data and creates a "best guess" of the data.  In these
situations, DOS may work correctly without errors.

System Commander must read this same data to properly appear before any
OS runs.  In these situations, System Commander must have a valid set of
values.

 Warnings and Errors 

If you are installing System Commander for the first time, we do not
recommend continuing with a damaged boot record.  Unfortunately, it is not
easy to correct a defective boot record.  The FORMAT utility will correct
problems in the boot record, but it will also erase all data within the
partition.  If you resort to this step, be sure to back up all your data
from the partition (usually C:) that is having the problem.

.scrollend
.. ............................................................................
.msg 359
.scroll
.title File Access Verification Diagnostic

This diagnostic confirms correct early level System Commander operations.
Any problems encountered are identified with a number error message and
the data relating to the error.

If System Commander is operating normally, on some systems this
diagnostic may report an error. You can safely ignore any errors if System
Commander is working. Some drivers can interfere with this test and cause
a false error indication.

The following list can assist you in locating the source of the problem:

 Error 1: Cannot open C:\SYSCMNDR.SYS 

Cause: The file SYSCMNDR.SYS could not be found

#if SERIES == SC2K || SERIES == SC7
Action: Perform a SETUP from the System Commander CD-ROM.  Be sure
#else
#if SERIES == PC5
Action: Perform a SETUP from the Partition Commander CD-ROM.  Be sure
#else
#if SERIES != SC
Action: Perform a SETUP from the System Commander diskette.  Be sure
#else
Action: Perform a INSTALL from the System Commander diskette.  Be sure
#endif
#endif
#endif
   to install to the non-compressed drive if you are using disk
   compression.

 Error 2: MBR BIOS read failure 

Cause: The BIOS returned an error reading the MBR (Master Boot Record).

Action: This might indicate a problem with the drive, the disk
   controller, or a TSR/driver that interferes with MBR access.

 Error 3: No DOS Partition or boot record found 

Cause: The test was unable to find any primary DOS partitions on the
   first drive, or if a DOS partition was found, it did not have a valid
   boot record.

Action: You must have a FAT primary partition on the first drive to
   install System Commander.  Use FDISK to create one, and then format
   and install DOS.

 Error 3a: BIOS Read drive parameters failed 

Cause: The BIOS returned an error when attempting to read the hard disk
   parameters.

Action: This may indicate a CMOS parameter error, or a drive or
   controller problem.

 Error 4: DOS read error 

Cause: While attempting to read a file from the disk, DOS returned an
   error.

Action: Run SCANDISK or CHKDSK /F to locate and fix any disk problems
   or bad sectors.

 Error 5: First sector comparison wrong 

Cause: This test reads the first sector of the file SYSCMNDR.SYS in the
   root directory through DOS and independently through the BIOS.  The
   byte for byte comparison failed, when it should be identical.

Action: If your system requires some type of unusual device driver for
   access to the hard disk, it may be impossible for System Commander to
   read the disk through the BIOS.  It is likely that other OSes will
   also have serious problems installing.  Consider a more standard
   drive, such as IDE, EIDE, or a current SCSI drive and controller.
   One product that might cause this is old versions of EZ-Drive/EZ-BIOS.

 Error 7: BIOS read error, 1st sector 

Cause: When the BIOS attempts to read the first sector from the disk,
   the BIOS returns an error.

Action: See the action portion of the previous errors 3a, 4, and 5.

 Error 8: BIOS read error, dir read 

Cause: When the BIOS attempts to read the root directory portion of the
   disk, it returns an error.

Action: See the action portion of the previous errors 3a, 4, and 5.

 Error 9: BIOS read error, FAT 

Cause: When the BIOS attempts to read the File Allocation Table (FAT)
   portion of the disk, it returns an error.

Action: See the action portion of the previous errors 3a, 4, and 5.

 Error 10: BIOS read error, SYSCMNDR.SYS 

Cause: When the BIOS attempts to read the SYSCMNDR.SYS file, it returns
   an error.

Action: See the action portion of the previous errors 4 and 5.

 Error 11: Bad cluster in chain 

Cause: While attempting to read the SYSCMNDR.SYS file, a bad cluster
   was encountered, which should never occur.

Action: See the action portion of the previous errors 4 and 5.

 Error 12: DOS read error, SYSCMNDR.SYS 

Cause: DOS returned an error when attempting to read the SYSCMNDR.SYS
   file.

Action: Run SCANDISK or CHKDSK to locate and fix any disk problems or
   bad sectors.  Try reinstalling System Commander from the diskette.

 Error 13: BIOS-DOS sector comparison mismatch 

Cause: The byte for byte comparison failed when reading the file
   SYSCMNDR.SYS from DOS and from the BIOS.

Action: Run SCANDISK or CHKDSK to locate and fix any disk problems or
   bad sectors.  Try reinstalling System Commander from the diskette.

 Error 14: Cannot find SYSCMNDR.SYS dir entry 

Cause: The SYSCMNDR.SYS file does not appear in the non-compressed C:
   root.

#if SERIES == SC2K || SERIES == SC7
Action: Perform a SETUP from the System Commander CD-ROM.  Be sure
#else
#if SERIES == PC5
Action: Perform a SETUP from the Partition Commander CD-ROM.  Be sure
#else
#if SERIES != SC
Action: Perform a SETUP from the System Commander diskette.  Be sure
#else
Action: Perform an INSTALL from the System Commander diskette.  Be sure
#endif
#endif
#endif
   to install to the non-compressed drive if you are using disk
   compression.

.scrollend
.. ............................................................................
.msg 360
.clear
.shade 7 BARTEXT " Hidden Files Accessible "
.margin 7
.line 9 NORMAL
It is not necessary to delete these files if you are temporarily
uninstalling, as the files are needed for a re-install. The hidden
files used for normal operation appear in the root directory. If
you are completely removing all files, the following files can be
deleted:
.. ............................................................................
.msg 361
.clear
.shade 7 BARTEXT " System Commander Security "
.margin 5
.line 9 NORMAL
The System Commander security system has been initialized. The system
administrator user ID & password have been created. Additional users
can be added from the Password Security menu at boot time. Please note
that security features are optional, and must be activated by the system
administrator. The administrator user ID & password are as follows:
.line 15 HIGHLIGHT
.margin 20
User ID:     Administrator
Password:    password
.line 18 NORMAL
.margin 5
Please remember that passwords are case sensitive, may contain up
to 32 ASCII characters and can be changed at boot time as desired.
.succbell
.continue
.. ............................................................................
.msg 362
.clear
.errbell
.shade 8 ATTENTION " Unknown Disk Boot Record "
.margin 12
.line 10 NORMAL
System Commander has detected a disk boot record that was
not written by System Commander. This boot record may be
newer or have information that has been altered since the
original disk boot record was saved by System Commander.
.menu 15  16 -1 "Restore original boot record"
.menu 17  16 -1 "Skip boot record restoration"
.select
.. ............................................................................
.msg 363
.clear
.errbell
.shade 8 ATTENTION " No Disk Boot Record Found "
.margin 16
.line 10 NORMAL
System Commander was unable to locate the disk boot
record which was saved during installation on both
the diskette and hard disk.  Try running SCIN from
the installation diskette and/or the hard disk to
restore the original MBR.
.continue
.. ............................................................................
.msg 364
.clear
.errbell
.shade 8 ATTENTION " Unable to Restore Master Boot Record "
.margin 9
.line 10 NORMAL
Access protection is active.  Reboot and at the password menu,
enter the global password to turn off access protection.
.continue
.. ............................................................................
.msg 365
.clear
.shade 11 BARTEXT " Restoring Original Disk Boot Record "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.. Message below has values inserted at specific places on the screen!
.msg 366
.clear
.errbell
.shade 4 ATTENTION " Confirm Restoration of Partition Table Data in MBR ? "
.margin 22
.line 6 GREENTEXT
Current Partition Information, Drive







Saved Partition Information to Restore
.. ............................................................................
.. Message below has values inserted at specific places on the screen!
.msg 367
.margin 2
.line 7 NORMAL
                Starting    Ending     Sector 
Partition  ID  Sector Head Cylinder  Sector Head Cylinder    First     Total






                Starting    Ending     Sector 
Partition  ID  Sector Head Cylinder  Sector Head Cylinder    First     Total
.. ............................................................................
.msg 368
.margin 12
.menu 22  16 -1 "Only restore boot record"
.menu 23  16 -1 "Restore partition data and boot record"
.select
.. ............................................................................
.msg 369
.clear
.shade 11 BARTEXT " Restoring Original Disk Boot Record "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 370
.clear
.errbell
.shade 8 ATTENTION " Unable to Restore Master Boot Record "
.bline MESSAGE "Press Esc key to exit."
.margin 8
.line 10 NORMAL
A TSR or OS is preventing the restoral of the master boot record.
Common problems include running this from a DOS box from inside
OS/2, Windows or NT.  If this is the case, boot to a real DOS
prompt (not a DOS box).  If a normal DOS is running, some virus
protection software will prevent anyone from writing the boot
#if SERIES != SC
sector.  Remove the virus software and re-run SCIN's Disable.
#else
sector.  Remove the virus software and re-run SCIN uninstall.
#endif
.. ............................................................................
.msg 371
.margin 56
.line 22 LOGO
(Windows Active)
.. ............................................................................
.msg 372
.clear
.shade 8 ATTENTION " No DOS Boot Record Found "
.margin 14
.line 10 NORMAL
System Commander was unable to locate the disk boot
record which was saved during installation.
.. ............................................................................
.msg 373
.clear
.shade 11 BARTEXT " Restoring Original DOS Boot Record "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 374
.clear
.shade 8 ATTENTION " Unable to Restore DOS Boot Record "
.margin 14
.line 10 NORMAL
The DOSBOOT.DAT boot record is corrupt or the hard
disk fails to properly write the boot sector.
.. ............................................................................
.msg 375
.clear
.shade 8 ATTENTION " Unable to Restore DOS Boot Record "
.margin 19
.line 10 NORMAL
Error attempting to read the master boot
record from the hard disk.
.. ............................................................................
.msg 376
.clear
.errbell
.shade 8 ATTENTION " No Disk Boot Record Found "
.margin 8
.line 10 NORMAL
System Commander was unable to locate the System Commander
disk boot record for installation (SCBOOT.DAT).
.continue
.. ............................................................................
.msg 377
.clear
.shade 8 BARTEXT " Select Master Boot Record to Load "
.margin 16
.line 11 NORMAL
Enter 0 for normal System Commander MBR
      1 for debug MBR register dump
      2 for debug MBR tracer
      3 for debug MBR syscmndr validity
      x for normal MBR, no disk reset
.. ............................................................................
.. Message below has values inserted at specific places on the screen!
.msg 378
.margin 16
.line 17 REVERSE
Your selection:
.. ............................................................................
.msg 379
.clear
.shade 11 BARTEXT " Installing Special MBR Boot Record "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 380
.clear
.errbell
.shade 8 ATTENTION " SCBOOT.DAT File Defective "
.margin 11
.line 10 NORMAL
The SCBOOT.DAT file is damaged and will be deleted.   This
might be due to a bad diskette or failure to properly copy
the file.  Try reinstalling from the original diskette.
.continue
.. ............................................................................
.msg 381
.clear
.shade 5 BARTEXT " Final Installation Step "
.bline MESSAGE "Press F1 for help and suggestions.               Press Esc to exit."
.margin 4
.line 8 NORMAL
The final installation step, writing the System Commander MBR, was
prevented by the specific OS, BIOS, or a TSR you are using.

To complete the installation:

   a) Insert a Windows or DOS boot diskette in the diskette drive.

   b) After exiting this install, shutdown and reboot the system
      (Ctrl-Alt-Del).

   c) Once the diskette boots up, at the prompt, run SCIN from the
      hard disk (typically C:\SC\SCIN), or run SCIN from our
#if SERIES != SC
      diskette. Select the menu option "Enable" to complete
#else
      diskette. Select the menu option "Enable/Reinstall" to complete
#endif
      the installation (this takes about 10 seconds).
.. ............................................................................
.msg 382
.clear
.shade 4 BARTEXT " Final Installation Step "
#if SERIES != PC5
.bline MESSAGE "Press F1 for help and suggestions.               Press Esc to exit."
#else
.bline MESSAGE "Press F1 for help and suggestions.       Press any key to continue."
#endif
.margin 4
.line 6 NORMAL
The final installation step, writing the System Commander MBR, was
prevented by the specific Windows 95/98/Me configuration you are using,
or prevented by anti-virus software in use.

To complete the installation:

   a) Insert a Windows or DOS boot diskette in the diskette drive.

   b) Shutdown Windows 95/98/Me using the "Restart the computer" option.
      (Do not use "Restart computer in MS-DOS mode" as it may
      cause the Windows configuration files to be lost!)

   c) Once the diskette boots up, at the prompt, run SCIN from the
      hard disk (typically C:\SC\SCIN), or run SCIN from our
#if SERIES != SC
      diskette. Select the menu option "Enable" to complete
#else
      diskette. Select the menu option "Enable/Reinstall" to complete
#endif
      the installation (this takes about 10 seconds).
.. ............................................................................
.msg 383
.clear
.shade 4 BARTEXT " Final Installation Step "
#if SERIES != PC5
.bline MESSAGE "Press F1 for help and suggestions.               Press Esc to exit."
#else
.bline MESSAGE "Press F1 for help and suggestions.       Press any key to continue."
#endif
.margin 4
.line 6 NORMAL
The final installation step, writing the System Commander FAT32 MBR
sectors, was prevented by the specific Windows configuration you
are using.

To complete the installation:

   a) Insert a Windows or DOS boot diskette in the diskette drive.

   b) Shutdown Windows 95/98/Me using the "Restart the computer"
      option. (Do not use "Restart computer in MS-DOS mode" as it
      may cause the Windows configuration files to be lost!)

   c) Once the diskette boots up, at the prompt, run SCIN from the
      hard disk (typically C:\SC\SCIN), or run SCIN from our
#if SERIES != SC
      diskette. Select the menu option "Enable" to complete
#else
      diskette. Select the menu option "Enable/Reinstall" to complete
#endif
      the installation (this takes about 10 seconds).
.. ............................................................................
.msg 384
.margin 7
.line 20 WARNING
The Debug MBR is now loaded.  After a reboot, record the data from
the screen.  Reboot from a boot floppy, and run SCIN again. Select
#if SERIES != SC
either Disable or Enable from the menu.
#else
either Uninstall or Re-install from the menu.
#endif
.. ............................................................................
.msg 385
.clear
.shade 4 BARWARNING " Partition Table Analysis Warning - Partitions overlap "
.. ............................................................................
.msg 386
.margin 2
.line 7 MAGENTA
           overlapped partitions
.. ............................................................................
.msg 387
.clear
.errbell
.shade 8  ATTENTION " Unable to Restore FAT 32 MBR Sectors "
.bline MESSAGE "Press F1 for help and suggestions.                        Press Esc to exit."
.margin 8
.line 11 NORMAL
The previously saved FAT 32 boot sectors could not be restored.
.. ............................................................................
.msg 388
.clear
.errbell
.shade 8 ATTENTION " Unable to Locate Saved FAT 32 Sectors "
.margin 8
.line 11 NORMAL
System Commander could not locate the FAT 32 sectors that were
previously saved to the EBIOS.DAT file.
.continue
.. ............................................................................
.msg 389
.clear
.errbell
.shade 8 ATTENTION " Disk Error "
.margin 7
.line 11 NORMAL
System Commander was unable to convert the file needed for multiFAT
operation.  It is likely there is not enough disk space.  Press any
key to exit and correct the problem before restarting installation.
.continue
.. ............................................................................
.msg 390
.clear
.errbell
.shade 8 ATTENTION " Disk Error "
.margin 7
.line 11 NORMAL
System Commander was unable to convert the file needed for multiFAT
operation.  It is likely there is not enough disk space.  Press Esc
key to exit and correct the problem before restarting installation.
.continue
.. ............................................................................
.msg 391
.clear
.shade 11 BARTEXT " Removing unused space from data files "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 392
.clear
.errbell
.shade 8 ATTENTION " Free Up Disk Space "
.margin 8
.line 10 NORMAL
System Commander has detected it can save some disk space within
its own data.  Your action?
.menu 14  16 -1 "Yes, free up disk space"
.menu 16  16 -1 "Skip file cleanup for now"
.select
.. ............................................................................
.msg 393
.clear
.errbell
.shade 6 BARTEXT " Alter Boot Record "
.margin 3
.line 8 NORMAL
In rare situations, two different operating systems from the same vendor
might have the identical boot record.  If you install a new OS in the DOS
partition and the boot record is identical to a previously saved boot
record, System Commander will not detect the new OS.

This option is used to force a change to the current boot record's serial
number to make the boot record different.  If the change is made, upon
reboot, System Commander will save the new OS. Only use this option after
installing a new OS that System Commander fails to automatically detect.
.menu 19  16 -1 "No, skip any change"
.menu 21  16 -1 "Yes, alter the boot record"
.select
.. ............................................................................
.msg 394
.clear
.shade 11 BARTEXT " Boot Record Alteration "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 395
.line 13 BADHIGH
Unable to Read or Write Boot Sector.
.continue
.. ............................................................................
.msg 396
.clear
.errbell
.shade 8 ATTENTION " Restore Option Not Allowed "
.margin 5
.line 10 NORMAL
The DOS boot record restoration is only allowed when SCIN is run from
a floppy drive.  This option is only used if the DOS partition is
inaccessible due to corruption of the DOS boot record.

.continue
.. ............................................................................
.msg 397
.clear
.errbell
.shade 4 BARTEXT " Emergency Restore DOS/Win95/98 Boot Record "
.margin 7
.line 6 NORMAL
System Commander previously saved the FAT boot record during its
installation.  This option allows you to restore the saved boot
record back to the hard disk.  This option should only be used if
the FAT partition is completely inaccessible or has a media byte
error due to corruption of the boot sector.

DO NOT USE this option if you have converted the partition to FAT32,
resized the partition, or moved or copied the partition.  If used
after any of these operations, the partition becomes unrecoverable!

Use of this function may not make a FAT partition bootable, but it
may allow boot floppy access to the files on the disk, and allow
System Commander, the OSes SYS command and disk utilities to work.
.menu 20  16 -1 "No, skip any change"
.menu 22  16 -1 "Yes, restore boot record"
.select
.. ............................................................................
.msg 399
.bline MESSAGE "No more strings to display.                                     Esc to exit."
.. ............................................................................
.msg 400
.clear
.errbell
.shade 5 BARTEXT " Transfer System for DOS and Windows 95/98 "
.margin 4
.line 8 NORMAL
This option is used to transfer a system from a bootable A diskette to
the C drive.  Like the standard SYS command, a new partition boot record
is created and installed.  In addition, the hidden system files and
COMMAND.COM are all transferred to drive C (the active primary
partition).  Unlike the SYS command, this option solves a number of bugs
and problems that may prevent the SYS command from working.  The boot
record we create also solves several bugs that prevents DOS from booting
when DOS is installed past 2 GB.

Select "Automatic" to transfer a system from A to the C drive.  Use the
option "Prompted" to specify which steps to perform.
.menu 20  24 -1 "Automatic Transfer"
.menu 21  24 -1 "Prompted Transfer"
.menu 22  24 -1 "Cancel"
.select
.. ............................................................................
.msg 401
.clear
.errbell
.shade 8 BARTEXT " Boot Record Installation "
.margin 5
.line 10 NORMAL
A new boot record should be installed to allow the partition to boot.
.menu 14  16 -1 "Yes, install new boot record"
.menu 16  16 -1 "Skip boot record"
.select
.. ............................................................................
.msg 402
.clear
.errbell
.shade 8 BARTEXT " Hidden IO file Transfer "
.margin 5
.line 10 NORMAL
The IO file (IO.SYS or IBMBIO.COM) is the first program to run.  It is
required to for normal operation.
.menu 14  16 -1 "Yes, install hidden IO file"
.menu 16  16 -1 "Skip IO file"
.select
.. ............................................................................
.msg 403
.clear
.errbell
.shade 4 BARTEXT " Hidden DOS file Transfer "
.margin 5
.line 6 NORMAL
For DOS, the hidden file (MSDOS.SYS or IBMDOS.COM) is the second
program to run. It is required for normal operation.

For the transfer of Windows 95/98, the Windows boot diskette often
has a damaged copy of MSDOS.SYS that only works for diskette boots.
The first option will check it's validity.  If invalid, a new valid
MS-DOS.SYS file for Windows 95/98 is created.  Use the second option
to copy the MSDOS.SYS file regardless of validity.
.menu 16  16 -1 "Copy, unless file appears damaged"
.menu 18  16 -1 "No matter what, copy file"
.menu 20  16 -1 "Skip copy"
.select
.. ............................................................................
.msg 404
.clear
.errbell
.shade 8 BARTEXT " COMMAND.COM file Transfer "
.margin 13
.line 10 NORMAL
The COMMAND.COM file is used to provide a DOS prompt.
.menu 14  16 -1 "Yes, copy COMMAND.COM"
.menu 16  16 -1 "Skip COMMAND.COM"
.select
.. ............................................................................
.msg 405
.clear
.errbell
.shade 8 BARTEXT " Disk Compression Driver "
.margin 6
.line 10 NORMAL
If disk compression is used and the driver appears on the diskette,
the driver can be transferred.  It is not necessary to transfer the
driver if you are not using disk compression, nor if you are using
a third party product like STACKER.
.menu 16  16 -1 "Copy, only if newer"
.menu 18  16 -1 "Copy, if present"
.menu 20  16 -1 "Skip copy"
.select
.. ............................................................................
.msg 406
.clear
.shade 5 BARTEXT " System Transfer - A: to C: "
.margin 10
.line 10 NORMAL
Boot
.. ............................................................................
.msg 407
.bline MESSAGE "Press Esc to exit"
.line 22 BADHIGH
Insert a good system boot disk in drive A and press the Enter key.
.. ............................................................................
.msg 408
.line 21 BADHIGH
DOS version 3 is not supported by this utility
.. ............................................................................
.. loc: " x" below must be in column 22 to allow one or two digit overwrite
.msg 409
.errbell
.bline MESSAGE "F1-Help and suggestions                   Enter key to continue."
.margin 16
.line 18 BADHIGH
Error  x: System transfer cannot be completed.
.. ............................................................................
.msg 410
.clear
.shade 6 BARTEXT " Installation Check "
.margin 4
.line 9 NORMAL
If you are installing from a diskette, please type the letter of the
drive where the installation diskette currently resides (typically A or
B). If you are running this program from your hard disk, and you DON'T
need to copy any files, press F10.
.. ............................................................................
.msg 411
.clear
.bline MESSAGE " Please stand by. "
.. ............................................................................
.msg 412
.bline MESSAGE " Esc to Exit without saving "
.. ............................................................................
.msg 413
.bline ATTENTION " Drive does not exist or is inaccessible.                       Esc to continue "
.. ............................................................................
.msg 414
.bline ATTENTION " Drive is Compressed!  Specify the non-compressed boot drive.  Esc to continue. "
.. ............................................................................
.msg 415
.clear
.shade 4 BARTEXT " File Access Verification "
.bline MESSAGE "Please wait."
.margin 10
.line 6 NORMAL
SYSCMNDR.SYS directory entry
.. ............................................................................
.msg 416
.margin 10
.line 22 HIGHLIGHT
Error 1: Cannot open C:\SYSCMNDR.SYS
.. ............................................................................
.msg 417
.margin 10
.line 22 HIGHLIGHT
Error 2: MBR BIOS read failure
.. ............................................................................
.msg 418
.margin 10
.line 22 HIGHLIGHT
Error 3: No DOS Partition or boot record found
.. ............................................................................
.msg 419
.margin 10
.line 22 HIGHLIGHT
Error 3a: BIOS Read drive parameters failed
.. ............................................................................
.msg 420
.margin 10
.line 22 HIGHLIGHT
Error 4: DOS read error
.. ............................................................................
.msg 421
.margin 10
.line 22 HIGHLIGHT
Error 5: First sector comparison wrong
.. ............................................................................
.msg 422
.margin 10
.line 22 HIGHLIGHT
Error 6: Unknown problem
.. ............................................................................
.msg 423
.margin 10
.line 22 HIGHLIGHT
Error 7: BIOS read error, 1st sector
.. ............................................................................
.msg 424
.margin 10
.line 22 HIGHLIGHT
Error 8: BIOS read error, dir read
.. ............................................................................
.msg 425
.margin 10
.line 22 HIGHLIGHT
Error 9: BIOS read error, FAT
.. ............................................................................
.msg 426
.margin 10
.line 22 HIGHLIGHT
Error 10: BIOS read error, SYSCMNDR.SYS
.. ............................................................................
.msg 427
.margin 10
.line 22 HIGHLIGHT
Error 11: Bad cluster in chain
.. ............................................................................
.msg 428
.margin 10
.line 22 HIGHLIGHT
Error 12: DOS read error, SYSCMNDR.SYS
.. ............................................................................
.msg 429
.margin 10
.line 22 HIGHLIGHT
Error 13: BIOS-DOS sector comparison mismatch
.. ............................................................................
.msg 430
.margin 10
.line 22 HIGHLIGHT
Error 14: Cannot find SYSCMNDR.SYS dir entry
.. ............................................................................
.msg 431
.margin 10
.line 22 HIGHLIGHT
Unknown error
.. ............................................................................
.msg 432
.margin 10
.line 22 HIGHLIGHT
.. ............................................................................
.msg 433
.margin 10
.line 22 HIGHLIGHT
.. ............................................................................
.msg 434
.margin 10
.line 22 HIGHLIGHT
.. ............................................................................
.msg 435
.clear
.shade 11 BARTEXT " Performing first-time initialization "
.margin 73
.line 23 NORMAL
d-mode
#if BUILD != BT_SCDTRIAL
.continue
#endif
.. ............................................................................
.msg 436
.clear
.errbell
.shade 6 ATTENTION " Update Cannot Be Installed "
.margin 7
.line 9 NORMAL
No prior version of System Commander was detected. To install this
update, you must have a prior version of System Commander already
installed in the same partition. If you have not purchased a prior
version, you must purchase the full version (not an update).

If you have the older version of System Commander, and it is not
currently installed:

    1)  Install the old version, and reboot once to save the
        current OS configuration data.

    2)  Install the new version to transfer the old data to
        the new version.
.continue
.. ............................................................................
.msg 437
.clear
.shade 11 BARTEXT " Uninstalling "
.line 13 NORMAL
Please Wait.
.. ............................................................................
.msg 438
.clear
.errbell
.shade 8 ATTENTION " Installation Cannot Proceed - Disk Manager not running "
.margin 4
.line 11 NORMAL
The first drive has Disk Manager installed, but is not currently running.
System Commander cannot be installed/uninstalled until Disk Manager is
properly running.

This Disk Manager problem typically occurs when you boot from a diskette
without waiting for Disk Manager to run.  Remove the boot diskette and
boot the system.  Watch on screen for Disk Manager to instruct you how to
boot the floppy (it usually gives you several seconds to do so).
.continue
.. ............................................................................
.msg 439
.clear
.errbell
.shade 8 BARTEXT " Windows FAT32 Detected "
.margin 11
.line 11 NORMAL
Please remove the diskette, and boot into Windows 95/98/Me.
Run A:\SETUP from Windows to begin the installation.
.continue
.. ............................................................................
.msg 440
.clear
.errbell
.shade 6 ATTENTION " Low Disk Space "
.margin 11
.line 9 NORMAL
The selected drive may not have enough disk space to load
System Commander.  If System Commander was already loaded
on this drive and directory, there may be enough space
for a new installation (press Spacebar).

Space available:

You can take one of the following actions:

        Ctrl-C    to Exit
        Esc       to try another drive
        Spacebar  to try anyway
.. ............................................................................
.msg 441
.clear
.errbell
.shade 8 BARTEXT " No active/bootable FAT partition "
.margin 11
.line 11 NORMAL
To install System Commander from our diskette, you must
have an active primary FAT partition on the first disk.

You can use DOS/Window's FDISK to make a partition active.
.continue
.. ............................................................................
.msg 442
.clear
.errbell
#if BUILD == BT_PC || BUILD == BT_PC5
.shade 7 ATTENTION " Confirm you wish to Uninstall "
.margin 4
.line 9 NORMAL
This option removes all Partition Commander and System Commander files.
If you are using System Commander, its OS save files will be deleted
and only the current OS will be accessible.  Use the disable command
if you only want to temporarily disable System Commander.
#else
.shade 7 ATTENTION " Confirm you wish to Uninstall System Commander "
.margin 4
.line 9 NORMAL
If you continue, System Commander and its OS save files will be deleted.
Only the current OS will be accessible.  Use the disable command if you
only want to temporarily remove System Commander.
#endif
#if BUILD == BT_SC98

IMPORTANT - If you choose uninstall, your non-selected Windows will be
deleted!  While this will save 50 MB or more disk space, you cannot
restore the deleted Windows without a complete system restore from your
backup.  If you are unsure, use Skip or Disable only.
.menu 18  16 -1 "Disable Only"
.menu 20  16 -1 "Uninstall and delete files"
.menu 22  16 -1 "Skip disable/uninstall"
#else
.menu 14  16 -1 "Disable Only"
.menu 16  16 -1 "Uninstall and delete files"
.menu 18  16 -1 "Skip disable/uninstall"
#endif
.select
.. ............................................................................
#if SC_DELUXE == 1
.msg 443
.clear
.shade 8 ATTENTION " Installation Cancelled "
.margin 9
.line 11 NORMAL
To re-start the installation at a later time, run SETUP again.

      Remove the installation diskette now.

      Press any key to exit and reboot.
.. ............................................................................
.msg 444
.clear
.shade 4 BARWARNING " Exit to make your boot diskette "
.margin 4
.line 6 NORMAL
Make your boot diskette now.  As a reminder, the typical process is to
boot into an OS, like DOS or Windows 95/98, and insert a new diskette (do
not use the System Commander diskette!).  At a prompt, run:
        sys  a:
        copy \PATH\sys.*  a:
        copy \PATH\fdisk.*  a:
        copy \PATH\format.*  a:
        copy \PATH\attrib.*  a:

For DOS, the path is typically \DOS, and for Windows 95/98, the default
path is typically \WINDOWS\COMMAND.

To re-start the installation at a later time, run SETUP again from the
System Commander diskette.

          Remove the installation diskette now.
          Press any key to exit and reboot.
.. ............................................................................
.msg 445
.clear
.shade 8 BARTEXT " Installation Complete "
.margin 8
.line 11 NORMAL
      Thank you for purchasing System Commander!

            Remove the installation diskette now.

            Press any key to exit and reboot.

System Commander will appear and save your currently installed
operating systems.
.. ............................................................................
.msg 446
.clear
.shade 8 BARTEXT " Installation Complete "
.margin 15
.line 11 NORMAL
Thank you for purchasing System Commander!

      Remove the installation diskette now.

      Press any key to exit and reboot.
.. ............................................................................
.msg 447
.clear
.shade 8 BARTEXT " Operation Complete "
.margin 20
.line 11 NORMAL
  Remove the installation diskette now.

  Press any key to exit and reboot.
.. ............................................................................
.msg 448
.clear
.shade 9 BARTEXT " Operation Complete "
.line 13 NORMAL
#if SERIES == SC2K || SERIES == PC5 || BUILD == BT_OEM_AL || SERIES == SC7
.margin 7
If you are installing from a CDROM, you can remove the CDROM now.
#else
.margin 5
If you are installing from a diskette, please remove the diskette now.
#endif
.continue
#endif
.. ............................................................................
.msg 449
.clear
.shade 11 BARTEXT " Saving System Files "
.bline MESSAGE " "
.line 13 NORMAL
Please wait.
.. ............................................................................
.msg 450
.clear
.shade 10 BARTEXT " Manual Partitioning "
.bline MESSAGE " "
.line 13 NORMAL
Insert Disk 2.
.continue
.. ............................................................................
.msg 451
.clear
.shade 10 ATTENTION " Wrong Disk Found "
.bline MESSAGE " "
.line 13 NORMAL
You must insert disk 2 for manual partitioning or press Ctrl-C
to exit now.
.continue
.. ............................................................................
.msg 452
.clear
.shade 7 BARTEXT " Setup Menu "
.margin 7
.line 8 NORMAL
.menu 10 20 -1 "Full installation"
.menu 12 21 -1 "SCIN - Enable/Disable, Troubleshooting, etc."
.menu 14 22 -1 "Manual Partitioning"
.menu 16 23 -1 "Exit to DOS 98 Prompt"
.select
.. ............................................................................
.msg 453
.clear
.shade 10 BARTEXT " Manual Partitioning "
.bline MESSAGE " Loading.... "
.line 13 NORMAL
Please wait.
.. ............................................................................
.msg 454
.clear
.shade 7 BARTEXT " Update files from Download "
.bline MESSAGE "Press Enter to Continue                                      Esc to Exit"
.line 10 NORMAL
.margin 4
To update to the latest version of System Commander, connect to our Web
site at WWW.V-COM.COM and download the current release file.  If this has
not been done yet, exit now and proceed to download the update file.
Return to SCIN when the file is available.  This feature is available for
all minor updates of the product.
.menu 17 20 -1 "Proceed with download update"
.menu 19 20 -1 "Return to prior menu"
.select
.. ............................................................................
.msg 455
.clear
.shade 10 BARTEXT " Path to the Download Update File "
.margin 2
.line 13 NORMAL
 Please enter the drive letter, path, and file name where you have placed
 the download update file.


 Path:
.. ............................................................................
.msg 456
.clear
.shade 10 ATTENTION " Incorrect Path to the Download Update File "
.margin 15
.line 13 NORMAL
The file was not found in the specified directory.
.continue
.. ............................................................................
.msg 457
.clear
.shade 8 ATTENTION " Cannot Update from Download "
.margin 4
.line 11 NORMAL
There's a problem with the existing installation that prevents the
download update process from working.

It will be necessary to make a full installation from the original
diskettes before proceeding.  All of your current OS choices and options
will be retained when using a full installation as well as the update.

If this message appears again after performing a full installation,
the original installation diskette is damaged, and you will need to
contact our technical support department.
.. ............................................................................
.msg 458
.clear
.shade 10 ATTENTION " The Download Process Cannot Complete "
.. ............................................................................
.msg 459
.margin 9
.line 14 NORMAL
There was an error creating target directory.  There may not be
enough disk space, or the same named directory exists.  Rename
the download file to a new directory name.
.continue
.. ............................................................................
.msg 460
.margin 9
.line 14 NORMAL
There was an error creating target directory.  There may not be
enough disk space, or the directory already exists.  Rename the
download file to a new directory name.
.continue
.. ............................................................................
.msg 461
.margin 9
.line 14 NORMAL
The down load file is damaged and not usable.  The file may have
not been downloaded properly. Try another file download.
.continue
.. ............................................................................
.msg 462
.margin 10
.line 14 NORMAL
This download file is for the wrong product.  You must use a
download file designed for this specific product.
.continue
.. ............................................................................
.msg 463
.margin 10
.line 14 NORMAL
This download file will not work for your version.  For major
version changes, you must order a full upgrade.
.continue
.. ............................................................................
.msg 464
.margin 10
.line 14 NORMAL
This download file will not work for your version.  Please
contact V Communications technical support to get a current
release.
.continue
.. ............................................................................
.msg 465
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - EZ-Drive not running "
.margin 4
.line 8 NORMAL
The first drive has EZ-Drive/EZ-BIOS software installed, but is not
currently running.  System Commander cannot be installed/uninstalled
until EZ-Drive is properly running.

This EZ-Drive problem typically occurs when you boot from a diskette
without waiting for EZ-Drive to run.  Remove the boot diskette and boot
the system.  Watch on screen for EZ-Drive to instruct you how to boot
the floppy (it usually gives you several seconds to do so).

When properly booted with EZ-Drive running, proceed to install System
Commander.
.continue
.. ............................................................................
.msg 466
.margin 2
.line 7 MAGENTA
           overlapped and/or multiple extended partitions
.. ............................................................................
.msg 467
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - SPExports detected "
.margin 4
.line 8 NORMAL
The SPExport software disk manager is running, and is not compatible
with boot managers.  SPExport makes your large disk drive work on a
system that does not normally support drives greater than 500 MB.

SPExport must be replaced or removed to install System Commander.  In
addition the SPExport software makes your system incompatible with most
OSes (except DOS and Windows).

A number of options are available, including the replacement of SPExport
with EZ-Drive or Disk Manager (a software solution) or the installation
of a minor hardware upgrade, such as an EIDE disk controller card.
Additional information resides in the System Commander installation
notes under Disk Managers.

.continue
.. ............................................................................
.msg 468
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - Old EZ-Drive detected "
.margin 4
.line 8 NORMAL
An old or upgrade version of the EZ-Drive/EZ-BIOS software disk manager
is running, and is not compatible with boot managers.  EZ-Drive makes
your drive work on systems that do not support drives beyond 504 MB.

You must update your EZ-Drive to a current release before continuing with
this installation.  Use EZ-Drive version 9 or later.  Keep in mind that
EZ-Drive is incompatible with many OSes, but is compatible with DOS and
Windows.  Check the MicroHouse Web site for the latest information at
WWW.MICROHOUSE.COM.  Some users report that EZ-Drive's upgrade fails to
allow our installation, even though all first time v9 installs do work!

As an alternative you could install a new EIDE disk controller card.  See
additional information in the System Commander installation notes under
Disk Managers.

.continue
.. ............................................................................
.msg 469
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - Unable to access boot drive "
.margin 4
.line 7 NORMAL
As a check for proper access to the boot drive failed.  The installation
cannot complete. This might occur if:

Cause 1: You are using disk compression, and failed to indicate the
    proper drive letter for the non-compressed boot drive.
    Action:  Exit this installation, and run SCIN from the hard disk.
    Select 'special options', then 'Specify non-compressed boot drive'.
    Enter the correct drive (rarely C:).  Return to main menu, and select
    the update option (Enable or Enable/Reinstall).
Cause 2: If you are not using disk compression, a virus or non-standard
    hard disk driver prevents proper access to your drive.
    Action: Run a good anti-virus software package and check if any non-
    standard device drivers are used to access the disk in CONFIG.SYS.
Cause 3: You are attempting to install System Commander in a FAT16
    partition that is beyond 8 GB.  System Commander can only be
    installed below 8 GB or in a FAT32 type partition past 8 GB.
.continue
.. .........................................................................
.msg 470
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - System Commander installed elsewhere "
.margin 4
.line 8 NORMAL
System Commander was found installed on another partition, which prevents
this installation from completing.

If installed in another partition, exit this installation, and reboot to
the partition where you originally installed System Commander.  Perform a
full installation into the partition where System Commander was
originally installed.

If you are using disk compression, you may have specified the wrong drive
letter for the non-compressed drive.  Exit this installation, and run
SCIN from the hard disk.  Select 'Special options', then 'Specify
non-compressed boot drive'.  Enter the correct drive (rarely C:).  Return
to the main menu, and select Enable.
.continue
.. ..........................................................................
.msg 471
.margin 13
.line 14 NORMAL
Installation cannot proceed because there was an error
accessing the diskette. Please insert another diskette
into the drive and try again.
.continue
.. ............................................................................
.msg 472
.clear
.shade 8 BARTEXT " Making Restart Disk 2 "
.bline MESSAGE "Please wait."
.line 12 NORMAL
.. ...........................................................................
.msg 473
.errbell
.clear
.shade 8 BARTEXT " Make a new Restart Disk 2 "
.margin 17
.line 12 HIGHLIGHT
The disk you inserted is either not formatted
or is not a blank disk. Please use another.
.continue
.. ...........................................................................
.msg 474
.margin 10
.clear
.shade 8 BARTEXT " Remove the new Restart Disk "
.margin 19
.line 12 NORMAL
Label this new disk:
    System Commander - Restart Disk 2

In addition, mark on the old restart disk:
    "OLD-use for install only".
.continue
.. ...........................................................................
.msg 475
.margin 3
.clear
.shade 8 BARTEXT " Make a new Restart Disk 2 "
.margin 10
.line 12 NORMAL
System Commander will now make a new bootable Restart Disk 2.
Please insert a blank formatted 3.5" 1.44MB floppy disk into
drive A.
.continue
.. ............................................................................
.msg 476
.clear
.errbell
.shade 8 ATTENTION " FAT Types do not match "
.margin 4
.line 10 NORMAL
It appears that the current boot record FAT type (FAT16 or FAT32) is
different than the previously saved boot record.  This would occur if the
partition type changed since the first installation.  Restoring the old
boot record will likely make the partition inaccessible.  This process
can not be reversed once done.
.menu 16  16 -1 "Skip update (recommended)"
.menu 18  16 -1 "Continue anyway"
.select
.. ............................................................................
.msg 477
.clear
.errbell
.shade 8 BARTEXT " Boot records are identical "
.margin 12
.line 10 NORMAL
The saved boot record is identical to the partition boot
record. No update is needed.
.menu 16  16 -1 "Skip update"
.menu 18  16 -1 "Continue anyway"
.select
.. ............................................................................
.msg 478
.clear
.shade 4 BARWARNING " Partition Table Analysis Warning - values too large "
.. ...........................................................................
.msg 479
.clear
.shade 10 BARTEXT " Activating System Commander "
.margin 12
.line 13 NORMAL
    Saving disk information for uninstall

    Installation of new boot record
.bline MESSAGE "Please wait."
.. ............................................................................
.msg 480
.clear
.errbell
.shade 10 ATTENTION " Wrong Install Disk "
.margin 6
.line 12 NORMAL
The correct numbered disk has been inserted, but it does not match
the first disk's version or product type.  Please insert the correct
diskette, and press Enter key to continue, or press Ctrl-C to exit
the installation now.
.continue
.. ............................................................................
.msg 481
.clear
.errbell
.shade 8 BARTEXT " Existing Partitioning Files are Newer "
.margin 6
.line 10 NORMAL
The OS Wizard and partitioning files that were previously installed
are newer than those from this installation.  We recommend you keep
the existing newer files.
.menu 14  16 -1 "Keep existing newer files"
.menu 16  16 -1 "Replace with old files"
.select
.. ............................................................................
.msg 482
.clear
.shade 8 BARTEXT " Activate System Commander Personal Edition "
.margin 10
.line 10 NORMAL
You can activate Personal Edition now or activate it later
by running SCIN.EXE and selecting Enable.
.menu 14 16 -1 "Activate Personal Edition now"
.menu 16 16 -1 "Skip activation for now"
.select
.. ............................................................................
.msg 483
.clear
.shade 8 BARTEXT " Install System Commander "
#if BUILD == BT_SC98
.margin 4
.line 10 NORMAL
Another, more advanced System Commander product was detected on your
system. We recommend you continue to use your existing System Commander.

If you install this version now, it will replace your current installed
version and remove all OS selections other than the current one from the
selection menu.
.menu 18 16 -1 "Do not replace the existing copy (recommended)"
.menu 20 16 -1 "Install now, and delete the existing copy"
.select
#else
#if BUILD == BT_PC || BUILD == BT_PC5
.margin 4
.line 10 NORMAL
A different System Commander edition was detected on your system that
supports multiple OSes in the same partition.  We recommend you continue
to use your existing System Commander.

If you install this version now, it will replace your current installed
version and remove all MultiFAT OS selections other than the current one
from the selection menu.

.menu 18 16 -1 "Do not replace the existing copy (recommended)"
.menu 20 16 -1 "Install now, and delete the existing copy"
.select
#else
#if BUILD == BT_SCDTRIAL
.warnbell
.margin 6
.line 10 NORMAL
A different System Commander product is already installed on your
system. This trial version will not be installed.
.continue
#else
#if (BUILD == BT_OEM_PHT) || (BUILD == BT_OEM_MDK) || (BUILD == BT_OEM_L5)
.margin 7
.line 10 NORMAL
Another, more advanced System Commander product was detected on
your system. Since installing this OEM version may remove access
to one or more OSes, installation cannot continue. If you need
to install this edition and do not care about access to all your
OSes, uninstall the existing System Commander first by running
the SCIN program and selecting Disable or Remove, and then Remove.

This OEM version can not be installed.
.continue
#else
.margin 6
.line 10 NORMAL
A different System Commander product is already installed on your
system. If you proceed with this installation, it will replace your
existing System Commander product and may disable some features. If
you are not sure, select 'Do not install'. You can re-install later
from the original install disks.
.menu 17 16 -1 "Do not install"
.menu 19 16 -1 "Install on top of existing"
.select
#endif
#endif
#endif
#endif
.. ............................................................................
.msg 484
.clear
.shade 8 BARTEXT " Enable/Update System Commander "
.margin 8
.line 11 NORMAL
#if BUILD == BT_PC || BUILD == BT_PC5
You do not have System Commander Personal Edition installed yet.
Please install System Commander Personal Edition from your install
disks before enabling it.
#else
You do not have System Commander Windows 98 Edition installed yet.
Please install System Commander Win98 Edition from your install
disks before continuing.
#endif
.continue
.. ............................................................................
.msg 485
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - Drive Up detected "
.margin 4
.line 8 NORMAL
The Drive Up disk manager is installed and is not compatible with boot
management.  This portion of Drive Up makes your drive work on systems
that do not support drives beyond 504 MB.

As an alternative you could install a new EIDE disk controller card.  See
additional information in the System Commander installation notes under
Disk Managers.

.continue
.. ............................................................................
.msg 486
.anykey
.errbell
.scroll
Although it may never be necessary to use a bootable Windows diskette,
it is important to have a bootable diskette in case of system problems
or should a new Windows installation cause a problem.

Before you continue with the installation, we recommend you make a boot
diskette.  You can exit the installation now or you can make a boot
diskette after you complete this installation.

 Creating a Windows 95/98 boot diskette 

At the Windows desktop, select Start, Settings, Control Panel, then click
on the Add/Remove Programs icon.  Select the Startup Disk tab, and click
on Ok.

Windows will make the bootable disk and add all the important files that
would be useful to you.

Press any key or Enter to continue the installation, or press Ctrl-X
to exit now.
.scrollend
.. ............................................................................
.msg 487
.clear
.shade 9 ATTENTION " Erase Windows 98 and start over "
.margin 14
.line 12 NORMAL
Confirm you wish to erase all the Windows 98 files!
.menu 14 18 -1 "Do not erase"
.menu 16 18 -1 "Erase files and start over"
.select
.. ............................................................................
.msg 488
.clear
.shade 9 ATTENTION " Erase Windows 98 and start over "
.margin 17
.line 12 NORMAL
Removing Windows 98 files.  This process make
take 5 minutes or more.  Please wait.
.. ............................................................................
.msg 489
.warnbell
.bline MESSAGE "Press Enter to exit."
.shade 11 ATTENTION " Start over function Unavailable "
.margin 7
.line 13 NORMAL
This function is not available under the current OS.  You must run
SCIN from Windows 3.x or Windows 95 to use this function.
.. ............................................................................
.msg 490
.clear
.succbell
.bline MESSAGE "Press Esc key to exit."
.shade 8 BARTEXT " Step 1 Complete! "
.margin 12
.line 10 NORMAL
You are now ready for Step 2, saving key Windows files.

After you exit this screen, return to Windows.  In
Program Manager, click on File, and then click on Run.
In the run box, enter the program name:

.. ............................................................................
.msg 491
.clear
.errbell
.shade 9 ATTENTION " MultiFAT features are not available "
.margin 10
.line 11 NORMAL
This edition of System Commander does not support multiFAT.
.continue
.. ............................................................................
#if BUILD == BT_PC || BUILD == BT_PC5
.msg 492
.clear
.shade 8 BARTEXT " Confirm Overwrite of System Commander "
.margin 10
.line 10 NORMAL
Select Yes if you wish to install System Commander Personal
edition.  You will lose access to all OSes installed in the
multiFAT partition, except for the last one selected.
.menu 16 20 -1 "No, leave the existing System Commander"
.menu 18 20 -1 "Yes, overwrite existing System Commander"
.select
#endif
.. ............................................................................
.msg 493
.clear
.shade 8 BARTEXT " Partition Editor "
.menu 12 20 -1 "Discard changes"
.menu 14 20 -1 "Return to editor"
.menu 16 20 -1 "Overwrite all partition information"
.select
.. ............................................................................
.msg 494
.bline MESSAGE "F1-Help  F3-Undo all  F4-Zero  F5-ExtViews  F6-Fix  F9-Bootable  Esc to exit"
.line 3 WARNING
PARTITION EDITOR ACTIVE
.. ............................................................................
.msg 495
.scroll
.title Partition Editor Help

The partition editor allows you change any values in the primary or
logical partition tables.

					             IMPORTANT    

Partition editing is designed only for the very advanced computer user
who is familiar with partition tables and what each value means.
Entering wrong values can destroy partitions and make the your system
unrecoverable!  Do not make changes unless you are very sure of what you
are doing.

Upon exit from the partition diagnostic, if any changes have been made,
you will have the option to discard the changes or commit the changes to
your drive.

For advanced users, partition editing allows you to possibly correct
damage to partition tables.  NO TECHNICAL SUPPORT is available for using
the partition editor.

 What is the Partition Table? 

The partition table defines different areas of a disk drive.  For
example, a system using DOS or Windows 95/98/Me with a single physical
drive could split the drive for a C drive and a D drive.  The location
and size of these "virtual" drives is specified by data in the partition
table.

 Partition Editor Functions 

	Move to a new cell    Tab, Back-Tab, Up, Down, Right, Left
	Restore field (undo)  Alt-Backspace
	Exit editing mode     Esc
	Function keys
	  F3-Undo all		  Undo all changes made since editor started.

	  F4-Zero			  All fields for partition entry are zeroed.

	  F5-ExtView		  Each logical partition has an associated
							extended partition that are not normally
							shown. You can toggle between logicals,
							extendeds, or both (up to 9 maximum).

	  F6-Fix			  When possible, Fix will align the Sector/Head/
	  						Cylinder values with the starting and total
							sectors (not recommended for Unix partitions).

							If the Start or End sector values are zero
							new values are calculated from the
							first/total if the First or Total sectors
							field is zero a new value is calculated from
							the Sector/Head/Cylinder values.

							Fix does not necessary correct all problems
							and it can create new ones, so review the
							changes that are made carefully.

	  F9-Bootable		  Toggle the bootable flag, which appears
							as a "+" if bootable, and a "-" if not.
							System Commander, if active, is unaffected
							by the bootable status.

 What does the Partition data mean? 

The table shows specific data directly from your partition table(s).

Drive and Partition - This shows the drive number (1st drive = 0) and
   the partition number (1st partition is 0).  A value of 1-3
   indicates the second drive, and the fourth primary partition.

   An extended partition is followed by all of the extended partitions
   on the drive.  Each partition with an id value of 5, points to
   another group of partitions.

id - This defines the type of partition.  The FAT type partition used
   by DOS, Windows 95/98/Me and others use ID values 1, 4, or 6.  Windows
   NT and OS/2's HPFS or NTFS file systems use a value of 7.  Other
   operating systems use other values.  Hidden partitions add 10h to the
   value.  An ID of 16 indicate a hidden FAT ID 6 partition.

Starting Sector-Head-Cylinder - This identifies where the partition
   begins on the drive.  Through a complex calculation, it directly
   relates to the Starting Sector value.

Ending Sector-Head-Cylinder - This identifies where the partition
   ends on the drive. This information can be wrong without affecting
   System Commander or an operating system, since neither use the
   information. Wrong information here may prevent partitioning tools
   from working.

Starting Sector - This is an alternative value to the Starting head,
   sector and cylinder value.  It treats the disk as one long string of
   sectors, and points to where this partition begins. It should point
   to the same place on the disk as the starting head-sector-cylinder.

   Most standard operating systems do not use this value. In some
   systems, bad values may appear in this field without affect.

Total Sectors - This specifies how many sectors reside in a partition.
   If you multiply this value by the sector size (almost always 512),
   you will get the number of total bytes in the partition.

   On FAT, FAT32, HPFS, and NTFS, a check is made to see if the value
   is smaller than that indicated in the related partition boot record.
   If so, the field is marked in Orange.  It indicates the partition
   size is smaller than that specified in the boot record.  While the OS
   may work correctly, you cannot safely partition the disk with this
   situation.

   Compaq, Dell, and others often image a new machine that creates this
   wierd condition (FDISK and other partitioning utilities will never
   create this condition).  You can try to use the F6-Fix option to
   resynchronize the partition table entry, but the partition will
   likely be larger than the specified BIOS parameters!

 Warnings and Errors 

   Warning - BIOS LBA setting wrong?

   Cause: One or more head values in the primary partitions exceed the
   BIOS heads number AND the BIOS heads number is 15.  This usually
   occurs when BIOS CMOS setting indicates LBA is off, yet the partition
   table was likely created when it was on.

   Action: First, get a good backup of your system.  Switching the LBA
   state might cause the loss of all data!  Next, activate your BIOS
   setup and set LBA on. Older systems (pre-1995) do not have such an
   option.  With LBA on, see if the system and data within each drive is
   valid and working.  You might use SCANDISK to test each drive.

   We have seen a number of new systems from major vendors shipping with
   LBA set incorrectly. Windows 95 and 98 can mask this problem, as they
   will work with LBA set incorrectly, but you cannot safely partition
   the disk with the option set wrong.

   Warning - values too large

   Cause: This indicates either:
   	 1) The start of the partition is beyond the size of the disk, as
   		reported by the BIOS.
	 2) The Start sector or total sectors value is above 64 GB (
		or 512 MB if an EBIOS type).

   Action: It is unclear why this damage has occurred. It might occur if
   the BIOS CMOS values were too small, or if EBIOS support was turned
   off (like switching to a old motherboard).  No advice is available to
   correct it, short of removing the partition and starting over
   (remember to back up before deleting the partition).

   Warning - First sector size mismatch

   Cause: The Starting Sector/Head/Cylinder do not match with the Logical
   Start value.

   Action: If you are not having problems, we recommend leaving it alone.
   This problem often occurs with some Unix versions, especially those
   older versions that do not understand LBA. If this is the case, do not
   change it, or the Unix OS may no longer work.

   For other situations you could try the F6-Fix option to see if it
   can correct it.

   Warning - Ending address too large

   Cause: The Ending Sector/Head/Cylinder is beyond the values specified
   from the BIOS.

   Action: Either the BIOS values are set wrong or the partition entry is
   wrong. This problem often occurs with some Unix versions, especially
   those older versions that do not understand LBA. If this is the case,
   do not change it, or the Unix OS may no longer work.

   If you know the partition entry is wrong you could try the F6-Fix
   option to see if it can correct it.

   Warning - Sector mismatch & Ending address

   Both of the prior problems are occurring. See the last two warnings for
   details of each problem.

   Warning - Overlapping partitions

   Cause: One or more partitions have values that conflict with another
   partition. This problem often occurs with some Unix versions,
   especially those older versions that do not understand LBA. If this is
   the case, do not change it, or the Unix OS may no longer work.

   Action: For overlaps with non-Unix partitions, it is unclear which
   partition is at fault. If you know what is damaged, you may be able
   to correct or remove the problem partition.

   overlapped and/or multiple extended partitions

   Cause: See above, and you may have more than one extended primary
   partition.  No partitioning tool allows more than one extended
   primary partition, and it is unclear what each OS will do when more
   than one extended partition appears.

   Action: We recommend removal of the extra extended partitions, so
   that you are left with one.  DO NOT remove any extended partition
   marked with ext-#.  These are ok, and are sub-extended partitions
   under one primary.  This problem only relates to multiple PRIMARY
   extended partitions.

   Warning - Id not EBIOS type

   A partition exists in whole or in part above 8 GB.  For FAT and
   FAT32 types, this normally is designated by a special partition
   type, typically id C, E, or F.  The partition type does not match
   this special designator and may not be seen by Windows
   9x/Me/2000/XP. If the partition is accessible, we recommend no
   change.  If it is not accessible, it should be deleted and
   re-created (although any data in that partition will be lost).

   Warning - No EBIOS support for id

   One or more partitions are designated as an EBIOS type partition
   using a partition id of C, E, or F.  No EBIOS support was detected
   for this drive.  This might occur if you boot into DOS on a system
   without EBIOS in the BIOS.  If you boot from a Windows 95 (OSR2),
   Windows 98/2000/XP, EBIOS will be supported and the partition will
   be usable.

.scrollend
.. ............................................................................
.msg 496
.clear
.anykey
.shade 12 BARTEXT " Partition Changes Discarded "
.. ............................................................................
.msg 497
.bline MESSAGE "No automatic fix available for this partition.     Press any key to continue"
.warnbell
.. ............................................................................
.msg 498
.clear
.shade 7 BARWARNING " Partition Editor "
.margin 4
.line 10 NORMAL
The Partition Editor allows you to make changes to the partition tables.

CAUTION - This feature is for advanced computer users who fully
understand partitioning.  See help for more details.

Saving defective changes can erase or damage partitions so that the data
may be unrecoverable!  Please make changes with extreme caution.
.continue
.. ............................................................................
.msg 499
.clear
.shade 4 BARWARNING " Partition Table Analysis Warning - BIOS LBA setting wrong? "
.. ..........................................................................
.msg 500
.margin 2
.line 6 NORMAL
BIOS Parameter Limits:

Drive &          Starting    Ending    Sector 
Partition   ID  Sector Head Cylinder  Sector Head Cylinder    First    Total
.. ............................................................................
.msg 501
.warnbell
.scroll
.htitle  Partition Table Analysis Warning - BIOS LBA setting wrong? 

The partition table has values that exceed the size of the drive as
reported by the BIOS.  This usually indicates that the LBA setting is
turned off, when it should be on.  Please read this entire note before
making any changes!

 What is "LBA"? 

LBA stands for Logical Block Addressing.  This is a method of accessing
hard drives larger than 504 MB by your computer.  Almost all computers with
a BIOS dated 1995 or later support LBA.  Older systems must use a special
software driver to do the same thing.  Disk Manager and EZ-Drive are the
two best known software drivers.  These software drivers will provide LBA
support for drives above 504 MB.

 Typical Causes 

	1) Hardware was changed or a hard drive was moved from one system to
	   another.

	2) CMOS settings were lost or altered, such that the LBA option was
	   set off.

	3) CMOS settings are wrong from the start. We have seen a number of
	   new, brand-name systems that have incorrectly shipped with the LBA
	   option off.  Windows 95/98/Me can tolerate this condition, but you
	   cannot safely partition the drive.

	4) If you were using Disk Manager or EZ-Drive, the system may have
	   been started without it running, or the software is damaged or
	   missing.

 Solutions 

If you have been using Disk Manager or EZ-Drive, you will need to get
it running again.  You may need to refer to your manuals or contact
On Track (Disk Manager) or Microhouse (EZ-Drive) for instructions.

For newer systems, you need to change the LBA option on.  BEFORE YOU
MAKE A CHANGE - make a backup of your important data.  Changing the LBA
option can, on some systems loose all the data on the drive!  Often,
the drive will look strange, or unreadable, and a full format will be
required.  If you perform no disk writes, you can turn back off LBA and
your data should reappear.

For technical experts, you can make the LBA change yourself, otherwise
you may wish to contact the system manufacturer or take your system
into a competent shop.  Just indicate you need to get LBA turned on,
and they should know what you need.

To change the LBA setting yourself, after a backup has been made, reboot
your system (shutdown Windows) and go into the BIOS CMOS settings.  Every
manufacturer is different, but often a quick message will appear like
"Press F1 for setup".  You may need to contact your computer manufacturer
for instructions.  Next go to the hard drive settings and look for an
option about LBA (or Advanced CHS).  If the system has an "Auto detect"
option, you may want to try that.  Most systems will show the size of the
drive.  If it shows 504 MB, either the LBA option is not on, or it does
not support it.

Once LBA is active, boot up and see if the drive is visible and working.
Run SCANDISK to see if any errors appear.  If many errors appear or the
drive returns error messages, you may need to boot from a diskette and
format the drive.

 V Communications Help 

We are sorry to say that we cannot provide technical support to get your
LBA working.  This is a system problem, and has nothing to do with this
software.  The warning is here to help make your system work correctly,
and ensure other software works correctly without damaging your
environment.

.scrollend
.. ..........................................................................
.msg 502
.clear
.shade 4 ATTENTION " Undo an OS-Wizard added OS "
.margin 4
.line 6 NORMAL
If you wish to undo your OS Wizard newly added OS partition, you must
do so from within OS Wizard.  To undo the OS, exit from SCIN, reboot,
and at the OS selection menu, press Alt-O (OS Wizard).  When the OS
Wizard selection screen appears, select Cancel, then Undo, Undo Wizard.

The Undo Wizard will then guide you through the undo process. After the
Undo Wizard has finished, reboot and continue your uninstall from SCIN.

If your last added OS resided in an isolated partition, this undo will
erase all data in that partition since it is no longer needed. After
undo, the data is not recoverable.  If you do not wish to run Undo
Wizard, then select the continue command.

.menu 19  16 -1 "Exit and undo OS-Wizard"
.menu 21  16 -1 "Continue without undo OS-Wizard"
.select
.. ..........................................................................
.msg 503
.clear
.shade 4 BARWARNING " Partition Table Analysis Warning - Id not EBIOS type "
.. ..........................................................................
.msg 504
.clear
.shade 4 BARWARNING " Partition Table Analysis Warning - No EBIOS support for id "
.. ..........................................................................
.msg 505
.clear
.succbell
.shade 8 BARTEXT " Uninstall Note "
.bline MESSAGE "Press any key to exit"
.margin 5
.line 11 NORMAL
Remember that if you wish to purchase the full System Commander
product in the future, you must first uninstall this current edition
of System Commander completely before installing the new product.
.. ..........................................................................
.msg 506
.clear
.shade 10 ATTENTION " Missing Installation File! "
.bline MESSAGE "Press any key to exit."
.margin 12
.line 12 NORMAL
The installation cannot continue.  The missing file is:
.. ..........................................................................
.msg 507
.clear
.shade 4 BARTEXT " Make Utility Diskettes "
.margin 7
.line 6 NORMAL
Utility Disk 1 - This diskette includes a number of utilities to
assist with OS preparation, diagnostics and uninstallation.  In
addition, several data files are backed up onto this diskette
(Recommended, not required).

#if BUILD == BT_PC || BUILD == BT_PC5
Partitioning/Restart Disk 2 - You can boot directly from this
#if BUILD == BT_DW
diskette to run DriveWorks Commander.  This diskette is also
#else
diskette to run Partition Commander.  This diskette is also
#endif
required for recovery should apower fail or reset occur during
some critical Wizard or partitioning operations. (Recommended)
#else
#if BUILD == BT_OEM_AL
Restart Disk 2 - This diskette is required for recovery should a
power fail or reset occur during some partitioning operations.
Should this diskette be needed, you will be prompted to boot
from the Restart disk. (Recommended)
#else
Restart Disk 2 - This diskette is required for recovery should a
power fail or reset occur during some critical OS Wizard or
partitioning operations.  Should this diskette be needed, you
will be prompted to boot from the Restart disk. (Recommended)
#endif
#endif

#if BUILD != BT_OEM_AL
If you are installing from the retail package which includes a
Restart disk, you do not need to make another of the same version.
#endif

.menu 19  16 -1 "Make both diskettes"
.menu 20  16 -1 "Utility diskette only"
.menu 21  16 -1 "Restart diskette only"
.menu 22  16 -1 "Skip making diskettes"
.select
.. ..........................................................................
.msg 508
.clear
.shade 8 BARTEXT " Make Utility Disk 1 "
.bline MESSAGE "Press any key to start."
.line 13 NORMAL
Insert a 1.44 MB diskette in drive A.
.. ..........................................................................
.msg 509
.clear
.shade 8 ATTENTION " Diskette not formatted "
.line 10 NORMAL
The diskette is not formatted for 1.44 MB.

.menu 13  16 -1 "I'll try another diskette"
.menu 14  16 -1 "Format diskette"
.menu 15  16 -1 "Skip making diskette"
.select
.. ..........................................................................
.msg 510
.clear
.shade 8 BARTEXT " Erasing files from Diskette "
.bline MESSAGE " "
.line 10 NORMAL
Please wait.
.. ..........................................................................
.msg 511
.clear
.shade 8 BARTEXT " Utility Disk 1 Done "
.bline MESSAGE "Press any key to continue."
.line 10 NORMAL
.margin 12
Remove the diskette from the drive.  Label the diskette:

#if BUILD == BT_SC2000
    System Commander 2000
#else
#if BUILD == BT_SC7
    System Commander 7
#else
#if BUILD == BT_PC || BUILD == BT_PC5
    Partition Commander
#else
#if BUILD == BT_DW
	DriveWorks
#else
#if SC_DELUXE == 1
    System Commander Deluxe
#else
    System Commander
#endif
#endif
#endif
#endif
#endif
    Boot Utility Disk 1
.. ..........................................................................
.msg 512
.clear
.shade 8 BARTEXT " Make Restart Disk 2 "
.bline MESSAGE "Press any key to start."
.line 13 NORMAL
Insert a 1.44 MB diskette in drive A.
.. ..........................................................................
.msg 513
.clear
.shade 8 BARTEXT " Making Utility Disk 1 "
.bline MESSAGE "Please wait."
.line 12 NORMAL
.. ..........................................................................
.msg 514
.clear
.shade 8 BARTEXT " Restart Disk 2 Done "
.bline MESSAGE "Press any key to continue."
.margin 12
.line 10 NORMAL
Remove the diskette from the drive.  Label the diskette:

#if BUILD == BT_SC2000
    System Commander 2000
    Restart Disk 2
#else
#if BUILD == BT_SC7
    System Commander 7
    Restart Disk 2
#else
#if BUILD == BT_PC || BUILD == BT_PC5
    Partition Commander
    Restart Disk 2 and Partitioning
#else
#if BUILD == BT_DW
	DriveWorks
    Restart Disk 2 and Partitioning
#else
#if SC_DELUXE == 1
    System Commander Deluxe
    Restart Disk 2
#else
    System Commander
    Restart Disk 2
#endif
#endif
#endif
#endif
#endif
.. ..........................................................................
.msg 515
.clear
.errbell
.shade 8 ATTENTION " Diskette is not Blank "
.margin 11
.line 10 NORMAL
The diskette has one or more files already on it.  A blank
diskette should be used.

.menu 14  16 -1 "I'll try another diskette"
.menu 15  16 -1 "View diskette root directory"
.menu 16  16 -1 "Erase all diskette files first and proceed"
.menu 17  16 -1 "Attempt to use anyway (may not fit)"
.menu 18  16 -1 "Skip making diskette"
.select
.. ............................................................................
.msg 516
.clear
.shade 8 ATTENTION " Unable to Make Diskette "
.bline MESSAGE "Press any key."
.margin 12
.line 10 NORMAL
You must run SCIN from either the install CDROM or from
the hard disk.
.. ............................................................................
.msg 517
.clear
.shade 8 ATTENTION " Unable to Make Diskette "
.bline MESSAGE "Press any key."
.margin 12
.line 10 NORMAL
One or more files are missing that are required to make
the diskette.  The first file missing is:
.. ............................................................................
.msg 518
.clear
.shade 8 ATTENTION " Unable to Write to Diskette "
.bline MESSAGE "Press ENTER to try again.                               Press Esc to exit."
.margin 11
.line 10 NORMAL
An error occurred while attempting to write the MBR to the
diskette. Please check that the write protect tab on the
diskette is closed (i.e. allows writes), and no Anti-virus
software limits disk writes.
.. ............................................................................
.msg 519
.clear
.shade 8 BARTEXT " Checking Diskette... "
.bline MESSAGE "Please wait."
.line 12 NORMAL
.. ............................................................................
.msg 520
.clear
.shade 4 BARTEXT " Contents of A: Root Directory "
.bline MESSAGE "Press any key."
.line 6 NORMAL
.. ............................................................................
.msg 521
.clear
.shade 8 BARTEXT " Formatting Diskette "
.bline MESSAGE "Please wait."
.line 10 NORMAL
.. ............................................................................
.msg 522
.clear
.shade 8 BARTEXT " Formatting Diskette Failed "
.bline MESSAGE "Press any key."
.line 10 NORMAL
Unable to format diskette - please try another 1.44 MB diskette.
.. ..........................................................................
.msg 523
.clear
.shade 8 BARTEXT " Make a Boot Diskette "
.bline MESSAGE "Press any key to start."
.line 13 NORMAL
Insert a 1.44 MB diskette in drive A.
.. ..........................................................................
.msg 524
.clear
.shade 8 ATTENTION " Diskette not formatted "
.line 10 NORMAL
The diskette is not formatted for 1.44 MB.

.menu 13  16 -1 "I'll try another diskette"
.menu 15  16 -1 "Skip making diskette"
.select
.. ..........................................................................
.msg 525
.clear
.shade 8 BARTEXT " OS Boot diskette Complete "
.bline MESSAGE "Press any key to continue."
.margin 17
.line 10 NORMAL
Remove the diskette from the drive.  Label the
diskette with "Boot Diskette" and include the
currently running OS name and version.
.. ..........................................................................
.msg 526
.clear
.shade 8 BARTEXT " Making OS Boot Diskette "
.bline MESSAGE "Please wait."
.line 12 NORMAL
.. ............................................................................
.msg 527
.clear
.shade 8 ATTENTION " Unable to locate System Files "
.bline MESSAGE "Press any key."
.margin 11
.line 10 NORMAL
The hidden system files were not found on the root of your
hard disk for DOS, Windows 95 or Windows 98, which are
necessary to make your boot diskette.

Please make your boot diskette manually from the OS after
the installation is complete.  (See your OS manual for
details).
.. ............................................................................
.msg 528
.clear
.shade 8 ATTENTION " Diskette Missing? "
.bline MESSAGE "Press ENTER to try again.                               Press Esc to exit."
.margin 17
.line 10 NORMAL
Unable to read the diskette - please verify a
valid 1.44 MB diskette is in the A drive.
.. ............................................................................
.msg 529
.warnbell
.scroll
.htitle  Installation Cannot Proceed - No Partition for Installation 

A check of the first hard disk found no FAT or FAT32 primary partition
for installation.  System Commander requires a FAT or FAT32 primary
partition to install its files.

If the hard disk is blank, or formatted for NTFS or Linux, we can create
the partition for you.  For NTFS and Linux systems, if no free space is
available, it will resize the existing partition slightly smaller and
create a small FAT partition.

Use the following instructions (print or jot these steps down):

1)  Boot from the restart disk 2, and it will detect that no FAT/FAT32
    partition exists.  After confirming you wish to create a new
    installation partition, it will automatically perform the necessary
	partitioning steps.

	If you need to create a restart disk 2, run SCIN.EXE and select
	Special Options, Make Utility Diskettes.

2)  Boot from a Windows 95/98 or DOS diskette that has CDROM support.
	At the prompt, type  dir c: and confirm there are no files yet
	(this ensures you are looking at the new partition).

3)  At the prompt type  sys c:  to transfer a base system.

4)  Switch to the CDROM drive (typically E:). At the prompt type
	e:  (use the drive letter for your CDROM).  Next switch
	to the install directory by typing  cd \install

5)  Install System Commander by typing  setup

.scrollend
.. ............................................................................
.msg 530
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - Unable to read MBR "
.margin 4
.line 7 NORMAL
In attempting to read from the first hard disk, a disk error occurred.
This might occur if no hard drive exists or the drive is malfunctioning
or the OS you are using does not allow normal disk access (Windows NT,
Windows 2000/XP and OS/2 do not allow full disk access).

You must install System Commander from Windows 95/98/Me/DOS or use the
Windows installer with System Commander 7. These OSes can be run from
your hard disk, or from a boot diskette. If the drive has a malfunction,
please correct it and run the installation program again.
.continue
.. ............................................................................
.msg 531
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - No Partition for Installation "
.margin 6
.line 7 NORMAL
A check of the first hard disk found no visible FAT/FAT32 primary
partition for installation.  System Commander requires a non-hidden
visible FAT or FAT32 primary partition to install its files.

Please un-hide the FAT or FAT32 partition. Once the FAT/FAT32 is
visible, you can proceed with the normal installation.
.continue
.. ............................................................................
.msg 532
.clear
.errbell
.shade 5 ATTENTION " Installation Cannot Proceed - GoBack detected "
.margin 6
.line 7 NORMAL
A check of the first hard disk found no primary FAT/FAT32 partition
for installation.  System Commander requires a FAT or FAT32 primary
partition to install its files.

It appears that the system may have GoBack installed which causes
this problem.  You must uninstall GoBack to install and use any boot
management or partitioning products, such as System Commander or
Partition Commander.
.continue
.. ............................................................................
.msg 533
.. Message when MultiFAT is FAT32 or FAT16 EBIOS, and no IO.SYS is
..  found that is compatible with OS Wizard (i.e. not Win2000 or DOS).
.clear
.errbell
.shade 7 ATTENTION " Installation requires Windows 95/98 boot diskette "
.margin 6
.line 9 NORMAL
To enable OS Wizard operations, it is necessary to copy several files
from a Windows 98 or Windows 95 OSR2 boot diskette. (A Windows 2000
boot disk is NOT suitable).

If you skip allowing OS Wizard operation, you will still be able to
boot from different OSes using System Commander's OS selection menu.

.menu 17  16 -1 "The Windows 95/98 boot diskette is in drive A"
.menu 19  16 -1 "Skip allowing OS Wizard operation"
.select
.. ..........................................................................
.msg 534
.clear
.shade 8 BARTEXT " Copying Files From Boot Diskette "
.bline MESSAGE "Please wait."
.line 12 NORMAL
.. ............................................................................
.msg 535
.clear
.errbell
.shade 5 ATTENTION " Unable to prepare for OS Wizard operation "
.margin 4
.line 7 NORMAL
For proper OS Wizard operation from this partition, a compatible
boot portion of Windows 98 or 95 ORS2 must be installed.  The
specific problem encountered was:



This will prevent the OS Wizard feature from working. To correct this
problem, once the installation completes, it will be necessary to
install a minimal Windows 98 or 95 OSR2 into this partition (less
than 500 KB).  To do this, once System Commander is fully installed,
and you have rebooted at least once (to see the System Commander OS
selection menu), boot from a Windows 95 or 98 boot diskette, and at
the prompt type in:

    A:\>  sys c:

This will transfer the necessary files for proper OS Wizard operation.
.. ............................................................................
.msg 536
.clear
.errbell
.shade 5 ATTENTION " No compatible OS for OS Wizard operation "
.margin 5
.line 7 NORMAL
For proper OS Wizard operation in a FAT32 or FAT EBIOS partition, a
limited portion of Windows 95 OSR2 or Windows 98 must be installed.
Other OS management features such as OS boot selection will work fine,
even without these files.

To add OS Wizard support, once this installation completes, it will be
necessary to install a minimal Windows 95 or 98 into this partition
(less than 300 KB).  To do this, once System Commander is fully
installed, and you have rebooted at least once (to see the System
Commander OS selection menu), boot from a Windows 95 or 98 boot
diskette, and at the prompt type in:

    A:\>  sys c:

This will transfer the necessary files for proper OS Wizard operation.
.. ............................................................................
.msg 537
.clear
.errbell
.shade 5 ATTENTION " Unable to complete installation "
.margin 5
.line 7 NORMAL
The SCBOOT.DAT file could not be found or had an error reading the
file.  To complete the installation, verify this file is in the
same directory as SCIN.EXE.  You may also try to boot from an OS
boot diskette, run SCIN at the prompt, select "Enable".
.. ............................................................................
.msg 538
.clear
.scroll
.title License and Warranty Agreement

By using the enclosed Software you indicate your acceptance of all terms
and conditions of this license agreement. If you do not agree with these
terms then V Communications is unwilling to license the Software to you,
in which event you should return the full product with proof of purchase
to the dealer from whom it was acquired within sixty days of purchase for
a refund of the purchase price, or destroy all copies of the Software and
the accompanying documentation.

The Software that accompanies this license (the "Software") is the
property of V Communications or its licensors and is protected by
copyright law. While V Communications continues to own the Software, you
will have certain rights and obligations to use the Software after
acceptance of this license as follows:

	Number of Copies Licensed. If you have not purchased a multi-site
	license, you are authorized to use only a single copy of the Software
	on a single computer. If you have purchased a multi-site license, you
	are authorized to use the Software on no more than the number of
	computers for which you have purchased licenses. To purchase or
	expand your multi-site license, contact V Communications at
	sales@v-com.com or at 1-408-965-4000.

    Copies. You can make only one copy of the Software for backup or
	archival purposes. You may not copy the documentation that
	accompanies the Software.

	Transfer of License.  After written notice to V Communications, you
	may transfer the Software, to another person or entity, provided that
	no copies or older versions of the Software are retained, and the
	transferee agrees to the terms of this agreement.

	Non-permitted Uses.  You may not modify, translate, sublicense, rent
	or lease any portion of the Software or accompanying documentation.
	You may not create any derivative works from the Software.  You may
	not use or transfer a previous version of the Software after you have
	received a media replacement or an upgraded version as a replacement
	to a prior version.

	Term. This license is effective from your date of purchase and will
	remain in force until terminated.  You may terminate this License
	agreement at any time by removing the software from your computer and
	destroying all copies of the Software in any form and
	destroying any accompanying documentation.

V Communications Limited Warranty

V Communications, Inc. warrants to the original purchaser that the media
on which the program is furnished to be free from defects in materials
and workmanship under normal use, and warrants that the Software conforms
substantially to any V Communications' advertised claims at the date of
sale. This limited warranty extends from thirty (30) days from the date
of purchase as evidenced by a copy of your receipt.

This warranty does not apply to any Software that has been altered,
abused, damaged, mis-applied, or used other than in accordance with this
license and any instructions included in the Software and accompanying
documentation. V Communications does not warrant that the Software will
meet your requirements or that operation of the Software will be
uninterrupted or that the Software will be error-free.

In the event of notification within the warranty period of failure to
meet any V Communications' advertised claims at the date of sale, you may
#if BUILD == BT_LITE_PCA
terminate this license by removing this program from your computer.
#else
return the program and all associated manuals in good condition to your
place of purchase for a refund.  If you need to exchange or return a
product purchased directly from V Communications, call our customer
service department to obtain a return authorization number.
#endif

To the maximum extent permitted by applicable law, V Communications and
its suppliers disclaim all other warranties, either express or implied,
including, but not limited to, implied warranties of merchantability,
fitness for a particular purpose, and non-infringement with regard to the
Software. This Warranty gives you specific legal rights. You may have
other rights, which vary in different jurisdictions.

Limitation of Liability

To the maximum extent permitted by applicable law, in no event shall V
Communications or its suppliers be liable for any special, incidental,
indirect or consequential damages whatsoever (including, without
limitation, damages for loss of business profits, loss of business or
personal information, or any other monetary loss) arising out of the use
of or the inability to use the Software, even if V Communications has
been advised of the possibility of damages. Because some states and
jurisdictions do not allow the exclusion or limitation of liability for
consequential or incidental damages, the above limitation may not apply
to you.  In no event shall V Communications liability exceed the purchase
price for the Software. The disclaimers and limitations set forth above
will apply regardless of whether you accept the Software.

Complete Agreement

Having read this Agreement, you agree that no contrary or inconsistent
statement, oral or written, has been made by any person and that this is
the complete and exclusive statement of the terms and conditions of the
Agreement between us, and any prior proposal or statement, whether
written or oral, is superseded.  In the event of any dispute regarding
the terms and conditions of this Agreement, you agree that the laws of
the State of California will govern the interpretation of the Agreement.

U.S. Government Restricted Rights Legend

The SOFTWARE and documentation are provided with RESTRICTED RIGHTS.  Use,
duplication, or disclosure by the Government are subject to restrictions
as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data
and Computer Software clause at DFARS 252.227-7013 or subparagraphs
(c)(1) and (2) of the Commercial Computer Software-Restricted Rights at
48 CFR 52.277-19, as applicable, V Communications, Inc., 2290 North First
St., Suite 101, San Jose, CA, 95131, USA.
.scrollend
.. ............................................................................
.msg 539
.clear
.scroll
.title Making a Boot Diskette from Windows

You can make the Windows Emergency Boot Diskette (EBD) at any time.

To do so, click on Start, then Settings, Control Panel. Select the
Add/Remove Programs Icon, click on the Startup Disk tab, and then
click on the Create Disk... button.
.scrollend
.. ............................................................................
.msg 540
.bline MESSAGE "Press Esc to exit"
.line 22 BADHIGH
Insert a valid system boot disk in drive A and press the Enter key.
(Transfer System does not support Windows Me)
.. ............................................................................
.msg 541
.clear
.shade 11 BARTEXT " Checking Environment "
.. ............................................................................
.msg 542
.clear
.shade 11 BARTEXT " Checking Environment "
.. ............................................................................
.msg 543
.bline MESSAGE "Press Esc to exit"
.line 22 BADHIGH
Insert a valid system boot disk in drive A and press the Enter key.
(Transfer System does not support MS/PC-DOS into FAT32).
.. ............................................................................
.msg 599
.shade 8 BARWARNING " End of Messages "