🚀 go-pugleaf

> When I hit the finish button of the intallation,  and on shutdown process
I
> got a warning saying that the partition is larger than 1024 Cylinder?
> When I reboot the computer it say it can't find operating system to
oot.( I
> had linux partition as active).

Where did you put LILO?
put it in the MBR, or make the win2k partition active again, and boot
through
the NT bootloader.

And to get rid of the 1024 cyl. problem:

boot from the bootfloppy you made, change the "linear" in /etc/lilo.conf to
"lba32"
run `/sbin/lilo -v` and reboot. The RH installer should have done this for
you, but
appearantly it failed at doing so.

> Note:  with my other PC that has 4GB I can partition it (2GB each) to boot
> between Windows 2000 server and Linux without a problem.

Then you don't cross the 1024 th cylinder there.

> Any help is much appreciated and you can reply to ungtu@hotmail.com or
> tung@connect.com.au.

you post here, you read here.

Eric

As I'm not using one of my linux OSes at the moment (so no access to the man
files), and probably won't be rebooting until well after you read this, what
does the v switch do?

Ari


"Eric" <scare.crow@oz.land> wrote in message
news:9a9sus$2rc$1@porthos.nl.uu.net...
> > When I hit the finish button of the intallation,  and on shutdown
process
> I
> > got a warning saying that the partition is larger than 1024 Cylinder?
> > When I reboot the computer it say it can't find operating system to
> oot.( I
> > had linux partition as active).
>
> Where did you put LILO?
> put it in the MBR, or make the win2k partition active again, and boot
> through
> the NT bootloader.
>
> And to get rid of the 1024 cyl. problem:
>
> boot from the bootfloppy you made, change the "linear" in /etc/lilo.conf
to
> "lba32"
> run `/sbin/lilo -v` and reboot. The RH installer should have done this for
> you, but
> appearantly it failed at doing so.
>
> > Note:  with my other PC that has 4GB I can partition it (2GB each) to
boot
> > between Windows 2000 server and Linux without a problem.
>
> Then you don't cross the 1024 th cylinder there.
>
> > Any help is much appreciated and you can reply to ungtu@hotmail.com or
> > tung@connect.com.au.
>
> you post here, you read here.
>
> Eric
>
>

(meaning of -v switch with lilo)

the -v switch is a verbosity switch, use more of them to get
more info about the actions lilo performs.

Eric

Eric, thanks for the response.
I believe I put lilo in Linux partition which is on /dev/hda2.
I can get Windows 2000 to boot again when I mark it's partition active.

I have a linux boot disk, how do I use it to boot and  be able to edit the
lilo.conf in the /dev/hda2 partition?

I will try again soon once I get home from work.

Regards,

Theng Ung



"Eric" <scare.crow@oz.land> wrote in message
news:9a9sus$2rc$1@porthos.nl.uu.net...
> > When I hit the finish button of the intallation,  and on shutdown
process
> I
> > got a warning saying that the partition is larger than 1024 Cylinder?
> > When I reboot the computer it say it can't find operating system to
> oot.( I
> > had linux partition as active).
>
> Where did you put LILO?
> put it in the MBR, or make the win2k partition active again, and boot
> through
> the NT bootloader.
>
> And to get rid of the 1024 cyl. problem:
>
> boot from the bootfloppy you made, change the "linear" in /etc/lilo.conf
to
> "lba32"
> run `/sbin/lilo -v` and reboot. The RH installer should have done this for
> you, but
> appearantly it failed at doing so.
>
> > Note:  with my other PC that has 4GB I can partition it (2GB each) to
boot
> > between Windows 2000 server and Linux without a problem.
>
> Then you don't cross the 1024 th cylinder there.
>
> > Any help is much appreciated and you can reply to ungtu@hotmail.com or
> > tung@connect.com.au.
>
> you post here, you read here.
>
> Eric
>
>

> Eric, thanks for the response.
> I believe I put lilo in Linux partition which is on /dev/hda2.

