I checked and I had not swapped the runtimes. I still had PalmOSRuntime_2i_A5.lib included in the project. I removed it and added PalmOSRuntine_2i_A4A5.lib, removed the object code from all targets and recompiled. When I debug the same section of code I mentioned in my initial post, I see that once the Char* has memory allocated to it, it is then a valid pointer. Thanks!
I read your post on the palm-dev-forum archive site (http://www.mail-archive.com/[email protected]/msg40853.html) that says that expanded mode only really helps C++ apps. Can you clarify? This app is currently a C app but has a lot of global arrays and such (Segment tab reports a Data column total of 69K over 4 segments) - I would like to eliminate as much of these as possible except where it hurts performance. If expanded mode is not going to help the project with regard to the amount of global variable storage then I will switch back to Standard Mode. Can you add a bit more on that? Like I said, I would like to read that white paper but the link is gone and I can't find the doc. By the way the project is still using the Macintosh 68K Linker and PalmRez Post Linker. I don't really want to have to change over all the resources to .rcp. I don't find PilRC easier to use than Constructor and from the instructions you gave on PalmOSWerks, it seems a requirement to switch to .rcp if switching to Palm OS 68K Linker. -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
