I'm running Red Hat 8.0 on my 98/2k/Linux box, and I'm having a a bit of a problem with the NTLoader *thunderclap*.
When I installed, I partitioned using the Linux fdisk, installed Linux, then 98 then 2k.
As suggested by the numerous installation guides around, in Linux I've used the following (hda1 = 98, hda2 = 2k, hda3 = swap, hda4 = / ):
dd if=/dev/hda4 bs=512 count=1 of=linux_bs.bin
I've chucked it over to the C:\, put it in the boot.ini:
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
C:\ = "Microsoft Windows 98"
C:\linux_bs.bin = "Red Hat Linux 8.0"
However, when I boot up using the Linux option, I end with a flashing cursor (and that's all). No boot-loader, nothing. I installed LILO as my boot loader (I've managed to get this working in the past, so I'm pretty sure it's not my hardware).
Oh, a side note: in the past, 2k has been able to see _a_ linux disk, but couldn't do anything with it besides suggesting that I format it and do away with Linux Heresy (I am aware MS stuff can't read ext3).
This time 'round, however, it can't see it at all... Maybe the NTLoader can't see it either?
Anyways, thanks,
Robbo :-P
PS: I've just read the 'mbr' thread, so I'll post my lilo.conf ASAP. Sorry. :-)
</Newb>
homey
03-29-2003, 10:25 AM
It is possible to use the boot.ini file for your linux boot like so....
When you reboot, the computer goes into the W2k system. If you want to use the Windows boot loader, you will need a file called bootsect.lnx. from your linux system.
# dd if=/dev/hda4 of=/bootsect.lnx bs=512 count=1
Copy that file to C:\ and edit boot.ini with the line C:\bootsect.lnx ="Linux"
Reboot the computer and you should have Linux in the Windows Boot Menu.
In Linux, edit the file /etc/grub.conf to start booting without the grub boot menu.
Timeout = 0
Otherwise, you will have to go through two bootloader menus.
However!!! I think that is more trouble than it's worth. :)
Since you have the partition information for your different systems, it would be relatively easy to setup the file /etc/lilo.conf to handle all of them.
Here is an example....
As for the first method... bootsect.lnx... linux_bs.bin... Same difference. Just different names.
Umm... The didn't actually solve my problems, but I eventually found a solution to my problems, hence let this be a warning to all newbs who enter here.
I have my Linux '/' partition past the first 8.6GB of the disk, but my lilo.conf contained 'linear', as opposed to 'lba32'.
Thanks anyways, mind. :D
Robbo
jetblackz
04-01-2003, 03:09 AM
My setup is identical to yours. The dd part didn't work for me. 2K "disappeared". If I let ntbootloader take over, it complained about missing NT files. I'm guessing it can only read in NTFS or with 2k being on the 1st part. Talk about catch 22. 98 is on the 1st.
FAT32, NTFS, EXT3.
The solution for me is to install a very tiny universal bootloader on MBR, lilo on root part of Linux, and the rest intact. It's working perfectly.
http://btmgr.sourceforge.net/
jglen490
04-01-2003, 11:50 AM
As you have found out, Win98's boot loader cannot load either Win2K or Linux. Thus, the common wisdom to load Win2k (or any NT) first, then Win9X, then Linux with Lilo or Grub boot code on the MBR. UNLESS, you have one of those systems with a diagnostic partition on hda1 and you do not have a complete copy of Windoze, as in the case of the very long MBR thread.
A Windoze that uses ntldr can be set up to boot any of the Windoze and any Linux. It's slightly more complicated than setting up Lilo or Grub, but works very well. If you do not have a system with a diag partition on hda1, then the simplest boot manager is either Lilo or Grub, the next simplest is to use NT's boot loader and boot.ini menu.
Regardless of your diag partition situation, the common wisdom is best. Install W2K/NT/WinXP first, then Win9X if it will be used, then finally Linux. The most capable boot managers in almost all multi boot situations are Lilo and Grub, the next are the Win versions that use the NT loader and boot.ini, the least capable are the Win9X boot managers. The other free third party loaders such as XOSL are quite capable but are not simpler to set up than NT's loader.
jetblackz
04-01-2003, 02:05 PM
"The other free third party loaders such as XOSL are quite capable but are not simpler to set up than NT's loader." - All I did is one command line in Linux. Nothing further typed. It can install under DOS & Linux.
It also boots your floppy, cdrom, all partitions that have correct boot sectors and even reboots PC or shuts it down.
With lilo, you must either chroot or boot into a working distro. Gain root access. Edit /etc/lilo.conf. And run lilo. Still not as simple as btmgr.
With NTloader, first you waste a min or two to boot NT up, log in as admin, next you open File Manager, last you open boot.ini in text editor. And reboot. Still not as simple as btmgr.
With btmgr, you boot to a Win98 CD or a bootable Linux CD or DOS floppy, run btmgr with a few parameters. Done. Redo if something screws it up.
I'm questioning this "Install W2K/NT/WinXP first, then Win9X if it will be used, then finally Linux." approach. You could still boot 2k/nt/xp, but not the next-installed 9x. It's not the way Microsoft recommends. MS recommends you install 9x first, then 2k/nt/xp. They wouldn't mention Linux. But most people here would tell you to install Linux last.
You should try installing 9x, 2k and Linux using NTbootloader. Like I said, 2k can't boot Linux via that 512kb file IF ntbootloader isn't on the 1st partition which must be NTFS. I could boot to old Linux via a floppy or CD tho.
I got the error msg that 2k couldn't find a certain file in system32 folder. It didn't say which drive. I copied it to fat32 98 partition. Same error. Eventually messed up the partitions. Thanks to recovery console which didn't ask me which partition to fix and freezed up a lot.
I wouldn't take another risk. Even though I have Ghost and backup's.
Or you could buy BootMagic which is basically the same thing, but the easiest for the average Joe, not us the experienced.
terribleRobbo
04-03-2003, 02:59 AM
Righti-o.
Firstly:
"load Win2k (or any NT) first, then Win9X,"
No no no no no no! :(
98 kindly overwrites the 2k bootloader if you install it second.
As for missing files...
I've had this problem before. I used Win98 fdisk to partition, then installed 98, then 2k, then Linux. 2k bombed out (missing nt____.__), Linux wouldn't boot (due to the problem I've now solved).
Nice and stuffed up.
What I did was to install Linux FIRST (and partition all the drives while I was at it). The 98 fdisk AND the 2k partitioner does a botch-job of the whole thing - 98 leaves extra '<1MB' partitions everywhere, and the 2k one will not set a FAT32 partition up correctly for 98 ('Missing Media Block' was the error the 98 installer threw up).
I partitioned, installed Linux (installing the boot stuff on hda4), then 98, then 2k.
After that, I did the