hi!
> Yes. I just forgot that part while writing the mail. Sorry for that!
>
> So the modified commands would be :
> sfdisk -d /dev/hda > parttab
>
> cat parttab | sfdisk --no-reread --force -H255 /dev/hda
>
> Sorry about the error!
>
> Kaustubh
:-)
so it's solved! well that gave me some gyan! 8-
>
> er...didn't you use -H255 as in:
> sfdisk --no-reread --force -H255 /dev/hda
> ??
Yes. I just forgot that part while writing the mail. Sorry for that!
So the modified commands would be :
sfdisk -d /dev/hda > parttab
cat parttab | sfdisk --no-reread --force -H255 /dev/hda
Sorry about the err
Hi!
> sfdisk -d /dev/hda > parttab
>
> Edited parttab to remove the warning ( first two lines ).
> cat parttab | sfdisk --no-reread --force /dev/hda
er...didn't you use -H255 as in:
sfdisk --no-reread --force -H255 /dev/hda
??
Without that, how did it work for you?
>
> Rebooted and everything work
> >Disk /dev/hda: 40.0 GB, 40020664320 bytes
> >16 heads, 63 sectors/track, 77545 cylinders
> >Units = cylinders of 1008 * 512 = 516096 bytes
>
> 16 heads--that's the problem. it should be 255. it's the same thing that
> caused the FC2 bootloader problem.
> read http://lwn.net/Articles/86835/
>
Yo
> 16 heads--that's the problem. it should be 255. it's the same thing that
> caused the FC2 bootloader problem.
> read http://lwn.net/Articles/86835/
>
Is it? I just checked up the disk geometry in the bios, and that does show 16
heads. Even after I tried to autodetect the drive, it shows the sam
Kaustubh Gadkari wrote:
Just check if you partation on which windows is istalled is still marked
active (ie bootable).
This is the output of fdisk -l.
Disk /dev/hda: 40.0 GB, 40020664320 bytes
16 heads, 63 sectors/track, 77545 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
16 h
On Thursday 09 Dec 2004 21:18, Kapil D. Pendse wrote:
> By the way, does windows allow us to install it's bootloader on it's own
> partition, rather than MBR?
Hi there.
I didn't want to jump into this thread, but the facts outweigh the
consequences.
Here's a kernel of truth:
http://librenix
> By the way, does windows allow us to install it's bootloader on it's own
> partition, rather than MBR?
> That would be very very useful! We can then install grub/lilo in MBR and
> keep windows loader on it's own partition. Then grub/lilo won't get erased
> everytime we re-install Windows(which i
Hi!
> This is what I plan to do. Reinstall window's bootloader, then make the
> partition inactive. Install grub on the linux partition after making it
> active. Anything wrong with this plan?
>
> Kaustubh
I think that should work. And I still think the "Loading Windows" message is
from the wind
Reply inline.
> hmmm, the usual case for me is when I have 2 windows installations and 1 or
> more linux installations on a harddisk, the linux bootloader (grub/lilo)
> has only one windows entry. Selecting this entry takes me to the windows
> bootloader, which is installed by XP(since in my case I
hi!
> > As i can see that hda1 and hda5 are marked bootable -- this can possibly
> > confuse windows. Try removing the bootable flag from hda5. Hope this
> > helps. ~
>
> Nope. So this is what I'm gonna do. I'm gonna reinstall the windows boot
> loader and then reinstall grub. It's gonna
> As i can see that hda1 and hda5 are marked bootable -- this can possibly
> confuse windows. Try removing the bootable flag from hda5. Hope this
> helps. ~
>
Nope. So this is what I'm gonna do. I'm gonna reinstall the windows boot
loader and then reinstall grub. It's gonna take some tim
On Wed, 8 Dec 2004 09:17:46 +0530
Kaustubh Gadkari <[EMAIL PROTECTED]> wrote:
>
>Device Boot Start End Blocks Id System
> /dev/hda1 * 1 2057610369926c W95 FAT32 (LBA)
> /dev/hda2 20576 7754528712691+ f W95 Ext'd (LBA)
> /de
>
> Just check if you partation on which windows is istalled is still marked
> active (ie bootable).
>
This is the output of fdisk -l.
Disk /dev/hda: 40.0 GB, 40020664320 bytes
16 heads, 63 sectors/track, 77545 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start
On Tue, 7 Dec 2004 14:29:59 +0530
Kaustubh Gadkari <[EMAIL PROTECTED]> wrote:
> >
> > Is it giving any error msg when you select windows from lilo?
> No. It just says "Loading Windows" and does nothing.
Just check if you partation on which windows is istalled is still marked
active (ie bootable
Hi!
> > Is it giving any error msg when you select windows from lilo?
>
> No. It just says "Loading Windows" and does nothing.
>
> Kaustubh
Did you try re-installing grub? Maybe that'll work. It works fine on my
machine.
Regards,
Kapil
--
"The Power to Imagine, is The Power to Create!"
-TTux
-
On Tuesday 07 Dec 2004 9:33 am, Kapil D. Pendse wrote:
> > Yes, because grub was booting debian and slack, but not windows. So I
> > reinstalled lilo into the mbr, because lilo was working fine before
> > debian was installed,
>
> Is it giving any error msg when you select windows from lilo?
No. It
> Yes, because grub was booting debian and slack, but not windows. So I
> reinstalled lilo into the mbr, because lilo was working fine before debian
> was installed,
Is it giving any error msg when you select windows from lilo?
--
"The Power to Imagine, is The Power to Create!"
-TTux
--
__
>
> You have mentioned debian installed 'grub' in mbr, and your have edited
> slack's lilo.conf.
>
Yes, because grub was booting debian and slack, but not windows. So I
reinstalled lilo into the mbr, because lilo was working fine before debian
was installed,
Kaustubh
--
I once witnessed a lon
Hi Kaustubh,
> Debian Sarge installed grub as its boot loader in the MBR.
> Now, Sarge and Slack worked, but Windows now would not boot. So I made the
> entry in the lilo.conf file from Slack ( from which Windows was booting )
> for Sarge. Still no luck and I'm stumped. Can anyone suggest a way ou
Kaustubh Gadkari wrote:
Hi!
Here's the situation. I have a 40GB harddrive with Win98,WinXP and Slackware
10 running. I had about 3GB of free space on which I installed Debian Sarge.
Debian Sarge installed grub as its boot loader in the MBR. Now, Sarge and
Slack worked, but Windows now would not
Hi!
Here's the situation. I have a 40GB harddrive with Win98,WinXP and Slackware
10 running. I had about 3GB of free space on which I installed Debian Sarge.
Debian Sarge installed grub as its boot loader in the MBR. Now, Sarge and
Slack worked, but Windows now would not boot. So I made the ent
22 matches
Mail list logo