|Java menu knowledge base|
Self-help (1): the most frequent user mistakes
Problem: I bought it but it still says "trial"
Problem: I bought it but says "error 2"
- Please read the delivery FAQ for the most
detailed description of how to implement the release version.
- Delete the trial version files from all locations, including your server.
- Locate the release files in the specially notified release-version download you obtained from our site on purchasing the product.
- Place the release files (cab, jar and class files, all of them) into the
directory where you had your trial versions.
- Edit the APPLET tag to point to the release class file. You may also need
to edit the CABBASE and ARCHIVE parameters to point to the new cab and jar files.
- Read and do anything else the delivery email says.
- Restart your browser and try the menu again now.
Did you read the delivery email (all of it) and do everything it told you
to do? If so, view the HTML source of the page on your server by
right-clicking, and check that the page on your server has the same
changes as the page you are developing locally. You may have different
page versions muddling you up.
Problem: it worked offline, but not after I uploaded it
Please read the detailed Uploading FAQ.
Problem: sometimes it works in some places, sometimes it fails
Checks: (1) clear out your browser cache; (2) connect to the net without
a proxy until you have finished developing.
Problem: it was working fine and then starting producing error 6
The meaning of error 6 is explained in the table of error codes, but you
might not accept this report after carefully writing your text file. The
problem is that the end-of-line characters in a text file can easily be
corrupted while saving/uploading, in which case the applet may start reading
the text file as a single entry. Solution: check your text file again.
Problem: I changed the name of the applet file and then it stopped working
You can't change the name of an applet file.
Problem: It doesn't load pages into my frames but into new windows
Read the support page on this topic.
Problem: when I unzipped the package I got a .cla file, but your
instructions say it should be .class
If you are using an old unzipper, it will do this. The applets cannot run
if they are called *.cla. Solutions: (i) rename the file; (ii) get a new
Problem: it's too slow
Cause: very probably you implemented the menu incorrectly. If properly
implemented, our menus are fast.
Solution: read the support pages on speed issues.
Problem: graphics are strange
Check how many colours you are using. 16 colours is too little. The applets
should cooperate with 256, but most people use higher numbers these days, and
our applets will work best with higher numbers of colours (provided you have
the system resources and graphics card/monitor for this).
Problem: graphics are strange with the Magic Buttons
Did you remember to put 1 pixel between each of the three images?
And are your size parameters correct?
Problem: I've updated my resources but I can't see the result
Java interpreters can cache the applet resources unusually deeply. A simple reload
may not show your new resources. You need to super-reload.
To super-reload with Netscape 4.x (Symantec VM), hold down the SHIFT-key while clicking the reload button with the
mouse. With Microsoft, use the CTRL-key instead. With Sun VM's (JRE), close down all your browser windows and restart
the browser if you suspect cache problems.
Problem: I got an update and now it doesn't work
This is most likely to be a cache problem. Clean out your browser
cache thoroughly and connect to your site without a proxy. You
should also check that you changed your HTML - remember that every
time we issue a new applet we give it a new and unique name - this
is so as to avoid cache problems (but it won't avoid cache problems
if the old version of the HTML file is still cached as well).
Problem: I got a bugfix but it still produces the same old error
Again, this is likely to be a cache problem. See above. (And make
sure you change your HTML to fit the new name of the applet file).
Problem: I changed the server and now it doesn't work
If you bought a single location licence, it is only valid for
a single location. There are also multiple location licences.
Please re-read the licencing FAQ.
Problem: your starter package works; my implementation doesn't
If this happens, we cannot emphasize too much: please read the documentation -
particularly the bit about making step-by-step modifications based on the
starter package and testing at each stage. Some of our applets are sophisticated
and powerful bits of design machinery, and while we try to make them as
user-friendly as possible, offering flexibility and power has its costs in terms
of intuitiveness of use.
Problem: The applet page is always replaced by an "error 404 file
not found" page as soon as the applet starts.
1. Read the support pages about "escape pages".
2. Remove the escapepage parameter.
3. Read the newly generated error code and refer to the error code
table in the support pages.
Problem: It works under Microsoft's browser but not Netscape's - under
Netscape I just get an empty space (no error code) where the applet should
This phenomenon is most frequently caused by forgetting a close tag (e.g.
close paragraph </p> or close applet </applet>) in
your HTML. With the advent of CSS, wrongly formatted CSS tags around the
applet may also cause it to disappear in a browser-specific manner.