OSL2000 Boot Manager - Documentation

Note: The new "Stealth mode" and "Desktop shortcuts" are very powerful features which let you boot OSs without even using the boot menu! Please read this document about these features before trying them out. You'll find it easier that way.

Frequently Asked Questions

• How can I download the latest version?
  • To download the new version, please click here and follow the instructions.

• How do I install?
  • (1) Please download a fresh copy of OSL2000 boot manager by clicking here. Create a folder in your (C:) drive called "OSL2000". Copy the downloaded file 'osl2000.zip' into that folder (C:\OSL2000) and unzip all the files into the folder using a program like WinZip.
    
    (2) Now, go to that folder (C:\OSL2000) and run 'setup.exe' to install. If you're using DOS, please run 'dosinst.exe' instead. If you do not properly unzip all the files, you will receive an error saying "cabinet file not found". Also, OSL2000 boot manager can be installed anytime (before or after installing the OSs).
    
    (3) If you're experiencing problems during installation, then use the boot floppy method to install. That is, create a boot floppy, copy all the OSL2000 files to that floppy, boot your system using that floppy and run 'dosinst.exe' to install. Most versions of Windows (and DOS) can create a boot floppy very easily.
• Do I have to create an uninstall disk during installation?
  • The uninstall disk is not required in most of the cases. But if your system has special boot-time low-level disk utilities, such as GoBack installed. Or, if your system has disk managers like OnTrack, EZ-Drive, MaxBlast, etc. Or if your system has a RAID array (esp. with stripping). Then you cannot use OSL2000 Boot Manager in one such system.
    
    If you install OSL2000 boot manager in one such system, you might need the emergency disk to roll back to your previous configuration. If you're not sure about your system specs, we suggest that you create an uninstall disk during installation. It doesn't take more than a minute. 
• On which drive or partition should I install OSL2000 boot manager?
  • OSL2000 boot manager does NOT require a partition to install. It always installs itself in the first track of your first hard disk, regardless of how or from where you install. In fact, you don't even need to worry about all these during installation. Just click on the install button and the installer will take care of the rest. 100% automatic.
• I'm getting errors during installation. What shall I do?
  • If you get any of the following errors, then it means that some specific compatibility issue has been detected and installation has failed due to that. For more information about these errors, please read the instructions below:
    
    (1) "Invalid free space in partition detected".
    
    If OSL2000 detects that your hard disk:
    
    (1) Does not conform to the BIOS LBA mode or
    (2) Is not directly supported by your BIOS at boot time or
    (3) Is very old,
    
    Then this error is displayed. If you get this error, you cannot use OSL2000.
    
    (2) "Device not found or responding" or
    (3) "The system cannot find the file specified".
    
    If OSL2000 detects that your primary device in your device chain is not a standard hard disk, you'll get this error. You can reconnect your hardware to eliminate this problem.
    
    If you receive this error, you may still be able to install OSL2000 using the boot floppy method. That is, create a boot floppy, copy all the OSL2000 files to that floppy, boot your system using that floppy and run 'dosinst.exe' to install. Most versions of Windows (and DOS) can create a boot floppy very easily.
    
    (4) "Bad Sector Flag Detected".
    
    If OSL2000 detects that your primary hard disk has errors in it's low-level disk sectors, you'll get this error. Recovering from one such error is beyond the scope of this document. You may also get this error when some anti-virus programs or some low-level disk utilities are running in your system. Disable these type of programs before installing OSL2000.
    
    If you receive this error, you may still be able to install OSL2000 using the boot floppy method. That is, create a boot floppy, copy all the OSL2000 files to that floppy, boot your system using that floppy and run 'dosinst.exe' to install. Most versions of Windows (and DOS) can create a boot floppy very easily.

• How do I uninstall?
  • (1) Please download a fresh copy of OSL2000 boot manager by clicking here. Create a folder in your (C:) drive called "OSL2000". Copy the downloaded file 'osl2000.zip' into that folder (C:\OSL2000) and unzip all the files into the folder using a program like WinZip.
    
    (2) Now, go to that folder (C:\OSL2000) and run 'setup.exe' to uninstall. If you're using DOS, please run 'dosinst.exe' instead. If you do not properly unzip all the files, you will receive an error saying "cabinet file not found". Also, OSL2000 boot manager can be uninstalled anytime.
    
    (3) If you're experiencing problems during uninstallation, then use the boot floppy method to uninstall. That is, create a boot floppy, copy all the OSL2000 files to that floppy, boot your system using that floppy and run 'dosinst.exe' to uninstall. Most versions of Windows (and DOS) can create a boot floppy very easily.
