wes58, on Nov 22 2009, 18:04, said:
If you still have problems with WMReloc I think I know why. We are trying to relocate files that are in the dump folder. I extracted files from language pack and noticed that some of them are not what you would expect to be if you look at file extension. For example file AutoUpdateRes_wpc.exe.0409.mui, if you look in hex you would expect first to bytes to be MZ (like all exe and dll files). But in this file you will find first four bytes to be MNGE. What it turns out to be, is a file consisting of imageinfo.bin and one or more file sections S000, S001 ....
In case of this file, there is only one S000 which starts at offset 8C, and imageinfo.bin that starts at offset 04 to 8B. I think that first byte in imageinfo.bin tells you how many file sections there are, which also means that first S000 will start at different offset.
What all this means that some files from language pack are also placed in virtual memory and may overlap with the relocations created by WMReloc.
It's a very good theory indeed!! SO more reasons we can make great use of supposed english-only ROM that secany has and hope he can provide me with.. I read that tacchan wrote him for this matter, and i also PM'ed him to see if he can give it to me.
If wes theory is correct , which i am totally sure it is, because it corresponds with other hiphotesis i've made in langpack, we now have 2 ways: getting deeper in langpack format, and trying to be able to properly 'cook it', or else, work with an one language-only ROM as a base. Second way is more likely, the first one involves too much work for now... we might leave langpack cooking for the future.
So, in short, if everyone can help me in persuading Secany to offer me his english-only recent official rom, i can finish the first cooked public-rom available within a pair of hours upon downloading it.
In reply to previous posts: first cooked rom i'll publish, will be as ultra-lite as possible.. I'll remove as much samsung-stuff as i can, while preserving all hardware functionality, and leaving as much storage and ram memory as i can. Everyone can then install their own CABs of their choice.
First attemp will remain on official WM 6.5 build, let's go step by step and not rush. Doing just this already is pretty messy, if we try to get too many things at once, we'll find more issues to deal with.
And YES, i am tempted not to realeasing to general public, because of all the support that i 'll have to do then , but giving it to a reduced size of beta testers instead.... all suggestions welcome though.