Don`t use ppcload anymore. When the ppc.library is active it`s running automaticly.


loop.c

 This program is a simple for(;;) loop on the ppc. Should only
 demonstrate how to compile something.
 Run: loop.elf

Trap.c
 This program causes a trap on the ppc so the ppctask causes
 an exception.
 Run: trap.elf

TaskA.c
 This program simples outputs "Task A is active"
 Can be used with TaskB to test the multitasking.
 Also uses some simple DOS calls.
 Run: taska.elf

TaskB.c
 This program simples outputs "Task B is active"
 Can be used with TaskA to test the multitasking.
 Also uses some simple DOS calls.
 Run: taskb.elf

TaskASemaphore.c
 This program outputs "0x%lx:Task A is active" with
 semaphore synchronizing.
 A public semaphore with the name "TaskSemaphore"
 is used to output 10 lines with the mentioned text.
 Can be used together with TaskBSemaphore.c to show
 the interaction between semaphore locking and multitasking.
 Run: taskasemaphore.elf

TaskBSemaphore.c
 This program outputs "0x%lx:Task B is active" with
 semaphore synchronizing.
 A public semaphore with the name "TaskSemaphore"
 is used to output 10 lines with the mentioned text.
 Can be used together with TaskASemaphore.c to show
 the interaction between semaphore locking and multitasking.
 Run: taskasemaphore.elf

TaskSignalTest.c
 This program waits for a certain signal. With the program
 tools/ppcsignaltask you can send the signal and the program terminates.
 Run: tasksignaltest.elf

CallM68kSync.c
 This program shows how PPCCallM68k is used. In this example the
 call is done synchron which should be the normal case.
 Run: CallM68kSync.elf

CallOSASync.c
 This program shows how PPCCallOS is used. In this example the
 call is done asynchron which means that the result has no meaning.
 Asynchron means that the PPC doesn`t wait until this operation completes.
 But if another normal systemcall(Not Message operation) is caused, it can
 only execute until the last job is completed.
 Run: CallOSASync.elf

Startup.c
 This program shows how to the task`s startup/exit msg mechansim to
 exit your M68k program without major synchronize problems.
 Run: Startup

Msg2.c
 Show how to send a Msg from the M68k to the PPC and from the PPC to the M68k.
 It also shows how to use the StartupMsg and PPCTask`s msgport functions to
 simplify the init and close phase.
 Run: Msg2

Msg2old.c
 This program uses oldstyle PPCObtainPort(not recommended)

Msg3.c
 This test program sends 1000 messages to the PPC and
 shows how long this takes.
 The Messages are send synchron and every msg must
 be replied after another.
 Each Message has the Body "Text sent by M68k processor\n"
 Run: Msg3

Msg4.c
 This program sends 1000 messages to the M68k and
 shows how long this takes.
 The Messages are send synchron and every msg must
 be replied after another.
 Each Message has the Body "Text sent by PPC processor\n"
 Run: Msg4

Msg5.c
 This test program sends 1000 messages to the PPC and
 shows how long this takes.
 The Messages are send asynchron and it`s not waited
 for the reply...until all messages are send
 Each Message has the Body "Text sent by M68k processor\n"
 Run: Msg5

Msg6.c
 This test program sends 1000 messages to the M68k and
 shows how long this takes.
 The Messages are send asynchron and every msg must
 be replied after another.
 Each Message has the Body "Text sent by PPC processor\n"
 Run: Msg6

Msg7.c
 This test program sends 1000 messages to the PPC and
 shows how long this takes.
 The Messages are send synchron and every msg must
 be replied after another.
 Each Message has a Body with the size of 3747 bytes
 and the PPC side checks if the msg was received correctly.
 Run: Msg7

Libs.c
 PPC program to test the PPC shared object library system including
 several version check tags.
 Run: Libs.elf

LibsModule.c
 PPC shared object library example for Libs.c.
 Run: not possible


Time.c

 Timer measurement submodul for the 68k side
 Run: not possible