Difference between revisions of "User manual"
(→What Are .PNDs?) |
(→Where Do .PNDs Go?) |
||
Line 88: | Line 88: | ||
==== Where Do .PNDs Go? ==== | ==== Where Do .PNDs Go? ==== | ||
+ | |||
+ | ==== Where does my data go? How do I make files visible to the applications? ==== | ||
+ | |||
+ | An application normally will see what is contained within the pnd-file, or your personal data created with the tool; it can of course look anywhere on the SD or device internal memory. For example a Quake port might expect to see extra level files in /quake, or give you a way of selecting a path to put files in.. or it might just expect it to be in your personal data folders, or in the pnd-file itself. Its up to the application, with suggestions in the pnd-guidelines for developers. | ||
+ | |||
+ | The first time a pnd-application is run, an "app data" directory is created for it; anything that app data folder contains will be visible to the application as if it was in the pnd-file (and in fact, this lets you override files in the pnd-file without modifying the .pnd itself, which could be handy.) If your app creates a file "foo", it'll show up in /pandora/appdata/appname-id as "foo". The actual appdata folder name depends on the name used by the developer, but should generally look like application-name and some funny number afterwards. It should be easy to spot. | ||
+ | |||
+ | ex: Quake 1 will probably put score or save data in /pandora/appdata/quake1-123/ or somesuch. | ||
+ | |||
+ | ===== Q: How do I make ROMs available to an emulator? ===== | ||
+ | |||
+ | For something like ROMs, hopefully a developer consensus will lead either to a canonicle location, or a convention of having a directory pickre or browser present, so that ROMs can be stored in SD locations of your choice; doesn't strike me as something that should be in a pnd-file, or to be pretended to be in a pnd-file with appdata tricks. | ||
+ | |||
+ | ===== Q: How do I make pak-files available to Quake? ===== | ||
+ | |||
+ | For some add-ons or data needed for a game, the developer may require it to be 'in the main application path'; as mentioned above, just drop it into the appdata folder and the app will just see it. | ||
+ | |||
==== How Do I Make .PNDs? ==== | ==== How Do I Make .PNDs? ==== | ||
==== More Info About .PNDs ==== | ==== More Info About .PNDs ==== |
Revision as of 16:30, 24 December 2009
So your Pandora just arrived after being in the post for two months. Jolly good! But now that it's actually here, what on earth do you do with it? Don't panic! Let's take a look at what's included in the box(so you don't miss anything!) and then hop on over to setting it up for that extended Ms. Pacman marathon I know you've been waiting for!
Contents
- 1 Safety Information
- 2 Box Contents
- 3 Specifications
- 4 First Time Use
- 5 Basic Use
- 6 Applications
- 7 Introduction To .PNDs
- 8 Configuration
Safety Information
First of all, let's get this out of the way. DO NOT EAT YOUR PANDORA! It will be hard enough to break your teeth, and it may or may not work after digestion.
The Pandora contains small parts that could be swallowed by children(and let's face it, we're all pretty much children the day we see our Pandora on our doorstep), such as the stylus or an odd button or screw.
Keep the Pandora in normal temperatures under 140F/60C. The battery is a standard Lithium Polymer battery. Do not dispose of in fire or water. Do not dissasemble, crush, or puncture the battery, or it may explode! Do not short circuit external contacts! Dispose of properly, please.
The Pandora contains a 4.3" touchscreen. Although you can touch it, do not hit it too hard or you may risk breaking it. Also, the touchscreen can(gasp!) display 16.7 million colors. That's 16.7 million ways to injure an epileptic person, so please! Exercise caution and common sense when handling the screen.
Box Contents
When you first open Pandora's box, a slew of demons and raging emotions may forcibly leave the box. This is normal. After that, you may or may not be surprised to find a:
- Pandora console
- Stylus(located in stylus slot on the side of the Pandora)
- DC Wall Charger
- TV-Out Cable(ONLY if you ordered it separately)
- Carrying Case(ONLY if you ordered it separately)
After you take those things out, you may find a sliver of Hope left over. It's best to keep it, as you never know when you could use some Hope.
Specifications
Highlights
- ARM® Cortex™-A8 600Mhz+ CPU running Linux
- 430-MHz TMS320C64x+™ DSP Core
- PowerVR SGX OpenGL 2.0 ES compliant 3D hardware
- 800x480 4.3" 16.7 million colours touchscreen LCD
- Wifi 802.11b/g, Bluetooth & High Speed USB 2.0 Host
- Dual SDHC card slots & SVideo TV output
- Dual Analogue and Digital gaming controls
- 43 button QWERTY and numeric keypad
- Around 10+ Hours battery life
Specs
- Texas Instruments OMAP3530 processor at 600MHz (officially)
- 256MB DDR-333 SDRAM
- 512MB NAND FLASH memory
- IVA2+ audio and video processor using TI's DaVinci™ technology (430MHz C64x DSP)
- ARM® Cortex™-A8 superscalar microprocessor core
- PowerVR SGX530 (110MHz officially) OpenGL ES 2.0 compliant 3D hardware
- integrated Wifi 802.11b/g (up to 18dBm output)
- integrated Bluetooth 2.0 + EDR (3Mbps) (Class 2, + 4dBm)
- 800x480 resolution LTPS LCD with resistive touch screen, 4.3" widescreen, 16.7 million colors (300 cd/m2 brightness, 450:1 contrast ratio)
- Dual analog controllers
- Full gamepad controls plus shoulder buttons
- Dual SDHC card slots (up to 64GB of storage currently)
- headphone output up to 150mW/channel into 16 ohms, 99dB SNR (up to 24 bit/48KHz)
- TV output (composite and S-Video)
- Internal microphone plus ability to connect external microphone through headset
- Stereo line level inputs and outputs
- 43 button QWERTY and numeric keypad
- USB 2.0 OTG port (1.5/12/480Mbps) with capability to charge device
- USB 2.0 HOST port (480Mbps) capable of providing the full 500mA to attached devices (examples include USB memory, keyboard, mouse, 3G modem, GPS)
- up to two externally accessible UARTs and/or four PWM signals for hardware hacking, robot control, debugging, etc.
- un-brickable design with integrated boot loader for safe code experimentation
- Power and hold switch useful for "instant on" and key lockout to aid in media player applications on the go
- Runs on the Linux operating system (2.6.x)
- Dimensions: 140x83.4x27.5mm
- Weight: 335g (with 4000mAh battery)
Features
The Pandora is a mixture between a PC and a gaming console. That's why it has gaming controls (Buttons, DPad and analogue nubs). It is fast enough to emulate many other systems, run a full desktop, access the internet via FireFox and play games such as Quake3. However, it is not as big as a netbook. Believe it or not, it will fit in your pocket. It's a bit bigger than the Nintendo DS.
First Time Use
Charging
First Boot
Calibrating The Touchscreen
Basic Use
Applications
What Is Included?
Where Can I Get More Apps?
Introduction To .PNDs
What Are .PNDs?
A .pnd ("pandora") file is an application (game, word processor, emulator, whatever.) More accurately, it is a full application bundled up into a single file; think of it like a zip, with a relatively well defined internal structure.
The pnd-file system was designed so you could use an application without the hastle of installation or uninstallation, or even having to organize it yourself if you don't want to. You just download or obtain the pnd-file, and use it.
More details can be found in the "libpnd hub" part of the wiki, but that is more oriented to techies and developers.
How do I run a PND-application?
Put your pnd-files in your SD (see below for some suggestions where.)
A pnd-file is usually invoked in one of the following ways
- browse to the file using the directory browser, and click to run it. (.pnd files are file-associated to another program, pnd_run which knows how to run them.) This lets you organize pnd-files in directories of your choice on the device NAND or SD.
- in PMenu, the applications will be shown by name; you can just select and run them from the menu
- for pnd-files placed into /pandora/menu on SD, the application will be shown in the Start menu on the device; use your stylus or buttons to invoke it
- for pnd-files placed into /pandora/desktop or /pandora/apps on SD, they will show up automarically on your desktop; invoke them with the stylus, your finger, or controls as you see fit
Where Do .PNDs Go?
Where does my data go? How do I make files visible to the applications?
An application normally will see what is contained within the pnd-file, or your personal data created with the tool; it can of course look anywhere on the SD or device internal memory. For example a Quake port might expect to see extra level files in /quake, or give you a way of selecting a path to put files in.. or it might just expect it to be in your personal data folders, or in the pnd-file itself. Its up to the application, with suggestions in the pnd-guidelines for developers.
The first time a pnd-application is run, an "app data" directory is created for it; anything that app data folder contains will be visible to the application as if it was in the pnd-file (and in fact, this lets you override files in the pnd-file without modifying the .pnd itself, which could be handy.) If your app creates a file "foo", it'll show up in /pandora/appdata/appname-id as "foo". The actual appdata folder name depends on the name used by the developer, but should generally look like application-name and some funny number afterwards. It should be easy to spot.
ex: Quake 1 will probably put score or save data in /pandora/appdata/quake1-123/ or somesuch.
Q: How do I make ROMs available to an emulator?
For something like ROMs, hopefully a developer consensus will lead either to a canonicle location, or a convention of having a directory pickre or browser present, so that ROMs can be stored in SD locations of your choice; doesn't strike me as something that should be in a pnd-file, or to be pretended to be in a pnd-file with appdata tricks.
Q: How do I make pak-files available to Quake?
For some add-ons or data needed for a game, the developer may require it to be 'in the main application path'; as mentioned above, just drop it into the appdata folder and the app will just see it.