Is the I/O range FFE0-FFFF valid for SB?

Nils-Erik · Nov 24, 2005, 01:40 PM

I've never got my SB Live to work in Windows XP, although all drivers can be installed successfully; XP default, Creative LiveDrvPack (but it doesn't recognize a soundblaster card present in the system) & kxDrivers.

The thing is that XP assigns the I/O range FFE0-FFFF to my soundcard (which by the way is a CT4760, subsys_80401102) and I have a feeling that this may be the problem.
Does anyone know if this is a valid I/O range for a soundblaster? Also, is it sufficient with only 32 I/O addresses? Is there any way to change the range allocated for the soundcard?

The things not working when using kxDrivers are:
- No analog sound (either from analog speakers or the headphones - cannot test if digital speakers work, since I don't have any)
- Cannot modify the 'Digital Output Only' or 'Bypass SPDF...' (on the general page)
- If I change the headphones volume, leave the page, and then go back - the volume is always reset to INF (I doubt that it was set in the first place)

I know that the kxDrivers aren't faulty, it's just that they don't seem to be able to communicate fully with the soundcard.

Btw, the soundcard works just fine if I clean the computer and install WinME instead. But going back to XP makes the problem appear again.
ACPI is enabled and I cannot make any adjustments in the BIOS. I have disabled ACPI but cannot make any adjustments to the I/O range anyways.

**dj_stick** · Nov 24, 2005, 01:50 PM

try moving the card to a new PCI slot to reset the bios's image of the card

Nils-Erik · Nov 24, 2005, 01:56 PM

Forgot to mention that I've tried every PCI-slot. It always maps the same I/O range anyway.

I've also tried installing the kxDrivers with a LogConfigOverride in the .inf-file that specifies that the starting I/O address should be aligned on a 256 bytes boundary. I've also tried allocating more I/O addresses to the card (64 and up to 256).

But all these experiments have not succeeded. In fact, overriding the default BasicConfigVector only results in the driver not being able to install correctly and the device not working at all.

Nov 24, 2005, 01:40 PM	#1
Nils-Erik DriverHeaven Newbie Join Date: Nov 2005 Posts: 3 Rep Power: 0	Is the I/O range FFE0-FFFF valid for SB? I've never got my SB Live to work in Windows XP, although all drivers can be installed successfully; XP default, Creative LiveDrvPack (but it doesn't recognize a soundblaster card present in the system) & kxDrivers. The thing is that XP assigns the I/O range FFE0-FFFF to my soundcard (which by the way is a CT4760, subsys_80401102) and I have a feeling that this may be the problem. Does anyone know if this is a valid I/O range for a soundblaster? Also, is it sufficient with only 32 I/O addresses? Is there any way to change the range allocated for the soundcard? The things not working when using kxDrivers are: - No analog sound (either from analog speakers or the headphones - cannot test if digital speakers work, since I don't have any) - Cannot modify the 'Digital Output Only' or 'Bypass SPDF...' (on the general page) - If I change the headphones volume, leave the page, and then go back - the volume is always reset to INF (I doubt that it was set in the first place) I know that the kxDrivers aren't faulty, it's just that they don't seem to be able to communicate fully with the soundcard. Btw, the soundcard works just fine if I clean the computer and install WinME instead. But going back to XP makes the problem appear again. ACPI is enabled and I cannot make any adjustments in the BIOS. I have disabled ACPI but cannot make any adjustments to the I/O range anyways.

Nov 24, 2005, 01:56 PM	Thread Starter #3
Nils-Erik DriverHeaven Newbie Join Date: Nov 2005 Posts: 3 Rep Power: 0	Forgot to mention that I've tried every PCI-slot. It always maps the same I/O range anyway. I've also tried installing the kxDrivers with a LogConfigOverride in the .inf-file that specifies that the starting I/O address should be aligned on a 256 bytes boundary. I've also tried allocating more I/O addresses to the card (64 and up to 256). But all these experiments have not succeeded. In fact, overriding the default BasicConfigVector only results in the driver not being able to install correctly and the device not working at all.