Page 1 of 1

Windows logo aarrgghhh

Posted: November 10, 2006, 6:02 am
by Gemily
Ok so I go and buy a new video card to play a game wich will remain unnamed. Installed it, no problem, works great.

Play the unnamed game for a week or so until they decide to upgrade the DirectX 9 with the october 2006 version.

Well, in order to continue to play the unnamed game, you must install this new DirectX version. Downloaded the zipfile fine. But cant install it. Says that my video card driver hasnt passed the WHQL (Windows Logo) So I go and dowmload the latest driver for my card. Still cant install the new DirectX9, same reason.
Like WTF. Went to Windows System/Hardware/ and disabled the Windows logo Certification thingy. But still doesnt let me install the freaking thing.

Anyone know what else to do?

Posted: November 10, 2006, 9:45 am
by Zaelath
Roll back the driver, install DX, then install the driver again? Not had this trouble though...

Posted: November 10, 2006, 1:13 pm
by Winnow
ATi cards are notorious for that. I think they even used to say to ignore the certification warning and keep installing.

It it an ATi card or nVidia?

You may have to uninstall the video drivers and then let the Windows XP Update center install whatever drivers they have, install DX9, and then install the latest drivers for your card afterwards.

Odd problem for a new card to have though.

Posted: November 10, 2006, 1:27 pm
by Boogahz
I have never experienced anything like that while installing/updating DirectX, but I have seen it on drivers. The warning can throw a person off, but you can still choose to install anyhow. I remember going through it a few times before actually noticing that it could be skipped. There was something about the pop-up box that made it seem like you actually could not complete the install...annoying.

Posted: November 11, 2006, 12:57 am
by Gemily
Though it was the Nvidia card, so uninstalled it, but still not able to upgrade DX9.
Called the card manufacturer, upgraded video driver, still no go. Tech said it seemed it was aDX9/Windows problem, sugested I call Microsoft.

Grrrrr I had to pay to get Microsoft Tech to help me. It worked though. After an hour of trying different things, finaly ended up renaming the Catroot2 files and that did it. Tech said something in it might have been corrupted.Totaly lame though, having to pay Microsoft for help fixing one of their own shit. *grumble*