Free Allegiance Forums

Pook wrote:QUOTE (Pook @ Aug 2 2006, 03:34 PM) Ok I give up.

Here's the latest ASGSClient and ASGSUpdate, as well as the R2 Builds of Allegiance.exe and AGC.dll

Put them all in your Allegiance directory and you should be good to go.

/ninja.gif" style="vertical-align:middle" emoid=":ninja:" border="0" alt="ninja.gif" />

Hi pook,

The autoupdate didn't work for me either, I did a manual update and that hasn't worked either

Here is what the log file had to say:

2/08/2006 9:38:20 PM: Initializing
2/08/2006 9:38:20 PM: Reading Settings
2/08/2006 9:38:20 PM: Logging Option: SIMPLE
2/08/2006 9:38:20 PM: Loading MRU Callsigns
2/08/2006 9:38:20 PM: Loading Form Position
2/08/2006 9:38:20 PM: Checking Installation
2/08/2006 9:38:20 PM: Ready
2/08/2006 9:39:20 PM: Checking for system updates
2/08/2006 9:39:20 PM: Checking for existing processes
2/08/2006 9:39:20 PM: Saving Settings
2/08/2006 9:39:20 PM: Saving MRU Callsigns
2/08/2006 9:39:22 PM: Checking connectivity
2/08/2006 9:39:22 PM: Using Port: DirectPlay
2/08/2006 9:39:24 PM: Checking ASGS Client Version
2/08/2006 9:39:24 PM: Client Version: 127
2/08/2006 9:39:24 PM: Server Version: 127
2/08/2006 9:39:24 PM: Securing Installation
2/08/2006 9:39:25 PM: Validating Installation
2/08/2006 9:39:26 PM: Preparing Key
2/08/2006 9:39:26 PM: Key Generated
2/08/2006 9:39:26 PM: Connecting to ASGS Server
2/08/2006 9:39:26 PM: Authenticating
2/08/2006 9:39:27 PM: Ticket Received
2/08/2006 9:39:27 PM: Return Value: 0
2/08/2006 9:39:27 PM: Callsign: Achtung@CDT-B(9)
2/08/2006 9:39:27 PM: Authenticated successfully
2/08/2006 9:39:27 PM: Checking messages
2/08/2006 9:39:28 PM: Return Value: 0
2/08/2006 9:39:28 PM: No messages
2/08/2006 9:39:28 PM: Checking polls
2/08/2006 9:39:29 PM: Return Value: 0
2/08/2006 9:39:29 PM: No polls
2/08/2006 9:39:29 PM: Logged In
2/08/2006 9:39:29 PM: Launching Allegiance
2/08/2006 9:39:52 PM: Unable to launch Allegiance.
2/08/2006 9:39:52 PM: Allegiance did not launch in the time allotted.
2/08/2006 9:39:52 PM: Beginning Logout
2/08/2006 9:39:52 PM: Closing processes

Crashes on the closing processes line


Any help would be appreciated

Thanks

Achtung

As an aside, last night aarm and blake both were having problems with it not updating properly. They renamed got latest build etc, however the only thing that worked was to send them my copy of allegiance.exe.

Achtung wrote:QUOTE (Achtung @ Aug 2 2006, 09:42 PM) Here is what the log file had to say:

2/08/2006 9:38:20 PM: Initializing
2/08/2006 9:38:20 PM: Reading Settings
2/08/2006 9:38:20 PM: Logging Option: SIMPLE
2/08/2006 9:38:20 PM: Loading MRU Callsigns
2/08/2006 9:38:20 PM: Loading Form Position
2/08/2006 9:38:20 PM: Checking Installation
2/08/2006 9:38:20 PM: Ready
2/08/2006 9:39:20 PM: Checking for system updates
2/08/2006 9:39:20 PM: Checking for existing processes
2/08/2006 9:39:20 PM: Saving Settings
2/08/2006 9:39:20 PM: Saving MRU Callsigns
2/08/2006 9:39:22 PM: Checking connectivity
2/08/2006 9:39:22 PM: Using Port: DirectPlay
2/08/2006 9:39:24 PM: Checking ASGS Client Version
2/08/2006 9:39:24 PM: Client Version: 127
2/08/2006 9:39:24 PM: Server Version: 127
2/08/2006 9:39:24 PM: Securing Installation
2/08/2006 9:39:25 PM: Validating Installation
2/08/2006 9:39:26 PM: Preparing Key
2/08/2006 9:39:26 PM: Key Generated
2/08/2006 9:39:26 PM: Connecting to ASGS Server
2/08/2006 9:39:26 PM: Authenticating
2/08/2006 9:39:27 PM: Ticket Received
2/08/2006 9:39:27 PM: Return Value: 0
2/08/2006 9:39:27 PM: Callsign: Achtung@CDT-B(9)
2/08/2006 9:39:27 PM: Authenticated successfully
2/08/2006 9:39:27 PM: Checking messages
2/08/2006 9:39:28 PM: Return Value: 0
2/08/2006 9:39:28 PM: No messages
2/08/2006 9:39:28 PM: Checking polls
2/08/2006 9:39:29 PM: Return Value: 0
2/08/2006 9:39:29 PM: No polls
2/08/2006 9:39:29 PM: Logged In
2/08/2006 9:39:29 PM: Launching Allegiance
2/08/2006 9:39:52 PM: Unable to launch Allegiance.
2/08/2006 9:39:52 PM: Allegiance did not launch in the time allotted.
2/08/2006 9:39:52 PM: Beginning Logout
2/08/2006 9:39:52 PM: Closing processes

