assuming you can do some typing at the word grub on your screen .....you are at the grub command centre.
you now type
rootnoverify (hd0,0)
makeactive
chainloader +1
with ENTER presses AT each line.....you should be booted into windows and so you know what to have in your linux file /boot/grub/menu.lst when we boot into that.
now reboot back to that nasty grub and see my troubleshooter here
http://www.linuxquestions.org/questi...hreadid=237511
we now get into linux thru a bit of detective work
commands
find /etc/fstab
response will be something like (hd1,4) or (hd1,X) where X is 0,1,2,...etc
eg if (hd1,4)
New command is
root (hd1,4)
cat /etc/fstab
will output your file system table and we are looking for one or two entries
eg
/dev/hdb1 /boot ext3 and other junk
/dev/hdb5 / ext3 and other junk
BUT you may have the /boot folder as a sub-folder of / so you will only find
/dev/hdb5 / ext3
See the tut for amending those names into grub speak /dev/hdbX = (hd1, (X minus 1) )
We now use that info to set the pathway to /boot partition/sub-folder
root (hd1,0)
kernel / AND PRESS THE TAB KEY to see what files are there
response should be a vmlinuz..........we also need to specify the / partttion so we then complete the command
kernel /vmlinuz root=/dev/hdb5
You may also need an initial ram disk image so try
initrd / AND PRESS THE TAB key
if you get a file called initrd.img or something like that then to boot its
root (hd1,0)
kernel /vmlinuz root=/dev/hdb5
initrd /initrd.img
MODIFIERS
some distros want the kernel line and the initrd line as including /boot like this
kernel /boot/vmlinuz root=/dev/hdb5
well you get the drift
