LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   WinXP+Slack10.1+LILO+BOOTLOADER (https://www.linuxquestions.org/questions/linux-hardware-18/winxp-slack10-1-lilo-bootloader-310111/)

securehack 04-05-2005 05:33 PM

WinXP+Slack10.1+LILO+BOOTLOADER
 
Hey guys,

I have read dozens of threads on linuxquestions.org and yet to have find the answer. Here is my setup:

/dev/hda1 - WinXPro
+Clean install. Bootloader on MBR.

/dev/hdb5 - Slackware 10.1
+Clean install. LiLo on root part.

When computer boots, goes directly to WinXPro. Realized I didn't edit the boot.ini file and so I did.

Code:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(1)rdisk(0)partition(1)\Linux="Slackware 10.1"

Start the system, both options are given, WinXPro fine, Slack10.1 gives an error stating that "Windows could not start due to incorrect hardware" etc.

I know I made a mistake in the boot.ini file. Any suggestions?

Thanks,
Abid Kazmi

tommyj27 04-06-2005 10:11 AM

have you tried using lilo instead of the windows bootloader? it's very easy to setup, edit /etc/lilo.conf with your linux and windows partitions, then run 'lilo' from a command prompt. i attached a copy of my lilo.conf from my desktop running slack-current (pre-10.1) and winxp. you may also want to backup your bootsector before you go doing things in case you go breaking things instead. if you aren't familiar with that, there's some information at http://www.sysdesign.ca/guides/partitions.html

good luck

Quote:

# lilo.conf

boot=/dev/sda
prompt
timeout=50
lba32
vga=normal
menu-title="-=edge=->"
default = vm26.114
#image = /boot/vmlinuz
# root = /dev/sda5
# label = Slackware
# read-only
image = /boot/vm26.114
root = /dev/sda5
label = vm26.114
read-only
image = /boot/vm26.10
root = /dev/sda5
label = vm26.10
read-only
other=/dev/sda1
label=Sindows

securehack 04-06-2005 01:07 PM

Hey,
Well, there is no real difference between lilo and winbl. I really want to link/point lilo through the boot.ini file. I am very well aware of the option of using lilo as the bootloader. I'm currently at my school so I will get back to you when I have completed your suggestion. I am still curious as to how to configure the boot file for windows to start up linux. And no, I'm not a noob, I don't mess things up :p Any suggestions will be appreciated.
BTW: This is not a difficult problem. It's a simple boot.ini problem.

Thank you,
Sincerely,
Abid Kazmi

securehack 04-07-2005 03:30 PM

Still trying to figure what the problem is. I'll be using LiLo as the bl I guess. If anyone finds out, please post.


Thanks,
Sincerely,
Abid KAzmi

teckk 04-10-2005 08:23 AM

Am I reading this wrong?

/dev/hdb5 - Slackware 10.1
That's partition 5 on the drive

multi(0)disk(1)rdisk(0)partition(1)\Linux="Slackware 10.1"
That's the 1st partition on the drive

securehack 04-10-2005 10:02 AM

No, you are reading correctly. It was my mistake. I tried multi(0)disk(1)rdisk(0)partition(5)\Linux="Slackware 10.1" and it still doesn't let me boot. It gives the same Windows hardware config err.

-Abid KAzmi

DoctorSubtle 04-11-2005 03:57 AM

There's a tool called boot.exe that can record your master boot record and turn it into something the windows bootup procedure can use. It's at http://www.computing.net/howto/advanced/linuxnt/. Just understand that you'll have to install lilo to the mbr to get this to work, and that you'll have to get a new copy of the lilo mbr every time you reinstall lilo (such as after installing a new kernel). Hope this helps.

securehack 04-11-2005 08:25 AM

As I have said before about lilo being on the MBR, I know it can be done but I want windows to link to lilo through its bootloader.

--Abid Kazmi

DoctorSubtle 04-11-2005 03:38 PM

I should have been more clear, but it was really late at night. The program I referenced makes a soon-to-be-restored copy of the windows version of your mbr, which you keep on a bootable floppy along with the tiny program. You then start linux and *temporarily* install lilo to the mbr. Once it's there, you boot to the floppy disk with that little program on it, run it again and get a copy of the lilo version of the mbr. Once you have that lilo copy, you restore the windows version. Lilo is out of the mbr, Windows is back in, and you can use the lilo version you just created as a bootsect file for the windows loader (the way DOS used to use a bootsect.dos file). All told, lilo is only on your mbr for about three or four minutes.

securehack 04-11-2005 05:34 PM

Oh, no problem. I just downloaded the program. I will try it out after I finish my stack of homework. Then I'll see what the difference is in the boot file and sectors. And most likely solve this problem.

Thanks alot,
Abid Kazmi

securehack 04-20-2005 07:37 PM

Hey,
Well I tried the program and it worked but for a normal user, it is not friendly. Will try a simpler way.

Thanks,
Abid Kazmi


All times are GMT -5. The time now is 06:43 AM.