Quote:
Originally Posted by joojoobee666
Yeah, I am familiar with ervius kitchen. That's why I was saying take the XIP building portion out of the equation by building it yourself. But I guess you can dump the XIP the kitchen made AFTER cooking, get your maps.txt from XIPPort and verify there are no !!!!!!!!!!! anywhere in it as well.
As far as the .VM goes, inside of there is a file called imageinfo.bin. Open that with a Hex Editing program. Bytes 0 - 7 define your slot 0 and slot 1 starting points for reallocation. For example, my imageinfo.bin starts with 00 00 F8 01 00 00 D7 03. This is encoded in little endian (i think). So my Slot 0 allocation should start at 01F80000 and end at 0x0000000 and slot 1 should start at 03D70000 and end at 0x02000000. If any part of your XIP is overlapping into those ranges (again, they will be different for you) then WMreloc will allocate windows module's into that range as well, causing an overlap.
If you open the map.txt generated by XIPPort, you should see portions of both Slot 0 (0x00000000 to 0x01FFFFFF) and Slot 1 (0x02000000 to 0x03FFFFFF) being used by the XIP. These are the first 2 sections of the XIP. Just verify that they are stopping short of these starting points for WMReloc as defined by the imageinfo.bin in the .VM folder.
|
So only the first part of your message showed up in the thread, but when i went to quote your message the whole thing showed up so i copied and pasted it into a word document so i could read and re-read it to try and follow your directions. But I already verified that i didn't have any !!!!!! in the map.txt