
                        Ŀ
                         System Commander Notes 
                        

    CONTENTS

        A. Installation Notes
        B. Disk Compression
        C. Features
        D. Problems
        E. Technical Support
        F. Ordering Information
            
    A. Installation Notes

        Although System Commander itself only takes a few minutes to 
        install, a number of very important decisions must be made.
        
        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. 

        Additional Notes not in the manual:
        
                Multiple Primary DOS Partitions
                Unix System V 
                Disk Error Message after OS Selection 
        

        Multiple Primary DOS Partitions
        
        Although extremely rare, it is possible to have a system with 
        more than one DOS primary partition on the first drive.  DOS by 
        itself (and DOS's FDISK) will NEVER create such a configuration. 
        If additional drives are necessary, FDISK will only allow one 
        primary DOS partition, but makes no restrictions on the number 
        of DOS logical partitions.  

        System Commander is designed to work on systems with multiple 
        DOS partitions, even if the bootable DOS partition is not the 
        first primary DOS partition.  For example, a system has OS/2 
        version 1.x installed (which always uses a DOS partition).  
        Later DOS is installed into another primary partition by using 
        OS/2's FDISK. 
        
        When installing System Commander on such a system, you must boot 
        up from the hard disk under DOS (i.e. not OS/2). To do this, use 
        FDISK or the SCDISK utility included on the System Commander 
        diskette to mark the DOS partition that holds DOS as bootable, 
        and reboot.  
        
        Once DOS is running, install System Commander.  System Commander 
        will automatically detect the unusual configuration.  If it has 
        any problems with the configuration (like no partitions marked 
        bootable), System Commander will notify you, and exit before 
        completing the installation. 

        Unix System V 
        
        Most operating systems expect to see a single partition bootable, 
        with all other primary partitions marked as non-bootable. Unix 
        System V requires all System V partitions be marked as bootable, 
        even if the partition is not truly bootable.  Bootable status is 
        often referred to as the "active partition" by FDISK.
        
        A new option was added to the local options menu, under setup, 
        to override the default operation.  The new option is 
        "Bootable/active status across partitions".  If using Unix 
        System V, set this option to OVERRIDE ON.  All other operating 
        systems, including other Unix variants, should use the default 
        setting of AUTO. 

        Disk Error Message after OS Selection 

        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, 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.  
        
        It is safe to select "Continue" instead of the recommended 
        "Reboot" from the disk error warning message.  To eliminate the 
        problem (without replacing the drive), from the OS selection 
        menu, select F2-Setup, then "Global special options menu".  
        Select the choice "Disk drives, above drive 0, ignored".  If 
        the problem drive is the third drive, select 2.  If the drive 
        is the second drive, select 1 & 2.  This option forces 
        System Commander to ignore the specified drives.  Drive 0
        must always be accessable.
        
        
    B. Disk Compression

        We do not recommend using System Commander with disk compression.
        Although it is possible to do so, the disk compression program
        can cause problems when different DOS versions are run.  In
        addition, System Commander itself must operate before the disk 
        compression software runs.  Drive swapping can cause compression 
        or misplacement of the System Commander files.  In all, there 
        may be a number of problems and you are ON YOUR OWN should you 
        attempt this!  

        If you attempt to install System Commander on a system using disk 
        compression, you MUST know which drive is the non-compressed boot 
        drive.  This is often hidden by the disk compression.  For 
        example, on two systems using Microsoft's DoubleSpace disk 
        compression, one uses drive D, and another uses drive H as the 
        non-compressed boot disk.  It is rarely drive C:.  Perform a DIR 
        command from each root directory to help locate which drive is 
        the non-compressed boot drive.  The boot drive usually has 
        a few files.  One file, usually marked as hidden, is used for 
        disk compression and will be huge. 

        After the System Commander installation, when you reboot, should 
        you get an "Boot Err n, Hit key." message, it indicates either 
        you selected the wrong drive to install System Commander and/or 
        the disk compression method prevents access to System 
        Commander's files.  Refer to Chapter 6, Troubleshooting for 
        notes on restoring the system to normal.  DO NOT go in and delete 
        System Commander files, one file holds the original master boot 
        record, needed to restore the system to normal.
        

    C. Features
        
        With System Commander you'll be able to have multiple operating 
        systems function on a single PC.  Once installed, when you boot 
        up, you will be provided with a menu of OS choices, based on the 
        operating systems you install. 

        Key Benefits

        * Management of up to 42 different operating systems including:
                up to 16 OSs in the DOS partition
                up to 16 non-DOS OSs in logical partitions
                up to 11 non-DOS OSs in primary partitions
        
        * Menu selections offered before any operating system runs

        * Remembers the last selection made

        * Choose from a number of unique sound effects when System 
            Commander's menu appears

        * Select time-out period to automatically make a selection

        * Automatically saves newly installed DOS versions

        * View partition information and change bootable status

        * Boot sector virus detect and correction

        
        Technical Highlights

        * MS/PC-DOS compatible, all released and beta versions, 3.0
            and later

        * DR-DOS/Novell DOS compatible, all released and beta versions 
            5.0 and later 

        * Fully compatible with NT, OS/2, Unix, NetWare, and most 
            other OSs

        * No bytes remain resident in memory

        * Comprehensive boot validity checks and recovery 


    D. Problems

        Most problems are easily resolved as described in the manual 
        under Chapter 6, Troubleshooting. 

        System Commander's installation always provides an Uninstall
        option, available from the hard disk or the diskette.  Refer
        to the Uninstallation instructions, should you need to do 
        this.

        Boot Err 2 - Hit Key

        If immediately after installation the "Boot Err 2" message 
        appears, see Chapter 6, Troubleshooting for reasons why this 
        might occur and how to correct for it.  
        
        One reason this can occur is if you simply copy the files from 
        the installation floppy to the hard disk.  You MUST install 
        System Commander from the diskette so it's files are properly 
        placed on the hard disk and uninstall information is saved onto 
        the diskette.  
        

    E. Technical Support

        If you followed the steps in Chapters 3 and 4, you are unlikely 
        to have any problems.  Chapter 6, Troubleshooting covers some of
        the rare problems which might be encountered.  Seemingly bad 
        problems like "Invalid COMMAND.COM" are usually solved easily, 
        and are described in Chapter 6.  
        
        Technical support is available to registered users for 90 days 
        after purchase.  If you call after this period, please have a 
        credit card ready for a nominal charge per call.  All technical 
        support calls require your serial number and version number, 
        which is found on your diskette label. 

                (408) 296-4385  (Tech support)


    F. Ordering Information

        To purchase additional copies contact us at:
        
                V Communications, Inc.
                4320 Stevens Creek Blvd., Suite 275
                San Jose, CA  95129
                USA

                (408) 296-4224  (Voice)
                (408) 296-4441  (FAX)

        We also offer very attractive volume discounts and multi-site 
        licenses.  Contact our Sales department for additional 
        information. 
                

                     Ŀ
                          End of Notes     
                     
        
