Forum :: Client Editing :: changing resources

Ok as most of you know when it comes to changing out all the resources within the EO launcher it's not possible, but i have alot of the files which shouldn't be seen by any user for example

1 VERSIONINFO
FILEVERSION 28,3,0,0
PRODUCTVERSION 28,3,0,0
FILEOS 0x4
FILETYPE 0x1
{
BLOCK "StringFileInfo"
{
    BLOCK "041304E4"
    {
        VALUE "CompanyName", ""
        VALUE "FileDescription", ""
        VALUE "FileVersion", ""
        VALUE "InternalName", ""
        VALUE "LegalCopyright", ""
        VALUE "LegalTrademarks", ""
        VALUE "OriginalFilename", ""
        VALUE "ProductName", ""
        VALUE "ProductVersion", ""
        VALUE "Comments", ""
    }
}

BLOCK "VarFileInfo"
{
    VALUE "Translation", 0x0413 0x04E4
}
}

Now for those of you who know what this is and what table it comes under, you might be able to help, i'm already working on my own client but it's taking months and months. So i'm trying to replace the original eo files.. Not having much luck, anyone have any hints or ideas on hw i can go about replacing the compressed .exe files with new one.. it must be possible without spending weeks trying to figure out a bunch of code from a decompressor.

Any ideas will be appreciated.

All you did was get the info for the endless.exe properties. Big deal. What good will that do?

---
May he now rest under aegis of mirage -
As the sands slowly turn to Elysian fields

It's an example.. Incase you can't read syran.

i'll repeat that for you EXAMPLE.

And you can't get that from properties. i just checked, no doubt dumb on my part.

But never the less try stay on topic, i didn't ask you where i got it from.

I assume when you say "eo launcher" you are not talking about a launcher but the actual client executable. Why are you having so many problems? Compressed .exe's are remarkably easy to decompress due to the fact the decompresser has to be active when the executable is running ready decompress upon page requests.

Simply write a .DLL that dumps the executables uncompressed PE image back to disk:

1. Use CreateProcess to launch endless.
2. Use VirtualAllocEx() to allocate some space within the clients context.
3. Use WriteProcessMemory to write the name of DLL into the memory.
4. Use CreateRemoteThread(Process, NULL, GetProcAddress(GetModuleHandle("kernel32.dll"), "LoadLibraryA"... etc to call the LoadLibrary function within the context of the clients executable.

(Your DLL will now have access to a full, uncompressed PE image of the client)

5. Use GetModuleHandle(0) to get the base address of the PE image (module handles on windows are actually their memory address =P)
6. Save back to disk. (You can now open this in any PE resource editor such as ResHacker)
7. ????
8. Profit.

Not sure how this will help you though. There are no interesting resources within the actual main executable. Just a load of crap the Borland CBuilder adds. You can however use it to look at Vults horrible use of the CBuilder VCL (visual component library):

---
http://sordie.co.uk
http://twitter.com/@SordieEO

Thankyou very much sordie, this actually is helping alot.

Much appreciated

I'll continue working on this tomorrow though, My eye's feel like there being weighed down by bricks.

if your talking about retrieving the original source code from the client then you can't

1. i already have most of the source code. (rebuilt)

2. when i said thanks to sordie, i think that ment i got what i needed.

3. it's obvious you can't get the original from the source.

EDITED: Im sorry i didnt fully get that my fault being a noob D: could someone make it and upload i really need that im doing same thing as you Avalanche im completely remaking gui and copyrights.

Endurance posted: (24th Oct 2009 10:40 am)

EDITED: Im sorry i didnt fully get that my fault being a noob D: could someone make it and upload i really need that im doing same thing as you Avalanche im completely remaking gui and copyrights.

Why the fuck would you want to remake the "Copyrights"?
Edit: Shit didn't realise its an extremely old topic T.T

---
Hmm.