- Joined
- Dec 10, 2009
- Messages
- 198
- Reaction score
- 103
Hi, I've been working on a more complete Eter management solution, still a work-in-progress.
Introduction & description
I've always hated the lack of organization when building or editing large quantities of files using the current tools, also they all lack a good UI, as a result I started making my own. It's meant to have a profile-based approach (you create your profile, which corresponds to a client) and all files regarding this and only this profile will be in the same place. This is a community-driven project, so I'll change it according to our needs.
Requirements
- .NET framework 4.5, previous versions won't work for the simple fact that I'm using some of the latest updates (which lack downward compatibility).
FAQs
Q: Is the project Open-Source?
A: No, not yet. I'll make it open-source once a stable version is released, this will guarantee that everyone works on maintainable code-base (still much work to be done).
Q: Why is the main executable file packed?
A: I'm trying to prevent code leakages until I make it open-source. You can easily test it in a VM and monitor its behaviour...
Q: What are all those files distributed along with the executable?
A: Since not everyone has the same version of .NET framework, I've included all additional dependencies (you still need .NET framework 4.5 installed).
Q:Found a bug. How should I report it?
A: If an exception was raised and not handled (a message will alert you), send me the errorLog.txt, aswell as athoroughdescription of your actions prior to said exception (or bug). If the bug is related to unpacking or packing any file, send me those files, aswell as your application.settings and profile.settings. Irreproducible bugs will be ignored.
Q: Where are unpacked & packed files stored?
A: userData/{ProfileName}/unpack & userData/{ProfileName}/pack
File description
- EterTool.exe => Main executable file, packed.
- System.Windows.Controls.Input.Toolkit.dll, System.Xaml.dll and WPFToolkit.dll => needed dependencies (local copies)
- LzoModule.dll => .NET wrapper of the
- msvcr120.dll => Needed dependency of LZoModule.dll, DO NOT replace this file, as some of you might have different versions of it, it might throw a "BadFormat" exception.
- ApplicationUpdater.exe => Very poorly coded (didn't want to waste any time on it hehe) application updater, just so you can easily update to the latest versions (this file isn't packed).
Main features list
Profile-based approach to improve organization
Index preview, and item selection (both for unpacking and packing
Quick unpack and repack functions
Size optimizer, it finds duplicates and not compressed files
Planned development
- Implement global quick pack & repack, it will enable users to quickly process files outside of the current profile. (implemented)
- Improve Size Optimizer, adding the capability to automatically repack all needed files instead of just showing informaton.
- Improve "Output log" and "Detailed log" windows. (implemented)
- Improve human-error prevention and exception handling (the most importat one, at the moment)
- Add support for multi-threaded unpacking & packing actions while also setting a user-defined limit, for example:
-- You can add 20 files to the operations list, while only X being processed at a time, to prevent crashes.
Known issues and limitations
- Limitation: if an item inside the epk file is greater than 600mb (or its encryption/decryption size), the file will be ignored, this is a known limitation of the .NET framework for programs targeting x86 architectures (the real cap is somewhere between 1.2-1.6gb, but to prevent crashes I downsized it)
- No support for multi-threaded actions.
- Sometimes when clicking enter it won't update the GridView (fixed)
How to setup your profile
- If needed, I might make a video or post some more images, but it's fairly simple:
1. Open the program, it will show up a message saying it didn't find the CWD.
2. Go to Profile Manager -> Manage
3. Change to your settings (at this stage, please include the CWD with backslashes given that Data Validation is in a very early stage)
3.1 Good example:
Bad example:
4. Hit "Save settings" button. (You might need to restart the program after saving)
5. Go to the "Select file from CWD" group and it all should be ready, start typing a file an auto-suggestion will show up
6. In order for the GridView to update, you MUST click enter on the selected file, this is the action trigger.
IMPORTANT NOTES:
In some files, you'll notice a message in the "Output log" window alerting you to some files with different hash than expected, this is due to the fact that most eix files are not 100% accuretly built. You can confirm the integrity of the file by extracting the same file with Tim's unpacker, you'll notice it's the same checksum.
Introduction & description
I've always hated the lack of organization when building or editing large quantities of files using the current tools, also they all lack a good UI, as a result I started making my own. It's meant to have a profile-based approach (you create your profile, which corresponds to a client) and all files regarding this and only this profile will be in the same place. This is a community-driven project, so I'll change it according to our needs.
Requirements
- .NET framework 4.5, previous versions won't work for the simple fact that I'm using some of the latest updates (which lack downward compatibility).
FAQs
Q: Is the project Open-Source?
A: No, not yet. I'll make it open-source once a stable version is released, this will guarantee that everyone works on maintainable code-base (still much work to be done).
Q: Why is the main executable file packed?
A: I'm trying to prevent code leakages until I make it open-source. You can easily test it in a VM and monitor its behaviour...
Q: What are all those files distributed along with the executable?
A: Since not everyone has the same version of .NET framework, I've included all additional dependencies (you still need .NET framework 4.5 installed).
Q:Found a bug. How should I report it?
A: If an exception was raised and not handled (a message will alert you), send me the errorLog.txt, aswell as athoroughdescription of your actions prior to said exception (or bug). If the bug is related to unpacking or packing any file, send me those files, aswell as your application.settings and profile.settings. Irreproducible bugs will be ignored.
Q: Where are unpacked & packed files stored?
A: userData/{ProfileName}/unpack & userData/{ProfileName}/pack
File description
- EterTool.exe => Main executable file, packed.
- System.Windows.Controls.Input.Toolkit.dll, System.Xaml.dll and WPFToolkit.dll => needed dependencies (local copies)
- LzoModule.dll => .NET wrapper of the
You must be registered to see links
LZO implementation.- msvcr120.dll => Needed dependency of LZoModule.dll, DO NOT replace this file, as some of you might have different versions of it, it might throw a "BadFormat" exception.
- ApplicationUpdater.exe => Very poorly coded (didn't want to waste any time on it hehe) application updater, just so you can easily update to the latest versions (this file isn't packed).
Main features list
Profile-based approach to improve organization
Index preview, and item selection (both for unpacking and packing
Quick unpack and repack functions
Size optimizer, it finds duplicates and not compressed files
Planned development
- Implement global quick pack & repack, it will enable users to quickly process files outside of the current profile. (implemented)
- Improve Size Optimizer, adding the capability to automatically repack all needed files instead of just showing informaton.
- Improve "Output log" and "Detailed log" windows. (implemented)
- Improve human-error prevention and exception handling (the most importat one, at the moment)
- Add support for multi-threaded unpacking & packing actions while also setting a user-defined limit, for example:
-- You can add 20 files to the operations list, while only X being processed at a time, to prevent crashes.
Known issues and limitations
- Limitation: if an item inside the epk file is greater than 600mb (or its encryption/decryption size), the file will be ignored, this is a known limitation of the .NET framework for programs targeting x86 architectures (the real cap is somewhere between 1.2-1.6gb, but to prevent crashes I downsized it)
- No support for multi-threaded actions.
- Sometimes when clicking enter it won't update the GridView (fixed)
How to setup your profile
- If needed, I might make a video or post some more images, but it's fairly simple:
1. Open the program, it will show up a message saying it didn't find the CWD.
2. Go to Profile Manager -> Manage
3. Change to your settings (at this stage, please include the CWD with backslashes given that Data Validation is in a very early stage)
3.1 Good example:
Bad example:
4. Hit "Save settings" button. (You might need to restart the program after saving)
5. Go to the "Select file from CWD" group and it all should be ready, start typing a file an auto-suggestion will show up
6. In order for the GridView to update, you MUST click enter on the selected file, this is the action trigger.
IMPORTANT NOTES:
In some files, you'll notice a message in the "Output log" window alerting you to some files with different hash than expected, this is due to the fact that most eix files are not 100% accuretly built. You can confirm the integrity of the file by extracting the same file with Tim's unpacker, you'll notice it's the same checksum.
You must be registered to see links
