[bravetanveer]

This is question from a newbie, when it comes to yoper.
1. I have recently tried my hand at installing yoper on machine with Windows NT already present. It also had a linux partition. I have used the ISO Cd.
MY yoper was 1.o version.

2. I have installed yoper in novesa mode.

3. I have chosen, the linux partition which was already present on that system as home and other partition, which was swap partition of earlier linux, as swap partition.

Before installing yoper my system was: (using fdisk -l)

filesystem
hda b w95 fat32
hda2 5 extended
hda3 85 linux
hda4 82 linux swap
hda5 b w95, fat32

***********
I have chosen hda3 as my home for yoper, and hda4 and linux swap.
This i have chosen with the intention, that it will overwrite the original linux partitions. Because i want to install yoper on top on available linux.

I got installed, giving me the message to reboot.

1.
But The first screen, did not show the Windows OS's existence.

2.
It showed "Yoper 1.0" after grub loaded.

3.
When i clicked on "Yoper 1.0" to allow it to boot and go to Yoper, the message it gave was:::
******************
Booting 'Yoper 1.0'
root(hd0, ROOTPART)
Error 11: Unrecognized device string
Press any key to continue
*********************
4.
When i edited using "e" to
root( hd0, 1) , in first line it showed when pressed 'e'

the message it showed was

******************
Booting 'Yoper 1.0'
root(hd0, 1)
File sytem type unknown partition type 0x5
kernel /boot/vmlinuz-2.6.7-2 root=/dev/ROOT ro
Error 17: Canont mount selected partition
Press any key to continue
*********************
5.
Next try was with : root( hd0, 2) ,
in first line it showed when pressed 'e'

the message it showed was

******************
Booting 'Yoper 1.0'
root(hd0, 1)
File sytem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.7-2 root=/dev/ROOT ro
Error 15: File not found
Press any key to continue
*********************

*************************************************

So after those trials and errors, i finally thought to post this question.

1.
My goal is to install yoper, with windows present,
i.e. it should show yoper and windows in grub

I know that if i able to go inside yoper, i can change the grub.conf file and add windows title with rootnoverify option.

But it seems i am stuck..

[Nerderello]

have a look at the general tutorial section of this site, for a post on solving boot problems with grub.

Nerderello

[drtvasudevan]

i have installed version which is latest.
during boot instal it adviced the grub is still experimental with yoper and one is better off with lilo.
i have no problem with it.

tv

[bravetanveer]

Thanks for the replies.

when i made a hard toil at what was the actual problem, i got to knew that:

Grub was showing the wrong version of kernel. This kernel version was not present in my CD.

It was showing 2.6.7-2 but when i checked that, the real version was : 2.6.8.1-3.
So i edited the grub entry as per that to:

kernel /boot/vmlinuz-2.6.8.1-3 root=/dev/hda3 ro

And phew !!! at last i could see, those messages on screen, "Uncompressing the kernel". So i was through with that.



But again when i changed the "grub.conf" file in "/boot/grub/" folder, i again got stuck. Because Grub failed to load.
I agree, my change was major one: I changed the label of "Yoper 1.0" to "linux-2.6.8.1-3".
My PROBLEM: How to escape grub in such situations. Is there any way to directly go to linux or windows, by escaping grub.
And is it necessary to have label names sames as the distribution we are using???

[Game master pro]

You could boot into something like knoppix to edit things, you wouldn't be in windows, but you _should_ be able to access both particions, or you could do a windows boot disk, but that would just be dos, although something i'm pretty sure that would get you back into windows is Reinstall windows but instead of going "format drive" go "Replace system files" or something like that so you still keep all you things on the harddrive but it chages all the boot files back to default, so you go into windows without grub or anything.
oh yeah i know now, make a windows boot disk and in A:/> prompt type "fdisk /mbr" and i'm pretty sure that'll fix it, but don't sue me if it doesn't