• How do I uninstall without the uninstall disk?
  • The uninstall disk is not required in most of the cases. You have to just follow the standard uninstall procedure as described above. But if your system has special boot-time low-level disk utilities, such as GoBack installed. Or, if your system has disk managers like OnTrack, EZ-Drive, MaxBlast, etc. Then you won't be able to uninstall without the uninstall disk.
• Will I lose any data or partitions during uninstall?
  • Not at all. OSL2000 uses only the first few bytes of the master boot record and the track zero of your primary hard disk. Under no circumstances you will lose any of your OSs or partitions in any of your hard disks or the data inside them.

• How do I register?
  • Registration is fast, secure and easy. All you need is a credit card and a couple of minutes. You can also order by phone, fax, purchase-order or post. To register your copy, please click here. Your order will be processed immediately and the registration codes will sent to you via email. Once you receive the registration code, please do the following to register:
    
    (1) Please download a fresh copy of OSL2000 boot manager by clicking here. Create a folder in your (C:) drive called "OSL2000". Copy the downloaded file 'osl2000.zip' into that folder (C:\OSL2000) and unzip all the files into the folder using a program like WinZip.
    
    (2) Now, go to that folder (C:\OSL2000) and run 'setup.exe' to register. If you're using DOS, please run 'dosinst.exe' instead. If you do not properly unzip all the files, you will receive an error saying "cabinet file not found".
    
    (3) If you're experiencing problems during registration, then use the boot floppy method to install. That is, create a boot floppy, copy all the OSL2000 files to that floppy, boot your system using that floppy and run 'dosinst.exe' to install. Most versions of Windows (and DOS) can create a boot floppy very easily.
• What is the difference between the registered and the unregistered version?
  • The unregistered version has a minor nag screen. No other differences.
• I have lost my registration code. I need a new one. What shall I do?
  • Please click here to contact the helpdesk for a new registration code. Please send us your full name and the email id you used during registration. Or the Order ID you received after registration. Once your order is verified, the new registration codes will be mailed to you at the earliest.
• While I can download OSL2000 boot manager, why can't I get a boxed version?
  • Primarily, the creation of packaging and other materials that are necessary for boxed versions significantly increases the cost of the product and the time to market. Also, the retail channel is not capable of efficiently handling software that has rapid development cycle. Therefore, only the downloadable version is available.

• What are the command-line options available?
  • The command-line options are very useful if you want to automate tasks such as installation, booting, etc. For example, using AutoBoot, you can boot into another OS from the current one by simply clicking on a desktop shortcut or running a batch file. Another example is, you can create a boot floppy or CD which automatically installs OSL2000, and then use that to install OSL2000 on multiple systems very easily.
    
    If you're running Windows, open the command prompt and go to the folder where the OSL2000 files exist (C:\OSL2000), and then type "setup /?" to view the list of options. If you're running DOS, go to the directory where the OSL2000 files exist, and then type "dosinst /?" to view the list of options. The complete list of options are as follows. These options are not case-sensitive.
    
            /?         - Displays the help screen.
            /i          - Install OSL2000 Boot Manager (uninstall disk will not be created).
            /u         - Uninstall OSL2000 Boot Manager (uninstall disk will not be used).
            /bN      - AutoBoot option (where N = 1 to 9).
            /r:code -  Register OSL2000 Boot Manager (where 'code' is the registration code you received from us after registration).
    
    For example, under real-mode DOS, if you type "dosinst /i", dosinst.exe will automatically install OSL2000 on that system. Another example is, under real-mode DOS, if you type "dosinst /b2", dosinst.exe will automatically restart your system and then automatically boot the second entry in the boot menu. "dosinst /b1" will boot the floppy drive, if available.
    
    Note: The AutoBoot option works best with Stealth mode. For more details about Stealth mode & AutoBoot please see the following section.
