I've just upgraded to 9.3 from 9.2 on my triple-boot machine (2.4Ghz P4, 1 20Gb HD, 1 200GB hd partitioned into three partitions: 115/40/38 (or close to that), nVidia GeForce 5200-256MB). I did a complete fresh install over partitions where 9.2 was sitting (that 40GB partition includes both the primary and swap partitions for SuSE). Now, when I try to log in, I get Linspire's bootloader. Fine, right? Nope. Well, in addition for the fact that it doesn't recognize SuSE, it also will not load either Linspire or Windows. I get "ERROR 17" when I try to run linspire and "Error 13" when I try to run Winblows and it does nothing. I can only reboot. Well, as this problem developed when I had upgraded Linspire from 4.5 to 5.0 and I still had SuSE 9.2, I would try to use SuSE's bootloader which recognized the "Other Linux" system on my computer along with Windoze. BUT, in order to access SuSE's boot loader, I had to keep my SuSE dvd in the drive and let it get to the menu where I could choose "Boot from Disk" (or hard drive or whatever that first option is) and THEN I could load any of the OS's as normal. However, after I upgraded to SuSE 9.3, I still have the same bootloader problem in that I have to go to the SuSE dvd first so that I can boot anything; additionally, now when I select the "Other Linux" option, instead of loading linspire, the computer just reboots. I can load Windoze and SuSE, but can't access my Linspire. Is there any way to access where the boot information is to clear it out and let SuSE insert it fresh? I've tried every option I could see in YaST to overwrite the MBR code, but it never solves the problem. Jack