OK, well, I've installed Suse on an Athlon XP system no problem. The system has primary volumes in pullout bays where I can change OSs by the drive. The system also has a 2-drive NTFS RAID 0 array used in XP Pro.

However, after Suse install, the RAID no longer shows up on the XP setup. The RAID contoller (a 3Ware 7000/8000 series controller) is on, active and shows up in the Windows device manager window, but the array itself does not show up under My Computer.

Any clues? Thanks.

I had a problem when installing SuSE 9.1 that's documented here: http://portal.suse.com/sdb/en/2004/0...booting91.html

Allthough your problem sounds quite different, you could try this (quoting link above):

<snip>
One quick solution is to activate the LBA or large access mode under which the hard disk was previously addressed for the hard disks in the computer's BIOS. It is important that the hard disk values not be set to "AUTO".
</snip>

So try setting LBA mode manually in bios. Not guaranteeing anything, but worth a go

Unfortunately that doesn't apply to a RAID. The RAID has it's own controller card.
What bothers me is that I had SuSE 8.2 Personal loaded on this system,
and not only did it not affect the RAID, I could actually see and access it in Linux.

This is why I didn't think anything about installing 9.2 on the system, and so far I
don't have any clues as to how to undo whatever it is that the install has done.
It's quite annoying to see the RAID driver loaded and running in Windows, but the
drive is not showing up. That's 220 gigs of data hanging in limbo.

Big problem.