I am back from been away, but during holiday I still thought about this problem :(.
Today I went at it again. To recap:
The system has two harddisks:
- The first disk had XP loaded on the second partition. I found out that the first partition was a recovery for an earlier ME system. During installation that first partition was described by the installation partitioner as type 0x83 (Linux) and the filesystem as ext2! Indeed (during my later struggle) I could mount it as ext2 in the rescue system and it contained one file windows.tar.gz. (besides lost+found).
- The second disk was all one big data partition.
After installation the first disk was not touched. On the second disk the data partition was shrinked and a swap, root and home partition were created to fill it. First boot during installation went OK.
After installation when booting we got:
GRUB Loading stage 1.5
GRUB loading, please wait...
Now all sorts of save and sound advice was given as you may read in the posts above. Until today the only thing I managed to do was restoring the MBR to boot XP (XP rescue) and going back to the Error 17 situation by using the SUSE rescue DVD and doing the grub statements:
The output from these where as expected: all normal and OK.
Coming back from holiday I found a thread on this forums where somebody mentioned the grub statement:
Using this I got:
floating point exception
Now that is very strange :X
I then tried to solve the situation by using the rescue partition (sda1) as a seperate boot partition. I copied all contents of boot in the root partition to it and then started grub:
On the first one I got a normal response, but the setup gave me a floating point exception again!.
This brought me to the point where I mistrusted the ext2 fs on sda1. I got permission to destroy the ME windows.tar.gz and did an mkfs to generate the fs anew. and copied the boot files to it again.
The grub find statement now did find both /boot/grub/stage1 files (no floating point exception anymore). And then setup of root (hd0,0) did go OK also.
Tried to boot and the menu screen poped up lol! Choosing Linux we got an error from the BIOS saying that the cylinder number was out of range. **This must be the cause of the original error! **
But now, by changing the several (hd1,2) in menu.lst to (hd0.0) that was also remedied.
Thanks to all who contributed a month ago and I hope the story above may help increasing your knowledge