
                           Frequently Asked Questions
                  Copyright (c) 1997 - 2000 Vijai K. Amarnath
                              All rights reserved.

    <Hint: You can directly locate the answers using the question number. >
    <Hint: To learn more about the boot menu, use it's online help system.>
    <Hint: You can always contact the author at "feedback@osloader.com".  >

*******************************************************************************

                                   Questions
                                   ~~~~~~~~~
*******************************************************************************

[A] Installing OSL2000
~~~~~~~~~~~~~~~~~~~~~~
Q01: If you have trouble installing OSL2000, check these first...
Q02: OSL2000 says, "Executable has been damaged". Why?
Q03: OSL2000 failed to detect device(s)/drive(s). Why?
Q04: I get an error message saying "Write protect error writing drive...". Why?
Q05: I get an error message saying "Abort, retry, fail?". Why?
Q06: I get an error message saying "Couldn't install bootmenu image". Why?
Q07: I get an error message saying "Couldn't install new mbr". Why?
Q08: I get an error message saying "Installation check failed". Why?
Q09: Why can't i install OSL2000 from a DOS box in windows?
Q10: I can't understand some of the error messages. What shall i do?

[B] Boot menu fails to pop-up
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q21: I installed Windows and my boot menu vanished. What do i do now?
Q22: I installed Linux and LILO replaced my boot menu. Why?

[C] Boot menu works fine but...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q31: If you're having trouble with the boot menu, try this first...
Q32: I have trouble booting DOS from my second harddisk. Why?
Q33: Boot menu says 'This device/partition doesn't support hiding'. Why?
Q34: Boot menu says 'This partition has been blocked from booting'. Why?
Q35: When I click on my NTFS partition, OSL2000 fails to boot WinNT. Why?
Q36: OSL2000 fails to boot Linux. Why?
Q37: How can i make OSL2000 recognize my CD-ROM drive?

[D] More about the boot menu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q41: What is Partition hiding? Do i need it?
Q42: How do I hide/unhide extended partitions or logical drives?
Q43: OSL2000 does not support passwords. What gives?
Q44: How do i permanently hide/unhide certain partitions?
Q45: How do i set/clear a fixed default boot partition?
Q46: Why did you remove the wallpaper?
Q47: Why can't i hide/unhide from the simple menu?

[E] Uninstalling OSL2000
~~~~~~~~~~~~~~~~~~~~~~~~
Q51: OSL2000 says that it has been partially uninstalled. Why?
Q52: OSL2000 says that it does not exist. Why?
Q53: How do i uninstall OSL2000 manually?

[F] More about OSL2000
~~~~~~~~~~~~~~~~~~~~~~
Q61: What the hell is 'debug.log'?
Q62: What are these 'mbr.sav' & 'image.sav' in the OSL2000 directory?
Q63: What is 'osl2000.sys' in my root directory?
Q64: What is this 8 GB barrier?

*******************************************************************************

                                    Answers
                                    ~~~~~~~
*******************************************************************************

Q01: If you have trouble installing OSL2000, check these first...

ANS: If boot sector virus protection is on, installation might fail. So,
     disable bios boot sector virus protection before installation.

     If your system is infected by a boot virus, installation might fail. So,
     remove all viruses before installation.

     Do not install from a DOS box inside windows. Instead, restart windows
     in MS-DOS mode and then install.

     Do not use disk cache like smartdrv. Cos, write buffering can cause
     trouble sometimes. To disable write buffering, type 'SMARTDRV /X'.

     If you have OSL2000 in a CD-ROM, copy it into your harddisk (or a floppy) 
     and then install it.

     If you're installing OSL2000 from a floppy, make sure the floppy's
     write-protection is off.

     Finally, if you want to know the exact problem, you can look it up in the
     log file 'debug.log' (usually in the last few lines).

     And remember, you can always contact me for help.

*******************************************************************************

Q02: OSL2000 says, "Executable has been damaged". Why?

ANS: Maybe the download was not completed properly or the executable is
     infected or corrupted.

        (1) Delete the executable.
        (2) Check your system for virus(es).
        (3) Get a fresh copy and install it.

*******************************************************************************

Q03: OSL2000 failed to detect device(s)/drive(s). Why?

ANS: Oops. This is the toughest problem i've been facing for sometime. You get
     this error if you don't have enough free space between your partitions
     and if you don't have any FAT partitions. To install OSL2000, you'll need
     some free space between partitions or *atleast* you should have one FAT
     partition in your system.

     Also, make sure your FAT partition meets the following demands:
         1. does not have any errors,
         2. is not hidden,
         3. is not write protected and
         4. is completely *below* the 8GB mark.

     If you have a FAT partition and you still get this error, send me a copy
     of your 'debug.log' to <feedback@osloader.com>. I'll *then* be able to
     find a way out.

*******************************************************************************

Q04: I get an error message saying "Write protect error writing drive...". Why?

ANS: Do not run OSL2000 from a read-only media (like CD-ROM, write protected
     floppy, etc.). The installer always saves the install log and the
     uninstall info in the current directory. If you run OSL2000 from a read-
     only media, these files will not be saved. So, make sure the media is not
     read-only.

