I've found several topics on this but none of them seemed to help me.
So I relate:
I had WindowsXP on my machine but it needed to be reinstalled, so I installed Suse9.1 Personal and used it to back up my Windows files. Then when I re-installed my Windows it over-wrote the boot loader as it does.

Like other threads have stated, I used the SuSE LIVE! CD to boot in but from there I can never access my Windows or Linux partitions. And mount gives me errors about the /etc/fstab.

Next, I boot into Rescue System from the SuSE install CD. It asks me to login and I do (as root) and it brings me to this screen:
Rescue:#
so I type lilo and it tells me "no lilo.cfg file found"
So I type grub and it brings me to the screen that says:
grub:#
so I type help and it gives me a list of all the commands I can use.
All of them give me errors like "invalid command" or "kernel must be loaded before ~ modules" or "multiboot kernel must be loaded to boot".
Alas, no dice.

So next I downloaded GRUB, and tried to re-install it. Too many errors to list here.

And so, in desperation I booted Windows and went to Control Panel-System-Advanced then clicked Settings for Startup and Recovery, then clicked Edit for the boot.ini
I can edit and save changes to boot.ini but I don't want to screw it up too badly so if anyone knows a way to fix it through that, please tell me.

And that, is my dillemma
Thank you for your time

You can go ahead with reinstall the grub and everything if you know...but if you are a newbie i would suggest you first load windows and then linux...that will take care fo everything.

Sorry, I'm a newbie too so can't help with rescue procedure...

Right, I knew I could re-install windows then linux but the problem is I would then lose all the files I had originally saved in Linux.
Plus I have fiddled with the install disk to try to install only grub, still having trouble with that though.
Thanks though for the input

Case Closed.

I booted up the install CD, selected Manual Install, selected Install, then Boot Installed System, then HDA3.
It's a nuissance to do everytime but it works.

I remember Suse has a feature called 'boot installed O.S.' booting from install cd 1 which lets you get into linux again when things like this happens.
Once into suse you could restore lilo/grub back

Anyway...

Cheers