- Downloaded
- 31 GB
- Uploaded
- 31.2 TB
- Ratio
- 1031.17
- Seedbonus
- 13,330,631
- Upload Count
- 0 (0)
Member for 6 years
Hi, anyone with experience in modifying .exe or .dll files can provide me some advice.
1. Some content, e.g. window title, text or buttons can be accessed and modified through exe editor or hex editor, but some can't, not even a single text that exist in the UI can be found in the exe HEX file, does that mean they are encrypted?
2. I have a few miscellaneous .exe file that blast audio in the background, for some occasion, the audio resource (in hex not wav format, i just delete stuff through trial and error and found out it was a audio RCData) can be found in exe resource software, and can be deleted easily. Other times, that similar resources doesn't show up for different file, is it also due to encryption?
3. If so, is there anyway to decrypt data for modifyiing? Is there some sort of documentation for .exe files for all its headers/length/and wheredo other components start and end.
I also saw some tutorials on using software like x64dbg, but this is more targeted towards the runtime data not the UI shell itself. Nevertheless, I still need more time to poke around x64dbg.
1. Some content, e.g. window title, text or buttons can be accessed and modified through exe editor or hex editor, but some can't, not even a single text that exist in the UI can be found in the exe HEX file, does that mean they are encrypted?
2. I have a few miscellaneous .exe file that blast audio in the background, for some occasion, the audio resource (in hex not wav format, i just delete stuff through trial and error and found out it was a audio RCData) can be found in exe resource software, and can be deleted easily. Other times, that similar resources doesn't show up for different file, is it also due to encryption?
3. If so, is there anyway to decrypt data for modifyiing? Is there some sort of documentation for .exe files for all its headers/length/and wheredo other components start and end.
I also saw some tutorials on using software like x64dbg, but this is more targeted towards the runtime data not the UI shell itself. Nevertheless, I still need more time to poke around x64dbg.