• How can I create a desktop shortcut (in Windows) to directly boot into another OS?
  • You can create shortcuts in your Windows desktop and boot into another OS by just clicking on a desktop shortcut. The following procedure will help you set up desktop shortcuts using the AutoBoot option to directly boot the OS of your choice:
    
    (1) Please download a fresh copy of OSL2000 boot manager by clicking here. Create a folder in your (C:) drive called "OSL2000". Copy the downloaded file 'osl2000.zip' into that folder (C:\OSL2000) and unzip all the files into it. Now install OSL2000.
    
    (2) Now, right-click on your desktop and select "New"> "Shortcut". Click on the "Browse" button, go to the folder (C:\OSL2000). Select "Setup.exe" and click next. Give it a suitable name and click finish.
    
    (3) Now, right-click on our new desktop shortcut and click properties. In the "Target" box instead of "C:\OSL2000\SETUP.EXE", type "C:\OSL2000\SETUP.EXE /b2".
    
    Note: The command-line AutoBoot option, /b1 will boot the floppy drive, /b2 will boot the second entry in the boot menu, /b3 will boot the third entry, etc. If you have multiple copies of Windows, you need to create one desktop shortcut for each copy. This may sound tedious, but usually you won't require more a few shortcuts (remember, the boot menu is always there for you).
    
    Note: The AutoBoot option works best with Stealth mode. For more details about Stealth mode & AutoBoot please see the following section.
• I use batch files or desktop shortcuts to boot other OSs and I don't need the boot menu. How can I hide it?
  • To hide the boot menu, you have to activate the Stealth mode in the options menu. This mode is very useful when used with the AutoBoot option. Once the Stealth mode is active, the boot menu will not pop up during system startup, but you can still use the desktop shortcuts or batch files to boot other OSs. This way, the Stealth mode lets you manage booting without the boot menu.
    
    Note: The AutoBoot option works best with Stealth mode. For more details about Stealth mode & AutoBoot please see the following section.
• The boot menu does not support passwords. Why?
  • The boot menu does not support passwords. Because it has a much advanced feature called Stealth Mode (with AutoBoot), which you'll find very suitable for your tasks. Also, it has MenuLock to freeze the menu settings (if you still insist on using a boot menu at system startup).
    
    Note: The AutoBoot option works best with Stealth mode. For more details about Stealth mode & AutoBoot please see the following section.

• My boot menu disappeared. What do I do now?
  • Very simple. Reinstall OSL2000 boot manager. While installing some OSs, they tend to disable the boot manager during install.
• How to bypass the boot menu in case it gives trouble?
  • Simple. Just press a shift, ctrl or alt key during system startup to bypass the boot menu.
• When I try to boot WinNT/2K/XP/2003, it fails to boot. Why?
  • This happens when the OS has installed it's boot loader in the wrong partition or hard disk or is corrupt. To correct the situation, please do the following:
    
    Copy the system files (ntldr, ntdetect.com and boot.ini) to the corresponding partition. It will then boot fine. Also, make sure that the file boot.ini is modified only if necessary.
• When I try to boot Win9x/ME/DOS, it fails to boot. Why?
  • This happens when the OS has installed it's boot loader in the wrong partition or hard disk or is corrupt. To correct the situation, please do the following:
    
    Transfer the system files to the corresponding partition using the command 'sys x:' from a bootable floppy. It will then boot fine. Most versions of Win9x, WinME and DOS can create a boot floppy very easily.
• When I try to boot Linux, it fails to boot. Why?
  • It means that GRUB or LILO has not been properly installed. While installing Linux, you have to install GRUB or LILO in the "First sector of boot partition". If it hasn't been done already, then follow these steps:
    
    1. Make a Linux boot disk (using a different computer, for example).
    2. Boot Linux using the Linux boot disk.
    3. Now, install GRUB or LILO (for more details, please read the Linux man pages).
    4. If your copy of Linux uses LILO, then it has to be configured properly.
    
    To configure LILO, please see Installing Linux in Multi OS installation Guide.
• How can I boot from my CD or DVD device (ATAPI, USB, FireWire, etc.)?
  • OSL2000 can boot most bootable devices provided it is recognized by your system BIOS at boot time. Whenever you select "CD-Rom" from the OSL2000 boot menu, it tries to boot the "second" boot device selected in your system BIOS. So, to boot your CD or DVD device, select that device as the second boot device. Once selected, you can directly boot your device from the OSL2000 boot menu by selecting "CD-Rom".
    
    Note: If you select some other device as the second boot device in your system BIOS, the boot menu will boot that device instead.
