• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2k driver troubles

DaveJ

Platinum Member
Hello all,

Booted my Win2k box this evening to two wonderful BSODs... anyone having problems with a Matrox G400 and a SB Live? The two I got were "Cannot load driver emu10k1.sys", and the same for G400m.sys. Nothing has changed on the system since the last reboot. I got the G400 working (reinstalled the latest drivers). The Live shows as working in Win2k, but I get no sound and my speaker icon is gone from the taskbar.

Any ideas? I'm paranoid about rebooting now... 🙂

Dave
 
I got the same error from my SoundBlaster when I installed 98 on a new setup, I just downloaded the newest driver from their site. I no this isn't that helpful but it worked for me and maybe you.
 
Been there, done that. 🙂 Installed DirectX 8, and the new LiveWare 3.0 for Win2k. Still nothing. Device Manager thinks nothing is wrong, but Sound properties shows no hardware installed for any of the recording or playback devices. I've swapped the PCI slot the card is in, and physically swapped the card for an identical SB Live, but still no go.

AARGH! :|

Dave
 
Gigabyte 7IX
Athlon classic 650
Matrox Marvel G400
SB Live! Value
Tekram DC390U2W
Maxtor DM+40 30GB HD
Plextor 12/10/32A
3com 10/100 NIC
256MB Corsair PC133

Dave
 
I use the SB live! and have had no problems under win2k.

Here is the most logical thing to do: uninstall any drivers for it. remove the card from the computer. reboot and run win2k. check device manager to make sure card is not listed. shutdown. install card. reboot win2k. install liveware 3.0 for win2k. let us know if it worked.

 
I have had no trouble with my SB Live Value. You might try to boot into the 'last known good configuration' or whatever it's called.
 
Back
Top