*******************************************************************************

Q05: I get an error message saying "Abory, retry, fail?". Why?

ANS: It's a harmless error message generated by the installer. Actually, when
     OSL2000 scans some unformatted partitions or your CD-ROM drive which is
     empty, you get this message. When you get this message, press 'f' to skip
     it. The installer will take care of the rest.

*******************************************************************************

Q06: I get an error message saying "Couldn't install bootmenu image". Why?

ANS: First, make sure you meet all the requirements listed in question [3].

     Try deleting 'osl2000.sys' in the root directory of *ALL* the drives.
     Including all the hidden FAT partitions (if you have any). This is to
     ensure that multiple installations of OSL2000's does not interfere with
     each other. Once you finish deleting *ALL* the copies of 'osl2000.sys',
     install OSL2000.

     If you still get this error, contact me at <feedback@osloader.com>. I'll
     then be able to find a solution for you. And please attach a copy of your
     'debug.log' with it.

*******************************************************************************

Q07: I get an error message saying "Couldn't install new mbr". Why?

ANS: Some possible solutions are:

       1. Disable boot sector virus protection.
       2. Check for boot sector virus(es).
       3. Run disk utils like Norton Disk Doctor.
          to check your partition table.

*******************************************************************************

Q08: I get an error message saying "Installation check failed". Why?

ANS: This error occurs only under some strange conditions. Conditions that
     are usually too extreme to be considered. Fortunately, this error can be
     handled under most circumstances.

     First, follow the instructions in question [3] and [6].

     If you still get this error, please send me a mail with some details
     that you feel is necessary and a copy of your 'debug.log' to
     <feedback@osloader.com>. I'll send you a fix as soon as possible.

*******************************************************************************

Q09: Why can't i install OSL2000 from a DOS box in windows?

ANS: The installer uses two types of disk access. DOS style file i/o and
     direct disk i/o. The problem is that the former is buffered and the later
     is not. This makes the former invisible to the later and thus makes the
     later think that the former has failed when it hasn't (race condition).
     Thus installation fails. God only knows why windows buffers one and not
     the other!!! AskBill...

     So, restart windows in MS-DOS mode and then install OSL2000. Do not use
     disk cache like smartdrv (especially with write buffering on). See Q01.

*******************************************************************************

Q10: I can't understand some of the error messages. What shall i do?

ANS: During installation if you can't diagnose the error messages, mail me
     a copy of 'debug.log' with your system details. I'll get back to you
     as soon as possible.

*******************************************************************************

Q21: I installed Windows and my boot menu vanished. What do i do now?

ANS: Very simple. Reinstall OSL2000.

*******************************************************************************

Q22: I installed Linux and LILO replaced my boot menu. Why?

ANS: While installing Linux, install LILO in the partition's boot sector 
     (superblock). And, then install OSL2000. To do that refer 'guide.txt'.

*******************************************************************************

Q31: If you're having trouble with the boot menu, try this first...

ANS: In the options menu, click the 'Reset' button. This will completely reset
     the boot menu. Now, try using the boot menu. If it still gives you any
     trouble, read further.

*******************************************************************************

Q32: I have trouble booting DOS from my second harddisk. Why?

ANS: 1. Make sure Partition hiding is ON.
     2. Make sure Autofix Boot Sector is ON.
     3. If the boot menu asks you whether to fix the boot sector bug, say OK.

     Still if it doesn't boot, try transferring the DOS system files again.

*******************************************************************************

Q33: Boot menu says 'This device/partition doesn't support hiding'. Why?

ANS: You can hide/unhide only harddisk primary partitions. Floppy drives and
     Extended partitions (logical drives) cannot be hidden. You can use the
     logical drives to store common/system-wide data such as your documents,
     spreadsheets, source codes, mp3, mpg, jpg, games, backups, etc.

*******************************************************************************

Q34: Boot menu says 'This partition has been blocked from booting'. Why?

ANS: Some partitions like extended partitions (logical drives), linux
     partitions, swap partitions, etc do no need hiding. If you hide them they
     might not function properly. To avoid this situation, OSL2000 blocks all
     the partitions from hiding except those that require hiding.

     In the options menu, you can unblock all partitions. By doing this you'll
     be able to hide/unhide *ALL* partitions. So, before doing this, make sure
     you know what you're doing.

*******************************************************************************

Q35: When I click on my NTFS partition, OSL2000 fails to boot WinNT. Why?

ANS: That's because, NT has installed it's boot loader in some other partition.
     The only way out is, BEFORE installing NT, hide all FAT partitions (except
     the one in which you want to install NT). As of now, i'm not aware of any
     ways of relocating NT's boot loader. Better ask Bill...

*******************************************************************************

Q36: OSL2000 fails to boot Linux. Why?