Crashes on the closing processes line
Any help would be appreciated

Any help would be appreciated /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Still having the same problem, allegiance is unable to launch and by the look of it the agsclient is unable to stop the allegiance.exe, for that matter neither the task manager, nor any of my adware programs that can kill processors can stop it either. Very weird, I am not experiencing any other problems with any other application. I have uninstalled, then reinstalled allegiance, even taken a copy of a friends and plonked it over the top yet all still have the above result.

Here is a summary of my machine any help would be appreciated /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Operating System Microsoft Windows 2000 Professional
OS Service Pack Service Pack 4
Internet Explorer 6.0.2800.1106 (IE 6.0 SP1)
DirectX 4.09.00.0904 (DirectX 9.0c)
Computer Name ****
User Name ****

Motherboard:
CPU Type AMD Athlon XP, 1100 MHz (11 x 100)
Motherboard Name ECS K7VTA3 v3 (5 PCI, 1 AGP, 1 CNR, 3 DIMM, Audio)
Motherboard Chipset VIA VT8367 Apollo KT333
System Memory 1024 MB (DDR SDRAM)
BIOS Type Award (08/02/02)

Display:
Video Adapter NVIDIA GeForce4 MX 420 (64 MB)
3D Accelerator nVIDIA GeForce4 MX 420

Multimedia:
Audio Adapter Creative SB PCI128 (Ensoniq ES5880) Sound Card
Audio Adapter VIA AC'97 Enhanced Audio Controller

Storage:
IDE Controller VIA Bus Master IDE Controller
Floppy Drive Floppy disk drive
Disk Drive USB 2.0 Flash Disk USB Device (494 MB, USB)
Disk Drive ST340016A (40 GB, 7200 RPM, Ultra-ATA/100)
Disk Drive WDC WD1200JB-00GVC0 (111 GB, IDE)
Optical Drive LITE-ON DVDRW SOHW-1693S
Optical Drive LITE-ON LTR-40125S (40x/12x/48x CD-RW)
SMART Hard Disks Status OK


Network:
Network Adapter Linksys Wireless-G PCI Adapter (192.168.1.64)

USB1 Controller VIA VT83C572 PCI-USB Controller
USB1 Controller VIA VT83C572 PCI-USB Controller
USB Device Logitech WingMan Extreme Digital 3D (USB)


This problem is really starting to get me down.

Achtung

What i dont understand is why Achtung is getting as time out after an update. What was updated as far as the network side of things go?
Everthing seems to work except allegiance.exe accessing what ever it is supposed to talk too.
He has not had to touch his router/modem to play before. but after the update it seems like there is some sort of miscommunication happening causing a time out; PORTs? forwarding? Did any of this change with the update? /ninja.gif" style="vertical-align:middle" emoid=":ninja:" border="0" alt="ninja.gif" />

Actually, it looks like Allegiance does not launch fast enough.
Try the following:
Open ASGS, do NOT sign in.
Open Allegiance without the ASGS shortcut.
Wait for it to launch.
Close Allegiance.
Hit login as fast as possible.

Does that work?

Grimmwolf_GB wrote:QUOTE (Grimmwolf_GB @ Aug 4 2006, 04:38 PM) Actually, it looks like Allegiance does not launch fast enough.
Try the following:
Open ASGS, do NOT sign in.
Open Allegiance without the ASGS shortcut.
Wait for it to launch.
Close Allegiance.
Hit login as fast as possible.

Does that work?

Thanks for the reply, unfortunately the problem seems to be a strange one. Allegiance.exe won't actually launch, if I look at the task manager it just sits in memory using about 60k (of memory). I have tried all of the copies of the .exe avaliable as well as one from sables machine. I have no problem authenicating with the server in fact when I login with agsclient my callsign can be seen listed as logged in. Also agsclient validates my allegience build. Since everything else on my computer runs perectly I'm beginning to think I might simply have a weird "ghost in the machine" problem. I am guessing allegiance is written in VB and it is beyond my understanding why the gui won't launch.

I will wait awhile to see if anyone else has experienced this problem ( I think this is a first) but sadly I feel if I wish to continue playing a machine rebuild is in order:(:(:(.

Suffering wihdrawl


Achtung