Recommended Posts

after installing these drivers, I finally get 5.1 through Control Panel in Vista. As mentioned before, this has not fixed the fact that I get no sound through mce or wmp.

a couple of things to note though after installing the drivers:

-there is a slight popping sound everytime at the beginning of every new sound played

-task manager no longer starts (which is really annoying!)

Yep, they work but if you try to install them through device manager they install but you get no sound and no BSOD. Looks like you have to run setup and go throught the BSOD once and then the sound works. Too bad the HD Xplosion didn't have drivers that work in x86. Tried to get them to work but no luck. Guess we have to wait until after RC1.

after installing these drivers, I finally get 5.1 through Control Panel in Vista. As mentioned before, this has not fixed the fact that I get no sound through mce or wmp.

a couple of things to note though after installing the drivers:

-there is a slight popping sound everytime at the beginning of every new sound played

-task manager no longer starts (which is really annoying!)

I have mine set at 2.1 digital output only and I don't get the issues you are reporting. It looks like that more people are having trouble with 5.1 (BSOD) in some cases) maybe check how 2 speaker configuration works?

Also its well known that creative drivers do not completely uninstall/overwrite new drivers. You may be left with an older version of a particular component if it wasn't a clean install.

Try this: http://www.driverheaven.net/showthread.php?t=48573 (Driver Cleaner) if you upgraded those drivers and it wasn't a clean install.

PS: I don't know if this works correctly on Vista, it might be worth doing a roll back to before you installed the original driver (System Restore) although that will take it back to when you first installed Vista :/

I did manage to get the new drivers to install; it is *required* to uninstall the old drivers first for the new ones to *take*. In addition to the Audio Console, you now have access to EAX sound environments within Vista (via the Audio Console), regardless of speaker settings.

I installed the new drivers using the setup. I got no BSOD during the install nor after reboot. I got a few popups saying something like "1 something unreased", I'll complete my post if I get these messages after my next reboot.

In the audio console, I set the speakers config to synchronise with the windows settings, and set 5.1 speakers in the windows audio control panel.

Everything works fine.

Another thing: PGHammer said it is required to uninstall the old drivers. I did that, but then the setup complained about no hardware required found. So I reinstalled the old drivers (the ones for build 5270), rebooted, installed the new ones, the setup went fine, rebooted, then the popups I told a few lignes before, and everything is now fine.

I have a SB Live! card my uncle gave me... It's pretty old, but Windows Update found its drivers immediately... Unfortunately, my microphone isn't giving any sound (but it has an icon in the audio devices and a bar that's called "Microphone," "Creative SB Live! (WDM)") in my Vista build 5384. It works perfectly in XP SP2.

Oh speaking of SB drivers for vista... I've got me here an old SB PCI 128. I used the XP drivers since none were available for my model. It was successful, however, in the hardware manager in the WDM properties where it lets you change the wave sets for the midi, I get the message "you do not have admin privileges"

Is anyone else getting that? Or is it only because the XP drivers arn't fully compatible? I'm in the admins account too.

I installed the new drivers using the setup. I got no BSOD during the install nor after reboot. I got a few popups saying something like "1 something unreased", I'll complete my post if I get these messages after my next reboot.

In the audio console, I set the speakers config to synchronise with the windows settings, and set 5.1 speakers in the windows audio control panel.

Everything works fine.

Another thing: PGHammer said it is required to uninstall the old drivers. I did that, but then the setup complained about no hardware required found. So I reinstalled the old drivers (the ones for build 5270), rebooted, installed the new ones, the setup went fine, rebooted, then the popups I told a few lignes before, and everything is now fine.

Here are the popup messages I got

They appear in a window which title is "Busted App":

There were 1 unreleased IDrvAdapterMgr interfaces

There were 1 unreleased IDrvDevice interfaces

There were 2 unreleased IDrvBMixer interfaces

There were 1 unreleased IDrvBMixerLine interfaces

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
    • They said by this time everyone will have flying cars. WELL...
    • A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. Maybe not as we now know that time can flow backwards.
    • Of course. Simply reverse the polarity.
    • It is clear from this aricle that "Time Is On My Side" no matter which direction it is flowing., https://noai.duckduckgo.com/?i...m%2Fwatch%3Fv%3DsEj8lUx0gwY
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      578
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      73
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!