Quote:
Originally Posted by FormerPalmOS
right now to check on G'Reloc I have to dump the resulting ROM to get the memory map and make sure the modules don't overlap the XIP (which they haven't as long as I have the .VM file correct in SYS) and that they leave sufficient room for non-moduled DLLs and EXEs.
|
G'reloc uses .VM to determine where to put stuff, hence you never have an overlap if it's correct.
Quote:
|
Also, will it automagically process all modules in a dump directory like G'Reloc.exe -dump -doit? Or do you have to have something else process the dump directory and call WMReloc.exe for each module? If the latter, I'm sure someone has written a utility to do this (I saw a "small G'Reloc.exe over at XDA that supposedly calls WMReloc.exe - wonder if that is it...?)
|
Yes, WMreloc processes all modules. The "small G'reloc" is a stub replacement that calls WMreloc. It's used to trick apps that want g'reloc into using wmreloc. Of course, there are limitations to using wmreloc that way, so it's better to use WMreloc directly.