I recently got myself a Sharp Zaurus. Here are some things I've done with/for it.
Last update: 20020629
See the page on Getting your Socket Low-Power CF WLAN card to work with your Sharp Zaurus.
Last update: 20020623
This is a Palm Pilot emulator for the Zaurus. As the README below explains, it's an emulator for the older Dragonball hardware. Maybe sometime later I'll be able to make it work with ROMs for the new hardware, as well. If you install from the ipk file into system RAM, you shouldn't need to move any files around. If you install into CF or SD, you may have to make a symlink from /home/root/.qcopilot to the right place.
This is qcopilot, a port of xcopilot v0.6.6 to Qt/Embedded. Version 0.5 by Ian Goldberg <firstname.lastname@example.org>, 20020623 This is my first Qt program. Hope you like it! :-) The license is GPL version 2 (see the file COPYING). Changes in 0.5: Version 0.5 makes the following two changes: - Clicks should now be much more responsive. - You can just keep qcopilot running in the background. It will go to sleep when it loses focus. This way, you can keep a common app running, without having to wait for the PalmOS bootup time. Changes in 0.4: Version 0.4 considerably reduces the RAM usage of qcopilot. One of the ways it achieves this is by mmap'ing the pilot ROM file; in order to get this benefit, though, you need to pre-process your ROM file to put it in little-endian format. Here are some instructions: * First, obtain a pilot ROM image. There are a couple of ways to do this. The best way is simply to copy it from an actual PalmOS device. *NOTE* qcopilot emulates the old Dragonball (_not_ Dragonball EZ or its successors) hardware. This means you need a ROM from a Palm III or earlier. Palm IIIx, IIIe, IIIxe, IIIc, V, etc. will _not_ work! If you copy it from an actual device, you should end up with a pilot.rom file that's 1MB (Palm Personal, Professional) or 2MB (Palm III) in size. If you download a ROM from the net (one that's intended for POSE), you may have to massage it a little. It turns out most POSE ROM images out there are only images of the "Big ROM", not the whole ROM (which is a 32K "Small ROM" followed by the "Big ROM"). If you've got an image like this, do this to construct a complete ROM: mv pilot.rom pose.rom dd if=pose.rom of=pilot.rom bs=32768 count=1 dd if=pose.rom of=pilot.rom bs=32768 seek=1 You'll then have a pilot.rom file that should be between 1 and 2 MB in size. * Now you need to make the little-endian file, which you'll call pilot.rmx : dd if=pilot.rom of=pilot.rmx conv=swab * Copy the pilot.rmx file into $HOME/.qcopilot/pilot.rmx on the Zaurus. (If you have an old pilot.rom file there, you can remove it.) If you want to install .prc or .pdb files on your qcopilot, the easiest way is to do this: * Copy your pilot.ram file from your Zaurus to ~/.xcopilot/pilot.ram on your desktop. Put your pilot.rom file (*not* the pilot.rmx file) in ~/.xcopilot/pilot.rom on your desktop. * Use xcopilot on your desktop to install the databases and programs into the pilot.ram file. * Copy the pilot.ram file back to the Zaurus. Some things to note: * Sound doesn't happen at all. I can't figure out how to make Qt/E play a beep of a specified pitch/amplitude/duration. * You sometimes have to hold down the stylus a bit when you're clicking, or the emulator misses the click. I think I know how to fix this, but that's for later. Changes in 0.3: - Clicks should now be a little more responsive, but it's still not great. - qcopilot now uses pthreads instead of forking
Last update: 20020619
The format of the 16MB flash ROM images is documented at http://www.btinternet.com/~p.flinders/sl-5000d/romimage-layout.html. I wrote a little program to tease apart the pieces of the ROM image for separate inspection. Here's the source.