Customize SBPCD support to your perticular setup. This saves time at
boot probeing (you shouldn't be, but ....), and (arguably) saves memory
too. You should answer yes only if you know your current setup
(looking at "dmesg |less" may help), and no if you don't (and no for
distributions).
Customize SBPCD support (CONFIG_SBPCD_CUST) [N/y/?] y
First controler type (SoundBlaster, LaserMate, SPEA, SoundScape, Tech16bit) [SoundBlaster]
defined CONFIG_SBPCD_CUST_SOUNDBLASTER
First controler I/O Base (CONFIG_SBPCD_CUST_FIRST_BASE) [330]
Second driver type (SoundBlaster, LaserMate, SPEA, SoundScape, Tech16bit, None) [None]
defined CONFIG_SBPCD_CUST_ONLY_ONE
If you don't tell it none, it keeps going until you've got them all defined,
and moans something like 'Are sure you want them all in ?) (ie they
proberbly don't want them all in unless they really know what they are
doing).
Bryn
-- PGP key pass phrase forgotten, \ Overload -- core meltdown sequence again :( | initiated. / This space is intentionally left | blank, apart from this text ;-) \____________________________________