@Hengis Stone & MithranArkanere
I just tried it, it does still work with today's update for me.

The thing to remember with update is. If you launch gw outside the utility, gw.exe will only update the path which is currently set in the registry. The surest thing to do with updates is update the different gw copies one at a time by launching it inside the utility. During updates, the gw client opens and closes multiple times, so it is safest to let one copy finish updating before launching another copy. (to ensure the opening/closing update windows use the right path)

This would have been vastly simplified if gw.exe would just use the gw.dat that is in the same folder. Unfortunately, it takes whichever folder is set in registry.

Let me know if you still have issues. And please tell me the OS so I can try to duplicate the problem.

@jeanne
There are instructions in the readme.txt file. If those are not clear enough, I will try to get a step by step picture tutorial up.

From readme.txt:

Q: How do I use Texmod with this?

A: To launch a Texmoded copy:
# Select the copy you will be launching and click "Set Registry Path"
# Click "Clear Mutex"
# Open Texmod and launch the copy

Quote:

Originally Posted by jeanne p

Hi all,
thanks a lot for this programm.
I have no problem to use it with 2 accounts.
But i'm totaly unable to run the accounts using texmod.
could someone explain me step by step haw to do?

I am using the 64 Bit with Vista x64, I had a few problems with it at the start, in the end I solved the problem by moving my original Guild Wars folder to another folder name (I tried the registry buttons), but the GW copy kept trying to read gw.dat from the original GW folder.

Then both the Copy and the "Original" worked.

Once again, brilliant program, makes life so much easier.
Thanks for your hard work.

I did update each copy by launching them from the utility. As I said, after the relaunch of the update, it started going for the original install path, completely ignoring the copy paths. Now all copies launched with the program always go for the original copy, as if the program no longer updates the registry path.

I've checked the registry, and it seems to change the CURRENT_USER path, but not the LOCAL_MACHINE path.

The unlock feature doesn't work, either, the second copies just close without error messages or warnings of any kind.

The OS is WinXP Home SP3.

EDIT: Fixed it. I just deleted the CURRENT USER path. Once that one is removed, the client goes only for the LOCAL MACHINE path.

It seems the loader doesn't check alternate paths and goes just for the local machine one, so if a computer has multiple users that run multiple different copies of the game, things can get a bit mixed up.

Thanks for the very useful info! Let me know if this makes sense, I'll have this in for the final release.

This is currently the behavior of how it reads/writes to registry.

1. Check for path key in LOCAL_MACHINE
2. If it does not exist, check for key from CURRENT_USER
3. Read/Write the key

It assumes that if the local_machine key exists, that would be the one that gw.exe uses. It seems that assumption is false. It seems gw.exe defaults to the CURRENT_USER key first? I could swap the order and check for the CURRENT_USER key before LOCAL_MACHINE if CURRENT_USER is the first one gw.exe checks/uses.

The other option is to of course, try to write values to both LOCAL_MACHINE and CURRENT_USER to be even more sure.

i have a question concerning this. i've been using gwx2 for a couple weeks now and love it but i have noticed i get horrid lag spikes at times and my cpu locks up if i have too much stuff running (which doesnt make sense to me cause my rig is pretty strong).

has anyone experienced the same with multi launch? if not, i'm definately going to try it out as it sounds superior to gwx2. i'm mostly concerned about the increase in lag spikes and network errors. they seem more frequent to me than people i play with but i dont know if gwx2 is a source of blame. just wondering how multilaunch would handle the frequency of spikes..

Running multiple gws is taxing on any system (CPU/HD/Memory/Vid card almost all get double work).

If you had latency/perf issues in GWx2, you will probably see the same issue using any other launcher. I doubt GWx2 is really doing anything intensive in the background.

Now the way that this launcher work is. If you use the specially made shortcuts, it starts up in the background, ensures environment is ready to launch another gw, launches gw, and immediately closes itself. The launcher does not stay OPEN in the background so it should not be adding any extra burden on the system. Also, if you use the launcher gui directly, you may close it at any time.

I recommend examining your system for spyware, making sure you have a good anti-virus package/firewall (I recommend NOD32 from eset) which isn't overtaxing your system in the background. An excellent program to see what is using your system resources is: Process Explorer.

If you do want to give this launcher a try, please be aware that since gw2x patches/modifies the gw.exe file, you may need to get a clean version from arenanet before the launcher will work. (just run gwsetup long enough to retrieve a fresh exe)

Thanks for the very useful info! Let me know if this makes sense, I'll have this in for the final release.

This is currently the behavior of how it reads/writes to registry.

1. Check for path key in LOCAL_MACHINE
2. If it does not exist, check for key from CURRENT_USER
3. Read/Write the key

It assumes that if the local_machine key exists, that would be the one that gw.exe uses. It seems that assumption is false. It seems gw.exe defaults to the CURRENT_USER key first? I could swap the order and check for the CURRENT_USER key before LOCAL_MACHINE if CURRENT_USER is the first one gw.exe checks/uses.

The other option is to of course, try to write values to both LOCAL_MACHINE and CURRENT_USER to be even more sure.

Yup. It's the other way around for the GW.exe
1.- The Client checks the current user path first.
2.- If no current user is found, then it goes for local machine.
3.- If no local machine is found, it prompts a install message. You set a path (the executable path by default), creates a local machine path, copies/moves the client to that path and resets.
4.- After resetting, if a gw.dat exists in the install path, you have a GW.dat, it will work just like it always does, the gw.dat version is checked, and if no updates are available, the game starts.

I currently don't know that triggers a current user entry to be created. It happened during one update, and only that update.