chainloading ubuntu hangs after displaying my entries in menu.lst

I have been asking questions and reading up on grub and the distro's booting sections but after a few re-installs and trials later I still cannot fully multiboot from my multidisk setup (as I had done with ubuntu's grub form earlier distro versions). I can boot into Suse and Windows (with some entry adjustments) but not Ubuntu Gutsy and Hardy.

My setup has my first IDE with a separate boot partition due to my bios limitations, and a swap also primary partition. For the rest on logical partitions, open Suse 11.0 is on the 11th partition and it's /home is on12th, I have Ubuntu Gutsy on the 8th, and others are either Ext3 data or NTFS partitions.

 My last re-install was the Ubuntu Hardy on sdb2 and it's own swap sdb1 - I added grub to the Hardy's / partition as suggested and then in Suse's grub/menu.lst I chainloaded it but Suse does something that is incompatible with grub later down the chain: I try to write:
title: Ubuntu
        rootnoverify (hd2,1) as grub sees it
        chainloader +1

but then Yast keeps saving this entry as:

title
     rootnoverify (hd0,0) which is where suse's master grub is
     chainloader (hd2,1)

this change allows me to still boot into my windows partition with added makeactive and mapping but for Ubuntu it causes my computer to hang in a grub path (it turns to a plain grub menu with the word grub on last line) with no way of editiing it!

the only work around I managed was to reboot into Suse's grub menu and to try my older ubuntu entry which says file not found (see later explanation) and then I end up in a black in white menu of same and there I can edit my Hardy Ubuntu entry back to the more universal way of entering a chainloader command as before Yast changes it and then I get into the menu.lst belonging to Ubuntu finally and there is another hitch to do with device mapping I believe: Ubuntu sees its root on (hd1,1) but I msut change it to (hd2,1) again in order to finally boot into hardy and there it seem that I have no gui or xserver installed, but I am hoping that that was something related to my omiting extra multimedia packages to do a quicker test installation.

I believe that I can change my groot permanently in my boot/grub/menu.lst to the appropiate (hd2,1) and change that problem, but what of Yast rewriting the chainloader entry?

I found out that for Ubuntu it uses UUIDs for listing it's kernel and other things and that this gets tricky when you add a new drive, partition or change the boot order in bios. Open Suse is on newly created partitions of my first drive, I had accidently erased my boot drive before these new re-installs and the drive with Ubuntu hardy is newi its a SCSI but was installed before putting on these OS new versions. I am mentioning this in order to figure out if any of these things are causing my difficulties. I don't understand it: you are supposed to be able to chainload many disros easily on many drives according to some (see the 145 OS chainloaded).

I will take a break and figure out my next steps. Since I have 2 OS on 2 drives-I have no space for both on this new SCSI) they both don't want to coexist bootfully!! I also erased my boot files for my entry into my older Ubuntu version gusty ( I still had some stuff left there) and so far instructions to cp the bkup files back to the boot partition failed... (kernel loads on screen with initdr messages and repeats "doesn't support DPO and FUA" and then system just hangs...)

Any ideas would be appreciated...