I had Liveware 3 working fine under RC2. However, after my upgrade to RC3, it converted the drivers to the built in ones. When following the newest fix instructions to install Liveware 3 again, I can't get past the first few steps. I ran RUN.CMD and after I go to "Update Driver..." and use the Liveware 3 drivers, they install and ask me to restart. When I boot up, the sound doesn't work at all. Under Device Manager, Creative SB Live! is said to be working fine and has no problems.

Basically, it installs the drivers fine, but the computer doesn't see them as sound card drivers. For example, when I go to Control Panel|Sound & Multimedia, the "Preferred Playback Device" is grayed out. No applications can use the card.

But the irony is that the driver is installed and supposedly has no problems.

HELP

Actually, it's rather funny... but at one point, I found this problem taking place in RC2 as well... I'm not on RC3 though (yet), but the same thing happened to me.

I bantered with Anthony about this stuff last night via email - he thinks it may have something to do with my USB Alaris QuickCam (which is working fine under Win2k). When I get my energy back from fighting with the system last evening, I will go at it again and make attempts at it. I was just happy to get my Voodoo3 working!

I have had the same problem. Finally gave up after 6 days of fighting these drivers. No sound ever. checked the hidden devices and the emu10k1 device could not start because it had a conflict. solved the conflict but still no sound. got things mapped correctly but showed volume at 100% in the red (stuck there actually.) No sound. quite a problem with system going to 100% cpu usage for no particular reason at all as well. Decided to give up and wait a while until creative has native drivers. Its only 2 months (I hope) If you come to a solution I might be willing to try it once. Happy with my current installation however and would hate to flub it up. I am using acpi on an LX motherboard, I think this may have something to do with it.

hi

i have the same problems with rc3 and liveware 3. after hours on trying i'm able to install the liveware (i can't remember the steps). but the performance was horrible. 100% cpu-usage. after that - i reinstalled w2k and uses the standard sb live-driver, which is included. no 4 speaker support, but it works. i will try to install liveware after a patch from cl is released.

galac

This My little Baby
Intel 300a@450a celeron
Abit BH6 Motherboard
2, 128meg SDRAM 168pin DIMM
Creative Lab's SB Live! Value
Realtek RTL8029(AS) PCI Ethernet NIC
Adaptec 2910c PCI
Mat****a CD-R CW-7501
Toshiba DVD-ROM SD-M1202
Western Digital 8.4gig IDE Primary
Hewlett Packard 420c Printer
Microsoft SideWinder 3D Pro
Microtek Scanmaker E3
Microsoft PS/2 IntelliMouse with Wheel
Microsoft Natural Keyboard PS/2
ViewSonic G773
3dfx Voodoo3 2000 PCI 16meg
PCWorks FourPointSurround FPS1000 speakers
I haven't fig out why some poeple system work & other don't.

New Drivers Fixed the problem.

Thanx to all who tried to help.

does that mean you have it working properly? I can't get the install program to even extract the files anymore. the installshield freezes after it loads (the bar goes to 100% then goes away) for liveware 3 install (the new, updated version). I'm sticking with the native drivers for now. I'm on RC3 currently, will upgrade to RTM soon.

Prophet

dont use the install prog to extract the files...use winzip and then boot to safe mode and use the run.cmd file that came with the instructions....i had the same problem, when i used the install to extract the liveware my machine would lock up or nothing would happen at all...i just created a folder and used winzip to extract all the files...my live works fine...have eax and all other features including 4 speaker support

The install program didn't work for me either, but I figured out that after it decompresses the five files (lv3lib1, 2, 3, setup, and lw3nt) the setup.exe file in the temp directory wasn't expanded. Go to the command prompt and expand that setup.ex_ file to setup.exe and run that from win. The setup then worked for me, but I never did get any sound after the whole process - resorted back to the standard drivers.