[Prev]
[Up]
[Next]
(Last updated 1st December 1997 by
DRH)
Pixie Warning and Error Messages
This page lists the main error and warning messages produced by the Pixie
system. They may help you diagnose any problems.
If you need to contact Support, you will probably be asked for the
full text of any messages that appear.
ConvPxi error messages
Here are the main error messages ConvPxi may produce.
You will see one of these if there is some problem that stops
PixiConv producing a .PXI file.
Usage: string
-
ConvPxi did not understand the commandline parameters
it found. The string tries to explain what it was
expecting.
- NumberFormat: string
-
ConvPxi was expecting a number (for example, 600), and
didn't understand what it found.
- FileNotFound: filename
-
ConvPxi could not open the given filename.
Perhaps it is misspelt, or in a different directory or folder.
This can also be reported for output files which are not writable.
- Error: Input and output must be different
-
You specified the same name for both the input file
and the output file. ConvPxi cannot cope with that.
- Error: Don't know how to convert filename
-
Filename is not a Windows Metafile or a Pixie script
file, and ConvPxi doesn't know what to do with it.
- Error: filename is not a real metafile
-
Although filename looks like a Windows Metafile
at first sight (for example, it probably has the .WMF extension),
there is something wrong with its file header.
- Error: EOF filename
-
The file was shorter than expected. It may
have been corrupted somehow.
- Error: IO
-
Some problem while reading or writing a file.
It might be due to the disk getting full while writing.
- Error: filename line_number: message
-
Syntax errors in Pixie Scripts are reported like this.
The filename and line_number indicated
where the error was found, and the message gives
more information. Usually if you look at the line concerned
you can see what has gone wrong. See also the Pixie Script
reference section.
ConvPxi warning messages
Here are the main warning messages ConvPxi may produce.
Generally they mean that although a Pixie image has been
produced, it probably won't look like what you expected.
Warning: record type name [number] was ignored
-
The metafile contained information which ConvPxi was not able to
convert.
The name and number indicate the type of Metafile record
that ConvPxi doesn't understand.
See Bitmaps and other unsupported
features for more information.
- Warning: brush style number was ignored
-
The metafile contained a fill pattern which ConvPxi was not able to
convert.
ConvPxi can only cope with solid fills.
- Warning: pen width number was ignored
-
The metafile contained a thick line which ConvPxi was not able to
convert. ConvPxi can only cope with thin lines.
- Warning: pen style number was ignored
-
The metafile contained a line pattern which ConvPxi was not able to
convert.
ConvPxi can only cope with solid lines; not dotted or dashed.
- Warning: "name" is not a portable font name.
-
The font face name is not one of the fonts listed
in Text and fonts.
The text might look alright on your machine, but wrong
on a user's machine if it doesn't have the named font installed.
Viewer applet warning messages
Here are the main warning messages the Pixie.class and PixieSlide.class
applets may produce. They appear at the bottom of the applet's window.
All except the first begin with SRC - that is the URL
of the image as given by the SRC
parameter,
which should help you locate the file causing the problem.
No SRC parameter
-
The
NAME=Src VALUE="URL"
line
was missing from the <Applet>
; tag,
so Pixie does not know what image file to use.
See The basic HTML for more information.
- SRC: java.net.MalformedUrlException: message
-
Pixie did not understand what SRC means.
The message gives more information.
- SRC: java.io.FileNotFoundException: URL
-
URL is the full path to the image file, which
could not be opened for some reason. Perhaps the
path is misspelt or the file has moved, or the
network connection is down.
- SRC: java.io.IOException: URL
-
URL is the full path to the image file, which
could not be opened for some reason. Perhaps the
path is misspelt or the file has moved, or the
network connection is down.
- SRC: java.lang.Exception: Bad Pixie header
-
The source file was found, but does not look like a proper
Pixie image. Pixie files usually have an extension of .PXI.
Perhaps some other file has been given that extension by mistake.
- SRC: java.lang.Exception: Bad Pixie version number
-
The source file is a valid Pixie image, but of a version that
this applet does not understand. For example, Pixie.class does
not recognize the slide-show and hotspot features that PixieSlide
uses.
- SRC: java.lang.Exception: Unknown header command
-
This usually means the image file has got corrupted somehow.
- SRC: java.lang.Exception: Unknown record type number
-
This usually means the image file has got corrupted somehow.
[Prev]
[Up]
[Next]
(Last updated 1st December 1997 by
DRH)