What you need:

1. Development tools

   • need to set up you complier as described here
   • probably don't really need qpe if you are not writing code with a GUI
   • don't need qvfp

2. The specs and header files for the DTM access

   • The files you need are here
   • dtm.zip
   • headers.zip

3. libzdtm.so

   • This is the actual shared library that you need to link against. It is found on the Zaurus in the /home/QtPalmtop/lib/ directory. It needs to be moved to /opt/Qtopia/sharp/lib/ for cross compiling.

4. Example program

   • Available here

1. header files aren't ansi-C. The header files are C++ compliant, but not ansi-C, so I ended up using the g++ compiler to avoid a slew of warning messages. I think it should be possible to translate the C++ files into ansi for greater compatibility.
2. no emulation. Since the only source for libzdtm.so is from the Zaurus itself and not a compiled library, it is not possible to emulate sofware on a PC architecture using qvfp or anything else. You can compile on your x86, but you'll have to move it to the Zaurus to actually make it run. I found that having the Zaurus on the network running sshd was critical to working effectively. I also put my ssh key on the Zaurus, so i wouldn't have to supply a password all the time. Then, I added an "install" directive to my makefile so that i could easily compile and copy over to code. I would run it in a seperate window on my desktop connected (again via ssh) to the Zaurus. This is the only way I could work efficiently. It would be really great if sharp released the source for DTM or at least an x86 compiled library.
3. unsigned char *. The header files define most strings as unsigned chars which is goofy. In particular, this is incompatible with all the standard string libraries on the Zaurus. As a consequence I had to do a lot of casting from (char *) to (unsigned char *) and back in order to get the compiler to quiet down.
4. Not without qte. The libzdtm.so requires libqte.so.2. I'm not sure why, it just does.

1. BACKUP YOUR MACHINE This code has only been tested on one single Zaurus. Although the database access in intended to be read-only...here comes the disclaimer... SHARP (nor Stefan Kremer) ASSUME ANY RESPONSIBILITY to any conflict, fault, or damage affecting the unit that rises from your tinkering with the DTM data.
2. Make sure you have the libzdrm.so on your computer in the appropriate directory and that all the links libzdtm.so.0.1 are there too.
3. Make sure you have the source code for the test program in the current directory.
4. Compile:
   1. arm-linux-g++ -I -c -Wall -ansi -pedantic -o arm-dtmdump.o dtmdump.cc
   2. arm-linux-g++ -Wall -ansi -pedantic -o arm-dtmdump arm-dtmdump.o -L/opt/Qtopia/sharp/lib -lzdtm
5. Transfer to Zaurus:
   • scp arm-dtmdump zaurus@zaurus:/home/zaurus/dtmdump

Coming Soon

1. I am working on an example program to add data to the database. In particular, I'm hoping to have a program that takes the XML data file from my original Zaurus and inserts it into the new database.
2. netsync - I am writing a network-based synchronization tool. This will allow you to synch your Zaurus over TCP/IP with a centralized server. At first this will provide convenient backup. The next stage will be to get other devices and software to sync with the same PIM server (linux tools, Apple's ical, web-interface, OPIE, old Zaurus). The idea is to allow any device, anywhere to get the latest info. If you are interested in helping out wit the project e-mail me. Project located here.