Anatomy of a PumpkinOS app

Stefan Mileschin · 27th September 2022, 13:08

We have seen how PumpkinOS runs a classic 68K application. First, code.0 and data.0 resources from the PRC are loaded and decoded. Then code.1 is loaded and the 68K emulator starts running it. Native applications, that is, applications compiled from source to the target architecture of PumpkinOS (x86 or ARM), are still stored in PRC files, having access to all PalmOS resources like forms, bitmaps, alerts, etc. In fact, the same resource compiler (pilrc) used to generate the binary resources for PalmOS is used in PumpkinOS. The difference lies in how code and data are stored and processed.

https://www.osnews.com/story/135347/...pumpkinos-app/

27th September 2022, 13:08	#1
Stefan Mileschin [M] Reviewer Join Date: May 2010 Location: Romania Posts: 153,575	Anatomy of a PumpkinOS app We have seen how PumpkinOS runs a classic 68K application. First, code.0 and data.0 resources from the PRC are loaded and decoded. Then code.1 is loaded and the 68K emulator starts running it. Native applications, that is, applications compiled from source to the target architecture of PumpkinOS (x86 or ARM), are still stored in PRC files, having access to all PalmOS resources like forms, bitmaps, alerts, etc. In fact, the same resource compiler (pilrc) used to generate the binary resources for PalmOS is used in PumpkinOS. The difference lies in how code and data are stored and processed. https://www.osnews.com/story/135347/...pumpkinos-app/

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Anatomy of a hack: How crackers ransack passwords like “qeadzcwrsfxv1331”	jmke	WebNews	0	28th May 2013 08:10
Anatomy of the Silent Fan	jmke	WebNews	0	14th November 2006 10:57