Humble request to unlink accounts

Nice_Guy_ · Post by **Nice_Guy_** » Sun Apr 13, 2008 2:07 am

/blush.gif" style="vertical-align:middle" emoid="

" border="0" alt="blush.gif" />

In his eagerness to dive into a game of Allegiance, my son caused his account on our gaming rig to become linked with mine on my laptop. This is a humble request to be able to PM an admin the account details to unlink them from each other.

As a peace offering (and out of curiosity to see just how tight the duplicate account checking logic was), I was able to finally get Allegiance to install on my Vista SP1 installation and would love to provide details on how I was able to accomplish that feat (it only required about 10 or so uninstalls/reinstalls of .NET and Allegiance before I finally figured it out).

Thanks...and sorry for the hassle.

Ian
(Nice_Guy_)

Post by **FreeBeer** » Sun Apr 13, 2008 2:13 am

I'll post up the request to TE. I understand that he's away for about a week, so it won't happen until he returns and launders his panties. /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />

juckto · Post by **juckto** » Sun Apr 13, 2008 2:28 am

So you want one account to be linked to the comp, and one linked to the laptop?

Nice_Guy_ · Post by **Nice_Guy_** » Sun Apr 13, 2008 4:58 pm

FreeBeer wrote:QUOTE (FreeBeer @ Apr 12 2008, 10:13 PM) I'll post up the request to TE. I understand that he's away for about a week, so it won't happen until he returns and launders his panties. /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />

Thanks, FB. No rush...we've got another box upstairs that I can play on while we get this worked out. I'll make sure my son is well schooled on which accounts are allowed on which machines to ensure this doesn't happen again.

Yes, juckto, as you can imagine, once two different computers get linked together it creates a horribly unfun experience as it becomes impossible to play on both machines at the same time. The MindJedi account (my son's) I will reassociate with the family gaming rig and all the others I will link to my laptop. I do have to say that I was impressed with the strength of the linking which worked no matter what OS I installed Allegiance under (including two separate copies of XP and one Vista SP1 install on my laptop). Clearly the hardware check looks past the OS that you're running, although I'll be if that Linux version of Allegiance ever comes out it'll be harder for it to work there ;-)

Nice_Guy_

Nice_Guy_ · Post by **Nice_Guy_** » Sun Apr 13, 2008 5:03 pm

Oh, and before I forget, 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.
3) Run the .NET cleanup tool (search Google for ".NET cleanup tool") for good measure. May not be necessary but who knows.

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

Yes, this probably should be in a different post. OK...I'm copying and pasting it now :-)

Ian

ogorass · Post by **ogorass** » Sun Apr 13, 2008 9:49 pm

Current ASGS build is compatibile with .NET 2.0 and 3.0 (although written in 1.1 still). Besides, you can't remove .NET 3.5 that comes with Vista SP1 in the way you described.

Nice_Guy_ · Post by **Nice_Guy_** » Tue Apr 15, 2008 12:48 am

ogorass wrote:QUOTE (ogorass @ Apr 13 2008, 05:49 PM) Current ASGS build is compatibile with .NET 2.0 and 3.0 (although written in 1.1 still). Besides, you can't remove .NET 3.5 that comes with Vista SP1 in the way you described.

Oops, you're right. My mistake is described in the other post I put out there. Pook's update is all that's needed. Just make sure you DON'T select "Replace and keep copy of files" when you overwrite the old ASGS files, or the desktop shortcut will stick with the old files that are incompatible with the newer .NET versions.

Post by **Tigereye** » Mon Apr 21, 2008 2:54 pm

NiceGuy,

I'm not sure which callsigns belong to you or which ones belong to your son, so I can't split you guys up just yet.

Send me a PM with the list of your callsigns and his so I know which ones belong on which computer.

Thanks,

--TE