Zaurus Handbook

This is the Zaurus handbook.
Want a printer-friendly and downloadable HTML version? Click here.

1. Introduction

This handbook is aimed at everyone, and hopefully easy enough for noobs to pick up and use.

1.01 Zaurus Introduction

The Zaurus is a line of PDAs made by Sharp. The original models from the 1990's and early 2000's ran a proprietary OSes; Synergy OS for the earlier PI and ZR models and Zaurus OS for the later MI and MT models. After the MT series Sharp released the ground breaking SL series in 2001 that ran Linux out of the box.

The scope of this document is to only provide in depth coverage on the SL and SL-C Zaurus models due to the fact that they run Linux natively, and have a wide variety of alternate operating systems available for it.

There is a large amount of open source software available for the SL and SL-C models and more can be fairly easily created for it thanks to the easy availability of native and crosscompilers.

1.02 Zaurus Model Comparison

In general terms the SL series refer to the tablet style models that were mainly marketed outside of Japan with one notable exception and the SL-C series refer to the convertible clamshell models that were marketed within Japan. The notable exception to this rule was the only official clamshell model available outside of Japan that Sharp jointly marketed with CEC in China known as the Sharp CEC SL-7500.

An Zaurus Model comparison needs to be written here.

-SL-5x00
-SL-6000
-SL-7500
-SL-Cxx0
-SL-Cxx00

1.03 Zaurus Distro Comparison

I fairly brief, unbiased Zaurus Distro comparison needs to be written here.

SL-5x00:
Sharp
OpenZaurus
Angstrom
Cacko (?)
Watapon
Crow (?)
Henteges (?)
QTopia
TKCROM

SL-C series (clamshells):

Sharp ROM
-Original ROM
-Stable
-QT interface
-2.4.x kernel

Cacko
-Based on the Sharp ROM
-Added applications
-Full/"Lite" versions
-2.4.x kernel

OpenZaurus
-Built with OE
-No longer maintained
-Succeeded by Angstrom
-Very mature and stable
-GPE and Opie variants
-Runs on all Zaurii (?)

Angstrom
-Built with OE
-Many devs
-RTFM
-Cutting-edge
-Not just for Zaurus
-Not stable
-2.6.x kernel
-GPE and other variants
-runs on all Zaurii (?)

pdaXrom
-Developed by a small team (Sashz, Laze, and InSearchOf)
-No recent release (just betas and revisions)
-Not considered stable
-2.6.16 kernel in the latest version
-Only one version (X11)
-Openbox/Matchbox is the default window manager/desktop manager
-does not run on C3000

pdaXii13
-Based on pdaXrom beta 1/2/3
-2.4.20 kernel
-made by Meanie
-stable
-runs on C3000

SL-C3x00-specific:

Debian/Titchy
-Appeared recently
-Apparently stable
-Run full Debian on your Z
-Use regular Debian ARM repositories
-OABI and EABI varieties

*BSD
-Full BSD
-Stable
-SD support (?)

1.04 Glossery

BT = Bluetooth
Short-range wireless to connect with mice, phones, etc.

CF = compact flash
Largish cards that provide storage or IO functions (Wi-Fi, bluetooth, etc.)

OE = OpenEmbedded
A build system for embedded Linux distributions. Used by OZ/Angstrom

OZ = OpenZaurus
A now-unmaintained ROM made with OE.

ROM = nickname for a distribution for the Zaurus

SD = Secure digital
Small cards about the size of a stamp. Sizes go up to about 4 GB.

SDHC = Secure digital high capacity
SD cards with capacity >4 GB. Not working with many ROMs.

SDIO = Secure Digital Input Output
SD cards that provide some functionality other than storage, eg Wi-Fi, bluetooth.

Wi-Fi = Wireless Fidelity

2. Zaurus Hardware

In brief intro of the Zaurus hardware section of this book needs to be written here.

2.01 SL-5000D (developer edition of SL-5500)

something

2.01.01 Hardware Tech Specs

Something

2.01.03 FAQ

something

2.02 SL-5500 (Collie)

someting

2.02.01 Hardware Tech Specs

something

2.02.03 FAQ

something

2.03 SL-5600 (Poodle)

something

2.03.01 Hardware Tech Specs

something

2.03.03 FAQ

something

2.04 SL-C700 (Corgi)

First (?) clamshell model.

2.04.01 Hardware Tech Specs

400 MHz Intel Xscale 255 CPU (bug limiting it to essentially 206 MHz)
32 MB RAM
32 MB NAND
3.7" VGA display (not sunlight-readable)

Below are unknown by me for sure:

1x SD card slot
1x CF card slot
1x IR port
1x Proprietary USB cord connector
1x 3.5mm headphone jack

2.04.03 FAQ

something

2.05 SL-C750 (Shepherd)

Successor to the SL-C700, with twice the RAM, twice the NAND, and a working CPU.

2.05.01 Hardware Tech Specs

400 MHz Intel Xscale 255 CPU
64 MB RAM
64 MB NAND
3.7" VGA display (not sunlight-readable)

1x SD card slot
1x CF card slot
1x IR port
1x Proprietary USB cord connector
1x 3.5mm headphone jack

2.05.03 FAQ

something

2.06 SL-7500C (Shepherd)

Chinese (?) version of the SL-C750. The only difference between the two models is the coloring.

2.06.01 Hardware Tech Specs

400 MHz Intel Xscale 255 CPU
64 MB RAM
64 MB NAND
3.7" VGA display (not sunlight-readable)

1x SD card slot
1x CF card slot
1x IR port
1x Proprietary USB cord connector
1x 3.5mm headphone jack

2.06.03 FAQ

something

2.07 SL-C760 (Husky)

Same as the SL-C750, but came standard with a larger battery/battery cover and 128 MB of NAND. This model also has a white bezel instead of black.

2.07.01 Hardware Tech Specs

400 MHz Intel Xscale 255 CPU
64 MB RAM
128 MB NAND
3.7" VGA display (not sunlight-readable)

1x SD card slot
1x CF card slot
1x IR port
1x Proprietary USB cord connector
1x 3.5mm headphone jack

2.07.03 FAQ

something

2.08 SL-C860 (Boxer)

Essentially the same as the SL-C760, but with a different color scheme and updated software (?).

2.08.01 Hardware Tech Specs

400 MHz Intel Xscale 255 CPU
64 MB RAM
128 MB NAND
3.7" VGA display (not sunlight-readable)

1x SD card slot
1x CF card slot
1x IR port
1x Proprietary USB cord connector
1x 3.5mm headphone jack

2.08.03 FAQ

something

2.09 SL-6000 (Tosa)

Information here should be mostly correct (I'm pretty sure there are 3 models, the suffixes may be mixed up, however):

-Comes in 3 (?) varieties: SL-6000N, SL-6000L, and SL-6000W

SL-6000N- No Wi-Fi or bluetooth
SL-6000L- With Wi-Fi, no bluetooth
SL-6000W- Wi-Fi and bluetooth

-Released in the US

2.09.01 Hardware Tech Specs

400 MHz Intel Xscale 255 CPU (Intel XScale-PXA255 rev 6 (v5l))
64 MB RAM
64 MB NAND (?)(OS uses NAND for RAM access, this is not another 64 MB)
4.0" VGA display (transflective/viewable in sunlight)

Internal Wi-Fi (SL-6000L and SL-6000W only)
Internal bluetooth (SL-6000W only)

1x 3.5mm headphone jack
1x CF card slot (one more with sled [sled not included])
1x SD card slot
1x IR port
1x serial port (connects to docking station [included] or serial cable[not included])
1x usb host port (no HOST cable included)
1x speaker
1x built-in microphone

2.09.03 FAQ

something

2.10 SL-C3000 (Spitz)

The SL-C3000 is on of the stranger Zaurii, as it runs off of the internal MicroDrive. This limits its choice of ROMs, as many run only from flash.

2.10.01 Hardware Tech Specs

Intel PXA270 CPU (416 MHz)
16MB Flash
64MB RAM
Internal 4GB MicroDrive (OS runs off of the MicroDrive)
SD and CF ports
USB client/host (with cable) port

2.10.03 FAQ

somehting

2.11 SL-C1000 (Akita)

The SL-C1000 is basically a small update to the SL-C860. It gains a newer CPU (PXA270 416MHz) and USB host capabilities.

Since it has the same form factor as the SL-C3x00 series, but lacks the internal MicroDrive, it is likely the most hackable Zaurus. At least one person has fitted USB Wi-Fi and Bluetooth sticks inside of the casing (and overrode the resistor limiting the USB output to 200mA(?)).

2.11.01 Hardware Tech Specs

something

2.11.03 FAQ

something

2.12 SL-C3100 (Borzoi)

The SL-C3100 is basically a C1000 with an internal 4 GB MicroDrive.

2.12.01 Hardware Tech Specs

Intel PXA270 CPU (416 MHz)
128MB Flash
64MB RAM
Internal 4 GB MicroDrive
SD and CF ports
USB client/host (with cable) port

2.12.03 FAQ

something

2.13 SL-C3200 (Terrier)

The SL-C3200 is basically an SL-C3100 with a larger MicroDrive. There have also been reports that its CPU is more difficult to overclock.

The >1GB SD driver was taken from an update to this Zaurus's OS.

2.13.01 Hardware Tech Specs

Intel PXA270 CPU (416 MHz)
128MB Flash
64MB RAM
Internal 6 GB MicroDrive
SD and CF ports

2.13.03 FAQ

something

3. Accessories

A plethora of Zaurus accessories!

3.01 CF Flash Memory and Micro Drives

-No known size limit
-Works in all Z models

3.02 CF Ethernet

something

3.03 CF Modems

something

3.04 CF VGA

-Very limited
-Works only with Sharp ROM/Cacko (?)
-Only can be used for slideshows (?)
-2 versions with similar abilities/limitations
--IODATA something
--some other one I can't remember

3.05 CF WiFi

-Probably the best way to get Wi-Fi on the Z
-HostAP or Orinoco drivers
-802.11G cards haven't been made to work yet (?), only 802.11B
-No cards are flush with the Z; all stick out some

Cards known to work:
Ambicom WL-1100C

3.06 CF GPS

something

3.07 CF Mobile Telecommunications

something

3.08 CF Cameras

something

3.09 SD Flash

-SD supported on all models
-1 GB limit on some/all models/ROMs without updated driver
-SDHC support in most distros using a 2.6.x kernel

3.09.01 SDHC Flash

-Does not work on most ROMs
-May work on Angstrom and/or Debian

3.10 SD WiFi

Does not work, there is not currently (or will likely be in the near future) SDIO support for the Zaurus, and thus no SD Wi-Fi

3.11 SD Bluetooth

something

3.12 SD GPS

something

3.13 USB Flash

Works on all ROMs. Tweaking /etc/fstab may be necessary to get it to automount.

3.14 USB External Hard Drives

Works like USB flash, but needs a powered USB hub or power to the hard drive itself.

3.15 USB Ethernet

-Works with most distros (with external modules, used to be found at OESF)
-Pegasus and DM9601 are the common drivers

3.16 USB VGA

something

3.17 USB WiFi

-Needs a powered USB hub to work (unless you mod your Z)

3.18 USB GPS

Models with SirfStar II/III chipsets should work "out of the box" on most distros (verified on pdaXrom r198, IIRC). The module that needed to be loaded was "pl2303"

3.19 USB Optical Drives

Works like USB hard drives.

3.20 USB Keyboards

-Work on all ROMs (?) [only those with USB drivers on board or available]
-Keymap will be messed up (letters are probably OK, outside of that is chaos).

3.21 USB Mice

Works out of the box with:
pdaXrom
pdaXii13
Cacko
Angstrom(?)
OZ(?)

3.22 USB Hubs

powered vs. non-powered

Powered hubs have an adapter that plugs into them, allowing the Zaurus to use USB devices that draw more than the 200mA(?) that that Zaurus can put out. These can likely work without the adapter as normal USB hubs.

Non-powered USB hubs simply allow you to connect more devices to the Zaurus's USB port. This works so long as they don't collectively draw more than 200mA(?).

3.23 USB Host Cables

-Available from the likes of TriSoft and Conics
-One can be created out of a standard Mini-USB cable and a USB extension cable by simply stripping and connecting the corresponding wires, with the exception of the ground wire, which is attached to the black wire (I can't remember which pin that is).
--Note that this FORCES the Z into host mode, so you CANNOT use this as a client cable

3.24 USB Client Cables

something

3.25 IRDA keyboards

something

3.26 Serial JTAG cable

somethig

3.27 Internal Batteries

-EA-BL06 is for SL-C700 and SL-C750
-EA-BL08/EA-BL11 is for all of the other clamshell models, and the above with large battery cover (C700?)
-3.7v
-Official EA-BL06 capacity is 950mAh
-third-party batteries often need some plastic sanded or carved away from the contacts before they will function properly.
-third-party batteries may need tape on the side opposite the contacts to make them connect to the terminals and work OK (I used some 6-10 layers of Scotch)

-Good place to get batteries:
http://www.batteryupgrade.com/

3.28 External Batteries

something

3.29 Styluses

something

3.30 Misc cables

something

3.31 Zaurus Cases

something

3.32 Accessories Cases

something

3.33 Screen Protectors

something

4. Distributions/ROMs

Brief intro to Distros/ROMs here.

4.01 Sharp

something

4.01.01 Installing

something

4.01.02 FAQ

something

4.01.03 Software

something

4.01.04 How-To's

something

4.01.05 Development

something

4.01.06 Version 2.38

something

4.01.07 Version 3.10

something

4.01.08 Version 3.13

something

4.02 Cacko

something

4.02.01 Installing

something

4.02.02 FAQ

something

4.02.03 Software

something

4.02.04 How-To's

something

4.02.05 Development

something

4.02.06 Version 1.23

something

4.03 OE-OZ

-Predecessor to Angstrom
-Stable/mature
-Supports all (?) Z models
-GPE and OPIE variants

4.03.01 Installing

something

4.03.02 FAQ

something

4.03.03 Software

something

4.03.04 How-To's

something

4.03.05 Development

someting

4.03.06 Version 3.5.4 (collie)

something

4.03.07 Version 3.5.4.1 (clamshells)

something

4.03.08 Version 3.5.4.2-rc2 (tosa, poodle)

something

4.03.09 Version 3.5.5 (not released yet)

something

4.04 OE-Angstrom

-Builds for devices other than the Zaurus (Pandora, iPAQs, Simpads, etc.)
-Quite up-to-date
-Optimized on a per-device basis
-Large number of pre-built packages
-2.6.x kernel

4.04.01 Installing

Installed via the "normal" method (OK, option 4, yes, SD, etc.)

4.04.02 FAQ

something

4.04.03 Software

something

4.04.04 How-To's

Yes, you DO need a Linux box (not necessarily x86, but I assume the fastest box you have is x86, and that's what you want to use, or at least one with decent specs). I know Ubuntu works for this. Debian Sid had some issues, but sort of worked.

Note that I assume you're following these directions pretty much to the letter (ie, step 2 assumes you are in /OE)

0. Install the necessary stuff:

apt-get install python m4 patch build-essential make python-psyco ccache perl diffstat git bison

You may want to manually make sure you get the right stuff installed:

http://wiki.openembedded.net/index.php/Required_Software

1a. Make the directory /OE (you can use a different directory, but it's something of a pain) and allow normal users to write to it (you could chown it, for example)

sudo mkdir /OE<br />
sudo chown yourusername:users /OE

1b. Download Bitbake:

cd /OE<br />
wget http://download.berlios.de/bitbake/bitbake-1.8.10.tar.gz

2. Install Bitbake:

tar -xf bitbake-1.8.10.tar.gz

3. Get the OE data and update it (you may want to make a script for the last two lines, calling it "update.sh" or something):

git clone git://git.openembedded.net/openembedded.git org.openembedded.stable<br />
cd org.openembedded.stable<br />
git checkout -b org.openembedded.stable origin/org.openembedded.stable<br />
cd /OE/org.openembedded.stable<br />
git pull

4. Set up the environment file:

cd /OE<br />
wget http://www.angstrom-distribution.org/files/source-me.txt

5. Set up the build config (if /OE/build/conf/ doesn't exist, create it):

mkdir -p /OE/build/conf/<br />
yourfavoriteeditor /OE/build/conf/local.conf

Contents:

# Where to store sources<br />
DL_DIR = "/OE/downloads"</p>
<p># Which files do we want to parse<br />
 BBFILES := "/OE/org.openembedded.stable/packages/*/*.bb"<br />
BBMASK = ""</p>
<p># ccache always overfill $HOME....<br />
CCACHE=""</p>
<p># What kind of images do we want?<br />
IMAGE_FSTYPES = "jffs2 tar.gz "</p>
<p># Set TMPDIR instead of defaulting it to $pwd/tmp<br />
TMPDIR = "/OE/${DISTRO}-stable/"</p>
<p># For multicore CPU boxes:<br />
#PARALLEL_MAKE="-j4"<br />
#BB_NUMBER_THREADS = "2"<br />
#for single-core boxes:<br />
PARALLEL_MAKE="-j2"<br />
BB_NUMBER_THREADS = "1"</p>
<p># Set the Distro<br />
DISTRO = "angstrom-2007.1"</p>
<p># 'uclibc' or 'glibc' or 'eglibc'<br />
ANGSTROM_MODE = "glibc"</p>
<p>MACHINE = "akita"

6a. Start building your kernel module:

source /OE/source-me.txt<br />
cd /OE/org.openembedded.stable<br />
./update.sh<br />
bitbake whatever

6b. Wait a good chunk of time (several hours; don't try to do anything useful on this box while it's working)
---------------------------OLD-------------------------------------
I don't know if this should be kept or not....

This is almost a direct copy & paste from the Angstrom website, yet the readability and clarity updates are in progress.

Step 1

Obtain BitBake and OpenEmbedded These (compressed for now) files can go anywhere for now.

Step 2

Install BitBake and OE:

mkdir /OE && cd /OE<br />
tar zxf /path/to/bitbake-1.8.8.tar.gz<br />
bunzip2 /path/to/OE.mtn.bz2<br />
mtn --db=/path/to/OE.mtn pull monotone.openembedded.org org.openembedded.{angstrom-2007.12-stable,dev}<br />
mtn --db=/path/to/OE.mtn checkout --branch=org.openembedded.angstrom-2007.12-stable<br />
cd /path/to/org.openembedded.angstrom-2007.12-stable ; mtn pull monotone.openembedded.org org.openembedded.angstrom-2007.12-stable ; mtn update

Make sure /OE and its subdirectories are read/writable by standard users, as BitBake won't work as root.

You should probably also install psyco (called "python-psyco" in Debian, IIRC, Homepage)

Make a file in /OE to setup the environment variables (ex, /OE/sources-me.txt):

BBPATH=/OE/:/OE/build/:/OE/org.openembedded.angstrom-2007.12-stable/<br />
PKGDIR=/OE/build/<br />
DL_DIR=/OE/downloads<br />
echo Setting up dev env for Ångström</p>
<p>if [ -z ${ORG_PATH} ]<br />
then<br />
 ORG_PATH=${PATH}<br />
  export ORG_PATH<br />
 fi</p>
<p> if [ -z ${ORG_LD_LIBRARY_PATH} ]<br />
  then<br />
   ORG_LD_LIBRARY_PATH=${LD_LIBRARY_PATH}<br />
    export ORG_LD_LIBRARY_PATH<br />
        fi<br />
        PATH=/OE/bitbake-1.8.8/bin:${ORG_PATH}<br />
        cd $PKGDIR<br />
        LD_LIBRARY_PATH=<br />
        export PATH LD_LIBRARY_PATH BBPATH<br />
        export LANG=C<br />
        echo "Altered environment for OE Development"

Step 3

Add the following to your local.conf. It doesn't currently exist. Make it in /OE/build/conf.

# Where to store sources<br />
DL_DIR = "/OE/downloads"</p>
<p># Which files do we want to parse:<br />
BBFILES := "/OE/org.openembedded.angstrom-2007.12-stable/packages/*/*.bb"<br />
BBMASK = ""</p>
<p># ccache always overfill $HOME....<br />
CCACHE=""</p>
<p># What kind of images do we want?<br />
IMAGE_FSTYPES = "jffs2 tar.gz "</p>
<p># Set TMPDIR instead of defaulting it to $pwd/tmp<br />
TMPDIR = "/OE/build/tmp/${DISTRO}"</p>
<p># Uncomment the following two lines if you have a multi-core CPU<br />
#PARALLEL_MAKE="-j4"<br />
#BB_NUMBER_THREADS = "2"</p>
<p># Set the Distro<br />
DISTRO = "angstrom-2007.1"</p>
<p># 'uclibc' or 'glibc' or 'eglibc'<br />
#ANGSTROM_MODE = "glibc"</p>
<p>MACHINE =  "YOURMACHINE" 

Substitute "YOURMACHINE" with the machine you want to build for, e.g.:

* c7x0 - For pxa25x zaurus clamshells (SL-C700, SL-C750, SL-C760, SL-C860, SL-7500)
* spitz - For pxa27x zaurus clamshells with a microdrive (SL-C3000, SL-C3100, SL-C3200)
* akita - For pxa27x zaurus clamshells without a microdrive (SL-C1000)
* tosa - For the SL-C6000

Note that the only difference between Spitz and Akita is that Akita will install to NAND and Spitz will install to the microdrive. You can use an Akita image on C3100 and C3200 machines. Spitz images cannot access the NAND AFAICT.

Step 4

Start building:

source source-me.txt ; cd /path/to/org.openembedded.angstrom-2007.12-stable ; mtn pull ; mtn update ; bitbake IMAGE_OR_PACKAGE_NAME

Where IMAGE_OR_PACKAGE_NAME is the name of the install image or package you want to build. Building the first package/image will take a good while, as EVERYTHING needs to be built (cross tools, all of the packages in the image, deps, etc.)

Step 5

Building for a different machine or C library is just a matter of changing the MACHINE= or ANGSTROM_MODE statement in local.conf to a new value. There is ABSOLUTELY no need for using different directories for that; Angstrom takes care of all the details, it was specifically designed for this.

Other notes
*These files take up a lot of space. If you intend to build more than a couple of packages/images, have some 10-20GB of space available.

4.04.05 Development

something

4.04.06 Unstable Releases

something

4.04.07 RC1

something

4.05 pdaXrom

something

4.05.01 Installing

something

4.05.02 FAQ

Q: (Jon_J) Can "pdaXii13-custom.tgz (patching only)" be used on a pdaxii13-akita5.3 installation to update it to pdaxii13-akita5.3.2 ?
A: (from a post by Meanie)
upgrading works for all versions (of course you won't get the new apps installed which you need to install yourself)
hdimage-custom.tgz != pdaXii13-custom.tgz

Q: What is the pdaXii13 boot sequence on a C3000?
A: (from a post by Meanie)
pdaXii13 boot sequence...

The boot and startup process on pdaXii13 Spitz is a bit different from the standard pdaXrom because of its small flash:
1. load kernel from NAND
2. read and mount NAND partitions
3. load /sbin/init interceptor from rootfs on NAND
4. initialize and mount MicroDrive
5. pivot rootfs to MicroDrive
6. execute /sbin/init from MicroDrive
7. initialise core hardware
9. mount internal filesystems
8. load kernel modules
10. load inittab and rc subsystem
11. run rc.local
12. run scripts in /etc/rc.d/rc3.d or /etc/rc.d/rc5.d
13. /etc/rc.d/init.d/local is run from either rc3.d or rc5.d
14. start X if runlevel 5
15. if using openbox/matchbox (default) load mb-applet-tasks
16. task applet will run /home/root/.matchbox/autoexec
17. once X is exited, console login is loaded
18. /etc/issue is displayed
19. when reboot is issued, scripts in /etc/rc.d/rc6.d are run
20. /etc/rc.d/init.d/halt is last script to be run before reboot

4.05.03 Software

something

4.05.04 How-To's

How to set up TCP/IP over USB with Win XP

How to set up TCP/IP over USB with Linux

4.05.06 Version Beta 1

something

4.05.05 Development

-Currently being re-built from scratch (2008/10/25)

4.05.07 Version Beta 2

something

4.05.08 Version Beta 3

something

4.05.09 Version Beta 4

something

4.05.10 Version R121

something

4.05.11 Version pdaXii13

pdaXii13 overview/info site
- http://www.users.on.net/~hluc/myZaurus/pdaxii13.html
- http://zaurus.daemons.gr/menaie/mirror/pdaxii13.html

pdaXii13 main (C3000) downloads
- http://www.tyrannozaurus.com/feed/pdaXii13/files/index.html

pdaXii13 alpha/beta downloads and release notes
- http://www.tyrannozaurus.com/feed/pdaXii13/tmp/index.html

pdaXii13 for C1000/C3100/C3200
- http://www.tyrannozaurus.com/feed/pdaXii13/akita/index.html

pdaXii13 5.3.x upgrade/info page
- http://www.tyrannozaurus.com/?q=node/210 (need to fix link)

pdaXii13 build/development files
- http://www.tyrannozaurus.com/feed/pdaXii13/build/index.html

pdaXii13 updates/development info
- http://www.tyrannozaurus.com/?q=node/74 (need to fix link)

zgcc image for pdaXrom/pdaXii13 info
- http://www.tyrannozaurus.com/?q=node/75 (need to fix link)

pdaXrom and pdaXii13 development info
- http://www.tyrannozaurus.com/?q=node/214 (need to fix link)

new packages for pdaXrom/pdaXii13
- http://www.tyrannozaurus.com/?q=node/141 (need to fix link)

installation/upgrade instructions

Antikx's pdaXii13 5.3.3 Akita Full install on SD Instructions

-Flash your Akita to 5.3.3 ( http://www.tyrannozaurus.com/feed/pdaXii13/akita/ )
-backup your card and then fdisk it so that you have two primary partitions (vfat first then ext2)
-download the latest hdimage-full file ( http://www.tyrannozaurus.com/feed/pdaXii13/tmp/hdimage-full.tgz )
-copy it over to your ext2 partition
-extract the tar/gzip file, and then move all the stuff in the hdd1 directory into the root of your ext2 partition
-at the root of your ext2 partition tar up the "home" and "etc" directories
-copy the tar files to the root of your flash
-copy the files /etc/rc.d/rc.rofilesys, /etc/rc.d/rc.sysinit, /etc/rc.d/init.d/halt and /etc/issue from etc and put them somewhere safe
-extract the tar files
-copy those four files you saved back to where you found them
-reboot

Meanie's pdaXii13 (5.3.x) Upgrade Instructions

You can use the upgrade process to upgrade from pdaXrom beta1/beta3 to pdaXii13 or upgrade an existing pdaXii13 to the latest release/build.

pdaXii13 starting from build 5.3.1 is available in 3 different editions:

Alice (pdaXii13 Spitz) for C3000 - this exists as base and full and can be installed via the flash installer. Alice for C3000 cannot be upgraded from pdaXrom since there is no official pdaXrom beta1/beta3 for C3000. Upgrading an existing Alice install can be done by simply reflashing hdimage-full.tgz or hdimage-base.tgz (full upgrade) or by using pdaXii13-custom.tgz (patching only). When using the patching only method, new or updated packages will need to be manually added and replaced. See the release notes for a list of newly added packages which you need to install manually and updated packages which need to be replaced, ie uninstall existing package and install new package. C3100/C3200 can also use Alice, but it is recommended for C3100/C3200 to use Sally instead. To install a new copy of Alice on C3100/C3200, you first need to either flash pdaXrom beta3 or pdaXii13 Akita base before flashing pdaXii13 Spitz. C3100/C3200 with Spitz installed can upgrade to latest version of Alice just like upgrading Alice for C3000.

Sally (pdaXii13 Akita) for C1000/C3100/C3200 - this exists as base only and can be installed via the flash installer. It can be extended to the full edition by additionally flashing the hdimage-full.tgz file for Alice on the C3100/C3200. Upgrading the base edition can be done by simply reflashing the NAND (full upgrade) or by using pdaXii13-custom.tgz (patching only). Upgrading the full edition requires both reflashing with hdimage-full.tgz and using pdaXii13-custom.tgz. pdaXrom beta1/beta3 can be upgraded to pdaXii13 Akita base using pdaXii13-custom.tgz as well

Charlie (pdaXii13 Corgi) for C7x0/C8x0 - this edition does not have a flash installer. It requires pdaXrom beta1 installed first and then can be upgraded using pdaXii13-custom.tgz

using pdaXii13-custom.tgz (make sure you have a backup in case something goes wrong)

1. download and extract http://www.tyrannozaurus.com/feed/pdaXii13/build/pdaXii13-custom.tgz (preferably to CF rather than SD)
2. exit X if you have not already done so
3. shutdown all unneccesary services including SD service (/etc/rc.d/init.d/sd stop)
4. change directory to where the files have been extracted (eg. cd /mnt/cf/custom)
5. run ./install-fix-beta3.sh / upgrade
6. reboot

For full install instructions see the following links:
http://www.users.on.net/~hluc/myZaurus/pdaxii13.html#install
http://www.tyrannozaurus.com/feed/pdaXii13/akita/

Alice vs Sally on C3100/C3200

Alice runs completely off the internal MicroDrive and is intended for C3000 since its NAND is too small. C3100/C3200 can pretend to be a C3000 and install to the MicroDrive as well and not use the NAND. The Alice installer puts a C3000 specific kernel and a small pivot rootfs onto the NAND. The Alice installer cannot do this for C3100/C3200, hence they need to have pdaXrom beta3 or pdaXii13 Akita base installed first which will provide the kernel and initial rootfs. Then using the Alice installer, the rootfs is patched to pivot to the MicroDrive just like for the C3000 and the hdimage is extracted to the MicroDrive.

Sally runs from the NAND and is intended for C1000/C3100/C3200 since they all have a 128MB NAND. But because the C3100/C3200 also have a MicroDrive in addition to the NAND, the hdimage used for Alice can be installed to the MicroDrive on C3100/C3200. The Sally installer has an option to install the hdimage for C3100/C3200. The difference to running Alice on C3100/C3200 is that the NAND is used to hold the rootfs and it is not pivoted to the MicroDrive, rather it extends /usr to the MicroDrive using the bind feature instead.

Danboid's Pdaxii13 (5.2) On C3100, Install Instructions

This is an unofficial method of installing pdaXii13 full on a c3100 or c3200 as first discovered by Archimark.

Note that there is now a pdaXii13 Akita which is a bug fixed and improved pdaXrom b3 for c1000, c3100 and c3200 models which in the future may let you upgrade to pdaXii13 full by storing /usr on the Microdrive but this install method isn't known to be working currently. pdaXii13 Akita is unsupported by Meanie and the pdaXrom team have moved onto a kernel 2.6 based distro.

Neither Meanie, Archimark, myself or anybody else will take any responsibility for any damage or loss of data that may arise as a result of following these instructions. You follow these instructions entirely at your own risk! Make sure to read all the bugs (it is not perfect yet - it has a 10m+ boot time for one) and that you know how to get restore a working OS in case you find you can't switch or prefer Sharp/Cacko/OZ. If you have any corrections let me know and I'll update this post.

pdaXii13 5.2 full installation on c3100/c3200

c3100 (and c3200) owners must use v0.25 of the pdaXii13 updater.sh and build 15 of updater-tools.bin which are available on the pdaXii13 alpha/beta page here

http://www.tyrannozaurus.com/feed/pdaXii13/tmp/

In addition to having all the files required to install pdaXii13 on a c3000, you will also need pdaXrom beta3, which you can download from

http://mail.pdaxrom.org/download/1.1.0beta...beta3-akita.zip

Install that first as per the instructions on the pdaXrom.org site. I don't think it matters what size you flash the NAND to, the point is just to get b3 installed before pdaXii13, but I'd recommend going for the maximum size of 121 and why not?

Then install pdaXii13 as per Meanies instructions for c3000 but you need to install the kernel and bootloader TWICE, once before and one after installing the hdimage.

Reboot and enjoy the joys of having a full, truly portable Linux workstation!

BUGS in 5.2, using this install method:

1. On the initial boot after install, it will pause and the MD light will flash for around 15 minutes just after it says

EXT3-fs: mounted filesystem with ordered data mode

On subsequent boots it pauses on this message for a while, 5-10m.

2. Shortly after that it will produce a few, if not a few hundred

invalidate:dirty buffer

errors but meanie says this is harmless- YMMV!

3. To mount your vfat hda3 partition as a USB disk, choose the device

Compact Flash (0,3)

under the USB settings tool- this option is the equivalent of what would show up as 'Internal Storage' on a c3000. You should find that you will have one SD card option and six CF slot options so if CF (0,3) doesn't work for you can try CF (0.2) or (1,3).

BUGS PRESENT ON pdaXii13 C3000 5.2 ALSO

1. Firefox crashes when accessing websites with Flash. Fix: remove the flash plugin library called libnpflash.so under /usr/lib/firefox/lib/firefix-1.5/plugins

2. The Cancel key on the side of the Zaurus doesn't seem to do anything when running xmms. To fix this, edit /etc/X11/kb/spitz.xmodmap and uncomment

keycode 92 = Return
keycode 102 = c

to make the OK button play and the cancel key pause. This also applies when installing on c3000

3. There are some unwanted keybindings remaining (in the openbox config file /etc/xdg/openbox/rc.xml I think) which could cause problems to those using USB keyboards. Below is a list of USB keys and their current actions under 5.2

KEY | ACTION

Alt_Gr (Right Alt) | Starts Stardict

Right Windows Key | Starts rox

Print Screen | Starts xmms

F5 | Starts mrxvt

F6 | Startx xmms

F7 | Starts rox

F9 | Starts dillo

ESSENTIAL TIPS

* Uninstall all the scim packages if you don't need Chinese input support! I used a stopwatch to time how long gnumeric took to load- it took 34s when it had to load scim and only SEVEN seconds to load when I uninstalled scim! Just turning off SCIM support in the pdaXii13 config file isn't enough.

* If you want to change the font size of GTK2 based apps like rox, abiword, gthumb, gnumeric (most X apps used under pdaXrom are GTK2 based) then edit this file

/usr/share/themes/Default/gtk-2.0/gtkrc

TO ADD/DUNNO LIST

Working instructions for upgrading pdaXii13 Akita to use the hdimage

How to fix the module dependencies error under pdaXii13 Akita

A comparison of the two pdaXii13 full install methods for c3100/c3200 owners

4.06 Open BSD

something

4.06.01 Installing

something

4.06.02 FAQ

someting

4.06.03 Software

something

4.06.04 How-To's

something

4.06.05 Development

something

4.06.06 Version ?

something

4.07 Net BSD

something

4.07.01 Installing

something

4.07.02 FAQ

something

4.07.03 Software

something

4.07.04 How-To's

something

4.07.05 Development

something

4.07.06 Version ?

something

4.08 Gentoo

something

4.08.01 Installing

something

4.08.02 FAQ

something

4.08.03 Software

something

4.08.04 How-To's

something

4.08.05 Development

something

4.08.06 Version ?

something

4.09 Debian

-Huge number or available packages (all of the Debian armel packages)
-Very up-to-date (as up-to-date as Debian)
-Not optimized for the Zaurus
-Fairly bug-free/supports most hardware
-Runs Angstrom or custom (yonggun/other) kernels

4.09.01 Installing

something

4.09.02 FAQ

something

4.09.03 Software

something

4.09.04 How-To's

something

4.09.05 Development

something

4.09.06 Version ?

something

5. Linux

very brief intro to Linux

5.01 Linux Primer

The following pages go through the basic Linux stuff to get you up to speed on things and terms that people may throw about.

5.01.01. File Structure

File structure:

Linux has a slightly different file structure from Windows. It doesn't have "drives," like C: or D:. Instead, it has one main drive (/), and everything else is mounted within that

A quick look at the directories:

/: The "root" of your filesystem. This is where everything begins and is stored; everything else branches out from here. / has no parent directory.

/dev: Since everything appears as a file in Linux, this is where devices appear (a device being a sound card, virtual terminal, GPS, USB drive, hard disk, etc.). You can't really do anything directly to these devices, but knowing if they exist or not is a good way to tell if drivers loaded OK or if the device is recognized at all.

/mnt and /media: This is where external things are mounted, such as CDROMs and USB drives. They would be mounted in subfolders, like /media/cdrom for a CD.

/etc: This subdirectory holds configuration files for just about everything.

/usr: Contains most user stuff (programs, libraries, etc.).
/usr/bin: Most executables go here
/usr/lib: Most libraries go here
/usr/include: Development headers for compiling go here

5.01.02. Devices

Devices

Everything in Linux is a file, even your hard drive (yes, your hard disk has a file representing itself on itself). This section covers these such files, the ones representing hardware and other devices.

These files, as stated in the previous section, are found in /dev, or the folder called "dev" in the very bottom or root of the drive. The following is a list of common files found there, what they are, and what you can do with them.

/dev/hdXN and /dev/sdXN: These devices (such as /dev/hda1 or /dev/sdb3) are hard drives/USB drives and partitions. X is a letter, starting from "a," then moving on as more devices get added. For instance, /dev/hda is the first IDE/CF drive in the computer, and /dev/hda1 is the first partition on that drive. N is the number of the partition.

USB devices appear as /dev/sdXN, as do SATA drives. SD/MMC devices appear as /dev/mmcblkXpN, but in that case X is a number as well (starting from 0). CF cards appear as IDE devices, or /dev/hdXN.

What you can do with them: There are several things to do with these devices, but the most common is to mount it, or make the drive accessable. You do that through the mount command:

mount /dev/deviceandpartition /mount/point

You can also format them, eg:

mkfs.ext2 /dev/sda1

will make an EXT2 filesystem on the first partition of the first USB/SATA device.

5.01.03. The Command Line

The Command Line

The command line is a commonly used tool in Linux, and, quite contrary to popular belief, it is NOT hard to use or frightening. This section will (hopefully|attempt to|try to) get you up to speed on the CLI (Command Line Interface).

Commands: A command is simply something you type into the CLI, such as "ping" or "grep." It may give useful output, run a program, or do something else.

Command flags: A flag is simply something you pass to the command to tell it to do something special or different. Take the example:

ls -l -h

In this example, 'ls' is the command (it lists the files in the current directory), and 'l' and 'h' are the flags. The '-' in front of the 'l' and 'h' mean that they are flags and not arguments. This command could actually have been written

ls -lh

because most Linux commands allow you to squish the flags together after the dash. That won't always work, however, if the flag requires an argument:

ping -c 4 127.0.0.1

You couldn't just add a random flag before or after (this may be false) the "c" and expect it to work fine (in this case, the 'c' flag means to limit the number of pings, and 4 is the argument given to that flag telling it how many pings to limit itself to).

In general, the 'h' flag (-h, or --help) gives information on what flags are available for the program and what they do:

#command -h
usage: command [flags] ARGUMENT [argument2...]
#

In this example, you run 'command' and optionally pass flags (the brackets mean optional), then give it an argument, optionally with more arguments.
Arguments:

Command reference: http://tyrannozaurus.com/node/181

5.02 Command Reference

something

5.02.A

A

5.02.B

B

5.02.C

C

cd NEW-DIRECTORY
Changes the working directory to NEW-DIRECTORY. If no argument is given, it will change you to your home directory.

clear
Clears all the text from the terminal screen (it is still stored in the scrollback buffer, however)

cp [-r] FILE|FOLDER PLACE|NAME-TO-COPY-TO
This command takes two arguments and copies the first one (the file, FILE|FOLDER) to the location and/or name specified in the second argument (PLACE|NAME-TO-COPY-TO). The -r flag can be passed if you wish to copy a directory.

5.02.D

D

df
This command will print information about what devices are mounted where and total/free space. Add the -h flag to print the space info in MB/GB instead of bytes (easier to read).

5.02.E

E

exit
Quits the shell (and, unless other tab are open or some other circumstance, the terminal)

5.02.F

F

fdisk DEVICE
This command starts the fdisk program to change partitions on a disk. The DEVICE is /dev/xyz (where xyz is NOT xyz1, xyz2, etc., eg no number).

free
This command prints out how much RAM/swap is available/used.

5.02.G

G

grep SEARCH-TERM FILE
Grep prints out every line SEARCH-TERM appears on in file FILE. If SEARCH-TERM is more than one word, you must put quotes around it.

5.02.H

H

5.02.I

I

insmod /FULL/PATH/TO/MODULE.ko
This inserts the given module into the kernel, similar to modprobe, but needs the full path to the module.

5.02.J

J

5.02.K

K

kill [-9] PID
Stops the process with the ID PID, which can be found with "top." The -9 flag can be used to force the stopping if the program is really locked up.

killall APPLICATION-NAME
Stops the process corresponding to APPLICATION-NAME. Works well if used with "top."

5.02.L

L

ln -s
Makes appear to be located in/at . Useful if you want to, for instance, put a shortcut to your SD card in your home directory.

ls [-a] []
Lists the files and folders in the current directory (or whatever directory you specify with the optional ). The -a flag will also make it list the hidden files/folders in said directory (files/folders starting with ".").

5.02.M

M

mkdir [-p] DIRECTORY
This command makes the directory DIRECTORY. If you use the -p flag, you can make a tree of directories, otherwise the outermost directory's parent directory must exist.

modprobe MODULE
This command loads the module MODULE. Underscores and dashes are treated the same. A smarter version of insmod.

mount DEVICE [LOCATION]
This mounts device DEVICE (/dev/xyzn, eg WITH the number) at location LOCATION. If the device is in /etc/fstab, you do not need to specify LOCATION (and have admin rights).

mv FILE|FOLDER DESTINATION
Move. This command moves FILE|FOLDER to DESTINATION. It is also used to rename a file (eg, "mv abc xyz" will rename abc to xyz).

5.02.N

N

5.02.O

O

5.02.O

O

5.02.P

P

ping HOSTNAME|IPADDRESS
This sends network packets to the given host, testing network connectivity.

ps aux|grep SEARCH_TERM
This command is good for finding process IDs. On full linux systems, "ps aux" lists more detail about the processes than does the straight "ps" command, and then by piping it through grep, you filter out all but the ones you're interested in.
Note that the busybox version of "ps" does not accept any arguments, so the same thing can be accomplished on Zaurii which only have the BusyBox version of "ps", by entering: "ps | grep SEARCH_TERM"
If you have a fully featured version of "ps" and just are looking for a particular application or command process, then it makes more sense to enter the command "ps -C COMMAND"

pwd
Print Working Directory The command prints your current working directory.

5.02.Q

Q

5.02.R

R

5.02.R

R

rm [-r]
Remove. This command removes file or, with the -r flag, folder . You can pass multiple files or folders to it ("rm -f folder1 file1 file2").

rmdir DIRECTORY_NAME(S)
This command removes a directory or set of directories. It will not remove the directory if the directory (folder) contains any files.

5.02.S

S

5.02.T

T

top
Shows information about running processes.

5.02.U

U

umount device|mount-point
This command unmounts (notice that the command is "umount," no "n") the device specified, or the device mounted at mountpoint mount-point.

uname -a
Prints out a bunch of potentially useful information about your system, including kernel version. See the output of "uname --help" for which flags to use to get specific information.

5.02.V

V

5.02.W

W

wget URL
Downloads the file at (useful for images, ipks, etc.).

whoami
Prints the current user's name

5.02.X

X

5.02.Y

Y

5.02.Z

Z

6. Links and Other Resources

Some how pulled from the ty "UserLink" list. *scratches head*
This is a work in progress.

6.1 Userlinks from tyrannozaurus.com

something

6.2 ScummVM for the Zaurus

Welcome to the homepage of ScummVM@tyrannozaurus

-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------

Table of Contents

Introduction
Acknowledgements
Downloads
What Games are Supported?
Configuration Tips
What files are needed?
Audio File Compression How-To
Video File Compression How-To
Adding a Game to the ScummVM Main Screen
In Game Controls
Available Themes
Hints and Walkthroughs
Useful Links

-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------

Introduction

This is a joint project between HoloVector and Antikx that strives to provide the fullest and best ScummVM experience for clamshell (CXX0 and CXX00) Zaurus users under the pdaXrom distro. One the main goals of project is to provide an accelerated ScummVM that could run Broken Sword MPEG2 cut scenes smoothly. Most of the previous builds for the Sharp-based and pdaxrom-based ROMs out there could not run the MPEG2 cut scenes from the Broken Sword games. The OE-based ports could only run jerky reencoded cut scenes at 320x240 because they lacked bvdd support. This version can run these cut scenes at 480x304 with minimal dropped frames.

Please comment below or PM us if you have comments or suggestions.
Please go to the project page and submit bugs and feature requests for the IPK.
-------------------------------------------------------------------------------------

Acknowledgements

Like all open source projects this port became a reality thanks to the work of many diverse people. We would like to take this opportunity to thank them. They are:

The ScummVM Team for making a great and highly portable interpreter for many of our favorite games and then creating the infamous ScummVM Tools that allows us to compress the data files to a more suitable Zaurus size.

Antikx for taking the time to build this port and host not only the ipk but all the associate files in the Downloads section and this home page.

Meanie for building his native GCC environment for the Zaurus and helping Antikx with the build details.

The pdaXrom Team for building the best Zaurus distro to run ScummVM on, IMHO .

Alex/Alez for creating the run script, desktop shortcut, keyboard remap and the original 0.9.0 Modern theme ipk.

kkazakov13 for creating the updated 0.9.1 theme ipks for Modern, Modern Ice, Modern Blue and Modern Dark.

Arisme for hosting the Broken Sword cutscene re-encoding package and creating the mini how-to for it.

bgbennyboy for creating the graphical ScummVM ToolBox for Windows.
-------------------------------------------------------------------------------------

Downloads

Here's the goodies...
Project page: get ipk here
Broken Sword 1 videos in English: bs1video
Broken Sword 1 videos in French/en Francais: bs1videofr
Broken Sword 2 videos in English: bs2video
Broken Sword 2 videos in French/en Francais: bs2videofr
Modern Theme: Modern
Modern Ice Theme: Modern Ice
Modern Blue Theme: Modern Blue
Modern Dark Theme: Modern Dark
-------------------------------------------------------------------------------------

What Games are Supported

The original scope of the main ScummVM project (not the Zaurus off-shoot) was to support all the Graphic Adventure games from LucasFilm Games/LucasArts that were written for the Scripting Creation Utility for Maniac Mansion (AKA SCUMM) engine so that the games could run on more modern computers and platforms that the original interpreters were never ported to (like the Zaurus). Later on it was decided to increase the scope of the project to include many other game engines.

Here is the basic list of supported games in this version:

LucasArts/Lucasfilm Games

Maniac Mansion
Zak McKracken and the Alien Mindbenders
Indiana Jones and the Last Crusade (A Graphic Adventure)
LOOM
The Secret of Monkey Island
Monkey Island 2: LeChuck's Revenge
Indiana Jones and the Fate of Atlantis (A Graphic Adventure)
Maniac Mansion 2: Day of the Tentacle
Sam & Max Hit the Road
Full Throttle
The Dig
The Curse of Monkey Island

Revolution Software

Beneath a Steel Sky*
Broken Sword 1: The Shadow of the Templars (AKA The Circle of Blood)
Broken Sword 2: The Smoking Mirror

Interactive Binary Illusions

Flight of Amazon Queen*

Coktel Vision

Gobliiins

The Dreamer's Guild/Wyrmkeep Entertainment Company

Inherit the Earth: Quest for the Orb

Adventure Soft Publishing Limited

Simon the Sorceror 1
Simon the Sorceror 2
The Feeble Files

Westwood Studios

The Legend of Kyrandia 1*

and a whole lot of Humongous Entertainment Games

A more complete compatibility list can be found here. Not all versions of the games are supported or are not completely supported so please check the above link for more detailed information. A general rule of thumb for support in ScummVM is that if you have the DOS or Windows version of a game it is highly likely that it will be completely supported.

Games marked with a * are either freely available for download or require additional files which you can get by clicking on the *. You do not need to download the Broken Sword cut scenes that are linked on the above page because they are unsuitable for use with the Zaurus. Please use the cut scenes above in our Downloads section.

The publishers of Beneath a Steel Sky and Flight of the Amazon Queen have graciously donated the source code for these games to the ScummVM team and have released these games as freeware so you can freely download them and play them in ScummVM. Many thanks to Revolution Software, John Passfield and Steve Stamatiadis for their wonderful donations.
-------------------------------------------------------------------------------------

Configuration Tips

To get the full ScummVM experience we recommend that you run ScummVM in Fullscreen mode with the Aspect ratio correction turned on and the AdvMAME2x graphics filter turned on. ScummVM will run slightly faster when you enable Fullscreen mode and use the optimized AdvMAME2x filter. The main purpose of the AdvMAME2x is to smoothly scale the graphics up to 640x480 without the nasty looking jaggies but, as an added benefit this filter is bvdd or ati accerelated thanks to it's dependency on SDL to do it's magic. We recommend AdvMAME2x because is well suited to the Zaurus due to it's low system requirements compared to the similar hq2x filter which was designed for a desktop environment. Aspect ratio correction is needed to fix the mouse cursor positioning in the scaled up games and prevent graphics distortion that would make a circle look like an oval.

You can turn on the Fullscreen mode and Aspect ratio correction by tapping on the Options button on the main GUI screen and then tapping on the checkboxes for both of those options. Both boxes should then have x's in them. Don't tap the OK button yet because we still need to turn on the graphics filter.

To turn on the AdvMAME 2x graphics filter tap and hold on the double headed arrows for the Graphics mode. A large list of the graphics filters will appear. Keeping your pen pressed to the screen, slide the tip to highlight the AdvMAME2x entry and release the pen tip from the screen. The Graphics mode box should then say AdvMAME2x.

After that tap the OK button to save and close the Options screen and then tap on the Quit button to exit ScummVM. You need to quit to enable the changes you just made.
-------------------------------------------------------------------------------------

What files are needed?

Because ScummVM is replacing the original interpreter you will only need the core data files in order play the game. This is a good thing since it will cut down on the amount of space you will need on your Zaurus. The following link lists the main files required in order to play the supported games. If you follow its guidance closely you will have a working game under ScummVM on Zaurus that will take the least amount of space. Audio and Video compression is covered in the next section

http://wiki.scummvm.org/index.php/Datafiles

Once you have determined what files you require you need to copy it over to your Zaurus. If you are copying it to a 3x00, we highly recommend copying under the /data/ folder (which links to hdc3)on those units. For the other clamshells we recommend copying the files over to /mnt/card/. Make sure that each game has its own subfolder. Here are a couple example layouts for you to consider:

/data/Documents/Game_Files/indy4/
or
/mnt/card/scummvm/zakfm/
-------------------------------------------------------------------------------------

Audio File Compression How-To

There are many types of audio used in the supported games such as sound effects, dialog, and music. The one thing that these audio types have in common is that the audio, in most cases, is stored in low or uncompressed formats. Uncompressed audio takes a significant amount of space so, it is in your best interest to compress the audio of these games.

ScummVM offers many choices for alternate audio formats, these include MP3, Ogg Vorbis, and FLAC. FLAC is not recommended for the Zaurus since this lossless format will actually create larger files than the original uncompressed files. Ogg Vorbis on the Zaurus has performance issues and therefore can lead to gameplay degradation. Therefore, MP3 should be your target format for the Zaurus since MP3 will give you the best performance/compression ratio of these choices.

You will require a copy of the lame encoder in order to perform these compression steps. Here is a link to a DOS based one that I have used. Depending on which type of compression you need to perform; it is possible to do some of this encoding on your Zaurus if you have a significant amount of disk space. However, since you will need a CD-ROM drive or in some cases a floppy drive to extract the raw audio files I recommend using a desktop platform of your choice instead.

Some of the games will require that you use something called the ScummVM Tools in addition to the lame encoder because of the way the audio was stored. The command line based ScummVM Tools are precompiled for the following platforms: Windows, Fedora Core 2 and 4, Mac OS X Universal, Solaris 8 and 10 and Atari/FreeMint. Since ScummVM is a LGPL licensed project, the source to the tools is available for your compiling pleasure. Please note that there are no plans at this time to compile these tools for the Zaurus but, you never know... Also note that there is a GUI front-end for Windows available for some of the ScummVM Tools tools called the ScummVM ToolBox. You can find it here.

Instead of reinventing wheel explaining the steps required to compress the audio for some of the supported games I will merely point you to the ScummVM 0.9.1 Read Me file which is located here. The section you require is 7.7.

I will spell out which subsection instructions you need to use for which game though so, here we go:

7.7.0 - Zak McKracken and the Alien Mindbenders (FM Towns only), Indiana Jones and the Last Crusade (FM Towns only), LOOM (PC CD and FM Towns), and The Secret of Monkey Island (PC CD and FM Towns)

7.7.3 - Monkey Island 2: LeChuck's Revenge (FM Towns only), Indiana Jones and the Fate of Atlantis (PC CD, Mac CD* and FM Towns), Maniac Mansion 2: Day of the Tentacle (PC CD, PC Floppy, and Mac CD*), Sam & Max Hit the Road (PC CD, PC Floppy and Mac CD*), Full Throttle (PC CD and Mac CD*)

7.7.6 - Simon the Sorceror 1 and 2 and The Feeble Files

7.7.7 - Broken Sword 1 (note this is for in game audio not the video cut scenes mentioned above)

7.7.8 - Broken Sword 2 (note this is for in game audio not the video cut scenes mentioned above)

* = The Mac CD monster.sou audio is stored in a single file called Game Name Data that also contains the rest of the game files. In order to compress the monster.sou file you will need to split up the Data file into it's component parts first (effectively turning it into the PC version) and then running the SOU compression utility. The ScummVM tool you would use to break up the Data file is called

extract_scumm_mac

The following games do not have their compression instructions included in the above linked ScummVM 0.9.1 ReadMe so, I will quote the ScummVM Tools ReadMe file included in the ScummVm Tools download instead.

For Full Throttle, The Dig and The Curse of Monkey Island follow these directions and compress the audio to MP3.

"compress_scumm_bun [inputfile] [inputdir] [outputdir] [--ogg] Compresses '.bun' music/voice files.

Example of usage: compress_scumm.bun digmusic.bun uncomp comp
For the Ogg or Mad compression feature, your ScummVM binary naturally must have been built with Ogg or Mad support enabled."

For The Legend of Kyrandia 1 follow these directions and compress the audio to MP3

"compress_kyra Used to compress The Legend of Kyrandia's speech files with MP3, Vorbis or FLAC.

Example of usage: compress_kyra [flags here] input/GEMCUT.VRM output/GEMCUT.VRM

Note: You have to keep the VRM extension, else it will NOT work. Use it like shown above, copy all *.VRM files to a directory and let the tool put the output file in another directory."

The flag you want to use in this case is --mp3
-------------------------------------------------------------------------------------

Video File Compression How-To

Several of the supported games use complex animated cut scenes to help move their stories along. Due the age of some of these games the cut scenes are using non-compressed video and audio formats. In order minimize the disk footprint of these games on your Zaurus it is in your best interest to compress these cut scenes using the tools mentioned below.

The following LucasArts Games make use of SMUSH formatted animation, Full Throttle, The Dig and The Curse of Monkey Island. You can one again use the ScummVM Tools or the ScummVM ToolBox for Windows previously mentioned in the Audio File Compression How-To above. Here is a quote from the ScummVM Tools readme on SMUSH compression tools usage.

"compress_scumm_san [inputfile] [inputdir] [outputdir] [--ogg]
Compresses '.san' smush animation files. It uses lossless
zlib for compressing FOBJ gfx chunks inside a san file.
It also can create a separate Ogg file with the audio track.

Example of usage: compress_Scumm_san opening.san uncomp comp

In order to use such compressed files, your ScummVM binary must have been built with zlib support enabled (you can find out whether that's the case by looking at the About dialog). For the Ogg or Mad compression feature, your ScummVM binary naturally must have been built with Ogg or Mad support enabled.

NOTE: For some '.san' files there is a corresponding '.flu' file, which contains offsets into the '.san' file. Hence, the compress_scumm_san has to modify the '.flu' file. This happens automatically, if the '.san' and '.flu' files are in the same directory (which is normally the case). If you want to move the '.san' files before compressing them, make sure to
move the '.flu' files, too!"

The Revolution games Broken Sword 1 and 2 also use an unsuitable, for the Zaurus, animation format called Smacker. The owners of the format, RADTools, have specifically requested that the ScummVM team does not reverse engineer the format. Luckily, Revolution Games have allowed the cut scenes to be reencoded into MPEG2 and Ogg Vorbis. Those cut scenes are currently posted on the Main ScummVM download page but, as I mentioned above those cut scenes are not appropriate for the Zaurus. Which is why we have included downloads to the reencoded cut scenes on this page.

However, some of you may want to play the games in a different language then what we have included in our downloads so, therefore this section will detail the tools and steps needed to roll your own cut scenes.

This process will require a Windows PC because the RADTools Smacker decoder only runs under Windows. In theory you might be able to do this through WINE but, it is not something we have tested.

You can find the conversion files (bsvideo.rar) required and the basic instructions to perform this in post #2 on the following link. In addition you will need a copy of the LAME encoder which you can find here.
-------------------------------------------------------------------------------------

Adding a Game to the ScummVM Main Screen

By this point you will have grabbed the files you need to run games, compressed the audio and video as needed and copied it all over to your Zaurus. Now you want to start playing them. This section walks you through adding a game to the ScummVM GUI mainscreen for quick startups so, let's get to it.

After starting ScummVM, tap the Add game button.

The Selection Window will open. Navigate to the location on your Zaurus where your individual game sublfolders are located. Tap once on the subfolder you want to add to the main screen to highlight it and then tap the Choose button.

The Game Details window will open. If you wish you can make any changes to entries like perhaps setting the platform, etc.... This is optional because the majority of the time the defaults are just fine.

Tap the OK button and you will return the ScummVM mainscreen with your new entry listed. Repeat these steps as needed to add the remainder of the games to the mainscreen list.

-------------------------------------------------------------------------------------

In Game Controls

Because there are multiple game engines supported by the ScummVM interpreter (some of which the original source code was provided to the team) there are multiple control keys and combinations (referred to as hot keys) included in ScummVM in order to execute certain actions. To make matters more interesting some of these hot keys (eg. Save and Load) are mapped to the function keys on most other platforms. The Zaurus typically does not have function keys so, a keymap was developed to provide this functionality. Listed below are the key hot keys that one will need to know in order to complete a game in ScummVM. There are many more than these but in the interest of brevity we are only going to include the essentials. Please note that the following game engine short cut keys could not be tested at this time due to a lack ownership of these supported titles. They are the AdventureSoft Publishing (Feeble Files, Simon the Sorceror 1 and 2), Westwood Games (The Legend of Kyrandia 1), Coktel Vision (Gobliiins), WyrmKeep Entertainment (Inherit the Earth) and the Humongous Entertainment games. For the sake of completeness we will include the known hot keys that should work but, please bear in mind that they have not been tested on a Zaurus.

Common Hot Keys

Ctrl-q - Quits the game you are running and exits the ScummVM without saving your progress

Alt-Enter - Toggles full screen/windowed . Alt is the Kanji key to the right of the Ctrl key

LucasArts (SCUMM) Hot Keys

Menu or Right Rocker - Displays a save/load box with in game options, help and quit

Space - Pauses the game

Cancel - Skips the active cutscene

Fn-Tap - Simulates right click

Beneath a Steel Sky Hot Keys

Menu or Right Rocker - Displays a save/load box with in game options, and quit

Cancel - skips the game intro

Fn-Tap - Simulates right click

Broken Sword 1

Menu or Right Rocker or Cancel - Displays save/load box with in game options and quit

Cancel - skips the active cutscene

Taping the upper black bar of the screen - Displays your inventory

Fn-Tap - Simulates right click

Broken Sword 2

Tapping the the upper black bar of the screen - Displays save/load box with in game options and quit

Fn-Tap - Simulates right click

P - Pauses the game

Cancel - skips the active cutscene

Flight of the Amazon Queen

Menu or Right Rocker - Displays the Journal a save/load box with in game options, and quit

Fn-Tap - Simulates right click

Cancel - skips the active cutscene

Simon the Sorceror 1 and 2

Ctrl 0-9 and Alt 0-9 - Load and save game state. Alt is the Kanji key to the right of the Ctrl key

p - Pauses the game

The Feeble Files

F7 - Switch characters

p - Pauses the game

The Legend of Kyrandia

Ctrl 0-9 and Alt 0-9 - Load and save game state. Alt is the Kanji key to the right of the Ctrl key

Tap on the blue gem on the lower left of the screen - Displays save/load box with in game options and quit

We have not found out what the default hot keys are for Gobliiins, Inherit the Earth and the Humongous Entertainment games.

-------------------------------------------------------------------------------------

Available Themes

Starting with ScummVM 0.9.0, GUI Themes were incorporated. This allows you to replace the default retro black and green GUI with a more "modern" look.

Default Classic Theme

There are currently four themes ported over to the Zaurus and they are available in IPKG format. They are:

Modern

Modern Ice

Modern Blue

Modern Dark

Unfortunately, since this is a new feature; the GUI selector is not working properly so it only works by manually specifying the path and renaming the theme to modern.ini and modern.zip (if you want to use one the other themes besides the Modern one) since that theme name is hard coded in theme engine.

To activate a theme you must follow the steps outlined below:

Install the ipk of your choice (or install them all if you want to). This can be done via the GUI installer or from the console.

If you have chosen the Modern Ice, Blue or Dark themes follow the next three steps. If you chose the Modern theme skip the next three steps and continue on to the end of this section. Start up a the file manager of your choice or use the command line to navigate to /usr/share/scummvm/themes.

Rename the modern.ini and modern.zip to modern-orange.ini and modern-orange.zip if you chose to install that one as well your preferred theme.

Rename your preferred theme to modern.ini and modern.zip

If you started a file manager or console session close it and start ScummVM.

Tap on the Options button then tap on the Paths tab and you should see this.

Tap on the Theme Path: button and navigate to the themes directory which is located under /usr/share/scummvm/themes/ and then tap the Choose button.

Exit and restart ScummVM and it should now load with the theme of your choice.
-------------------------------------------------------------------------------------

Hints and Walkthroughs

There are many resources on the internet that provide hints and walkthroughs. In this section we will highlight some of our favorite hints and walkthroughs:

LucasArts/Lucasfilm Games

Maniac Mansion | hints | walkthrough |

Zak McKracken and the Alien Mindbenders | hints | walkthrough |

Indiana Jones and the Last Crusade (A Graphic Adventure) | hints | walkthrough |

LOOM | hints | walkthrough |

The Secret of Monkey Island | hints | walkthrough |

Monkey Island 2: LeChuck's Revenge | hints | walkthrough |

Indiana Jones and the Fate of Atlantis (A Graphic Adventure) | hints | walkthrough |

Maniac Mansion 2: Day of the Tentacle | hints | walkthrough |

Sam & Max Hit the Road | hints | walkthrough |

Full Throttle | hints | walkthrough |

The Dig | hints | walkthrough |

The Curse of Monkey Island | hints | walkthrough |

Revolution Software

Beneath a Steel Sky | hints | walkthrough |

Broken Sword 1: The Shadow of the Templars (AKA The Circle of Blood) | hints | walkthrough |

Broken Sword 2: The Smoking Mirror | hints | walkthrough |

Interactive Binary Illusions

Flight of Amazon Queen | hints | walkthrough |

Coktel Vision

Gobliiins | hints | walkthrough |

The Dreamer's Guild/Wyrmkeep Entertainment Company

Inherit the Earth: Quest for the Orb | hints | walkthrough |

Adventure Soft Publishing Limited

Simon the Sorceror 1 | hints | walkthrough |

Simon the Sorceror 2 | hints | walkthrough |

The Feeble Files | hints | walkthrough |

Westwood Studios

The Legend of Kyrandia 1 | hints | walkthrough |

-------------------------------------------------------------------------------------

Useful Links

Here are some links that you may find useful and interesting. Links to Abandonware and Pirated games are not permitted.

Where to acquire these games

eBay for LucasArts, Westwood, Coktel Vision and Humongous Games

AdventureSoft for Feeble Files, Simon the Sorcerer 1 and 2

Wyrmkeep for Inherit the Earth

Sold Out! for the Broken Sword Double Pack or 1 and 2 individually

ScummVM for Beneath a Steel Sky and Flight of the Amazon Queen

Background Information on the Games

Moby Games

Adventure Gamers

LucasFilm Games and LucasArts

The International House of Mojo

LucasArts Museum

The Zak McKracken Archive

Revolution Software

Broken Sword Planet

Beneath a Steel Sky Installer

Interactive Binary Illusions

Flight of the Amazon Queen Installer

Coktel Vision

Gobliiins at Vintage Sierra

The Dreamer's Guild/Wyrmkeep Entertainment Company

Inherit the Earth Web Comic

AdventureSoft Publishing

The Best Simon the Sorcerer fanpage

Westwood Studios

None at this time

6.3 psx4all the Playstation emulator

Info about psx4all here.

6.3.1 Compatibilty List



A game compatibility table for the psx4all emulator on the Zaurus
GameEmu VerHardwareWorks?Comment
Azure DreamsB44/CackoC3100YesDemos play at 5 to 15fps, game at 10, without underclocking. Seems to work, no idea how to play!
Back Street BilliardsB44C1000NoVideo Visible. Menu and gameplay are invisible
Breath of Fire IIIB4C1000Yesplayable OCed on B4
Bubble Bobble 2B44C1000Yesplayable without OCing
Castlevania: ChroniclesB4C1000NoFreezes at beginning
Castlevania: ChroniclesB43C1000NoFreezes
Crash BandicootB44C3100Yes
Crash Bandicoot 2: Cortex Strikes BackB4C1000No
ChronotriggerB4C1000YesA little slow, but playable OCed
Chrono CrossB43C1000NoFreezes
Colin Mcrae 2.0B43C1000YesPlayable but too slow to be fun
Crash Team Racing PAL (French)B44C1000NoFreeze from the 1st image
DarkstoneB44C1000NoFreezes before game starts up.
DiabloB4, B43,B44C1000Yes/NoGM, playable OCed until King Leoric's Tomb
Dragon Warrior VII (Disc1)B4C1000NoGets stuck after menu
Family FeudB44C1000NoSegfauls right away
FIFA2002 PAL (French)B44C1000Yes10 fps without sound
Final Fantasy IVB43C1000YesGS but playable OCed
Final Fantasy VIB44C1000Yes
Final Fantasy VII NTSCB4C1000Yesplayable OCed
Final Fantasy VII PALB44C1000Yesslower then NTSC but mostly playable OCed
Final Fantasy VII PAL (French)B44C1000Yes
Final Fantasy IX PAL (French) Disc 1B44C1000Nohangs at start
Final Fantasy TacticsB43C1000Yesplayable OCed
Game of Life, TheB44C1000YesVery playable OCed
Gauntlet LegendsB44C1000Yes10-20fps OCed
Gran TurismoB4ZaurusYesWorks but too slow to be fun
GunfighterB43C1000Yesa little slow, but mostly playable OCed
Harvest Moon: BTNB44C1000NoFreezes before games starts
Jeopardy 2B44C1000NoSegfaults right away.
Konami Arcade ClassicsB44C3100YesA little slow but playable
Koudelka (disc1)B43C1000YesGF and a little slow, but mostly playable OCed
Kula WorldB4ZaurusNo
Legend of LegaiaB44C3100yesvery slow
Lunar: Silver Star Story (Disc1)B4C1000YesGV and a little slow, but playable OCed
Lunar2 Eternal Blue080407C3200Yesplays at or almost full speed with frameskip 1/2 and better at 1/3
Metal of Honor: UndergroundB44C1000Yes/NoGM, a little slow OCed (8-10 fps). Map ends strangely 15 min in to single player game. Haven't tried Multi-play yet.
Metal Gear SolidB44C1000No
Metal Slug XB4ZaurusNofreezes
Midevil 2B44C1000YesSlow. 3-10fps OCed
Myst080407C3200NoGame starts to load, microdrive light flashes some, then stops. Zaurus is now froze. need to reset in battery compartment. Myst works on desktop PC using ePSXe.
Need For Speed: HSB43C1000Yesplayable but too slow to be fun, OCed
Need For Speed: PUB43C1000Nosegfaults at main menu
Nightmare CreaturesB43C1000No
Tactics OgreB44C1000YesOnly tried it OCed
Parasite Eve (Disc1)B44C1000YesSome GG (main character is invisible or wrong colors sometimes) and a little slow, but playable OCed
PersonaB44C1000Yesplayable
RaidenB43ZaurusYessome GG, but playable OCed
Raiden DXB44C1000Yessimilar performance to Raiden
Resident EvilB4ZaurusYesplayable OCed
Resident Evil 2B44C1000Yesnearly full speed
Resident Evil 3B44C1000No
RPG MakerB44C1000YesSome GG, 15-20fps NOT OCed
Shanghai: True ValorB4C1000Yesplayable OCed
Sim City 2000B44C1000Nosegfaults
SkullmonkeysB4C1000Yesa little slow but playable OCed
Soul ReaverB44C1000Yes5-10fps OCed
SpidermanB44C1000NoFreezes before games starts
Star Wars - Episode 1 - Jedi Power BattlesB44C1000NoFreezes before game starts
Strider 2B3ZaurusYes
SuikodenB44C1000YesGM but playable without OCing
Super Puzzle Fighter 2 TurboB44C1000NoFreezes after the first intro movie
Tales of DestinyB44C1000Yesruns very well OCed
Tomb Raider 3B44C1000NoFreezes after menu, and intro movie
Vampire Hunter DB43C1000YesGV and an invisible main menu, but playable OCed
Wild ArmsB44C1000NoIt segfaults right away
wipEout XL (wipEout 2097 in Europe)B4ZaurusYesplayable OCed
You Don't Know Jack:Mock2B44C1000NoHangs at start when checking for memcard

Glossary:
playable = means you can play it, even though it might be slow or un-pretty.
B3 = Beta 3
B4 = Beta 4
B43 = Beta 4.3
B44 = Beta 4.4
OCed = Over Clocked
GS = Goofy Sound
GG = Goofy Graphics
GV = Goofy Video
GF = Goofy Fonts
GM = Goofy Music