• How can I boot from my hardware device (ATA, USB, FireWire, ZIP, etc.)?
  • OSL2000 can boot most bootable devices provided it is recognized by your system BIOS at boot time. To check whether your system BIOS supports booting from your device, do the following:
    
    (1) Connect your device and start Windows (or DOS).
    (2) If the device requires initialization (like partitioning, formatting, etc.), then do it.
    (3) Install OSL2000 and restart your system.
    
    Note: If the device appears in the boot menu, then OSL2000 can boot that device. If you're experiencing problems, then please try the following:
    
    (1) In some systems, the BIOS support for booting some devices is disabled by default. If you have one such system, then you have to enter the BIOS setup during startup and manually enable the option to boot from the device.
    
    (2) Sometimes, the boot menu might recognize your hardware device as a hard disk. This is a cosmetic issue and can be safely ignored.
    
    (3) Whenever you select "CD-Rom" from the OSL2000 boot menu, it tries to boot the "second" boot device selected in your system BIOS. So, if you select your device as the second boot device in your system BIOS, you can boot your device directly from the OSL2000 boot menu by selecting "CD-Rom".

• What is 'debug.log'?
  • It's a complete record of OSL2000 boot manager's internal activity. This file has information we need to locate the source of the problem (if any). This file gets generated every time you run the OSL2000 installer ('setup.exe' or 'dosinst.exe').
• What are these 'mbr.sav' & 'image.sav' files?
  • Once you install OSL2000 boot manager, the installer saves the required uninstall info in these files. These files are used by the uninstaller during the uninstall process to give you a perfect rollback. So, don't delete them until you're sure that you don't need them.
• What is 'outline.js'?
  • It is a companion file for the HTML documentation. It is required for the HTML document to work properly.

List of Features

• [F6] key - Special Boot Modes
  • You can press the [F6] key to enable the SWAP mode. You have to enable the SWAP mode for some OSs to boot from the second (or higher) hard disk. OSs in the first hard disk do not require the SWAP mode.
    
    Windows (all versions) and DOS are not fully compatible with SWAP mode. So, they always use the advanced AUTO mode to boot from second (or higher) higher hard disk. This is set by default and cannot be modified.
• [F8] key - Manual Hiding
  • You can press the [F8] key to manually hide or unhide selected Windows and DOS partitions in your system. Manual hiding is required only under rare circumstances, when you have to manually administer specific changes to select partitions. It is usually not required in most of the cases.
    
    Remember, when you enable the AutoHide feature in the options menu, manual hiding gets disabled automatically. To use manual hiding, the AutoHide feature should be disabled.

• AutoBoot

  • This is a very powerful option which lets you boot into different OSs automatically from the current OS itself (i.e. without using the boot menu). For example, it lets you boot into another copy of Windows from the current one by clicking on a desktop shortcut or by running a batch file. This option becomes very important when it comes to running unattended jobs or remote maintenance, such as restoring images for regular system maintenance, etc.
    
    The AutoBoot option works best with Stealth mode. Also note that the AutoBoot option will automatically restart your system and then automatically boot the boot menu entry you had specified. So, close all applications before using this option. To use this option, Windows users should run "setup.exe" with the required command-line options. DOS users should instead run "dosinst.exe" with the required command-line options.
    
    The details of the AutoBoot command-line options "/b" are as follows:
        /b1 will boot the first boot menu entry (Floppy),
        /b2 will boot the second boot menu entry and so on...
    
    Once you enable the 'Stealth mode', it hides the boot menu during system startup and you can pop-up the boot menu when needed. When the AutoBoot option is enabled, the Self-Timer and the default OS settings are not required and hence ignored.
    
    Note: For more information please see Self-Timer, Stealth Mode & Set Default OS in this section.

• Stealth Mode

  • This is a very powerful feature which lets you hide the boot menu. If you want to hide the boot menu during system startup, you can enable the Stealth mode in the options menu. This feature is very useful when used in combination with the AutoBoot mode.
    
    Once you enable this feature, the system will not pop-up the boot menu during system startup. But during system startup, the boot menu will actually wait for one second before starting the OS. During this period, you can press any key to pop-up the boot menu. Once the boot menu pops-up, you can do all the normal menu operations.
    
    After one second (if no key has been pressed), the boot menu automatically boots the default OS. If a default OS is not set, it boots the last booted OS.
    
    When Stealth mode is enabled, the Self-Timer is not required and hence ignored. When both AutoBoot and Stealth mode are enabled, the boot menu is not popped-up and it does not wait at all. It just directly boots the parameter specified by the AutoBoot option.
    
    Note: For more information please see AutoBoot, Self-Timer & Set Default OS in this section.

• Self-Timer

  • The Self-Timer is very useful to automatically boot the system after a fixed delay. The delay can be varied between 1 to 99 seconds. The Self-Timer automatically boots the default OS. If a default OS is not set, it boots the last booted OS. Set the value to ZERO to disable the Self-Timer.
    
    When AutoBoot mode or Stealth mode is enabled, the Self-Timer is not required and hence ignored by the boot menu during system startup.
    
    Note: For more information please see AutoBoot, Stealth Mode & Set Default OS in this section.

• Set Default OS

  • This feature is very useful when used with the Self-Timer or the Stealth mode. The default OS can be set in the boot menu by pressing (Ctrl+F2). The default OS setting can be cancelled in the boot menu by pressing (Alt+F2).
    
    When AutoBoot is enabled, this feature is not required and hence ignored.
    
    Note: For more information please see AutoBoot, Self-Timer & Stealth Mode in this section.

• AutoHide

  • This is a very powerful feature which lets you have multiple independent copies of Windows in your system. Normally, when you boot into Windows or DOS, you will be able to access all other Windows and DOS partitions in your system. With AutoHide enabled, all copies of Windows and DOS in your system will be completely hidden from each other.
    
    Note: When you boot Windows or DOS from a primary partition (any hard disk), this feature hides all other partitions except logical partitions. So, even with this feature enabled, you can still use your logical partitions to store and share common programs and data. But, when you boot Windows or DOS from a logical partition (any hard disk), the AutoHide feature hides all other partitions including logical partitions.
    
    When you enable the AutoHide feature in the options menu, manual hiding gets disabled automatically. To use manual hiding, the AutoHide feature should be disabled.

• Show All Partitions
  • This is a cosmetic feature and it is disabled by default to avoid confusion for the beginners. Some partitions like the Linux swap partitions, cannot be booted. Even if you try to boot them, they still won't boot because they are not bootable partitions. So, to avoid confusion, unnecessary partitions are not displayed in the boot menu.
    
    To display all the partitions in the boot menu, enable the "Show All Partitions" feature in the options menu.
• CD Alternate Boot
  • This is a very powerful feature which lets you boot CD-ROMs. By default, OSL2000 uses the alternate boot mode (an advanced boot mode) to boot CD-ROMs. But, some systems do not support this mode. In these cases, you'll have to use the "Standard Boot" mode. If you disable the alternate boot mode in the options menu, the standard boot mode will be selected automatically.

• MenuLock

  • This feature is useful for protecting the boot menu settings. Once you customize the boot menu, you can enable the MenuLock feature to preserve the setting from accidental modifications. Once the MenuLock is on, the boot menu options such as the timer menu, options menu, edit menu, etc are hidden and disabled.
    
    Press (Ctrl+F3) to enable the MenuLock. Press (Alt+F3) to disable the MenuLock.

• AutoScan

  • This is a built-in feature. This feature automatically configures the boot menu. It can automatically detect new operating systems when they are added or removed. Without this feature, users will be forced to manually go thru a series of complex configuration screens in order to get the boot manager working.

• AutoSense

  • This is a built-in feature. This feature automatically senses what OS is installed in the current boot partition and automatically configures the boot engine before loading the OS. Without this feature, users will be forced to manually go thru a series of complex configuration screens in order to get the boot manager working.

• SafeBoot

  • This is a built-in feature. This feature increases the stability of the system. Some operating systems like Windows and DOS has a habit of writing to the master boot record during installation thereby disabling the boot manager. So, even if the master boot record gets overwritten or if some other program disturbs the integrity of the boot manager, SafeBoot will still boot your system.

Multi OS Installation Guide

• Can I have 100 copies of Windows in my system?
  • Yes, you can. Most OSs can be directly booted from a logical partition. So, you can keep multiple copies of these OSs in a single hard disk. For example, you can have 1 copy in a primary partition and 99 copies in separate logical partitions.
