Free Allegiance Forums

For anybody who's struggling to get ASGS running on a computer that has Vista SP1 already installed, read on. I got this going on a "slipstream" install of Vista + SP1, that already has .NET 3.0 installed.

The secret to installing Allegiance under Vista SP1 is in the "Add Remove Windows Components" portion of the Control Panel. Short steps below:

1) Uninstall anything and everything to do with Allegiance and with .NET in the Add/Remove Programs portion of Control Panel
2) Fire up Add/Remove Windows Components in control panel and uncheck everything in the .NET 3.0 section. Make sure you expand it and uncheck all of the sub-tree items, too, not just the top-of-the-tree item. After you do this, go back and inspect it and make sure that the checkbox for .NET 3.0 is completely cleared.
3) Run the .NET cleanup tool for good measure (search Google for ".NET cleanup tool"...it's on an MSDN blog site). May not be necessary but it certainly doesn't hurt.

Now you should be able to install .NET 1.1, the Allegiance setup program, and Pook's ASGS update (in that order) to get it up and running.

Hope this helps somebody!

Ian
(Nice_Guy_)

You do not have to do this, and this also would not have worked in the past since deactivating .net 3 doesn't actually remove any of the components on Vista. The reason the install works now is because asgs (more specifically xenocode) updated to be compatible with .net 3.0. I tried the "slipstream" install about two weeks ago with no luck. No need to bother with that now though, just install normally and it will work fine (unless the installer is an old version of asgs in which case you would need to manually update, there's a news thread explaining how to do that with a link).

I will give this a try. Thanks for your work.

Thank you very much. I just tried it and now it works. Good job!
I copied your steps into the sticky. I would never have found that section.

Grimm, I have just tested on Vista Ultimate SP1 system. Just copying Pooks update was sufficient to make ASGS work (it was giving the 0xc0000007b error prior to that). The above steps are not necesary as far as i'm concerned.

EDIT: Vista SP1 comes with .NET 3.5 that is not listed in the above mentioned list AFAIK.

Damn, I knew I forgot something... Ok. You can edit the sticky. Update is obviously enough.

kalveth wrote:QUOTE (kalveth @ Apr 13 2008, 01:25 PM) You do not have to do this, and this also would not have worked in the past since deactivating .net 3 doesn't actually remove any of the components on Vista. The reason the install works now is because asgs (more specifically xenocode) updated to be compatible with .net 3.0. I tried the "slipstream" install about two weeks ago with no luck. No need to bother with that now though, just install normally and it will work fine (unless the installer is an old version of asgs in which case you would need to manually update, there's a news thread explaining how to do that with a link).

Well, interestingly I'm pretty darn sure I was trying to install with Pook's update and Allegiance would not run until I unchecked the .NET components in Add/Remove Windows Components. I do have to say that I was installing and uninstalling so many times that it could be that I was fooled into believing that was a necessary step.

Anyway, while my accounts are still linked and I can't play on my laptop anyway, I'm gonna go ahead and uninstall Allegiance and recheck the boxes to see what happens. I'll report my findings shortly.

OK, I have confirmed that kalveth and ogorass are correct. I have rechecked .NET 3.0 components and can still get Allegiance to install and run successfully. It appears that my methods were broken, I was "backing up" the old ASGSClient and ASGSUpdate files into a "backup" folder before installing Pook's updates. Unbeknownst to to me, Vista was kindly redirecting the desktop shortcut to point to the files I had moved to the "backup" folder. This caused me to believe that I was running the new ASGS files when I was actually still running the old ones. Sorry for the confusion!

Thanks for the clarification.