Could not initialize Direct3d

[EDanaII]

I just recently upgraded to v4.6. Everything works fine except the interface. Whenever I start that, it fails with the message "Could not initialize Direct3d." Version 4.3 worked with no problems. Reinstalling to 4.3 and even wiping the hard drive and installing XP from scratch does not fix the problem.

Anybody got any clues as to what's going on. I'd like to be able to use my software again.

And, for the record, I'm using an old beta version of XP, since any other version of XP caused a BSOD, never allowing me to even start XP. But as I mentioned before, everything worked fine until I installed v4.6.

Thanks in advance,
Ed.

[ZetaVu]

I don't think the beta xp versions have the correct directx, in fact I would assume they are expired and shouldn't work at all. (plus how do you get them to sp2?) Can you install 4.3 on your beta and get that to work? I would guess your issues are video card related, and I'd start by looking into the drivers or maybe new hardware. If you can get 4.3 to work on it, that might be as good as it gets.

[EDanaII]

All of this happened AFTER the v4.6 installer installed the latest DirectX, so the DirectX should be up to date. I've been using all BTV versions since version three without issue other than a few hiccups, and I believe they have been installing the appropriate DirectX versions too. In fact, I'm wondering if the older installers aren't fetching the most current DirectX and that is somehow related to my problem.

Yes, I suspect this is graphics card related as well, but when the initial problem occured, I installed the latest drivers for my nVidia card, and the problem still persisted.

Ed.

[ZetaVu]

Can you fix it by reverting back to 4.5 (or a clean 4.5 install)?

[ClamsTheCat]

Originally Posted by EDanaII

And, for the record, I'm using an old beta version of XP, since any other version of XP caused a BSOD, never allowing me to even start XP.

This sentence is a bit troubling. You are saying that your computer is crashing when you run a new version of XP? That sounds like hardware trouble my friend! If you have another computer try to troubleshoot the problem (try the video card). Especially since you got the problem after installing a new DirectX. You can also try new drivers.

The inability to run a new version of windows without crashing does not bode well when it comes to running BTV. You say you had no problems before 4.6, but if that is true then why were you running the old XP beta? It sounds like you had a problem when you installed a recent version windows, but then just ignored it once you got it working with the old version of XP. Out of sight out of mind?

[EDanaII]

@ ZetaVu

I reverted to version 4.3, which is the last known good version that worked. It now gives me that very same error.

Ed.

[ZetaVu]

Then it's probably not 4.6, something got changed on your system. That's why I ghost my OS before any installs. Only thing I can think of at this point is to wipe, reinstall xp, reinstall 4.3, see if that works, otherwise something on your hardware that was causing the BSOD finally gave out.

[EDanaII]

The problem is, as I stated in my first post, I already did a wipe and reinstall of everything and still I get the "could not initialize Direct3D" error.

To make matters more annoying, according to dxdiag: "no problems found," including Direct3D. Running the tests, the box with the green direct x logo displays and rotates without any problems. And it's direct x 9b that is installed.

I wish I had a clue.

Ed.

[ZetaVu]

I thought Beyondtv needs directx 9c, summer update installed, in fact the installer should install that automatically if you don't have it (or maybe that's Beyond Media?) Try installing the latest 9c, see if that does the trick?

[EDanaII]

OK, here's the deal. This happened when I first installed 4.6, and it keeps happening every time I try to install DirectX. When the DirectX installation starts up, it begins to copy files and instantly completes. By instantly, I mean instantly: too fast to actually copy any sizeable amount of files. Something appears to be fooling the installation into thinking it's finished, maybe even before it starts.

The problem is, I even tried some software that uninstalls directX. What it actually does is revert the system to directX 8.1 but, when I then try to install directX 9.0c, I get the same result. It finishes instantly and says it is complete. Dxdiag then reports that 8.1 is still installed.

Not only do I still need clues, I'm getting damn frustrated.

Ed.

[ZetaVu]

That is beyond me. I'd try googling directx install issues or contact SS tech support, see what they say. Might be an issue with your xp beta.

[EDanaII]

I'm beginning to think it's a problem with the beta too, but I'm left to wonder why it wasn't one until I installed 4.6.

Ed.

[ZetaVu]

4.6 changed something that made it more obvious, or could just be coincidence, something finally gave out