ANS: You haven't installed LILO in the beginning of that linux partition. To do
     that follow these steps.

     1. Make a linux boot disk (using your friend's computer, for example).
     2. Boot your linux using that disk.
     3. To install LILO, follow the steps in 'guide.txt'.

*******************************************************************************

Q37: How can i make OSL2000 recognize my CD-ROM drive?

ANS: No. As of now OSL2000 will not recognize your CD-ROM drive. I'm planning
     to add CD-ROM detection in the next release.

*******************************************************************************

Q41: What is Partition hiding? Do i need it?

ANS: If you want to install a combination of DOS,Win95/98/NT, or multiple
     copies of any of these, you'll be better of with partition hiding. Hiding
     always leaves one primary partition open & hides the rest. Partition
     hiding does not hide extended partitions (logical drives).

     Let us assume you have 2 primary partitions and you have a copy of Win98
     in each partition. With FAT hiding ON, whenever you start one copy of
     Win98, the other copy will be hidden from its view. Therefore, each copy
     will think, it's the only one that exists in the system.

*******************************************************************************

Q42: How do I hide/unhide extended partitions or logical drives?

ANS: No. Logical drives don't support hiding/unhiding.

*******************************************************************************

Q43: OSL2000 does not support passwords. What gives?

ANS: The main problem with passwords is, we'll be requiring (say) 8 bytes per
     partition and around 1K for the code. As of now, the boot menu has almost
     touched it's physical limits. Once i find a way out, i'll add this
     feature.

*******************************************************************************

Q44: How do i permanently hide/unhide certain partitions?

ANS: This option has still not been implemented. I'm planning to put this in
     the next version. Until then the only way out is turn partition hiding
     OFF and do the hiding stuff manually. A little practise is all you need.

*******************************************************************************

Q45: How do i set/clear a fixed default boot partition?

ANS: In the main menu, keep the cursor over a partition and then press
     <CTRL>+<F2> to set it as the default boot partition. You should then
     see a small green indicator.

     To clear a default boot partition, press <ALT>+<F2> in the main menu.
     Once you do that, the green indicator should then disappear.

     If the default boot partition is not set. OSL2000 chooses the last boot
     partition as the default boot partition.

*******************************************************************************

Q46: Why did you remove the wall paper?

ANS: OSL2000 looks a lot better now. Also it lets you see what's there in the
     boot up screen. Alternatively, you can press <ALT>+<F5> to see the entire
     screen (from the main menu).

*******************************************************************************

Q47: Why can't i hide/unhide from the simple menu?

ANS: Very simple. You'll not know which partitions are open or hidden. If you
     have a simple configuration like linux and win98 in your system, you can
     directly use the simple menu. If you have a complex configuration like
     mine, better start using the advanced menu.

*******************************************************************************

Q51: OSL2000 says that it has been partially uninstalled. Why?

ANS: The possible reasons are

     1. You didn't uninstall OSL2000 from the same drive/directory from where
        you installed OSL2000.

     2. The uninstall files 'mbr.sav' & 'image.sav' are missing.

     3. Some unknown errors occurred during the uninstall process.

     The solutions is

     1. Uninstall OSL2000 from the same drive/directory from where you
        installed OSL2000.

     2. Try a manual uninstall (see below).

     3. Send an e-mail to feedback@osloader.com with your system details
        and the file 'debug.log'. I'll send you further instructions, if
        required.

*******************************************************************************

Q52: OSL2000 uninstaller says that it does not exist. Why?

ANS: Hmmm... *ANY* software you install can be uninstalled only once!!!

*******************************************************************************

Q53: How do i uninstall OSL2000 manually?

ANS: 1. Run `OSL2000' and press 'U'. This will unhide all hidden partitions.

     2. Type 'FDISK /MBR' at the DOS prompt to restore the master boot record.

     3. Finally, run fdisk and set the boot flag (your choice).

*******************************************************************************

Q61: What the hell is 'debug.log'?

ANS: It's a complete dump of your system's devices & what OSL2000 has done.
     Everytime you run OSL2000, it automatically generates this file. If you
     are planning to submit a bug report, don't forget to attach this file
     with it.

     Sometimes you'll be able to pin point the actual problem by looking at
     the last few lines of this file. I use the same approach.

*******************************************************************************

Q62: What are these 'mbr.sav' & 'image.sav' in the OSL2000 directory?

ANS: Once you install OSL2000, the installer saves all the required uninstall
     info in the current directory. These files are used by the uninstaller
     during the uninstall process. So, don't delete them until you're sure you
     don't want them!

*******************************************************************************

Q63: What is 'osl2000.sys' in my root directory?

ANS: This is the boot menu image that is loaded by the primary loader during
     system startup. This is a static file. If it is modified or moved or
     deleted, the system will boot properly, but the boot menu will fail to
     pop-up. So, better don't touch this file. If the boot menu fails to
     pop-up, re-install OSL2000.

*******************************************************************************

Q64: What is this 8 GB barrier?

ANS: OSL2000 uses the BIOS int 13h for all disk i/o. The sad part is, this
     method doesn't let you access more than 8 GB of your harddisk space.
     Although the new extensions can take you beyond this barrier, it's not
     available in many BIOSes during the boot time. If you have any possible
     solutions, please let me know. I'll never forget this help.

*******************************************************************************

                            ^..^ Happy Booting ^..^

*******************************************************************************
