Soundblaster PCI 128 on W2000

[hanterp 0]

Last week you guys helped me out with my topic about the diamond viper 550 drivers for Windows 2000 pro. It works! Thanks again!

But now I have still one problem: My soundcard, the soundblaster 128 PCI suddenly doesn't support hardwarebuffering.

At least, that's what dxdiag (from directx) tells me.

Under windows '98 se I was able to use the drivers on the supplied CD.

Then it was possible to use hardwarebuffering.

But on that CD are no drivers for W2000, there are for Windows NT 4.0, but that doesn't work.

Now it gives me a standard SB driver which works for more compatible SB cards

That's why it doesn't use hardware buffering.

I already downloaded the capp-setupus.exe file plus the library-files from the creative.com site, but after installing it uses stil NO hardwarebuffering

 

My question: are there specific soundblaster PCI 128 setup-files or driver-files for the W2000, and where can I download them??

 

Hope you can help me out.

 

Han.

[biniou 0]

Well, I had the same problem under 98 (SE), but once everything was reinstalled, no problem any more.

But my card doesn't work AT ALL under 2k. As soon as I play a sound, even the Windows sounds, the computer hangs, and I have to hard reboot. I have tried many different drivers, with no success. My card is Model CT4810 (the chips is a CT5880)...

[TiNenfant 0]

Look in your mobo manual PCI slots sharing and try to switch cards.

Try whith and without ACPI.

Should be recognized with W2K native drivers as Creative AudioPCI.

[hanterp 0]

TinEnfant, I changed the card from PCIslot, but there's no difference.

Also ACPI off and on doesn't help.

But ACPI has to do with powermanagement, right? What is the connection with my soundcard?

I 'v heard about a small proggy for SB live in Windows 2000, where you can adjust the settings for that card. Something like that would be nice for my card as well.

I am afraid it has nothing to do with other settings in Windows 2000, but with the inferior quality of the driver in Windows 2000.

...or can somebody surprise me with a solution?

 

Thanks sofar.

Han.