Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have not been able to install Ubuntu 5.10 as a dual boot with Windows XP. I am trying to use Windows' NTLDR boot loader as people have said Windows has a problem if something other than that is on the MBR. (Is that true?)
Installed GRUB on /dev/hda8 (the Ubuntu / ).
The installer gave a message saying to remove cd's etc, that we will now reboot into Ubuntu which I knew would not happen the way I had set it up. So I used SystemRescueCd and mounted hda1 on /c and did:
dd if=/dev/hda8 of=/c/ubuntu.bin bs=512 count=1
Then I edited /c/boot.ini, adding the following to the bottom:
C:\ubuntu.bin="Ubuntu 5.10 Breezy Badger"
On rebooting, the new entry shows up, but if chosen I get this message:
Windows could not start because the following file is missing or corrupt:
I don't really know whether this is related to Linux at all or not, but please help.
You might fine [URL=http://www.ubuntuforums.org/archive/index.php/t-80508.html]this site[/URL helpful. In general, though, it's easiest just putting GRUB on the MBR. GRUB has no problem booting Windows XP and I've used it to dual boot XP and Fedora on a number of laptop machines.
Well my version of Ubuntu 5.10 installed just fine with Windows aside, no problem, and I'm using GRUB without problems for booting. GRUB (Grand Unified Boot Loader) causing problems..that's crap. You really don't need any 3rd party bootloader or windows bootloader, because GRUB (or LILO if you like older stuff) works perfectly. I wonder where you heard that it wouldn't?
First of all, when installing Ubuntu, you only need to create some free space to your HD - by resizing existing partitions, for example (this can be done with gparted that is on the Ubuntu LiveCD, or Partition Magic, or some other tool like that). Then start the installation and choose to install ubuntu in the free space, and not format the whole HD (yes, this is an option in the installer, and it does the process automatically for you, no need to be afraid of it removing Windows). Install GRUB into MBR (works fine, I've tried -- it has only messed up in an old pc with an old version of win98 for me, and I think it was my own fault back then too). Then boot. My installation, which was done exactly like that, worked - and works - like a charm.
As a precaution some people like to install GRUB not to MBR but to the "first free sector of...", well anyway the 2nd choise in the installers that's usually present. That works well too, but you'll need to make sure the partition in which you install it is selected as "active" (or "boot"). I suggest installing the bootloader to MBR, and if you later want to remove it and put Windows back, just run "fdisk /mbr". As you see in your own thread, Windows's bootloader didn't seem to do the job..so just use GRUB. Why make things difficult if they are easy? I've never met friendlier dual-boot installation than that of Ubuntu's -- at least if you install Windows first, Linux 2nd. Because Windows's bootloader is almost every time the one that fails.
EDIT: by the way, Ubuntu has got a new version coming out next month (last time I heard about the schedule). The latest beta version ("Flight") is stable enough already, I've been using it much and haven't seen big problems (mainly seen them in translations and so); consider getting the Flight6 (if that's the latest now) installcd/livecd/install+live -dvd, since it really is worth it. Or then install 5.10 and update quickly to Breezy
I think everyone who does much with his system runs into the Case of the Missing HAL. I have quite a few times. Not for awhile, so I don't recall which fix method I found easiest and quickest. If you are still tangling with the problem, follow the advice in the URL. I seem to recall you need the HAL that is totally specific to YOUR Windows system (from your CD) so that is why you don't simply grab a replacement from the internet—but I'm not absolutely sure about that.
Normally your HAL.DLL hangs out in your WINDOWS directory, in system32, so some place like C:\WINDOWS\system32\HAL.dll. That is likely the corrupt or missing file. It might also be in your WINDOWS\servicepackfiles\i386\ . Wherever you find it, once it's fixed, it's a good idea to keep a copy of all your boot files—including boot.ini and NTLDR—someplace handy, such as in your system partition, viz. C:\Booteroo, or whatever you wish to call it. ("Booteroo" is obviously not a stock Windows folder, but it is found when somebody looks around "boot", so I like that name.)