• 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.

Windows ME + Diamond MX300 = Bad ???

err

Platinum Member
Anyone has this setup ? I am trying so hard to find the driver that would be right for my WinME and MX300.

Using the latest aureal or monster driver, I would get a hard lock into the operating system right after I rebooted from the install. It even gave me windows protection errors 🙁 I had to do scanreg /restore to get back into the OS?

Is this hardware even supported? or was it because of poor drivers?

I hate Diamond :|

any inputs appreciated 🙂

eRr
 
Wingnutz: what driver did you use for WinME?

I just fresh installed WinME and installed the diamond driver and I got a damn Windows protection error bluescreen again...

Will try the A3D driver now 🙁

Thanks for the headsup 🙂

eRr
 
I tried the Vortex2 driver and still got a Windows protection error ... oh god... been reintalling WinME at least 3 times today ...

🙁

I'll try again tommorow.

Thx

eRR
 
1. I am/was a ME beta tester.
2. I have my MX300 working with the latest drivers from Aureal (2048, I think)

The problems I've had with this device in ME have revolved around the SoundBlaster Pro Emulation for DOS. Since, ME has no real mode DOS the SB emulation will obviously have problems. I think this problem is unique to ALL Vortex2 cards and ME.

BTW, do you happen to have an ATi video card? It seems that there is some resource that is shared by the ATi and the MX300.

So what did I do? I changed my video card to Standard VGA and then installed the Vortex 2 driver. After rebooting, I disabled the SB emulation and then set my video card back to its proper settings. All has been well since.

This was reported to the ME beta team as a bug. In fact, I was in contact with someone at MS with the same exact problem.

-SUO
 
Back
Top