Hello,

I recently installed Suse Linux 9.2 Pro on second SATA drive as the 1st partition next to Windows XP.(80GB total split in half between the 2). I also have another disk with only Windows XP(120GB). After configring Yast to display only Suse, Windows XP (120GB on solitary drive) and my floppy drive, everything seemed to work fine. I booted to both the Suse login screen and to Windows. Then, I tried to login to Suse and I couldn't. Each attempt started to log me in and then it bounced me back to the login screen. NOTE: this is not a passoword issue. If I use the wrong password I get "login failed". Otherwise I get bounced back. I tried to login as "root" and anohter user account and the same thing happened.
Then I booted to the Suse DVD-ROM and ran automatic repair. I recieved 2 errors:

1. My boot sectors "might be invalid" but if I can boot to them I can igore the message.
2. a data package error.

I ran the auto fix

The result: I cannot boot to Widnows because NTLDR is missing and I still cannot log into Suse as it still bounces me out.

I created a Windows boot floppy for now ( I realize this is not a windows forum) but I still cannot get into Suse, I cannot help but think the issues are related. Any advice would be VERY much appreciated.

Thank You

Perhaps X is crashing right after you enter your credentials? Did you check the log files? Popping over to a virtual terminal and checking /var/log/Xorg.0.log and /var/log/messages might give you a good start to see if something's going on.

Also, just curious...have you tried SuSE 10.0? If you have access to it, it might support your hardware a bit better and have less bugs. Just a suggestion though...

As for restoring Ntldr, you can boot up off an XP disk, go to a recovery console, and run fixboot or fixmbr. That'll restore your ntldr, but it'll also overwrite grub...you might want to read this forum. It's got some good info in it.

Thanks for the advice. I tried to boot back into Linux and ended up at a command line: "GRUB vs 0.95 Minimal BASH-like line editing" I could not do much from here and when i tried to boot to the command line from DVD-ROM it crashed right after the kernel was mounted. (I think) I want to see those log directories you listed but I fear I will not be able to.
I am worried now because in a fast effort to restore my system I have installed the boot loader on each of my drives. I have been changing the CMOS settings from starting with each disk, back and forth untill I can find the right configuration.
Most of files are on the Windows XP drive (single partition). My goal was to move as many of the supported files to Suse. It is not currently backed up and up and I need to avoid making my Windows partition unbootable. I will also follow your advice using the Windows Recovery Console but that will overwrite GRUB as you stated.
Should I allow Yast to overwrite the MBR? I have been leaving it "untouched" What does "activate Boot loader partition" mean? If it is written to the top of the disk and that disk is selected by the BIOS to be read fist, isn't that activated?
Again, thanks for your help with this.