fdisk /mbr works great. Get a win98 boot floppy and boot with it. Type the command "fdisk /mbr". Then use your linux disk for rescue and edit /etc/lilo.conf:
# configuring DOS/Win/WinNT boot partition
other = /dev/hda1            #  Adapt this:  start partition
    label = WinNT              #  whatever you like
    table = /dev/hda         #  Adapt this: must be sda with SCSI instead of hda
# configuring DOS/Win/WinNT boot partition: end

Dont forget to run /sbin/lilo -v!

Type "reboot"
Ralph :^)

[EMAIL PROTECTED] wrote:
fdisk /mbr does not work on win2k, ifdisk /mbr works greatf I remember correctly, you'd have to
reinstall the ntloader files.  It's been a long time since I've dual
booted, so I don't remember exactly.  When you install a linux system,
don't let lilo be installed to the mbr - you'll probably have to do a
custom / expert install to avoid this - again, I don't remember for sure. 
After you've installed your systems, then use the nt loader to load linux.
 I have always had problems with m$ systems running continually, so much
so, that I created ghost images as soon as my system was loaded with
everything I needed, then when windows blew a fuse, I just reloaded
everything from the ghost images.  I don't believe that linux had anything
to do with it - windows does the same thing when on a disk by itself!

Mike

  
You mean "fdisk /mbr" right??
That will over write your boot sector.
But rember you will need to reinstall Lilo, so you will need to have a
rescue
disk ready.  :^)

Ralph

On Wednesday 02 July 2003 12:53 pm, Adrian Golumbovici wrote:
    
Hi everyone,

Before you flame me for using Windows 2000 Pro :) , I am a gamer and
since
my favourite games don't exist for linux, I have to dualboot. I already
installed Mandrake 3 times on this machine :) after managing to thrash
my
linux severely when my mobo was not yet supported and I have same funny
effect each time. Windows 2000 boots ok till before the login screen and
then it stays there aparently doing nothing for almost 2 minutes... It
is
annoying. After I do a repair installation of windows 2000 it works ok
again till next time I recompile the kernel and install it. Same thing
happened to me when I tried to install debian on this machine. So I am
starting to beleive it is linux/lilo related. I started letting my
system
permanently on just to avoid the annoying effect, but don't think this
is a
good longterm solution.

Another funny thing is that a "repair" install of win2k doesn't remove
lilo. I wanted to clean up my system at one point to move linux to a new
hdd, but lilo remained. Trying a format /mbr didn't do anything. Does
anyone know how to remove lilo and let the previous OS boot normally?

Best regards,
Adrian
      
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com

    


  

Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com

Reply via email to