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?
Thanks.
have a nice day
Jeanne
Introducing: Guild Wars Multi-Launch
jeanne p
Hengis
Had this working for quite a while now and not only do I love it but I can't imagine playing Guild Wars any other way now!! .. but..
After today's update, I've got some strange problems.
I can only get one version to run at a time from the shortcuts.
I've made new copies of my Guild Wars and Guild Wars2 folders.
I've deleted the ini file and reset GWML to point to the new exe files and created new shortcuts.
The weird thing is, if I launch GWML as an administrator, and then launch both copies from within GWML they both work.
Any ideas?
After today's update, I've got some strange problems.
I can only get one version to run at a time from the shortcuts.
I've made new copies of my Guild Wars and Guild Wars2 folders.
I've deleted the ini file and reset GWML to point to the new exe files and created new shortcuts.
The weird thing is, if I launch GWML as an administrator, and then launch both copies from within GWML they both work.
Any ideas?
Ultra Ranger
Thanks for this!
MithranArkanere
Same happened to me. After today's upate, the program no longer can change the registry and gw.exe always looks for the gw.dat in the same pot.
The unlock feature doesn't work either.
The unlock feature doesn't work either.
imkey
@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
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? Thanks. have a nice day Jeanne |
udoh
Brilliant Program.
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 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.
MithranArkanere
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.
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.
imkey
@ Mithran
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.
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.
Hengis
My symptoms are pretty much exactly the same as Mithran.
Launched and updated both clients, but now only one wants to run at a time. The second will not load at all and not give any error messages.
Launching one copy at a time from newly created shortcuts launches the same copy from both shortcuts.
I checked the registry and it seems the same as Mithran, i.e. hkey_current_user is being updated, but hkey_local_machine isn't.
The only difference is that I am using Vista Home Premium, SP1.
Hope this is of some use.
Regards
Hengis
Launched and updated both clients, but now only one wants to run at a time. The second will not load at all and not give any error messages.
Launching one copy at a time from newly created shortcuts launches the same copy from both shortcuts.
I checked the registry and it seems the same as Mithran, i.e. hkey_current_user is being updated, but hkey_local_machine isn't.
The only difference is that I am using Vista Home Premium, SP1.
Hope this is of some use.
Regards
Hengis
imkey
just to clarify, I think there are two different issues here:
Case 1) If the registry path is not set to the right path, you get this when you try to open a second copy with the path still set to the first copy you already launched:
Solution) I will update this for the next release to write to both registry locations (local_machine and current_user) if they exist.
Case 2) If launching the second gw copy just refocuses to the first copy's window, it means the mutex was not closed properly.
Solution) You must right click and run as admin (either the launcher or the specially made shortcut) if that is the case since the first gw.exe was launched as admin.
Case 1) If the registry path is not set to the right path, you get this when you try to open a second copy with the path still set to the first copy you already launched:
Solution) I will update this for the next release to write to both registry locations (local_machine and current_user) if they exist.
Case 2) If launching the second gw copy just refocuses to the first copy's window, it means the mutex was not closed properly.
Solution) You must right click and run as admin (either the launcher or the specially made shortcut) if that is the case since the first gw.exe was launched as admin.
coil
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..
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..
imkey
my experience:
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.
http://technet.microsoft.com/en-us/s.../bb896653.aspx
That will let you narrow down what is hitting your system hardest.
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)
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.
http://technet.microsoft.com/en-us/s.../bb896653.aspx
That will let you narrow down what is hitting your system hardest.
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)
Bubba
Nice, will use this one from now on. It's a lot easier to start the second one mid through instead of having to restart the first client as well.
rickprice407
Many thanks - working fine in Vista
Atrocity
Works like a charm, quick glance at the readme, duplicate gw files and it was a first time go.
Great program, thanks a mill. Really loving the shortcut feature.
Keep up the good work!
Great program, thanks a mill. Really loving the shortcut feature.
Keep up the good work!
Pariah
Been playing around with this. I like that I can put all of my accounts in it and then open any combination of them I want. Very handy program - Great job!
MithranArkanere
Quote:
|
Originally Posted by imkey
@ Mithran
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. |
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.
bilinast
i love u 
thx for the program lol
thx for the program lol
MrGuildBoi
So, this or GWx2?
Racerbamf
I'm able to open two copies of GW, but when I log into the second one, the first one kicks me back to the login screen with a "Code 007" error popup.
I'm using Vista 64 and am running everything as an administrator.
I don't think it's an issue with guild wars, I think it's an issue with the server verifying my account.
Any help would be appreciated.
-Bamf
I'm using Vista 64 and am running everything as an administrator.
I don't think it's an issue with guild wars, I think it's an issue with the server verifying my account.
Any help would be appreciated.
-Bamf
Sjeng
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.
Demandred
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
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
Icy The Mage
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 ^^!
Sierraa
Quote:
|
Originally Posted by MrGuildBoi
So, this or GWx2?
|
- Easy to use
- Multiple Texmodded copies
- No dragging the .exe after every update
- More than 2 copies can be ran.
<3
imkey
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.
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.
Quote:
|
Originally Posted by Demandred
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 |
Feather
cool thanks it works 
Demandred
Quote:
|
Originally Posted by imkey
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. |
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.
imkey
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.
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.
Quote:
|
Originally Posted by Demandred
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.
|
Snograt
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
Hehe
Magi Ultimatus
Quote:
|
Originally Posted by MithranArkanere
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. |
NOTE: I'm running Windows Vista Home Premium SP1
imkey
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.
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.
connor nightwind
Sweet tool. A bit light on the instructions in the readme, but it works great with XP Pro 64.
You just got tomahawked
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.
imkey
you need to get a fresh exe from anet if its been modified by gwx2.
it's in a note in the first post
it's in a note in the first post
Quote:
|
Originally Posted by You just got tomahawked
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.
|
Shred Di
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.
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.
imkey
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.
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.
Shred Di
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
thanks
AnClar
Quote:
|
Originally Posted by imkey
I want to share this project with the community. An open source (GPLv3 license) program to make opening multiple copies of Guild Wars simpler. There is also support for multiple Texmodded Guild Wars and experimental support for opening multiple Guild Wars of the same copy. (no need to make extra copies for quick mule sessions)
|
Killamus
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.
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.
imkey
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.
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.
Quote:
|
Originally Posted by Killamus
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. |