Free Allegiance Forums

First off, the template followed by the ASGS log:

Windows Version (and Service Packs):WinXP Home, SP1
Processor Speed: 1.6 GHz
RAM: 512 MB PC2100 DDR
Video Card (Make and Model#): ATI Radeon 9600 Pro, 128MB
Sound Card (Make and Model#): Soundmax Integrated Digital Audio.
Connection Type (Dialup, Cable, DSL, other): Fiberoptic LAN 1Mb
Modem (Make and Model#): NA
Router (Make and Model#): NA
Internet Service Provider(company name): Local Company
Location(State/Province/Locality, and Country): Bristol, VA, USA

• Initializing
• Reading Settings
• Logging Option: SIMPLE
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• Ready
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: HTTP
• Checking ASGS Client Version
• Client Version: 136
• Server Version: 136
• Securing Installation
• Validating Installation
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 0
• Callsign: Perihelion(15)
• Authenticated successfully
• Checking messages
• Return Value: 0
• No messages
• Checking polls
• Return Value: 0
• No polls
• Logged In
• Launching Allegiance
• Active
• Checking In
• Return Code: 0
• Check-in succeeded
• Last Check-in: 9/30/2006 12:43:01 AM
• Allegiance exited with code: 128
• Creating Crashfile
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out


Now I logged into a game a few days ago just fine. There is no router involved and I've never had connection issues before, at least not like this. I can log into the lobby and when I try to join a game, it will get to "joining mission" and sit there for a few seconds and then dump me to desktop.

*edited in the template. Sorry bout that. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Azman!

Could you complete the template for us? We shall get you playing yet! Also, maybe one of the devs can chime in on that exit code.

ImmortalZ wrote:QUOTE (ImmortalZ @ Sep 30 2006, 10:25 AM) maybe one of the devs can chime in on that exit code.

That exit code just refers to the process that Allegiance was unable to complete. In this case the process is ENTER_GAME so that doesn't help much. Have you tried joining different servers? Sometimes you may have issues connecting to a particular server, but I don't think that usually causes Allegiance to crash.

Alright. I think I've made some headway. Apparently Im screwed locally. I downloaded the installer and uninstalled my current Alleg version, but there are some files that cannot be deleted. Specifically, utl205.cvh, utl20abmp.mdl, utl205.mdl, utl205bmp.mdl, VeryCenterHudbmp.mdl, and WEPIN.ogg. Any attempt to delete these files results in a long wait period followed by an error message stating that these files cannot be deleted because of a data error: Cyclic Redundancy Check.
Did some research, but I'm not sure if this is just corruption in the checksums of the files or physical disk damage. Ideas?

CRC error on the HDD is bad. Backup your data ASAP. Your disk might be failing. Do a scandisk and see if that fixes it.

Checkdisk found four unreadable sectors, all sequential and could not continue in read-only mode. Can I get it out of read-only, or would that even help the situation? I've got 2 other hdds I can put in here, but they'd only total about a third of the size....

When you run scandisk from Windows you can select 'fix errors'.
My Computer -> Local Disk -> Properties -> Tools -> Scandisk


You will then get a warning about unable to run right now... Do you want to schedule on the next reboot? Say yes and reboot. Your first screen will be blue while the chkdsk runs.

[[Or you could boot off the CD and run 'chkdsk /f']

Note: BACK UP YOUR DATA. CRC errors are not really that common anymore and could indicate that your HD is failing ... it might be fine, but just be safe. A new HD is $80 ... the data ... well your call...

Thanks guys. I'll post tomorrow and let you know how it goes. Cross your fingers. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Alrighty. Chkdsk "fixed" the issues and I was at least able to install and successfully run (!) alleg. Sweet. I'm putting in another small hdd to back up data to in case this one dies, which would of course not be sweet. Thanks for the help guys. See you in game this evening. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Glad you found a solution to the problem. Enjoy the game and make backups. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />