Injector v1.2

Being that this is my first injector, I have made it nice to look at without compromising it's performance. The instructions are relatively simple, so please read them before asking a question.

Instructions

1. Run "Injector.exe" as administrator.
2. In the "Target Process" field, type in the process name with or without the ".exe". V1.1 now supports saving process name! V1.2 now supports injecting with or without ".exe" for the process name!
3. Click the "..." browse button to add a .dll file. Repeat this step for every .dll file you want to inject. V1.1 now supports multiselect! V1.2 now saves the dll list!
4. Choose either "Auto Inject" or "Manual Inject". I recommend using manual as it works 100% of the time.
5. (For Manual Inject only) Click the Inject button when you are ready to inject the .dll's into the process. For Nexon games, this is when the HackShield updater (at the bottom right) shows

Download Information

I have attached the Injector as an Installer package and also as a plain zip package. Each package contains 4 files which all must be in the same directory. The .dll extension files are by a company named DevExpress.

Virus Scan Information

The assembly is clean but does come up with false positives. I am currently unsure why the assembly comes up with these false positives but my best guess is that it is because the nature of an injector is usually malicious. (i.e. Injecting viruses into system files.)



Screenshot
[IMG]http://i1000.photobucke*****m/albums/af121/MetaPheonix7/Injectorv12.png[/IMG]

Requirements
.NET 4.0 Framework (by Microsoft)

FAQ
Q. The injector will not open.
A. Please be sure you have installed the .NET 4.0 Framework (by Microsoft) and then try opening the Injector.

Q. The process "Vindictus.exe" is not running.
A. This error occurs if you try to inject the files WHILE Vindictus is NOT running. If that is the case, please remember you need to inject the files during the HackShield loader after opening Vindictus.

Q. The injector does not inject properly.
A. Ensure you are running the injector as administrator by right clicking the file and clicking "Run as Administrator". If you have disabled UAC, I am unsure if the injector would work on your machine.
A2. Ensure the .dll files you are using are not patched or out of date. Try using an alternate injector to rule out if it is the .dll files or the injector itself is the problem.

Q. None of these FAQs answered my question? What do I do now?
A. You can feel free to message me or comment to this thread. Be sure to be as descriptive as possible regarding the problem and give system information such as Operating System, RAM, x32 or x64 bit, and other relevant information towards your problem. This will allow me to answer you quickly.

Update Log
v1.1

• Added function to remember last process that was injected.
• Added multiselect feature when browsing for dlls
• Fixed bug where "Close on Inject" would not save the setting on Injector's next run.

v1.2

• Added function to load dll from application.startup directory.
• Added function to auto remember dlls that were selected.
• Added function to allow "processName" or "processName.exe".
• Added new settings form that saves all settings instantly.
• BUG: Clear Item temporarily does not work properly with saving and loading files... Will be fixed in the next update.

Next Update:
Fix the damn Clear Item bug... I was aiming to fix it before this release but I cannot seem to fix it with the current method of saving/loading last saved dlls.

And Lastly...
If you are kind, please use the "thanks" button if this Injector has helped you.

Feel free to donate:



@Nico