ETA or ATA on the new Allegiance download? (that works on Net 3.5)

TrashMan · Post by **TrashMan** » Mon Apr 14, 2008 6:15 pm

Was wondering if anyone knows and Aproximate Time of Arrival of the new packed Allegiance download? The new update allegedly works but one has to apply it on the already installed Allegiance...and you can't install it if you don't have Net 1.1..
So I'm waiting patiently for the new 90Mb (or so) of pure goodness /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

Grimmwolf_GB · Post by **Grimmwolf_GB** » Mon Apr 14, 2008 6:30 pm

Install 1.1. ?

TrashMan · Post by **TrashMan** » Mon Apr 14, 2008 11:17 pm

I kinda need 3.5 installed...I have some projects and a few Beta phase games that require it to run.

ImmortalZ · Post by **ImmortalZ** » Tue Apr 15, 2008 5:18 am

You still need .NET 1.1. The new ASGS update makes the program compatible to .NET 3.5, but it still runs on .NET 1.1. The .NET 2.0 based ASGS is still in testing.

Icky · Post by **Icky** » Tue Apr 15, 2008 5:25 am

TrashMan wrote:QUOTE (TrashMan @ Apr 14 2008, 02:15 PM) Was wondering if anyone knows and Aproximate Time of Arrival of the new packed Allegiance download? The new update allegedly works but one has to apply it on the already installed Allegiance...and you can't install it if you don't have Net 1.1..
So I'm waiting patiently for the new 90Mb (or so) of pure goodness /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

Two Weeks™

ogorass · Post by **ogorass** » Tue Apr 15, 2008 7:47 am

TrashMan wrote:QUOTE (TrashMan @ Apr 15 2008, 01:17 AM) I kinda need 3.5 installed...I have some projects and a few Beta phase games that require it to run.

How exactly is this stopping you from installing 1.1? .NET Framework versions are separate runtime enviroments, they can coexist with eachother on one system. I have 1.1, 2.0, 3.0 and 3.5 installed on my work lappy: only problem used to be the 0xc0000007b error in ASGS. Download .NET 1.1, Service Pack 1 for .NET 1.1 install both, rebooting between installs. After that, go to Windows Update: Hotfix for .NET 1.1 SP1 is now available. Install it and reboot. Now you are set to play Allegiance without having to wait or interrupting your work.

madpeople · Post by **madpeople** » Tue Apr 15, 2008 12:19 pm

.net 1.1 and 3.5 are different things. they don't overwrite each other

you don't upgrade your .net from 1.1 to 2.0 to 3.0 to 3.5, you can use them all together at the same time.

if you install .net 1.1 you won't lose the .net 3.5

install .net 1.1, install allegiance, copy over the new asgs

TrashMan · Post by **TrashMan** » Tue Apr 15, 2008 5:52 pm

Strange...installed 1.1, SP1 for it and the windows security update for Net 1.1. SP1

Then I installed the game (and got a 00000b7 error) so I installed the asgs patch

Nothing happens when I enter the username and password..I get this in the console:

• Unable to manage previous exit state.
• Object reference not set to an instance of an object.
• Initializing
• Reading Settings
• Unable to Read Registry Values
• Object reference not set to an instance of an object.
• Checking Installation
• Checking OOBE
• OOBE Failed.
• Object reference not set to an instance of an object.

ogorass · Post by **ogorass** » Tue Apr 15, 2008 8:12 pm

Registry entries for Allegiance are broken. Did you move your Allegiance folder? Did you meddle with registry and/or run any registry cleaner programs?

Easiest way of fixing this is to uninstall Allegiance completely, reboot, reinstall Allegiance, update ASGS manually and play. More complex way is to manually fix registry entries. Take your pick.

TrashMan · Post by **TrashMan** » Tue Apr 15, 2008 8:41 pm

Nope..doesn't work.. I even though SpyBot Search and Destroy might have to do something with it since it popped a warning window because of registry changes, but I allowed them.

I tried re-installing with SPSDS turned off.

Nothing. Still won't work. I get the same error.