it ain't done until Lotus won't run
There's an article over at Infoweek (referenced by Dan Gillmor, in turn referenced by Karlin Lillington, which is how I stumbled across it) about how Fred Langa tried to install Linux on new (but unnamed) hardware and couldn't get the sound working. Fair enough; sound support in Linux is lamentable in places, particularly if you're trying to get real-time sound/video sync going on, but also if you've got stuff like the emu10k1-based cards that aren't documented because, you know, frobbing the speaker is a trade secret and all that. Langa then went to try a Virtual PC running on the hardware, emulating a SoundBlaster, and lo, 8 different Linux distros still refused to work the sound interface. The followups to the article appear to be the usual flood of kneejerk responses ("Infoweak", "What do you expect from a windows user" "sure, sound is broken, but have you tried running Windows$version on $esoteric_hardware" etc. etc.) but in typical Linux flamer style there's no actual thought behind the posts. Me, I had a look at the article Langa references when he mentions the Virtual PC software, and lo, it's a review of Microsoft's Virtual PC. Now, why on earth would a bog-standard SoundBlaster interface fail to work under Linux? Could it perhaps be because Someone Doesn't Want It To Work? (mutter mutter where's me tinfoil hat mutter mutter millennium hand and shrimp I telled 'em)

no subject
no subject
no subject
no subject
The only options left for a non-working SoundBlaster emulation are (a) the guy writing the article had the volume turned down (note, this was the solution to using ALSA) (b) the guy writing the article was shilling for Microsoft, or (c) Microsoft really did break the SoundBlaster emulation but only for Linux.