From the information that you have posted I agree that the hdc versus hdd is the problem. First, you are editing lilo.conf and I think Mandy is Grub based and not lilo based. However, that can be changed and if you are sure that you are running lilo as the boot manager make sure that the coomand "lilo" is run after the file is modified to write the new boot loader info. Another configuration where it might not work as desired is when lilo or grub is being used and installed to the partition but it is not really being used as the boot manager. If Win2K or XP is being used as the boot manager then after lilo or grub is written to the partition, the new partition boot info has to be read and written to the Win partition again for Windows to use it instead of the old info.

If you are running Mandy I seem to recall from the short period I used it that there was GUI program to configure it with. I know SuSE has one, but I thought Mandy did as well. I haven't used Mandy for quite some time, since version 7.1 or something.

Perhaps some of this will be of some limited assistance to configure your cd drive.

i am runing the command lilo after modifying, and am not dual-booting anything, especially not $atan, i mean $indows, oops

lilo is my bootloader for sure, but i've noticed another problem now that i think is connected - i modified the lilo.conf file to have different labels, and when i run the command lilo it shows up correctly, but not at boot time - at boot time it still shows the default names, which i think should mean that i am still not giving mandy the right commands to get it to use the new lilo.conf file.

might this have something to do with the fact that i'm booting /dev/hda7 rather than /dev/hda1? is the boot sector, or a little piece of it being written to /dev/hda1 so the bios sees it to boot it, and is that not being updated? i KNOW that linux makes sense, so i KNOW i'm just not doing SOMETHING right.

thank you for your help - it is more than "limited assistance"!!!

i will post a new thread in the linux-software section that references this one to give you a break from mandy, unless you wanna keep beating this issue with me!

If this machine is dedicated to the system, then why not just config lilo to write to the MBR. (boot=/dev/hda)

that did it. i initially set boot=/dev/hda7 because i thought that is what set the default boot selection. oops. now it's working perfectly.

thank you for your well-thought replies.

Ey DarkXtar could you mailme? plz, i have exactly the same problem and i don't known how to figure it out.

maverick010@ubbi.com


Thank you.

He's turned back to windoze, however if you want to describe your problem and why this thread cannot fix it, I am sure others here would be glad to assist

Cool

Well the problem is quite simple.

I'm using SlackWare 9, i have a cdrw drive and a standart cd-rom.
Both IDE, both at the 2nd channel (ID1 i guess), cdrw is Master (0), cd-rom is slave (1).

The OS only recognise the cdrw (1:0) as standar cd-rom reader.
My priority is to have cd-rw availability, second (less important), that cd-rom (1:1) is recognised.

I think that is useless to said that works on Win and discard any type of hardware config.

Thanks.