Hey Hey! Problem summary is in topic title, here are the other details:
Windows Version (and Service Packs): Win2k SP4.
Processor Speed: AMD 64bit (32bit emulation mode) ~2GHz
RAM: 1024MB
Video Card (Make and Model#): ATI X800
Sound Card (Make and Model#): Onboard Realtek AC'97
Connection Type (Dialup, Cable, DSL, other): DSL
Modem (Make and Model#): N/A
Router (Make and Model#): N/A (not an issue here, removed network related stuff below as well)
Which Program (ASGS/Allegiance): ASGS
What Error Message: No error message, just no "ASGS Login Window", this only occurs after ASGS crash, see below.
Comments (What you tried, description, etc):
After I exit Allegiance, the ASGS window is still open and showing 'Logged In', I therefore click the X in the top left to close it. So sometimes, I'd say about 30% of the time, ASGS crashes when I do this, giving me: "This program has caused an error and must be terminated". So no biggie, I do, and in task manager the program successfully terminates after a few seconds. Problem: If I try to launch ASGS again, (after a said 'crash' incident) the program executable will run but the 'Login Window' never re-appears on screen. Task Manager shows that ASGSClient.exe is running (and it is being a system hog too! 90%) but no window. I try to force quit this (it will force quit) and restart again but same issue.
My resolution is to restart my computer a-fresh.
Any help with this? Fluke? ASGS bug? Been playing for about 18 months now and has only really come up over the last few weeks. Best;
Ty.
ASGS Crash After Exit
That's definitely not normal...
It sounds like maybe your .NET installation got goofed.
Try uninstalling all .NET-related hotfixes and the .NET framework itself, and rebooting. Then install it all again from scratch using WindowsUpdate. Grab all the hotfixes etc, and then try ASGS again.
Good luck,
--TE
It sounds like maybe your .NET installation got goofed.
Try uninstalling all .NET-related hotfixes and the .NET framework itself, and rebooting. Then install it all again from scratch using WindowsUpdate. Grab all the hotfixes etc, and then try ASGS again.
Good luck,
--TE
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.
Pook wrote:QUOTE (Pook @ Jul 7 2006, 07:23 PM) Definately something amiss.
ASGS should auto-log you out as soon as the Allegiance process terminates. Try as Tiger suggests.
Last edited by Ligion on Wed Jul 12, 2006 4:18 am, edited 1 time in total.
What do you mean by crashes? Does it give you any error messages? Describe exactly what happens when it 'crashes' on you.
--TE
--TE
Last edited by Tigereye on Wed Jul 12, 2006 4:57 am, edited 1 time in total.
The Allegiance community currently hates their sysadmin because he is doing: [Too Much] [____________|] [Too Little]
Current reason: Removing the PayPal contribute page. Send Bitcoin instead: 1EccFi98tR5S9BYLuB61sFfxKqqgSKK8Yz. This scale updates regularly.