then it will indeed not boot, as that is beyond cylinder 1024.
The default DOS MBR probably cannot access that region.

> I can get Windows 2000 to boot again when I mark it's partition active.

that's at least a good thing.
You can use the nt loader to boot linux too if you like.
(I never tried this, I always use LILO as the main bootloader, but there's
a good howto on the subject)

> I have a linux boot disk, how do I use it to boot and  be able to edit the
> lilo.conf in the /dev/hda2 partition?

just put the floppy in, and reboot. It will use the partitions you defined,
so
no worry, you'll be able to correct them once you booted from floppy.

Eric

Hi Eric,

Yes, It is now up and running. But I had to install  Red Hat again as I had
to create a boot disk.
and modify lilo.conf and add another line to boot Windows 2000.

Many thanks for your help.

Theng


"Eric" <scare.crow@oz.land> wrote in message
news:9aa0fq$4tn$1@porthos.nl.uu.net...
> > Eric, thanks for the response.
> > I believe I put lilo in Linux partition which is on /dev/hda2.
>
> then it will indeed not boot, as that is beyond cylinder 1024.
> The default DOS MBR probably cannot access that region.
>
> > I can get Windows 2000 to boot again when I mark it's partition active.
>
> that's at least a good thing.
> You can use the nt loader to boot linux too if you like.
> (I never tried this, I always use LILO as the main bootloader, but there's
> a good howto on the subject)
>
> > I have a linux boot disk, how do I use it to boot and  be able to edit
the
> > lilo.conf in the /dev/hda2 partition?
>
> just put the floppy in, and reboot. It will use the partitions you
defined,
> so
> no worry, you'll be able to correct them once you booted from floppy.
>
> Eric
>
>
>

> Yes, It is now up and running. But I had to install  Red Hat again as I
had
> to create a boot disk.

you don't need to reinstall. just to create a bootdisk!
the CD has this option:

linux root=/dev/where-your-root-is

> and modify lilo.conf and add another line to boot Windows 2000.

That you needed to do indeed, but reinstalling was a bit drastic.
Anyway, I'm glad you got it up and running now.

Eric

"Theng Ung" <tung@connect.com.au> wrote in message
news:9a9s0s$19h$1@perki.connect.com.au...
> Hi,
>
> I have a Celeron 733  that has :
>    1. 40GB ATA 66
>    2.128 SDRAM
>
>
> I had install Windows 2000 professional on a 20GB partition, so leave 20GB
> left.
> I boot up from Red Hat bootable floppy and install Red Hat 7.0 on rougly
> 10GB partition with 300MB swap partition.
>
>
> When I hit the finish button of the intallation,  and on shutdown process
I
> got a warning saying that the partition is larger than 1024 Cylinder?
> When I reboot the computer it say it can't find operating system to
boot.( I
> had linux partition as active).
>
> Note:  with my other PC that has 4GB I can partition it (2GB each) to boot
> between Windows 2000 server and Linux without a problem.
>
> Any help is much appreciated and you can reply to ungtu@hotmail.com or
> tung@connect.com.au.
>
>
> Regards,
>
> Theng Ung

Newer Versions of LILO (version >= 21.4) actually supports the options LBA32
and LINEAR that will allow you to go over 1024 Cylinders for HDD that
supports it.

=-
Elem103

Theng Ung wrote:

> Yes, It is now up and running. But I had to install  Red Hat again as I had
> to create a boot disk.
> and modify lilo.conf and add another line to boot Windows 2000.

You shouldn't need to reinstall to do that.  You can boot into
"rescue" mode from your installation CD and fix things that way.

-- 


-John (John.Thompson@attglobal.net)

Theng Ung <tung@connect.com.au> wrote:

> Yes, It is now up and running. But I had to install  Red Hat again as I had
> to create a boot disk.
> and modify lilo.conf and add another line to boot Windows 2000.

