> >there lies another issue, which, would definately be something for > >ben combee (metrowerks) to look into, and, handle more correctly > >on their side. the resource output is a whopping 84096 bytes. > > > >yes, thats > 65505 (max limit set allowed for a resource). most > >likely, rez is barfing within codewarrior because it cannot handle > >the large resource. > > Ah... you hit a bug in the V9 linker where it would crash if an input PRC > file (or PilRC RO file) had a resource that was too larget. This is fixed > in 9.2 -- the linker doesn't crash, but instead warns you that your > resource is larger than supported by HotSync. The CW debugger supports > downloading these "larger than 64K" resources, but you can't get them on to > a device by normal means (HotSync, beaming, VFS).
:) good now it is documented *g* > BTW, 65505 isn't the limit anymore... the OS 5 devices actually have a > slightly lower limit due to the larger size of the internal data > structures. I don't know the exact number, so I'm warning for 64000 bytes > or more in a single resource to be safe. i tend to stay away from > 32k these days.. the max resource i like is 32767 - keeps it within an int16 range and gives the OS 32k of extra space for doing what it wants :) of course, i had to update all my algorithms to work with data over multi-ple resources when they are that size :) --- Aaron Ardiri [EMAIL PROTECTED] CEO - CTO +46 70 656 1143 Mobile Wizardry http://www.mobilewizardry.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