• Multi OS Installation - A simple step-by-step procedure (read this first)
  • The following procedure will help you install multiple OSs in your system.
    
    (1) Read the "known multi boot issues" section (see below).
    (2) Decide what all OSs you want to install in your system.
    (3) Choose partition type, size and file system based on the OSs.
    (4) Create all the partitions (for your partitioning needs, click here to download a free partition manager).
    (5) Install the OSs.
    (6) Install OSL2000 boot manager.
    
    That's all.
    
    Important: Please note that before installing an OS in a primary partition in the first hard disk, mark it as active, reboot the system and then install the OS. If you fail to do it, the OS might install it's boot loader in the wrong partition, which is highly undesirable. To install OSs in logical partitions or the second hard disk, please read the sections below.
• Known multi boot issues and possible workarounds
  • If you're installing old OSs along with newer ones, Or if you're installing old OSs in a new hard disk, you should make sure that you meet the following conditions for the old OSs to work properly.
    
    (1) Most versions of DOS and some old versions of Windows (released before 98SE) won't boot, if their primary partition is not completely below the first 2GB or the first 8GB mark.
    
    (2) If you're installing 2K or XP on a system running NT4 on NTFS without NT4 Service Pack 4 (SP4) installed, NT4 will fail to boot after you finish installing 2K or XP. This is because, 2K or XP silently upgrades NTFS4 to NTFS5 without any intervention. To solve this problem, you have to install SP4 in NT4 before installing 2K or XP. You will not receive this problem, if you're running NT4 on FAT16.
    
    (3) Some old versions of Linux won't boot, if it's root partition is not completely below the first 8GB. Since Linux has plenty of flavors, we cannot specify the versions with this problem. You have to test it by yourself. The new versions do not have this problem.
    
    (4)  The last logical drive in any extended partition must be a FAT partition for some old versions of Windows and DOS to work properly. Remember, in this case, you can always use a logical FAT partition to store common data.
• Installing multiple copies of WinNT/2K/XP/2003 in any partition or any hard disk
  • There are many ways to install multiple copies of WinNT/2K/XP/2003 in any partition or any hard disk. The first two methods are easy to use but they require the use of the undocumented 'registry fix' option. The third method is safe, but is a bit time consuming.
    
    Warning: The 'registry fix' option is an undocumented option and is not supported by us. Use it at your own risk. It may stop your system from booting or may cause data loss. We noticed that this option caused problems in some systems if the Windows files are not in the 'C:\Windows' folder. So, we strongly suggest that you backup your system before using this option. To apply the registry fix, please run the OSL2000 setup program 'setup.exe' with the command-line option '/x'.
    
    Primary method is, first install the OS in the primary hard disk and boot into it. Now, apply the registry fix, quick format the desired partition and copy all the files into it (swap file is not necessary). If you do not format, it will not boot. You can copy the files to any partition in any hard disk. It can even be a logical partition. After copying files, please update the boot.ini 'partition' setting. Finally, install OSL2000 and you should be able to boot all the partitions directly.
    
    Second method is, use a disk imaging utility like Norton Ghost or Power Quest Drive Image. First, install the OS in the primary hard disk and boot into it. Now, apply the registry fix and then create an image of that partition. Now you can restore the image into any number of partitions in any hard disk. It can even be a logical partition. After restoring images, please update the boot.ini 'partition' setting. Finally, install OSL2000 and you should be able to boot all the partitions directly.
    
    Third method is, if you have multiple hard disks, connect the desired hard disk as the primary master. Create the partitions and manually install each OS. Then, connect the hard disks back the way they were before. Finally, install OSL2000 and you should be able to boot all the partitions directly. Remember, before installing each OS, it is important that you mark that partition as active. Using this method, you can install OSs only in primary partitions.
• Installing multiple copies of Win9x/ME/DOS in any partition or any hard disk
  • There are many easy ways to install multiple copies of Win9x/ME/DOS in any partition or any hard disk.
    
    Primary method is, first install the OS in the primary hard disk. Copy all the files (swap file is not necessary) to any partition in any hard disk. It can even be a logical partition. Run the command "sys x:" to transfer the system files to that partition, where x: is the drive letter of that partition. Finally, install OSL2000 and you should be able to boot all the partitions directly.
    
    Second method is, use a disk imaging utility like Norton Ghost or Power Quest Drive Image. First install the OS in the primary hard disk. Create an image of that partition. Then, restore it into any number of partitions in any hard disk. It can even be a logical partition. Finally, install OSL2000 and you should be able to boot all the partitions directly.
    
    Third method is, if you have multiple hard disks, connect the desired hard disk as the primary master. Create the partitions and manually install each OS. Then, connect the hard disks back the way they were before. Finally, install OSL2000 and you should be able to boot all the partitions directly. Remember, before installing each OS, it is important that you mark that partition as active. Using this method, you can install OSs only in primary partitions.
