Introducing: Guild Wars Multi-Launch

Racerbamf: you're probably logging in with the same account twice. You obviously cannot log into the same account multiple times. The program is meant to run multiple instances of guildwars, but you have to log in with different accounts.

ok im just having one problem atm, iv made 3 folders for guildwars as follows: Guildwars, guildwars02 guildwars 03, as folder names, with their own .dats and .exe's for multilaunch to use.

Now it all worked fine for the first couple of times, until guildwars and guildwars 03's .dats kept being corrupted (as in the launcher would repair the data archive automatically, as well as stuff like:Rangers appearing as white cubes, assassins using daggers as hammers, large white orbs in kamadan)

I have the run multiple instances off 1 .dat unchecked and didnt check it once. iv reinstalled already, and im running windows 7.

Does anyone else know what else i can try? Coping my .dat backup each time is getting annoying :P

Great tool, I commend you for making it so user-friendly and making it so we don't have to copy over the .dat and .exe after every update ^^!

Multi-Launch.
- Easy to use
- Multiple Texmodded copies
- No dragging the .exe after every update
- More than 2 copies can be ran.

<3

It really sounds like you may have bad ram/hd or bad bios settings. If .dats are being repaired by gw.exe automatically, that means gw.exe is having trouble writing/reading data to it.

Common issue is heat causing hard drives/memory to go bad. Definitely run a scan on your memory and hd, especially if you have important data on it. HDs are easily replaced but lost document/family photos are not.

cool thanks it works

The thing is, it only did this after I used multi launch, iv reinstalled windows and its working fine now, without multilaunch that is, not gna try it again for a while,or at least till the full windows 7 is out.

Multilauncher may indeed be the catalyst (higher load on system io from multiple gws) but I would still give your memory/hd a good scan (http://www.hdtune.com/, http://www.memtest86.com/) when you get the chance. The reason I mention this is I've had first hand experience of how badly it can suck to lose photos/documents which you really cannot retrieve again in case of hd going bad.

When there are multiple gws running, the things that get stressed alot are hard drives and memory.

more gws loaded = more memory being used (increases heat). same applies for hd. heat in general is really bad for electronics.

Hey imkey - now you've got this to a pretty stable build, can you do us an open source version of Texmod that doesn't throw AV into fits and bluescreen Win7?

Hehe

I had everything working perfectly fine pre-update, but now I'm encountering (I believe) the same problem as Mithran. I updated both copies of GW through the GWML though. Now, I'm not really a savant when it comes to the intricacies of working with anything computer-related, so I'm not completely sure what exactly Mithran did to fix the problem. That being said, what should I be doing?

NOTE: I'm running Windows Vista Home Premium SP1

What MithranArkanere did was delete a registry key for when gw reads from hkey_current_user instead.
This is not necessary in the final v0.5. The final v0.5 currently sets both paths.

If you are running the final v0.5 release, the other thing you can try is running as admin. (right click->run as admin)

If you want the details, read a few posts back about the scenarios.

Sweet tool. A bit light on the instructions in the readme, but it works great with XP Pro 64.

okay i am dumb founded on this. i have tried running gwx2 and only one copy opens. i run GWML and i can launch one of them (either one) but i can't open the other. i made two directories. I run it as an admin and i cant do anything.

you need to get a fresh exe from anet if its been modified by gwx2.

it's in a note in the first post

I don't have a google account (to report bugs) so i'll just do it here.

What i've found is that when i have opened any copy of guildwars from the multi launcher, I can't use vent with that version of guildwars selected.

If i launch Guildwars from the default shortcut (i.e. without multilauncher), i can still use vent while i have that guildwars program selected. The problem only happens when i have a guildwars program that i launched from the multi-launch and I have selected at the time. If i am playing on a guildwars that i have launched from the multi-launcher, I have to minimize that copy (and any other guildwars from the launcer) in order for my push-to-talk on vent to work.

My push to talk is mouse button 5 (on G5 mouse) and i checked that i don't have it mapped to any actions on any guildwars accounts.

Any feedback would be great, its a pain in the ass to minimize just to use vent.

Btw, i can also get around the problem with vent by just using "restore down" and unselecting guildwars when i want to speak, so its definitely a problem with the active copy of guildwars (from multi-launch) that i'm on.

I use vent all the time with multiple windows. I have my mouse 5 set to it was well. Using a mx518 with WinXp 32bit.

I am puzzled by why there would be a conflict. Possibly it is from custom logitech software? I did not install any logitech drivers/packages for my mx518.

Also which OS, 32bit/64bit are you using? Are both gws (launched via launcher and regular) ran as admin? Could the gw that was ran as admin not be letting the pushkey thru to vent?

I don't know how the key catcher in vent works. My guess is on the combination issue of different gw behavior when ran as admin and how vent intercepts the keys from OS? If you have logitech mouse software also installed, that might also be catching the clicks.

If you are running Win7/Vista, possibly the security models does not allow non-admin programs to catch clicks from programs ran as admin? If that is the case, try running vent as admin?

Like I mentioned before, gwmultilaunch does not stay active in the background. All it does to the gw.exe process is close a mutex handle which should not alter push-key talk activation behavior in vent.

Oh, after reading your post i realised that i had been running gw multi launch as admin (because of update issues i had before). I just ran it normally (without admin) and it works fine now. thanks

Just wanted to say a big THANKS! for making this. GWx2 will not work on my system despite much effort on my part, but GW Multi-Launch works like a charm on my Vista 32-bit setup. Great job!

Alright, I like the way you did your code. But going through it, I think I missed the part where it interacts with Texmod. I found path supervising, and launching of it, but in that function, it seems to lose all references to it after that. Did I miss something, or does your program work like Matty's loader, where it just checks to see if GW is loading every .00x seconds?

Either way, good job. I look forward to looking through this in a real editor, instead of notepad, as soon as I get not lazy.

Thanks.

The way the system is readied for another guild wars instance is the "kill mutex" button which calls a function that iterates through the nt process list looking at all active guild wars instances. For each instance it finds, it attempts to find/kill the mutex handle which would prevent more gw instances from opening.

Putting the mutex killing functionality in a timer would eat up unnecessary cpu cycles. That mutex does not just get created randomly by guild wars, it only happens during the initialization function when guild wars starts. One just needs to make sure to hit the button once after a new gw instance is created to be ready to launch another.

I would have liked better integration with Texmod but since that is a closed source product and I am not aware of it accepting command arguments, you are correct in assuming that it basically just launches it. It was mainly added as a convenience to the user.

On another note, check out HandleManager.cs. I spent the majority my coding time on that file. Partly due to the fact that it P/invokes into Nt kernel api functions which are not well documented by Microsoft. Had to look at several sources to get the required constants and applicable functions. It contains the core mutex killing code which makes this application possible. All the other code is really just utility and gui.