MDKE 9.0 will not boot on second hard drive???
 

I recently installed a new hard drive (slave), and I loaded the Mandrake 9.0 to that drive (hdb). When I try to boot to the "Linux OS", I get an error msg. of "99 99 99 99 99".... I am working with an old Award BIOS 4.51PG.... Is there something I need to be doing with the bios?? or, is there something I need to be doing with the MBR........I am thinking there is a clash of the "Partition Commander" bootloader, and the LILO bootloader..????
Please point me in the right direction...(PS. - Newbie here)
Thanx :-))

99999

represents a bad or missing MBR.

When you set up the bootloader, where did you tell Mandrake to install it?

I don't recall where I sent the MBR to....I used the LILO option for the bootloader...
I guess I will reinstall the MDKE 9.0 disc's and take note of where it sends it to.

Thanks....

i have a simmaler prob i get 99 99 99 99 99 99 99 99 99 99 99 ........................ for about 4 or five lines

i just lost my boot loader so i tryed to re load it wiith the install disk by hitting f1 and typing rescue then i chose the reinstall lilo bootloader I am run ind 98 and mandrake i can still boot to windos via lilo of floppy drive but i can't chose linux since i took it out by acodent that is how i lost my mbr one trying to put it back can you tell me what i need to do

You need to re-install Mandrake from the CD.

Make sure that when you get to the bootloader screen that you tell it to install Lilo/Grub to the MBR (not the partition!) of the first bootable hard drive.

e.g. the Primary Master drive on your system.

This will also recreate the entry automatically, to let you boot up Windows.

(Another good question) Why does'nt the keyboard get recognized when the linux download starts?...It is on when I begin the process, then it get's probed, and it goes off...???? Hmmmm???? H E L P...

That's usually due to a conflicting device or a probed driver hitting I/O addresses on your system that cause the machine to do strange things.

Unfortunately when this happens you have to play with kernel parameters and loaded modules to see what exactly is to blame.

It's a bug.