To Carielf

from Stardock Forums
A question... I sent you a save file from my game that I submitted but which failed to register in the Metaverse a few days ago, but haven't heard anything. What's your policy regarding this sort of thing, should I expect a response? I am concerned about what happens to the possibility of that game being submitted if I submit another one. I'm also wondering if I will have the same problem with the next game I submit.

What's the scoop? A response of some sort would be appreciated.
302 views 5 replies
Reply #1 from Stardock Forums Top
She will answer to you, but I think that hey all are gone for the holidays. ;) Merry Christmas.
Reply #2 from Stardock Forums Top
She will answer, but to help when she gets back it might help to keep this on the first page of the forum.
Elemental: Reforged
Reply #3 from Stardock Forums Top
I submitted another game, this time it seems to have worked. No sign of my previous game though.
Reply #4 from Stardock Forums Top
Hi CariElf,

My Current Version of Stardock Central = 1.21.241 Build 37

My Current Version of GalCiv = 1.13


Each time that I try to Install the Beta of Altarian Prophecy SDC crashes to desktop. Below is the smartexception file generated.

As usual any help will be appreciated.

Elrikk


Stardock SmartException Logging Information
-------------------------------------------

OS Version : Windows XP
Video Card : NVIDIA GeForce3 Ti 500
Application Exception code: C0000005 ACCESS_VIOLATION
Crash Addr: 002E7266 02:02BCD350 Ž

Processor Registers (x86):
EAX:00000081
EBX:000203A4
ECX:00000000
EDX:0000000F
ESI:73DD8E76
EDI:00000000
CS:EIP:001B:002E7266
SS:ESP:0023:02BCD728 EBP:02BCD750
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00010216


Current Application Call Stack:

Addr Frame Logical addr Module Name
---------------------------------------------
002E7266 02BCD750 0000:00000000
77D6CDE5 02BCD7BC 0001:0002BDE5 D:\WXP\system32\USER32.dll
77D57137 02BCD804 0001:00016137 D:\WXP\system32\USER32.dll
77D5B763 02BCD848 0001:0001A763 D:\WXP\system32\USER32.dll
77D6CCD4 02BCD8B0 0001:0002BCD4 D:\WXP\system32\USER32.dll
77D45CD6 02BCD8E0 0001:00004CD6 D:\WXP\system32\USER32.dll
77D45CF5 02BCD900 0001:00004CF5 D:\WXP\system32\USER32.dll
73DD20F2 02BCD920 0001:000010F2 D:\WXP\System32\MFC42.DLL
73DD1902 02BCD9C0 0001:00000902 D:\WXP\System32\MFC42.DLL
73DD1CEA 02BCD9E0 0001:00000CEA D:\WXP\System32\MFC42.DLL
73DD1C73 02BCDA40 0001:00000C73 D:\WXP\System32\MFC42.DLL
73DD1BFB 02BCDA5C 0001:00000BFB D:\WXP\System32\MFC42.DLL
73DD1BBA 02BCDA88 0001:00000BBA D:\WXP\System32\MFC42.DLL
77D67AD7 02BCDAB4 0001:00026AD7 D:\WXP\system32\USER32.dll
77D6CCD4 02BCDB1C 0001:0002BCD4 D:\WXP\system32\USER32.dll
77D456B6 02BCDB58 0001:000046B6 D:\WXP\system32\USER32.dll
77D581F1 02BCDBB4 0001:000171F1 D:\WXP\system32\USER32.dll


Debug information for each stardock app follows ....


~SDC~
Reply #5 from Stardock Forums Top

Zed, I responded to your e-mail.

Elrikk, have you gotten this resolved?  There was another thread (you might have to go back a few pages) about this where the sdc developer was responding.