NEW BUG!!!

Wintermin · #1 November 21st, 2005, 07:27 AM

I'm having (had) the same problem, and it's a sound issue. It's brand new for me, I haven't had sound problems before. Turning off the sound fixes the problem. Turning the mouse click off doesn't help, but turning sound FX off does, and battle FX doesn't affect things. Reinstalling from the CD and upgrading to 2.0 then 2.5 didn't work. DirectX isn't reporting any problems. Changing to WinME compatibility didn't seem to fix things, _but_ uninstalling my new 3rd party (non-MS) sound and video codecs fixed the problem. My suggestion would be to see if you have installed any new sound codecs and remove them and revert to Microsoft ones if you can. If you want to replicate the problem you could start by downloading the Satsuki Decoder Pack 2.0.0.6 from Satsuki's Website

Michael H.

DRG · #2 November 21st, 2005, 02:32 PM

Thanks for that info. Hopefully this will help some of the other guys with sound problems as well

Don

JJAVN · #3 November 21st, 2005, 03:22 PM

Ok.
I turned my Sound FX.. works fine now.
Kinda sucks without sound though

Ive still got Battle FX which is a good thing

Can someone run me through a step-by-step on how to remove/debug my sound codecs?
Im know my way around a computer but.. thats a little too advanced for me. Trust me, ive tried looking in the FAQs and other threads and i just dont understand them

BaronvonBeer · #4 November 21st, 2005, 07:36 PM

Don't worry about the second video card. Just the secondary output for dual monitor support.

Pepper · #5 November 21st, 2005, 09:26 PM

JJAVN--

This site may help: http://www.free-codecs.com/guides/Ho...ws_XP_2000.htm

JJAVN · #6 November 22nd, 2005, 04:49 AM

hmm.. will taking these codecs out affect anything else on my system?
Im thinking it might.
Like certain videos might not play or other games might have troubles. Am i thinking right here?

Pepper · #7 November 22nd, 2005, 11:28 AM

The standard windows CODECs are pretty comprehensive, and will cover most items. If something you have requires an additional CODEC then typically it will self-install and/or tell you what you need to install. But what sometimes happens is that you goto a site and view something or do something once that requires a certain codec that may not be fully windows compliant, and that could be your culprit -- even though you may not ever use that codec again.
Anyhow, the short answer is that yes there is some risk that something you do won't work, but that shouldn't be hard to fix.