• Installing multiple copies of Linux in logical partitions and second hard disk
  • Linux can be easily installed in logical partitions and second hard disk using the Linux distribution itself.
    
    While installing Linux, for each copy, you have to install GRUB or LILO in the "First sector of boot partition". If your copy of Linux uses LILO, then it should be configured as follows. A standard 'lilo.conf' is shown below. All you need to do is, simply replace the value marked in red with the value marked in green. Also, if you remove the 'prompt' & 'timeout=nn' lines, it will speed up the boot process.
    
        ---start-of-file------------
        boot=/dev/hda
        map=/boot/map
        install=/boot/boot.b
        image=/boot/vmlinuz-2.2.5-15
        label=Linux
        root=/dev/hdb3
        read-only
        ---end-of-file--------------
    
    After modification, run LILO by typing 'lilo' (upon successful completion, LILO should say '*Added Linux'). Then, restart your system and then install OSL2000 boot manager (if not already installed).

• Adding, deleting and modifying partitions
  • To add, delete or modify partitions or to create multiple primary partitions, you'll require a advanced partition manager. Most of the OSs like Linux and Windows have their own built-in basic partitioning tools. For your partitioning needs, please click here to download a free advanced partition manager.

Knowledge Base

• Increasing your system's boot speed
  • Modify your BIOS settings (boot sequence) as follows:
    
    First boot device = First hard disk
    Second boot device = CD drive or DVD drive
    Third boot device = Floppy drive
    
    You will get the following benefits only if you modify your BIOS settings as shown above. Once you update your BIOS settings:
    
    (1) You will be able to boot your CD-ROMS directly from the OSL2000 boot menu.
    (2) Prevent boot sector infections that are caused by accidentally booting from an infected floppy.
    (3) Your system will boot faster because it will skip other devices and directly boot your hard disk.
    
    Note that, modifying BIOS settings is a delicate task and requires some level of expertise. Be careful while modifying your BIOS settings. DO NOT modify those settings that you don't understand.
• Some known compatibility issues
  • The compatibility issues mentioned below are rare and does not affect most of the people. But, if your system meets any of the following conditions, then we suggest that you first test the required configuration in a test-bed system before deploying it in main-stream systems. In most of the cases, an uninstall disk will be helpful. List of known compatibility issues:
    
    (1) OSL2000 is not completely compatible with some RAID configurations (esp. stripping). If your system is a RAID server with a multiple hard disk array, please backup all critical data before installation. Warning: Multi-booting a system with a RAID stripping array is a very delicate task and should be handled very carefully.
    
    (2) If your system has special boot-time low-level disk utilities, such as GoBack installed. Or, if your system has disk managers like OnTrack, EZ-Drive, MaxBlast, etc. Then you won't be able to use OSL2000.
    
    (3) OSL2000 might fail to hide some partitions in specific configurations when you boot into Win2000. This is due to a minor compatibility issue between the AutoHide feature and Win2000's Disk Management Service. After booting into Win2000, you can still hide partitions by using Disk Management in Administrative Tools. That is, right-click on the drive letter, choose "Change Drive Letter" and click on "remove". This issue does not affect other versions of Windows.
