Many thanks for your replies everyone
I agree re hardware issues - it's hard for the development stream to keep up with new hardware - even if some of them seem to be paid to do it. I suspect some hardware vendors have done exclusive business deals with MS. (Hopefully, it will turn out to be their loss one day)
FWIW I have had Apache 1.x series on both 7.3 and 8.2 with no problems. Am sure that Samba was available on both of those two versions as well but I never used it. I'd agree that sound shifting into the kernel is a 'new thing' and therefore probably buggy. Displays have always been an issue of one sort or another with Linux.
I once had a TFT (Iiyama I think) die and was never sure whether it was the card, the terminal, or dual boot RH and NT that was the problem.
and yes you have to do the research first... I'd agree with that.
My pet points of issue with SuSE are :
1. not providing gcc 2.95 This is the stable version of gcc used for kernel builds. 8.3 provided the world with a pre release of gcc v3.3 and I have yet to manage to install 2.95 safely i.e. being sure I wasn't about to wreck v3.3. Given that I bought the professional version and I think it's feasible that someone who buys the professional version would want a 'safe' 'industry-standard' 'standards compatible' compiler, I was a bit miffed that 2.95 wasn't available for install alongside 3.3
2. Twice I have had problems with code compile. Once was the winmodem code (no MOD_VERSIONS IIRC) and once was attempting to recompile my existing kernel using the source code provided on the distro. Having said that I took CVS out of rpm db and installed v 1.11.17 outside the rpm db structure (no rpm available) and I have recently compiled Apache 1.3.31 ok too. One thing that SuSE does tend to do is wander away from the 'structure of things' so there are some tweaks in the httpd.conf for v1.3.27 which are SuSE dept.
As far as wrecking a system goes, been there done that got the T-shirt
I was dual booting XP/7.3 and backed up to do a fresh install of 8.2. I completely missed the change in the 'how do you want to boot up' (GRUB v LILO, floopy v. hdd etc) and it's placement in the install procedure and managed to overwrite my MBR. That was the day I went totally Linux.
Regards
Lesley