Installation Orbiter Installation Verification stuck at "Test 3: Checking DirectX"

[jzilla]

I installed Orbiter2010 using the zip installation. Whenever I attempt to start orbiter using orbiter.exe, it starts the Orbiter Installation Verification and the app gets stuck at "Test 3: Checking DirectX". I have DirectX 11 installed, so I'm not really sure what the problem is.

Some system info:
OS: Windows 7 32-bit
CPU: Intel Core2Duo 6600
GPU: ATI Radeon HD 5870
RAM: 3GB of DDR2

What the text file "install" displays

Orbiter installation verification.

w tests to verify a valid
Orbiter installation. Normally, this test needs to be executed
only once after installation. To run it again, execute the
'testinstall' utility in the Install subdirectory.
-----------------------------------------------------
Test 1: Directory structure
	Orbiter root directory:	C:\Program Files\Orbiter2010
	Folder Config	 found.
	Folder Meshes	 found.
	Folder Textures	 found.
	Folder Scenarios	 found.
	Folder Doc	 found.
	Folder Script	 found.
	Folder Modules	 found.
	Folder Flights	 found.
	Folder Html	 found.
	Folder Install	 found.
-----------------------------------------------------
Test 2: C++ runtime libraries
	Runtime libraries ok.
-----------------------------------------------------
Test 3: Checking DirectX

EDIT:
Here is a screen capture of what the Orbiter Installation Verfication looks like.

 

[Nistenf]

How much time did you leave it?
It takes some minutes on my machine, it seems to be stuck but it isn't and finishes eventualy

 

[jzilla]

Left it do its testing for approximately 2-3 hours. Left the house and did some stuff and came back to see nothing had changed.

 

[TSPenguin]

I'd try to install a new directx version, this is general maintenance and might unclog whatever hangs it.
Renaming the orbiter.exe yourself to circumvent the check is always an option too.

[/LazyUserMode]

 

[orb]

If you aren't sure what TSPenguin suggests with renaming orbiter.exe, search on the forums or in Orbiter 2010-P1 project for "verification tool" (with quotes). Almost all the results you'll get will have the answer, and you'll see you aren't the first with this problem.

 

[kevin580]

Oh,yes it takes too long. I don't know why, but I waited 10 minutes for that.

 

[martins]

Note that all the "DirectX" diagnosis part of the verification does is to run

dxdiag.exe /t dxdiag.log

to generate a diagnosis log, and then checking a few lines from the log. (The log can also later be used for problemshooting). You could try to run the same command from a console window to see if that causes similar problems. If that works ok, the only other thing I can think of is that the verification tool may find a wrong version of dxdiag on your system which for whatever reason hangs.

I am slightly puzzled anyway that dxdiag seems to take so long on some systems. Does anybody know if dxdiag tries to do something smart behind the scenes, e.g. getting data via network communication, which may time out?

 

[Nistenf]

Probably. When you execute dxdiag is asks you if you want it to check "digital signatures from the Windows Hardware Quality Labs (WHQL)" (I'm translating from my spanish dxdiag, so maybe in english is a bit different). I don't know if that's still done when doing the log though

 

[orb]

Probably. When you execute dxdiag is asks you if you want it to check "digital signatures from the Windows Hardware Quality Labs (WHQL)" (I'm translating from my spanish dxdiag, so maybe in english is a bit different). I don't know if that's still done when doing the log though

I'd need to install not signed drivers to check that, but in any case checking for WHQL signatures can be disabled by "/whqlff" switch.