Merge/Compile/Pack the Dll's into Gunz.exe

is there any way i can do that ?
I wanted to merge the fmod.dll , gdiplus.dll anf dbghelp.dll into Gunz.exe to prevent them from being edited

I have tried a few apps to merge but it did not suceed
i tried
molebox
Themidas Xbundler
PGwares Alloy
ILMerge

upload your files then pm me or email me the link o.o

Acheron@apexgaming.net

Encrypt them with your own algorithm, add them as resources, have Gunz call LoadResource(), decrypt said files, and lastly call LoadLibrary for each DLL.

Leaving them unencrypted would make the editing process very, very easy. The other alternative is to have a checksum for each DLL be sent to the server, and virtualize the process of calculating and sending the check.

i want to know how its done
i have added you BetrayedAcheron

@ gWX0
i dont understand your pro language :P
a detailed TUT if possible ??, dont flame me for this pls

yes gWX0 u ar telling this to people who dont understand and NEED it...

Quote:

---

Originally Posted by katsumi

i want to know how its done
i have added you BetrayedAcheron

@ gWX0
i dont understand your pro language :P
a detailed TUT if possible ??, dont flame me for this pls

---

No Tutorials. Learn Assembly (ASM), Some C-Double-Plus (CPP/C++), Understand the GunZ Protocols Properly, and spend a couple of years trying to make your own MRS Compression Algorithm, THEN you can try to Merge the GunZ Client files into your own File System.
Following a Tutorial is basically dumb, you don't understand whatever's going on. The person posting the tutorial could easily be teaching you how to make a backdoor and give him the keys to your computer.

Remove dbghelp.dll, It's not needed.

gdiplus.dll should come with windows, it's not needed.

Have your installer move fmod.dll into the SYSTEM32 directory and gunz will automatically load it from there.

incase if i have a antihack.dll too ?

When a program calls LoadLibrary() it will look for the dll in the following order with it going to the next step if nothing is found in the current step:

1. The directory from which the application loaded.
2. The current directory.
3. The 32-bit Windows system directory. Use the GetSystemDirectory function to get the path of this directory. The name of this directory is SYSTEM32.
5. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
6. The directories that are listed in the PATH environment variable.

Quote:

---

Originally Posted by ThievingSix

When a program calls LoadLibrary() it will look for the dll in the following order with it going to the next step if nothing is found in the current step:

1. The directory from which the application loaded.
2. The current directory.
3. The 32-bit Windows system directory. Use the GetSystemDirectory function to get the path of this directory. The name of this directory is SYSTEM32.
5. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
6. The directories that are listed in the PATH environment variable.

---

ohh thanks so ill make the installer to throw the dll into the WIndows system directory

Quote:

---

Originally Posted by [S]pirit

No Tutorials. Learn Assembly (ASM), Some C-Double-Plus (CPP/C++), Understand the GunZ Protocols Properly, and spend a couple of years trying to make your own MRS Compression Algorithm, THEN you can try to Merge the GunZ Client files into your own File System.
Following a Tutorial is basically dumb, you don't understand whatever's going on. The person posting the tutorial could easily be teaching you how to make a backdoor and give him the keys to your computer.

---

It's "C-Plus-Plus", not "C-Double-Plus"; regardless, the OP only needs to understand basic usage of WinAPI, and some familarity w/working with ASM (Be it MASM-style, nASM, etc).

Quote:

---

Originally Posted by ThievingSix

Remove dbghelp.dll, It's not needed.

gdiplus.dll should come with windows, it's not needed.

Have your installer move fmod.dll into the SYSTEM32 directory and gunz will automatically load it from there.

---

More or less, embedding the DLLs into the executable is slightly more original.

Quote:

---

Originally Posted by gWX0

It's "C-Plus-Plus", not "C-Double-Plus"; regardless, the OP only needs to understand basic usage of WinAPI, and some familarity w/working with ASM (Be it MASM-style, nASM, etc).



More or less, embedding the DLLs into the executable is slightly more original.

---

True, but only slightly =P

Embedding the dll's into gunz.exe will be more secure from ppl Injecting stuffs thru it
thats the reason i needed it

detecting remote threads are easy

Quote:

---

Originally Posted by katsumi

Embedding the dll's into gunz.exe will be more secure from ppl Injecting stuffs thru it
thats the reason i needed it

detecting remote threads are easy

---

Modifying currently running threads to do as desired is easy as well.

Quote:

---

Originally Posted by ThievingSix

Remove dbghelp.dll, It's not needed.

gdiplus.dll should come with windows, it's not needed.

Have your installer move fmod.dll into the SYSTEM32 directory and gunz will automatically load it from there.

---

You just proved to me that I'm dumber than George Bush and his family put together =O
I'm gonna go slit my wrists brb. D: