Free Allegiance Forums

I need help. I tried logging in today after having my computer rebuilt by my dad (OPTIMUSPRIME@BS) and all it keep doing at the asgs login in is it acts like its logging in then does this • Initializing
• Reading Settings
• Logging Option: SIMPLE
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• Checking OOBE
• Ready
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 165
• Server Version: 165
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 0
• Callsign: STARSCREAM92(2)
• Authenticated successfully
• Checking messages
• Return Value: 0
• No messages
• Checking polls
• Return Value: 0
• No polls
• Logged In
• Launching Allegiance
• Active
• Allegiance exited with code: x5c9b035fed62d487
• Creating Crashfile
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out
I dont know why it keeps crashing out! But maybe somone else does, even my mother DAWIFE@SPQR says she has never seen this along with my dad opti. He told me i should post it here and see if anyone had any suggestions.

Is Allegiance installed on the system drive?

ogorass wrote:QUOTE (ogorass @ Apr 24 2008, 07:25 PM) Is Allegiance installed on the system drive?

Yes i made sure it was on main c drive forher bro!

Damn, I'm too tired to think straight now. Check out other threads on the x5c9b035fed62d487 thiing. I recall a solution there /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />

ogorass wrote:QUOTE (ogorass @ Apr 24 2008, 08:02 PM) Damn, I'm too tired to think straight now. Check out other threads on the x5c9b035fed62d487 thiing. I recall a solution there /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />

Yeah they mostly said unistall/reinstall. That was the first thing i tried and it still came up with same problemon her pc. I suppose i can try it again. Maybe i need to edit the reg too?

Try this.

Uninstall allegiance
Delete registry keys
Re-install Allegiance to a different directory (IE C:\Program Files\Allegiance rather than C:\Program Files\Microsoft Games\Allegiance)

If that doesn't work, then there may be some other weird things.

I know Allegiance requires:
Direct X
C++ Runtimes
video card drivers
.Net

Perhaps one of them was corrupted. Re-installing them may work.

Copy out your entire Allegiance folder structure to a different folder outside of the normal allegiance folder. I use C:\Program Files\Microsoft Games\AllegCopy

Un-install allegiance.

Delete the non-copied part.

Re-install allegiance.

Launch ASGS from the FOLDER. (Do not use the shortcut, click the exe itself in the system drive)

Run an update/repair from ASGS.

Try to log in.

There's a really weird .NET bug involving the desktop that I keep trying to track down. I'm encountering it myself on occasion across multiple machines, but running the exe directly and updating every time before I sign in seems to help me. I think it's .Net 1.1 SP related.

Let me know how it turns out. I have a few more ideas, but I want to start simple.

Andon wrote:QUOTE (Andon @ Apr 24 2008, 08:31 PM) Delete registry keys

The alleg registry keys are mostly inconsequential unless you're trying to host a server, play the beta, or use a widescreen monitor format that's not automatically included.

Ok well here is what i did try on her computer. And so you know her windows XP pro version was freshly installed a few days ago so the drive is freshly formated also. (and yes it has all the proper updates and no i didnt go any higher than .net 1.0) I had only the net.1 installed like on all our other machines as well. This is what i have done. I removed all .net versions using the special removal tool. I edited the registry, I manually removed anything and everything asgs and allegiance. Hell i even renamed the stupid computer. I also tried putting the program into a diff directory, reinstalling .net and the game several times and diff ways IE..... diff directories and drives etc etc... This one even has me baffled. I may be great at building computers and laptops but this software problem has me stumped I must say! Ok all you software braniacs, this hardware braniac can admit when he is lost and man am i sooo lost with this one. Only other crazy thing i can think of is doing yet another intire computer reformat but that seems a bit overkill. Not to mention its a pain in the arse calling Microshaft everytime one needs to reuse their install disk as well as calling norton antivirus and explaining to them yet again why u need to redownload their antivirus crap for the upteenth time. And i know her account is ok, I tried using her account on a nighbors pc just to make sure her account would work and it logs in fine on any other pc but hers so.................. ANYONE?? BULLER? BULLER? BULLER? lol And yes i tried all that bard suggested also.
Yeah and it still says this
• Initializing
• Reading Settings
• Logging Option: SIMPLE
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• Checking OOBE
• Ready
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 165
• Server Version: 165
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 0
• Callsign: starscream92(2)
• Authenticated successfully
• Checking messages
• Return Value: 0
• No messages
• Checking polls
• Return Value: 0
• Displaying polls
• Vote Recorded.
• Logged In
• Launching Allegiance
• Active
• Allegiance exited with code: x5c9b035fed62d487
• Creating Crashfile
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out

Its not .NET related since its not ASGS that's crashing.

Did you use a fresh installer downloaded from this site in the last few days to install? If yes, did you clean out the old Allegiance directory before you reinstalled?