• Running games at maximum speed
  • Disclaimer: We have obtained the following information after extensive analysis. But, we cannot guarantee it's accuracy. Before continuing, please note that these are strictly our views and might not accurately reflect the performances of any of the products or services mentioned below. We make no warranties, express or implied, as to the information in this document. Nor do we assume any liability for damages, direct or consequential, that may arise from the use this information. Use it at your own risk.
    
    Having read the disclaimer, we'll now continue with our little analysis. The best operating system for playing games as of now is Windows XP. Also, it is very important to have a separate gaming OS for maximum performance. The reasons are as follows:
    
    (1) Has terrific hardware support (lot better than its predecessors).
    (2) The Most stable OS in the Windows line of products.
    (3) Newer games run faster (with the latest DirectX installed).
    (4) Most new games don't work well with previous versions of Windows.
    
    To get the most out of your gaming OS, follow the steps exactly as mentioned below:
    
    (1) Create a FAT32 partition and Format it.
    (2) Install Windows in that partition.
    (3) Install the hardware drivers and then DirectX.
    (4) Turn off Virtual memory and restart your system.
    (5) Defrag the partition using the Windows disk defragmenter.
    (6) Turn virtual memory on and select "Let me specify my own settings".
    (7) Set both the values at 1024 MB and restart your system.
    
    End of procedure. Now, install the games and have fun.
    
    To get the best performance, install ONLY those drivers that are absolutely necessary for playing games. Do not install device drivers for devices like Modems, Camera, TV Tuner, Printer, Network, Infrared, etc. You will not need any of these devices while playing games. Also, your system speed and stability decreases as you add more device drivers. Think twice before installing a device driver.
    
    Please make sure that you DO NOT install any unwanted applications as every single application you install decreases the performance and stability of the system. Also, after a couple of months, if you feel that your gaming OS performance has gone down, simply format the partition and start all over again from step (1).
    
    Happy gaming.

Glossary

• Sector
  • A sector is the smallest unit of data that can be read or written to the hard disk. A sector is typically 512 bytes in size. And each hard disk (and floppy) is made up of plenty of sectors. A 10GB hard disk will typically have a little more than 20 million sectors. There are two ways to read and write sectors. The old CHS mode and the latest LBA mode.
• Master Boot Record
  • The master boot record resides in the first sector of the first hard disk. During system startup, the master boot record first receives control and then boots the default operating system. Once the master boot record receives control, it actually loads the desired partition's boot record and transfers control to it. Once the control is transferred, the master boot record no longer resides in memory. The boot record then loads the kernel (or equivalent) into memory and transfers control to it.
• Partition Table
  • The partition table is located in the first sector of each hard disk. The partition table has important information about the partitions in that hard disk. To edit the partition table, you can use tools like fdisk, Ranish, DiskEdit, etc. For your partitioning needs, please click here to download a free advanced partition manager. Before modifying the partition table, make sure you know what you're doing. A wrong move might destroy all the data in that hard disk.
• Partition
  • In order to share the hard disk among operating systems, the hard disk may be divided into partitions. The partition information is kept in the partition table. Each partition may contain a boot record on its first sector (to load the kernel) and a file system to store the operating system and user information. Due to a limitation in the partition table itself, each hard disk can have a maximum of only 4 primary partitions OR 3 primary partitions and one extended partition. Extended partition can store many logical partitions inside them. For your partitioning needs, please click here to download a free advanced partition manager.
• Normal Boot Sequence
  • 1. The system bios first attempts to load the operating system from diskette drive A. If the drive is not ready or a read error occurs, it then attempts to read the master boot record from the hard disk. If unsuccessful, it displays a disk error message on most systems. If the read succeeds, the system then transfers control to the maser boot record.
    
    2. If the boot flag in not present in the primary partition table, or if more than one indicator (or none) is marked as bootable, the message INVALID PARTITION TABLE is displayed and the system stops.
    
    3. The master boot record then examines the partition table embedded within it. If one of the entries indicate an active (bootable) partition, it's boot record is read from that partition's first sector. If unsuccessful the message ERROR LOADING OPERATING SYSTEM appears and the system stops. If the partition's boot record does not contain a valid "signature", the message MISSING OPERATING SYSTEM appears, and the system stops.
    
    5. The partition's boot record is then given control which in turn loads the rest of the operating system.
• Boot Manager
  • A boot manager is a software that helps the user boot the operating system of his/her choice. Let us say you have WinME, WinXP and Linux in your system. When you start your system, the boot manager will present you with a list of OSs in the system and let you choose which ever you want. Boot managers, like OSL2000 boot manager, will let you have multiple copies of Windows or DOS. It will let you boot windows even from your second hard disk and logical partitions.
• The 8 GB Barrier
  • OSL2000 boot manager can boot OSs even beyond the 8GB barrier. Older BIOS that do not support the new LBA disk addressing mode, uses the old CHS mode. So, if your BIOS does not support the LBA mode and you're hard disk is more that 8GB in size, you'll not be able to boot OSs that reside in partitions that are after the 8GB mark. To correct this issue, the BIOS or the PC should be upgraded.

If you can't find the answers you're looking for or if you have any suggestions/opinions or if you need further assistance,
please click here to contact the helpdesk. We're eager to help you.