Hi,

I purchased GAR - RoA on Steam. When I try to launch it the screen goes black and then crashes with a windows message 'Grand Ages has stopped working'.

Before the add-on I was able to play GAR, whereas now I no longer can :'(

Looking at the event logs I see this error: Faulting application Rome.exe, version 2.1.290.26707, time stamp 0x4b475f00, faulting module Rome.exe, version 2.1.290.26707, time stamp 0x4b475f00, exception code 0xc0000005, fault offset 0x001fc039, process id 0xe04, application start time 0x01caa3997c8f33d3

I've 64bit Vista and gtx285 (drivers up to date). Any ideas? Thanks

(02-02-2010 01:02 AM)Diet H2O Wrote:  Hi,

I purchased GAR - RoA on Steam. When I try to launch it the screen goes black and then crashes with a windows message 'Grand Ages has stopped working'.

Before the add-on I was able to play GAR, whereas now I no longer can :'(

Looking at the event logs I see this error: Faulting application Rome.exe, version 2.1.290.26707, time stamp 0x4b475f00, faulting module Rome.exe, version 2.1.290.26707, time stamp 0x4b475f00, exception code 0xc0000005, fault offset 0x001fc039, process id 0xe04, application start time 0x01caa3997c8f33d3

I've 64bit Vista and gtx285 (drivers up to date). Any ideas? Thanks

Hi check this thread: http://forum.kalypsomedia.com/showthread.php?tid=3662

If you check in the crashlog file in the install directory do you see the cannot parse map thing?

Thanks

Yes - it's the same error:
Module: Rome.exe
Address: 0023:0050ce1e
Function: COULDN'T FIND OR PARSE MAP FILE
Error: Access violation
Remarks:
Read from location 0000006f

Verifying integrity of files has no effect.

Any ideas?

I've installed Windows 7 x64 Ulimate (clean install). Still no difference. Although no it gives no error. I click launch... and nothing.

I can confirm it's a secondary display.

Running Win 7 64 bit as well, with a secondary display.
Turning it off through the nvidia control panel and the game works perfectly. Turning it back on and it causes the crash with earlier mentioned error in the log files.

While I understand it can be problematic to run older games on newer hardware, one would guess there could be a fix for this. Especially since the game is still sold through various outlets. Or at the very least attach a warning label "Don't buy if you have 2 monitors"

Edit: Woops, this reply was for the other topic, tho I guess it's relevant here as well. Do turn off your second monitor

(22-12-2010 06:27 PM)Belsameth Wrote:  I can confirm it's a secondary display.

Running Win 7 64 bit as well, with a secondary display.
Turning it off through the nvidia control panel and the game works perfectly. Turning it back on and it causes the crash with earlier mentioned error in the log files.

While I understand it can be problematic to run older games on newer hardware, one would guess there could be a fix for this. Especially since the game is still sold through various outlets. Or at the very least attach a warning label "Don't buy if you have 2 monitors"

Edit: Woops, this reply was for the other topic, tho I guess it's relevant here as well. Do turn off your second monitor

Option number 2:
Download the config.lua file from this thread: http://forum.kalypsomedia.com/showthread.php?tid=2746

It will run the game in windowed mode... (I am using it on Grand Ages so its working for this too)...
It works well with both my monitors enabled...

what happened with your primary display, was it enough good at all ?

(22-12-2010 06:27 PM)Belsameth Wrote:  I can confirm it's a secondary display.

Running Win 7 64 bit as well, with a secondary display.
Turning it off through the nvidia control panel and the game works perfectly. Turning it back on and it causes the crash with earlier mentioned error in the log files.

While I understand it can be problematic to run older games on newer hardware, one would guess there could be a fix for this. Especially since the game is still sold through various outlets. Or at the very least attach a warning label "Don't buy if you have 2 monitors"

Can confirm this does indeed work. It sux but it works. Hope they sort out a patch soon, maybe, hopefully...