On Thu, Jan 10, 2002 at 04:59:20AM -0000, Vandana  Sudheer wrote:
> 
> In my system I have Win98, Win 2000 Server and Redhat 7.1. 
> I use LILO to boot. But today when I tried to start Win 98 
> from boot menu it rejected to start  Win 98 with a message 
> saying
> 
> I/O Error
> multi(0)disk(0)rdisk(0)partition
> 
> I am able to start Redhat and Windows 2000.
> 
---end quoted text---

Vandana,

   It is my personal view, that LILO (though very much the
default loader for Linux), is not very hot in handling the
multi-OS scene. The preferred  multi-booter to my  experi-
ence should belong to the OS which is placed at /dev/hda1.
It ovecomes the large-drive/ EDO support in  BIOS problems
(1024-voodoo), and the purpose is also achieved.

   Though Linux is very gracious, M$ is rather possessive
about the MBR, and NT/ 2k/ XP/ 9x disk managers  may com-
plain or even "correct" MBR entries! You maybe aware that
unlike M$ MBR which is 512 bytes, LILO boot record is 446
bytes long.

   Normally, if every bootable OS is on PRIMARY partition
there are no problems. The  problems  arise  when  one of
these (ususally Linux) is placed on an extended, a common
practice with modern Linux distros.
    
   I am of the view that; if Linux is in  /dev/hda1, LILO 
will do with the exception that it cannot  handle  UMSDOS 
installs. If Win-2k or NT is at  /dev/hda1, it  should be 
through NT/2k boot.ini, and if it is Win-9x, do a loadlin 
multi-boot. It keeps M$ happy, (and  also  various  virus 
checkers happy). I repeat, this is my  personal view, and 
not the universal law, or anything such ... From  experi-
ence, I know that this combination poses the least amount
of problems.

   Alternatively, use dedicated boot loaders like grub, if
under Linux or things like Xosl for M$. Virus checkers may
still growl !

   To set your  system  right at the  moment, all  that is      
needed is to go through your  /etc/lilo.conf,  check  that
everyting is in order and  re-run lilo as  root "lilo -v".
You will get back to normal LILO triple boot until you run
some M$ disk managers which do their own magic !

HTH

Bish

-- 
:
####[ Linux One Stanza Tip (LOST) ]###########################
  
Sub : Are your X paramaters correct ?                LOST #181

In case not, you may face situations where  either  the screen
does not fit properly, or there is flicker or snow. Under such
conditions probe for the actual parameters for your card using
"xvidtune" utility, in the  [auto] mode ...  Try output values
as Modeline in the Monitor section of XF86Config file.
                                                                 
####<[EMAIL PROTECTED]>################################
:

_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help

Reply via email to