"Machine information package was incorrect."

niklindg · Post by **niklindg** » Sun Apr 12, 2015 6:46 am

Okay, I got the launcher to work!
What I did:
I renamed autoupdate.ds to autoupdates.ds (probably deleting would have done the trick, too)
When launched, the client started two rounds of updates: first round of 325 updates and a second round of 600 updates.
(These updates weren't served to me without that autoupdate.ds trick)
Then it started working.

Strange thing is that I completely reinstalled Allegiance about 7 times, each time manually making sure there's nothing under program files/microsoft games...
(output.log after successful login: http://pastebin.com/TthZZ5iM)

raumvogel · Post by **raumvogel** » Sun Apr 12, 2015 12:23 pm

Wow..good job. Backtrak is going to be very interested in that.He's one of the main programmer wizards here.I'm guessing that it may be unique to you're machine as we haven't had anyone else mention any problems and with the e-mail and the latest install package we should have a fair amount of fresh installs.

Post by **BackTrak** » Mon Apr 13, 2015 3:54 pm

The issue was a lock on the .pdb file which is the debug information for the launcher. When the temp launcher fired up and tried to over-write the previous versions .pdb file, it would crash because the new version also started to load the same .pdb file. The solution was to make a temp .pdb file for the temp launcher to use. This lets the launcher continue the bootstrap update. Because there's a bit of chicken+egg issue here (how to get the next version of launcher out), I've removed the .pdb file from AU for the time being.

Not sure why this just started happening, the .pdb has been bundled with the launcher from the beginning.

Thanks niklindg for the detailed info!

Imago · Post by **Imago** » Thu Apr 16, 2015 6:50 pm

becasue he crashed on an in-game AU update. this has been fixed in R8 if your case

EDIT:
R8 != AllegianceZone

This an ACSS problem.