In the search for variable module mapping options I have come across this kitchen and it looks very promising. I noticed however that some of the more interesting insight options are "not available in the public version" - so I wonder if these options are existing at all and if (and how) I can get access to such a version to play with?
My intention is the following:
I cook (well, more reuse an old kitchen) for the Tornado (yes, a 2006 device...) and want to port this result to an even older device (Hurricane). In the process of porting XIP from Tornado WM6 to an oder WM6 Hurricane build and rebuilding the ROM I came across a strange behavior of - I suspect the ddi.dll module:
- When re-assembling the WM6 Hurricane (an original wm2k3 device) ROM behavior is normal, i.e. the screen updates regarding GUI elements is as expected. Just dump the ROM and rebuild it, no remapping.
- After a remapping with wmreloc (g'reloc creates non booting ROMs), the scrollbars "gap" space is filled with random garbage when scrolling. No other side effects, but this is annoying and I have no clue how to resolve this.
I noticed there is an option to supply a list of modules that should not be mapped. Is this existing - and does it work?
The ddi.dll that is used for the Hurricane WM6 ROM is coming from the Elf (not sure if patched or not) and my simple idea to replace it by the Tornado ddi.dll module was not successful.
Any help?
