Wyvern Handheld Client — Troubleshooting

Although the Wyvern Zaurus client works for almost everyone, it's possible that minor configuration differences on your Zaurus could prevent Wyvern from running. You might experience different kinds of problems:

Wyvern doesn't install properly
Wyvern can't install to my SD card
Wyvern installs properly but doesn't run

Wyvern Doesn't Install

If Wyvern doesn't install properly, uninstall it, re-download it, and follow the Installation Instructions again (you don't need to create a character again, though).

We haven't had anyone have trouble with the installation yet, so if you do, please drop us a note.

Wyvern can't install to my SD card

We've had some reports from users who can install to RAM, but don't have any luck installing to their SD card.

The entire Wyvern installation only adds 4 files to your Zaurus:

wyvern.png — the application icon
wyvern.jar — the application, all in one file
wyvern.desktop — an initfile describing the app
runwyvern — the launcher script

If you install to SD card, it puts two of these files (wyvern.png and wyvern.jar) on the SD card, and makes symbolic links to them from RAM.

It's pretty straightforward to figure out whether the installer put all the files in the right places. If you've installed Wyvern to your SD card, and it's not running, make sure the following files were all created on your Zaurus:

  /mnt/card/QtPalmtop/pics/wyvern.png
  /mnt/card/QtPalmtop/wyvern.jar
  /home/QtPalmtop/bin/runwyvern
  /home/QtPalmtop/apps/Jeode/wyvern.desktop
  /home/QtPalmtop/java/wyvern.jar@  (a symlink to the one on the card)
  /home/QtPalmtop/java/wyvern.png@  (also a symlink)

You can check these files in one of three ways:

if you have File Manager, you can go to each of these directories in the tree, and look for the file that's supposed to be there.
if you have Terminal, you can launch it and do 'ls -l' on each of the paths above to make sure they're there.
if you have ssh, you can ssh in and do 'ls -l' on each of the paths above.

Note: we've seen at least one variation on the list above:

  /mnt/card/QtPalmtop/pics/wyvern.png
  /mnt/card/QtPalmtop/java/wyvern.jar
  /home/QtPalmtop/bin/runwyvern
  /home/QtPalmtop/apps/Jeode/wyvern.desktop
  /home/QtPalmtop/java/wyvern.jar -> /var/mnt/card/QtPalmtop/java/wyvern.jar

Depending on the ROM version you're using, the Package Installer may point the symlink to /mnt/card/QtPalmtop/java or to /var/mnt/card/QtPalmtop/java, which are in fact both the same directory. It also appears that the wyvern.png symlink is optional.

If your configuration doesn't match one of the configurations above, and you can't launch the app, try following the instructions below to diagnose it.

Wyvern installs properly but doesn't run

Note: If you have a proxy server, and/or a firewall, make sure it lets traffic on port 2222 through, or Wyvern won't be able to find the server. This should fix most peoples' problems.

If you can't run Wyvern, or it experiences some sort of crash or lockup, you can help us figure out what's happening. If you follow the steps below, it should give us enough information to find and fix the problem.

Be warned, though — it's not simple. You have to follow the steps exactly as we've written them down here. You should only do this if (a) Wyvern doesn't work for you on your Zaurus, and (b) you're desperate enough to spend 15-20 minutes following our obscure instructions.

Step 1 — get Terminal Application

First you need the Terminal app for your Zaurus. It's free and you can download it from the Zaurus Software Downloads page. The Terminal is a console/shell application that lets you execute Linux commands.

Download and install the Terminal, either to RAM or SD card, and an icon for it should appear in your main Applications tab.

Step 2 — launch Wyvern from Terminal

You'll have to type in a fairly long command to launch Wyvern from your Terminal. Doing this will allow you to see the output as the application is loading, including any error messages.

Launch the Terminal app, and type:

  evm   -XappName=runwyvern   -cp   /home/QtPalmtop/java/wyvern.jar   wyvern.client.palm.PalmClient

It's really important that you get the capitalization right. We've highlighted the capital letters in red:

  evm   -XappName=runwyvern   -cp   /home/QtPalmtop/java/wyvern.jar   wyvern.client.palm.PalmClient

Before you hit Enter, close the popup keyboard or handwriting recognizer, so you can see more on the screen. Then hit the OK button.

If Wyvern is launching correctly, you should see:

  creating game window...

and other startup-type messages. If Wyvern is not launching (or running) properly, you should see something like this:

  java.lang.NoClassDefFoundError:  wyvern/client/palm/PalmClient

or (more likely) an Exception looking a bit like this:

java.lang.NullPointerException
	at wyvern.client.palm.PalmGameWindow.createUIObjects (bytecode 33)
	at wyvern.client.palm.PalmGameWindow.initUI (bytecode 37)
	at wyvern.client.palm.PalmGameWindow.<init> (bytecode 69)
	at wyvern.client.palm.PalmClient.createClientControl (bytecode 5)
	at wyvern.client.Client.<init> (bytecode 30)
	at wyvern.client.palm.PalmClient.<init> (bytecode 1)
	at wyvern.client.palm.PalmClient.startClient (bytecode 16)
	at wyvern.client.palm.PalmClient.main (bytecode 1)

Your Exception output will be different from this one, but it should follow the same format: a blah.blahBlahException line, followed by at a bunch of "at wyvern.whatever" lines.

This stuff may look odd to you, but it will tell us exactly what problem you're having. There isn't a convenient way to cut and paste this output, so you'll have to type it into your email to us, as best you can. You can omit the "(bytecode xyz)" at the end of each line, but please try to get everything else.

If you send the entire output you're seeing in an email to us, we should be able to identify your problem and get a fix for you very quickly.