Direct-X must be reborn!
Direct-X is b0rked. Specifically, I’ve noticed it with the Direct-Sound failure, which prevents Winamp from working properly, and the Generic Host Process failure when I boot up.
However, Direct-X can’t be uninstalled, and “reinstalling” the same version doesn’t seem to help.
Dammit, I don’t have time to reload right now. Nor an external drive. :\
wait, so directx is being blocked unfairly by senate hearings? i didn’t even know that Windows XP even HAD a senate!
I wouldn’t be surprised, it often seems like petty bureaucratic arguing occurs every time I tell XP to do something.
ENGLISH, MAN! SPEAK ENGLISH!!!
Computer icky. No sound. Want Music.
bet-ter… me understand
( no really i had no idea what you said in that crazy moonman speak…always have english subtiles please)
Have you tried installing a new version? If there is one? If there’s not one, I think WinMediaPLayer (pfft) has it bundled, un-and-reinstall that maybe? Fun fun.
I might try that. I’ve already tried installing a new version of Direct-X to no effect. I don’t like updating windows media player, though, they get more and more intrusive.
i know it can’t be uninstalled but you could try ripping out all teh directx files and registry keys until Windows “forgets” that its installed, then reinstall
(never did that with directx, but its worked with other system components)
Well, that’s kind of the problem. I believe there’s a registry key or service that’s messed up, so on bootup, it goes “shit! this is all wrong!” and I get the generic host process (win32) error, which means that my sound is borked.
If I reboot a few times, often I can get everything to work, which is the weirdest damned thing.
right, i’m just say to fuck it up even MORE to the point that windows doesn’t even know about direct-x anymore, then reinstall the whole shebang
I don’t know if that’s possible. *chuckle* I think that’s why you can’t uninstall Direct-X – it has its fingers in so many danged pies.
You should be able to pull it out of the registry, though, as that’s the pie that other programs stick their fingers into.
The problem is, Direct-X is a substitution for other methods of audio and video production. I believe the whole reason I have this error in the first place is because I messed up one of my services. Turning off all services that use Direct-X in XP is … unlikely to function at all.
That’s funny. I remember when DirectX first came out and everyone’s computers exploded and it was OMG a mess and the antichrist devil spawn and stuff, and then apparently it started
going undergroundworking okay. :)Twas a different operating system, though.
I suppose so. What are you running? XP?
Yep