| |
|
|
|
|
|
Related Downloads |
|
|
|
|
|
|
|
 |
|
Startup Process |
|
On the initial Pippin,
CD-ROMs developers were taught a simple way of setting up the startup
application by modifying the boot blocks on the volume. While this worked as
needed, it was a hack and is not an acceptable solution for shipping disks.
It required the target application to be in the "blessed" System Folder,
or in some cases, people made the root level of the volume the System
Folder. This makes the disks very unattractive when the disk is used in a
non-Pippin system (due to the need for the startup application to be in the
System Folder). It could also cause problems with future Pippins as there
would be more "unique" considerations that would need to be handled as the
ROM attempts to override what is on the Pippin CD-ROMs. |
|
Technical Note |
| |
|
|
|
|
|
|
|
|
|
Pippin Standard File |
|
When developing titles for
the Pippin Power Player, many assumptions about storage that are typically
made in the Macintosh environment must be slightly altered. Unlike a
Macintosh, Pippin does not have a hard disk and the only guaranteed storage
media available is 128k of internal NVRAM (non-volatile random access
memory). An optional floppy disk drive could be installed as well, but this
should not be assumed. Of the 128k built-in NVRAM, 8k is used by the system
software, leaving 120k for general purpose storage. Obviously, assumptions
made about file storage while working with virtually unlimited hard disk
space are very different than working with a limited and relatively small
amount of storage. |
|
Technical Note
|
| |
|
|
|
|
|
|
|
|
|
Pippin Launch |
|
The PippinFinder Technical Note describes
the "replacement" Finder file for the Pippin System Folder, and that the
actual code that drives a multiple application-interface is inside the
Pippin Launch file. Apple provides an initial interface, a simple button
interface, with the buttons changing appearance when they are selected. In
summary, Pippin Launch is the file that PippinFinder uses, and this document
is describing the "PCde" resource that Apple provides for developers to use.
If you wish functionality beyond what
PCde
code implements, you will need to write your own code module. (See the PippinFinder
Technical Note for details on how to create your own code module.) |
|
Technical Note
|
| |
|
|
|
|
|
|
|
|
|
Pippin Finder |
|
The PippinFinder file is
only to be used with CDs that have a multiple-application interface. Since
most titles developed for Pippin will involve only a single application
launched immediately at start-up, the PippinFinder file is not used and
therefore should not be placed in the System Folder. Even with multiple
application titles, the PippinFinder does not provide the interface for
launching the applications within a title CD; the interface is provided by a
Pippin Launch file. |
|
Technical Note
|
| |
|
|
|
|
|
|
|
|
|
Stopping INIT Icons |
|
The Pippin OS frequently
includes extensions such as QuickTime and Applejack. Extensions almost
always draw an icon when loading, which is what produces the row of icons
across the bottom of the screen when the system is booting. The Pippin user
experience though should not include such computer specific messages. The
user probably will not even know what QuickTime is. Therefore, developers
should stop the drawing of icons during the boot process for Pippin CDs. |
|
Technical Note
|
| |
|
|
|
|
|
|
|
|
|
Creating Pippin CD-ROMs |
|
All CD-ROM titles to be
played on Pippin Power Players must be "Pippinized" in order to successfully
run on a Pippin. This technical note describes the hardware, software, and
procedures required to make Pippin-ready CD-ROMs though either modification
of already released CD-ROM titles, or in initializing a brand new CD-ROM
title. |
|
Technical Note
|
| |
|
|
|
|
|
|
|
|
|
Flash Access |
|
The Flash Access chip is a
writable FlashROM chip with a 120K maximum capacity located on the Pippin
main logic board. Since the Pippin does not have a hard drive to store
information, and external storage devices cannot be assumed to always be
present, a developer has very limited space to work with. Developers must
therefore recognize the storage limitations of the Flash Access chip, and
plan their titles accordingly. |
|
Technical Note
|
| |
|
|
|
|
|
|
|
|
|
Pippin Authentication |
|
In order for Pippin CD-ROMs
to run on a Pippin Power Player, they must first go through a Pippin
authentication process. The authentication process is about applying an
Apple-approved RSA signature, in the form of an electronic encrypted key,
onto a Pippin CD-ROM. |
|
Technical Note
|
|
|
|
|
|
|
|
|
|
|
|
Applejack Input Device Driver |
|
The Applejack input device
driver combines the features of a game-player pad and a mouse or trackball
in a small handheld device. Generally, Applejack input devices are attached
to a Pippin Power Player (a CD-ROM multimedia player device derived from the
PowerPC Macintosh). |
|
Technical Note
|
| |
|
|
|
|
|
|
|
|
|
Pippin Video |
|
This document contains
PippinVideo.h and
myPippinVideo.c.
PippinVideo.h is a header file that contains enumerated constants and structures necessary
to access functionality unique to the Pippin video architecture.
myPippinVideo.c is sample code that illustrates features unique to the Pippin video
architecture. |
|
Technical Note
|
|
|
|
|
|
|
|
|
|
|
|
Logo Usage Guidelines |
|
These usage guidelines for
the Pippin logo
and CD-ROM packaging are available in
Adobe Acrobat PDF format and are intended for Apple Developers. The download
contains an Adobe Acrobat PDF file. (3.35MB) |
|
PippinGuidelines.sit |
