It appears that in order to load Linux through NTLDR, you need to still use LILO (or grub) to do the actual loading. Lilo has an unusual method of displaying error codes. At different stages during the bootup process, it displays one letter from the word LILO. If an error occurs, it displays the error number again and again. Presumably, you''re supposed to determine what stage LILO was up to by checking which letter has been displayed. You could probably find out what error 01 is somewhere in the LILO documentation, and it will help if you can see what is displayed (i.e. what percentage of the word "LILO" before the error message occurs).

Here's a great way to do it (I've used it before, works nicely!) http://www.xminc.com/linux/WindowsXPGrubMandrake82.html

This method involves using both the Win2k/XP boot loader and Grub. You need Grub so that the win2k/xp boot loader has a boot sector to load. The only annoyance is of course going through two boot screens, but that's not too much of a problem. Let me know if you need help!

Oh, and just a reminder, if your boot sector ever gets messed up for either win2k or linux, the install cd's should get you back up and running. For win2k you just have to use the recovery console provided in the install, and of course the actions will vary depending on the linux distro you have for getting linux back.

[edited by - Puffy_Taco on September 21, 2003 11:57:13 PM]

http://www.geocities.com/epark/linux/grub-w2k-HOWTO.html
is the one I used to get the NT bootloader to load linux. Works like a charm.

There''s also a setting in grub.conf to set the display time to 0 - grub doesn''t even show up.

---

"The sun is the same in a relative way,
but you''re older"
--Pink Floyd

01 is a lilo error code, google it

solved 01, but now iam getting LI error and i dont know exactly why its happening... i mean setting bios to boot from hdd works, but using the bootloader, lilo generates a LI error... hmm


T2k

quote:

---

Original post by Schmedly

quote:

---

Original post by Ready4Dis
The point he''s trying to make is, why try to get something to work that wasn''t designed to, when there is something designed to work properly for it. It''s like saying: "I have a philips head screwdriver and an easily accessible wrench, I need to remove this bolt, but I don''t feel like using the wrench, so how can I remove it with a philips head screwdriver."

---

That''s not a valid analogy. Wrenches and screwdrivers are designed for different purposes. A bootloader is a bootloader is a bootloader and all were designed to initiate the loading of an operating system.

---

It''s a more valid analogy than the one used . Also, not all bootloaders were created equal, and some where meant to load a single operating system, while others follow the multi-boot specification much better... just because they are both meant to load an OS, doesn''t mean they were both meant to load multiple OS''s properly.


Well, he''s looking to get Linux to multi-boot with Win2k... so, I suggest using a multi-boot bootloader, simple as that. Why choose a single-boot bootloader to load multiple OS''s. I beleive (like stated) even the NTLDR tricks that people are doing, still loads up LILO anyways, so what''s the point?

There''s no reason to use the Windows bootloader. Linux recognizes windows and linux, and the windows one would only recognize linux through some kind of nasty hack.

http://www.linuxforum.com/forums/index.php?showtopic=2648