GunnerMBT

Sadly, I don't have a working version anymore, the old project (the public version) was lost during a major disk failure a few months ago. I have a semi-working version which I might tweak a bit so it's at least useable. Feel free to reverse it all you'd like .

Indeed it is, the project has been put on hold.

As fun as it might sound, nobody will go through your entire code and tell you exactly what to do (at least, they shouldn't). Please provide us with a meaningful part of your code, your problem and what isn't working as expected, what have you tried, etc... If you show no research effort whatsoever, why should we?

Target platform is indeed x86, so I'm not sure why that error occurs. Anyhow, I expect it to be solved with the new version which will also include the revamped GUI (bear in mind that I work on this on my free time, so it might and will take a while).

Sorry for the delay, use this (put it in appSettings).

That does not change the fact, that ovh is leader in europe combining protection, hardware and price. I will test my MG-256 server. I think will only problems with double logging when server is under ddos. Thing with OVH is that unless you pay for VIP support, you'll get pretty much the less help possible. Don't get me wrong, they'll fix any hardware issues in a blink of an eye, but if you need someone to hold your hand, even in the most problematic scenario, you're screwed.

My domain was cancelled for no apparent reason, thus the Tool won't be able to check for the latest version and will throw an exception. Nonetheless you might be able to use it anyway, just ignore the exception. Edit: I've prepared a temporary version which won't check for the latest version, just replace your EterTool.exe with this one.

Which operative system are you running? Which .NET framework version have you installed? Have you tried completely unninstalling all .NET frameworks and install only the 4.5 version (it includes backwards compatibility)? Before reporting bugs, please read the FAQ... I am NOT a wizard, guys.

You should skim-read through this. This is your current scenario: Prepatcher explicitly needs admin privileges, since you're now running in a high integrity level (VS ran as admin) it works fine. It should however prompt you with the UAC message upon hitting the "Debug or Run button", doesn't it? This is confirmed by my second question: To fix this, I'd guess you have to edit the manifest file of the target process. Edit: Also, try what @Sanchez said.

If you run Visual Studio as administrator, and execute the prepatcher within it, does it work? If you run the prepatcher as admin (without VS), does it work? Lastly, if you run the patcher with double-click (normal execution), does it ask for higher level privileges? And you can remove the: procinfo.Verb = "runas" Given that you don't want higher level privileges.

Tiny (not so relevant, but still relevant ) things: -> You should use the standard naming conventions of C# (procinfo should be procInfo, for example). This is entirely up to you, these are just the usual guidelines. -> MessageBox.Show(String.Format("Es gab ein Fehler beim Starten des Patchers! /n" + e.ToString(), "Fehler", MessageBoxButton.OK, MessageBoxImage.Error)); Are you sure you didn't mean: MessageBox.Show(String.Format("Es gab ein Fehler beim Starten des Patchers! /n {0}", e.ToString()), "Fehler", MessageBoxButton.OK, MessageBoxImage.Error); Why would pass all those arguments to String.Format if you have no place-holders? Also, for string concatenation you don't need to use String.Format. -> Might I recommend using another approach on the "logging mechanism"? Regardless of the size of the project, a centralized logging class should be a better approach, one that would enable you to alert the user with custom messages just by changing the message in one place. The main issue now, if I got it right, you don't want to obligate the user to execute as administrator, then why this: procinfo.Verb = "runas"; This will prompt the user with the UAC message, asking for higher permissions...

The average user seems to think the program's UI is a bit too complex given its functionality, and after some thinking, I'm beginning to agree, the main issue seems to be the Main View ([Hidden Content]). Users tend to discard it completely, and use Quick unpack and Quick repack instead. Given this, I'll be completely re-working the UI before even starting new features (reverse file search, virtual file view, new type support, and the prototype files support, etc), for this, I need your help... I want you to tell me how you'd like the UI to be, the best would be a simple scheme/image describing the structure, bear in mind the following: - The idea is to make the main view simpler, thus removing the detailed view from it (this would ofc, be available through a context menu) - Try to think of neat ways to organize all the information (available files to be processed, both packed and unpacked, its properties, etc).

Try with this application.settings file. Also, there still is a bug when packing files (the driver points), I've found where the bug is, I know how to solve it, still don't know the best way though; I'll also be moving to log4net instead of my custom logging class. A new version should be up soon.

No problem. Tell me how you guys think the UI should be improved and which new features you'd like to have.

Change-log: Version 1.1.0.58 - On 25-02-2014 -> Fixed a bug which prevented Quick Unpack from creating valid files. -> Added 2 new options to applicationSettings (self-explanatory): - BypassUnpackingIfAlreadyUnpacked - BypassPackingIfAlreadyPacked -> You can now select which files to overwrite individually (overriding the global settings)Image -> Compression level changed to 999 from 1 (it will be slightly slower but the final size will be smaller) Download from Mega (Or execute ApplicationUpdater.exe) Also, the Global quick unpacker/packer has been already started, but some problems came up, and it was postponed.