major lock up

from Stardock Forums
anyone else getting a major lock up when either attempting to exit to menu from in game or launching a new game after playting and saving an old one for a bit? I am. I have to hard reeboot when this happens - often as control-alt-delete is totally locked oyut as well. System is totally catatonic when this happens. I need to do some more testing shutting down TSR's but I have not cracked it yet

I am running winME with a Gforce2 on an Athlon 900 Asus motherboard
123 views 7 replies
Reply #1 from Stardock Forums Top
strange

just tried exiting the game back to win - normal exit, locked up on game main screen again.
In my attempts to exit I pressed and held down the tab key and three buttons (poss from my obscured desktop?) break through.
A row of three grey windows-esque grey buttons stating 'abort' 'retry' and 'ignore' appear flickering through the game screen, unfortunately only the buttons appear no contextual message is breaking through.
Reply #2 from Stardock Forums Top
Same problem here, but I have found that after clicking "quit game" on the option menu if I wait a couple of seconds and press the space key once it goes right to the desk top. Since SE isn't working I can't tell if it causes a trap, but it works. Otherwise, the game does not exit and Alt-Tab, Ctrl-Esc, and C-A-D do nothing.

In addition, after using the space key to complete the quit, the debug file has the following two lines as the last lines. None of the other usual cleanup lines appear:
--------------
Debug Message: Posting WM_CLOSE message.
Debug Message: GameUninitialize start
-----------------------

Cheers,
Jack
Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from Stardock Forums Top
What's seems to be happening is that something is crashing while GalCiv is trying to shut down, and the dialog box isn't popping up on top because of some display bug. Hitting the space bar selects the default button, which should be 'abort.'
Reply #4 from Stardock Forums Top
You may be right. Since the SE is still failing on my system it could be that SE is trynig to display the first crash and then aborting when I hit the space key. This might also explain why I don't see any GalCiv.CRA files afterwards. Can someone suggest a "blind" response that might gather crash data - that is, if I can't see a SE display what keys could I press to cause SE to at least store the exception data to disk?

Thanks,
Jack
Reply #5 from Stardock Forums Top
thanks for the spacebar tip guys - will try it soon.

somethig about 'abort' 'retry' and 'ignore' is bugging me - why is something in the back of my mind trying to tell me something?

B*gger.

s >:(
Reply #6 from Stardock Forums Top
'Can someone suggest a "blind" response that might gather crash data - that is, if I can't see a SE display what keys could I press to cause SE to at least store the exception data to disk?'

If it is indeed related to SmartException, you could try hitting 'r,' which would generally be the keyboard shortcut for a 'retry' button.

Just for reference though, I see it when I close GalCiv from in a game, and I haven't tried to restart SE yet after removing it to copy in that patch. It seems to be something in GalCiv's shutdown code.
Reply #7 from Stardock Forums Top
some developer comments would be handy ;)