> Many thanks for your help.

> Theng

Can Win 2k boot loader run after lilo has taken in? I had the idea that 2k
acts like NT and doesn't boot if it doesn't 'own' the MBR? Am I wrong?

Anyway, if you have lilo in MBR and you're able to boot 2k, please let me
know your configuration.

Yes, I have similiar problem, I have first 3 Fat32 partitions
(hde1,hde5,hd6) 8 Gigs each and then linux / and swap. Tried to do that
MINI-HOWTO-procedure for NT-bootloader, but lilo says then only 'LI' and
repeats it over and over again... Like this:
LI
LI
LI
LI ...and so on.

(I've RH 7.0)

Even tried both 'linear' and 'lba32'. Would grub work better?

	tiki

"Markku Tikkanen" <mtikkane@remove.hytti.uku.fi> wrote in message
news:9agsrq$14og$1@luotsi.uku.fi...
> Theng Ung <tung@connect.com.au> wrote:
>
> > Yes, It is now up and running. But I had to install  Red Hat again as I
had
> > to create a boot disk.
> > and modify lilo.conf and add another line to boot Windows 2000.
>
> > Many thanks for your help.
>
> > Theng
>
> Can Win 2k boot loader run after lilo has taken in? I had the idea that 2k
> acts like NT and doesn't boot if it doesn't 'own' the MBR? Am I wrong?

I'm running my system with NT and Linux and Linux owns MBR.  Also have a
system with Win2K and linux and it works fine too.

> Anyway, if you have lilo in MBR and you're able to boot 2k, please let me
> know your configuration.

Err.. everyone has different lilo config.

Generally the important parts are:

# Set LILO to go on the MBR
boot=/dev/hda

# My Linux Partition
image=/boot/vmlinuz-2.4.3
        label=Linux243
        root=/dev/hda2
        read-only

# My Windows Partition
other=/dev/hda3
       label=WinNT

> Yes, I have similiar problem, I have first 3 Fat32 partitions
> (hde1,hde5,hd6) 8 Gigs each and then linux / and swap. Tried to do that
> MINI-HOWTO-procedure for NT-bootloader, but lilo says then only 'LI' and
> repeats it over and over again... Like this:
> LI
> LI
> LI
> LI ...and so on.
>
> (I've RH 7.0)
>
> Even tried both 'linear' and 'lba32'. Would grub work better?

=-
Elem103

Elem103 <elem103@smokey.aic.net.au> wrote:


>> Can Win 2k boot loader run after lilo has taken in? I had the idea that 2k
>> acts like NT and doesn't boot if it doesn't 'own' the MBR? Am I wrong?

> I'm running my system with NT and Linux and Linux owns MBR.  Also have a
> system with Win2K and linux and it works fine too.

OK. I'm just making sure that this is possible, because Red Hat guides
state that: "To create a dual-boot environment on a system that currently
has NT, you must install LILO on the first sector of the root partition,
not the MBR." 

I have also assumed, that NT or 2k won't boot if it doesn't
own the MBR. Glad that you made it. How did you install the OS's? First
the M$ stuff and then Linux, writing the MBR over?


>> Anyway, if you have lilo in MBR and you're able to boot 2k, please let me
>> know your configuration.

> Err.. everyone has different lilo config.

> Generally the important parts are:

Yes, I assume that I know what rows in lilo.conf mean. I just asked that
also to know if there was something special. 

Just asked both due to scepticism on 2k booting without 'owning' the MBR.
Didn't want to experiment, you know?


Anyway this prob below was odd, I thought that newer lilo's could load
with that lba32 setting the OS being quite far from beginning of drive. Or
is that the problem I'm having?

>> Yes, I have similiar problem, I have first 3 Fat32 partitions
>> (hde1,hde5,hd6) 8 Gigs each and then linux / and swap. Tried to do that
>> MINI-HOWTO-procedure for NT-bootloader, but lilo says then only 'LI' and
>> repeats it over and over again... Like this:
>> LI
>> LI
>> LI
>> LI ...and so on.
>>
>> (I've RH 7.0)
>>
>> Even tried both 'linear' and 'lba32'. Would grub work better?

"Markku Tikkanen" <mtikkane@remove.hytti.uku.fi> wrote in message
news:9ah85a$obg$1@luotsi.uku.fi...
> Elem103 <elem103@smokey.aic.net.au> wrote:
>
>
> >> Can Win 2k boot loader run after lilo has taken in? I had the idea that
2k
> >> acts like NT and doesn't boot if it doesn't 'own' the MBR? Am I wrong?
>
> > I'm running my system with NT and Linux and Linux owns MBR.  Also have a
> > system with Win2K and linux and it works fine too.
>
> OK. I'm just making sure that this is possible, because Red Hat guides
> state that: "To create a dual-boot environment on a system that currently
> has NT, you must install LILO on the first sector of the root partition,
> not the MBR."
>
> I have also assumed, that NT or 2k won't boot if it doesn't
> own the MBR. Glad that you made it. How did you install the OS's? First
> the M$ stuff and then Linux, writing the MBR over?

Hmm.. i did this about a year ago.  Hope i still remember how to do it ..
properly.  Anyway, i think this is what i did.

I made sure that everything is in the first 1024 cylinders of the hard
drive, due to the use of old lilo.

ie.

Partition your hard drive with Linux first.  I use fdisk to partition
everything, specifying the correct partition type for each partition.  What
i have is:

/dev/hda1             1       131   1052226    b  Win95 FAT32
/dev/hda2           132       262   1052257+   6  FAT16
/dev/hda3           263       279    136552+  82  Linux swap
/dev/hda4   *       280       526   1984027+   5  Extended
/dev/hda5           280       296    136521   83  Linux
/dev/hda6           297       305     72261   83  Linux
/dev/hda7           306       338    265041   83  Linux
/dev/hda8           339       469   1052226   83  Linux
/dev/hda9           470       526    457821   83  Linux

Win98 goes in /dev/hda1, WinNT goes into /dev/hda2 and Linux root partition
/ goes into ... /dev/hda5 :)  Yeah i know this is messy oh well.

Always always install Win95/98/ME2000 first.  That thing always mess around
with your MBR.

Then install WinNT.

Then it's time to install linux.  Install normally.

/dev/hda5               /
/dev/hda6               /tmp
/dev/hda7               /var
/dev/hda8               /usr
/dev/hda9               /home

Add LILO to MBR with /dev/hda1 as Win98, /dev/hda2 as WinNT and image in
/dev/hda5 as linux.

Then again, i manually edit lilo so that i can boot into those 3 operating
system and i'm using Debian.

eg.

boot=/dev/hda
root=/dev/hda5
install=/boot/boot.b
map=/boot/map
delay=5
default=Linux243
image=/boot/vmlinuz-2.4.3
        label=Linux243
        read-only
other=/dev/hda1
       label=Win95
other=/dev/hda2
       label=WinNT

> Anyway this prob below was odd, I thought that newer lilo's could load
> with that lba32 setting the OS being quite far from beginning of drive. Or
> is that the problem I'm having?

Well, i have not tested lilo much, so i can't really say.  Most of the time,
i just made sure that my boot partition is above 1024.

Cheers,
Elem103

Elem103 <elem103@smokey.aic.net.au> wrote:

> Hmm.. i did this about a year ago.  Hope i still remember how to do it ..
> properly.  Anyway, i think this is what i did.

> I made sure that everything is in the first 1024 cylinders of the hard
> drive, due to the use of old lilo.

Well, the partitions you have are basically the same way I'm having - with
the exception that my first linux partition (/boot) is waaaay beyond the
1024 limit. Somewhere was said that newer lilo's can boot beyond the limit
- but I didn't check that is it included in RH7...

BTW: how much is 1k cylinders in GB's? Or does it depend on HD in use?
8 Gigs?


> Well, i have not tested lilo much, so i can't really say.  Most of the time,
> i just made sure that my boot partition is above 1024.
                                             -----
You mean below?

I think my problems are all because of having about 24 Gigs of Fat32
-partitions in beginning of drive. And, I'm having the drive on HPT370
conroller (KT7-RAID)

Perhaps I try not to get blood out of my nose (a finnish way of saying)
and create a 16-meg /boot -partition at the beginning of the drive.

thanks for your concern, Elem.

	tiki

(ahh, the spring is coming! ...how about there? ;] )

> > Hmm.. i did this about a year ago.  Hope i still remember how to do it
..
> > properly.  Anyway, i think this is what i did.
>
> > I made sure that everything is in the first 1024 cylinders of the hard
> > drive, due to the use of old lilo.
>
> Well, the partitions you have are basically the same way I'm having - with
> the exception that my first linux partition (/boot) is waaaay beyond the
> 1024 limit. Somewhere was said that newer lilo's can boot beyond the limit
> - but I didn't check that is it included in RH7...

it is.
(version 21.4.3 and above I think)
But your BIOS must support it too.
But if your system isn't over 3 years old, it probably will.

> BTW: how much is 1k cylinders in GB's? Or does it depend on HD in use?
> 8 Gigs?

depends on the settings
Cylinders(=1024)*Heads*Sectors*512=Number_of_bytes

>
> > Well, i have not tested lilo much, so i can't really say.  Most of the
time,
> > i just made sure that my boot partition is above 1024.
>                                              -----
> You mean below?

He must have meant that indeed.

> I think my problems are all because of having about 24 Gigs of Fat32
> -partitions in beginning of drive. And, I'm having the drive on HPT370
> conroller (KT7-RAID)

don't know about RAID, but 24 GIG will be way beyond 1024 indeed.

If you would *show* your lilo.conf and your partitiontables,
we would perhaps be able to help.

> Perhaps I try not to get blood out of my nose (a finnish way of saying)
> and create a 16-meg /boot -partition at the beginning of the drive.

it would probably be the easiest solution, if you can do this.

Eric

Markku Tikkanen wrote:
> 
> Elem103 <elem103@smokey.aic.net.au> wrote:
> 
> > Hmm.. i did this about a year ago.  Hope i still remember how to do it ..
> > properly.  Anyway, i think this is what i did.
> 
> > I made sure that everything is in the first 1024 cylinders of the hard
> > drive, due to the use of old lilo.
> 
> Well, the partitions you have are basically the same way I'm having - with
> the exception that my first linux partition (/boot) is waaaay beyond the
> 1024 limit. Somewhere was said that newer lilo's can boot beyond the limit
> - but I didn't check that is it included in RH7...

** Yes the new lilo can boot above the 1024 line **BUT** it requires a bios
that recognizes certain calls - usually these bios are 1998 and newer.
Having the latest software isn't going to help if it needs a hardware feature.
> 
> BTW: how much is 1k cylinders in GB's? Or does it depend on HD in use?
> 8 Gigs?
> 
> > Well, i have not tested lilo much, so i can't really say.  Most of the time,
> > i just made sure that my boot partition is above 1024.
>                                              -----
> You mean below?
> 
> I think my problems are all because of having about 24 Gigs of Fat32
> -partitions in beginning of drive. And, I'm having the drive on HPT370
> conroller (KT7-RAID)
> 
> Perhaps I try not to get blood out of my nose (a finnish way of saying)
> and create a 16-meg /boot -partition at the beginning of the drive.
> 
> thanks for your concern, Elem.
> 
>         tiki
> 
> (ahh, the spring is coming! ...how about there? ;] )

-- 
Norman Levin

"In 1555, Nostradamus wrote: 'Come the millennium, month 12, in the home of
greatest power, the village idiot will come forth to be acclaimed the
leader.'"