Ben,
You are correct, the startup code does load the code segment(s) and fix up the addresses. But it's all done with local variables. The key to the information seems to be the SysAppInfoPtr which is filled out by a call to SysAppStartup.
The SysAppInfoPtr is local to the startup routine however. Do you know if there is some way to ask for that pointer from some other Sys routine OR if it is in fact safe to call SysAppStart() again from my pilotMain() (this doesn't seem smart but I'm not sure what it does).
You don't need that info. Just open your app's database, get resources code 1..code n, and lock each resource. Since they are already locked, you won't change their address, and you can then use standard calls to find their location and size. You can determine the global variable range by checking A5 and reading the high/low values out of the data 0 resource.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
