1 # General Support: Palm OS
3 Rumor has it that Palm OS was inspired by Mac OS Classic (creator and type
4 IDs are rather noticeable).
6 Note that Cobalt (Palm OS 6) is very different and the only known instance of
7 it is the simulator which runs on Windows and uses DLLs for native libraries.
11 There are two supported architectures in PalmOS:
13 * [m68k](m68k_palmos_generic__dev.mkd)
14 * All Palm OS versions up to 4.
15 * [ARM](arm32_palmos_generic__dev.mkd)
17 * m68k is run on an emulator which integrates quite well, however it has
18 limitations on what it can do.
22 ## "Illegal" Threading
24 Palm was under contract to not expose any threading API and make it
25 available to developers. There are no threading headers at all. From what I
26 remember, the limitations were only for the kernel used for the m68k devices
27 since they licensed another company's kernel. The kernel is the AMX kernel by
30 Palm however is no longer around and HP has buried everything pertaining to
33 Note that Kadak is also dead, they left a note on their website stating
34 "KADAK Products Ltd. regrets to announce that, effective January 29, 2016
35 it will cease operation world-wide.". I suppose if Palm OS had threading since
36 AMX was a RTOS, it probably could have competed a bit better.
40 IPC would be the most complex process, it can either be fast or it will be
45 If the undocumented mailboxes are figured out and if their name makes any
46 sense, they can be used as IPC. Otherwise, IPC would be layered on the feature
51 The feature manager will be used heavily. New features can be declared and
52 they are not saved in RAM across reboots (well they are wiped). The feature
53 manager will essentially be the only way there can be safe IPC across various
54 threads. That is, unless the undocumented mailboxes are workable. The feature
55 manager is well documented however.
59 Palm OS does not support daemons at all. With thread creation however,
60 background tasks can be created. These along with IPC would allow the threads
61 to act as virtual machine daemons.
63 ## Launch Codes and the Notification Manager
65 These two important bits will be a way to have system notifications be sent to
66 programs running the JVM, perhaps even URL handling and such.