Interesting... What version of Linux are you running? I recall reading
all the howto's and tried making it part of my MBR and using LILO to
boot up NT. It was a disaster :D Nothing worked (cept for the linux
piece).
Can you provide details on this? I"m no longer running NT cept at
work. Just got the the point where I wasn't interested in dealing with
Micro$oft anymore...
Frank
Miroslav Skoric wrote:
> Frank Carreiro wrote:
[snip]
> Well, interesting is that I have one fully functional Linux (and LILO)
> on an IDE system where I have two large NTFS partitions (cca 3 gigs
> each), and AFTER them I have /dev/hda3 as native and /dev/hda4 as swap
> partitions. I can't recall if the instalation process of Linux was
> complaining regarding that 1024 cyl problem, but I made it working.
>
Reading through the lilo documentation I came across a mention of 1024
cylynders being an issue for some systems. Something to remember when
using lilo.
[snip]
>
> One more note. On my IDE system, I have made that you wrote NOT to do: I
> have put LILO in the MBR and, of course, it disabled NT's loader. (But,
> after that, I made an NT entry within LILO and both Linux and NT boot
> again without problems).
I've had issues with it in the past. I'm surprised to hear it works at
all. I've had NT freak out during boot when I did it this way. Course
that was like a year ago when I was learning how to make it happen :-)
I'm sure some things have changed since then.
[snip]
>
> I know that procedure, if I remember properly, that is covered by an
> NT-lilo-howto. It is ok, but I made it my way :-) on an ide disk. Beside
> that, I can't make Linux to boot even if it is alone on a scsi disk
> system. FYI, I tried to make the procedure you wrote and I only got NT
> working (as if NT is alone there). For Linux entry, I got an error
> message that there is no system disk for Linux or sth like that. If I
> use LILO instead of NT's loader, system hangs after "LI".
Nice thing about UNIX / LINUX, there are many ways to do the same
thing. I've come across that "LI" problem before. Under the Lilo howto
they have all the error's explained. Helped alot in getting through
it. Lilo is a pretty nifty boot manager with many option
[snip]
>
> Beside that, I found on the Internet a little utility called BOOTPART or
> sth like that, that do this procedure automatically. It gave me a
> "Linux" entry under NT's loader but when I tried this entry I got 'no
> system disk' or similar error. Looks to me that is something wrong with
> scsi disks, but NT runs ok on those disks.
I've heard of it. I do it manually as it's not too tough to do plus you
never know how the utility will work out.
>
> > Final note. NT boot partition cannot be NTFS. Period. Linux will be
> > unable to boot properly if you convert to NTFS. If after all the above
> > you want more NT partitions (and have the space), you can use disk
> > manager for NT and make them NTFS.
> >
>
> This is new for me. On an IDE system I also have NTFS partitions
> pre-made during the instalation and, after that, linux partitions on the
> same disk and it is ok. On an SCSI it is NOT ok. If Linux is even alone
> on the 1st scsi disk /dev/sda it also hangs after "LI". Seems to me that
> I need some samples of /etc/lilo.conf (or any other config file needed)
> to compare with my setup. The problem is a 4 scsi disk system that runs
> NT without problems. It also accepts Linux instalation and (sometimes)
> the initial first run ok (before the first re-boot). But, I can not
> start installed Linux again, either as alone OS or in a connection with
> an NT on the same system.
How big is your partition on that scsi drive? You might want to
consider putting it on a 3 or 4 gig partition at the begining of the
drive (if alone on the 1st disk). I usually do that then create another
partition for my data/apps. See if that helps. It almost sounds like
you may have run into that lilo limitation (with hard drives that have
more than 1024 cylynders). Fdisk will warn you if you are in that
situation. Just run it and see what it says. You can boot from your
linux boot disk created during installation then run fdisk to check.
>
> I wonder also, if it is possible to make bootable floppies on another
> (working) Linux and to dedicate them to this problematic system (if so,
> how to do this),
Check out my web site. I found a great minix boot disk which I use to
mount linux partitions. The commands and feel is alot like linux. Here
is the link ...
http://www.xmission.com/~dmacleod/unix/linux/contents.html
Near the bottom of that page is my minix rescue disk with over 100
tools/applications. Hope it helps. BTW, it's not mine but I found it
while looking through the Internet. Some guy name Tom built it and did
I fine job I might add.
in order to avoid repetitive re-instalations of Linux
> that are not successive at the end? At the moment, I have two Linuxes
> installed (Caldera on /dev/sdc1 and RH on /dev/sdd1) that I can not
> boot. I also have running RH on /dev/hda3 on another system and wonder
> if I can use it to solve the problem with the first system?
>
::grinz:: You have alot of work ahead of you :D Perhaps checking what
fdisk says will give some insight.
I've never setup a system with two versions of linux on it. lilo.conf
shouldn't have problems booting into either one (I would think).
Frank
--
There is nothing wrong with
WINDOWS 2000
that Linux couldn't fix
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
