Black Screen Hang on Start

hasn't worked since re-install

Hi! After a Windows/Impulse reinstall and updating/reinstalling GC2/DA and Twlilight, Twlight doesn't start anymore. It fails on the opening screen, presumably since it cant find the video card according to debug.err, which is c&p'sted.

Debug Message:  Version v2.02 Twilight of the Arnor last updated on: Wed Dec  3 09:43:09 2008
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE SOFTWARE\Stardock\ComponentManager\Drengin.net\GalCiv2UL
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE SOFTWARE\Stardock\ComponentManager\Drengin.net\GC2EU
Debug Message:  Could not query reg key HKEY_LOCAL_MACHINE SOFTWARE\Stardock\ComponentManager\Drengin.net value named Serial No
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE Software\Stardock\Drengin.net\GalCiv2UL
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE Software\Stardock\Drengin.net\GC2EU
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE Software\Stardock\Drengin.net\GalCiv2UL
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE Software\Stardock\Drengin.net\GC2EU
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE Software\Stardock\Drengin.net\GalCiv2UL
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE Software\Stardock\Drengin.net\GC2EU
Debug Message:  Checking DX Version.
Debug Message:  *********DXDiag info follows.*********

 

Display Info
Display device 1:
Device Name: \\.\DISPLAY1
Card Name: NVIDIA GeForce 8800 GTS 512
Manufacturer: NVIDIA
Chip Type: GeForce 8800 GTS 512
DAC Type: Integrated RAMDAC
Key Device: Enum\PCI\VEN_10DE&DEV_0600&SUBSYS_80101462&REV_A2
Display Memory: 512.0 MB
Current Display Mode: 1600 x 1200 (32 bit) (85Hz)
Monitor Name: ViewSonic P815
Monitor Max Resolution: 1800,1440
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.8247
Driver Date: 3/20/2009 00:33:00
DirectX Acceleration Enabled: Yes
 


Sound info
Sound device 1:
Description: SB X-Fi Audio [D800]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_002F1102&REV_00
Manufacturer ID: 1
Product ID: 100
Driver Name: ctaud2k.sys
Provider: Creative
Driver Version: 6.00.0001.1368
Driver Date: 10/8/2008 01:21:50
Type: WDM
Other Drivers:
Acceleration Level: 3
Cap Flags: 0
Min/Max Sample Rate: 0, 0
 


Debug Message:  *********END dxdiag info.*********
Debug Message:  Entering WinMain
Debug Message:  ******* Starting Game Shell *******
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE Software\Stardock\Drengin.net\GalCiv2UL
Debug Message:  Could not open reg key HKEY_LOCAL_MACHINE Software\Stardock\Drengin.net\GC2EU
Debug Message:  Could not query reg key HKEY_LOCAL_MACHINE SOFTWARE\Stardock\Drengin.net\GalCiv2 value named Language
Debug Message:  Going Fullscreen
Debug Message:  Preparing to change display settings.
Debug Message:  Failed to find a device that can start with hardware vp mode.  Trying sw vp.
Debug Message:  No compatible devices found.
Debug Message:  InitializeDirect3D Failed.
Debug Message:  Now Fullscreen
Debug Message:  Shell initialization complete
Debug Message:  GalCiv2 is activated.
Debug Message:  WM_CLOSE message received.
Debug Message:  GameUninitialize start

 

N.B. Both GC2 and DA run fine, and I can get the Twilight launcher to switch chapters and start both GC2 or DA, and all activations are activated (It seems).

I reinstalled directx, installled new forceware betas, no joy! Did the registry dance as well....Halp!

 

4,172 views 3 replies
Reply #1 Top

Is that the extent of the debugg.err?

Have you tried to use the 182.50 forceware drivers that just came out today?  Perhaps something in the 182.47 forceware beta ya had was buggy.

Reply #2 Top

Do you have any other D3D apps running?

Reply #3 Top

<post production snippage>

It all used to work no issues. One thing I have noticed is that PhysX can not be enabled anymore in the control panel (8800 GTS 512) that's not right at all. I'm going to change drivers yet again to see what's up with that.

Edit : Success...uninstalled all three apps then installed new 182.50 Forceware (4/2/09) then installed the three apps and Twilight runs now...(PhysX still not able to be enabled anymore)

Educated guess: Either operator forced different directory install locations caused registry confusion (unlikely) or the firewall/defense permissions got confused/revoked or not enabled at the right time duirng installation and caused problems at the inital runtime for Twilight (more likely).

Yay! Space 4x here I come! Thx all.