Amiga ISO Collection/AmigaUtilCD1.iso/GFX/Painting/PAINTDOC.DMS/in.adf/ASCII_Files/A.pp/A

Text File | 1995-10-28 | 19.9 KB | 558 lines

A.         Program Messages

   This appendix lists (in alphabetical order) and explains the most
important messages of Personal Paint. A more complete description can be
found in the referenced sections.

   If the message is displayed in a requester containing only the Proceed,
Cancel or OK gadgets, the <Return> key can be used instead of the OK or
Proceed gadget, while <Esc> can be pressed instead of selecting the Cancel
gadget. Sections 1.10.12 ("The <Return> key") and 1.10.16 ("The <Esc>
key") have more on the topic.


All rights reserved - Unauthorized reproduction or transfer is illegal

   This message has to be displayed for strictly legal reasons. More in
Appendix E.


Another program is using the file

   The operation on the specified file cannot be performed because the
file is currently being locked by another process. This can happen, for
example, if another program is writing to the same picture file which
Personal Paint is trying to load.


Audio cannot be activated

   Personal Paint cannot start the CloantoAudio module, after searching
for it in the "DEVS" logical volume and in the drawer (or volume) from
where Personal Paint was loaded. By default, the "DEVS" logical volume is
assigned to the "Devs" drawer of the boot disk (which may be the Workbench
disk containing Personal Paint). It may also be that the CloantoAudio file
was found, but the CloantoAudio module could not reply in time (handshake
function) because it was slowed down by another disk operation, or because
there was not enough memory. Personal Paint tries to load the audio module
if there is enough memory to do so, and no other Cloanto program has
already loaded CloantoAudio. The same CloantoAudio module can serve an
unlimited number of Cloanto programs, thus overcoming the limitations set
by the Amiga on the maximum number of open audio channels. If the
CloantoAudio module is started manually (e.g. by selecting its icon), it
remains RAM-resident until the computer is reset or switched off, and does
not need to be loaded every time from its client programs. Sections 1.11
and 1.13.


Bad IFF structure

   The file read by Personal Paint is recognized as being in IFF format,
but its content does not keep to the rules defined for the IFF standard.
Some programs do not use the IFF format correctly.


Brush ... will be lost

   This warning message is displayed before Free Brush is executed
(section 5.6). If the operation is confirmed, it will not be possible to
recover the brush with Restore Brush.


Brush size is ..., ... planes
Used size is ..., ... planes

   This information is provided by the Chop Information function. More in
section 5.12.


Clipboard device cannot be opened

   The Amiga public clipboard cannot be opened. The "clipboard.device"
file in the "DEVS" logical unit probably cannot be loaded. Personal Paint
tries to open the Clipboard (if it is not already open) whenever this is
required by a program function. Sections 1.13.4 and 1.15.


Clipboard does not contain the required data

   A function which should read data from the clipboard has been used
(e.g. brush data), but the clipboard is empty, or only contains a
different type of data (for example, digitized audio) than what was
expected. Sections 5.9 and 6.1.


Clipboard write error

   In most cases, this message indicates that there is not enough memory
(RAM or disk) for the Amiga operating system to store the specified
clipboard data. Sections 5.9.2 and 10.1.


Data compression algorithm not identified

   Graphical data can occupy more memory than one would believe. Different
techniques exist to compress this data, so that it occupies less space
than it would otherwise. Personal Paint uses and recognizes different
standard image compression techniques in the different file formats it
uses (IFF-ILBM, GIF, PCX, etc.) Another program may write some data using
a compression method (or algorithm) not recognized by Personal Paint. When
Personal Paint tries to load this data, it displays this message. This
means that the data cannot be loaded by Personal Paint unless it is saved
in another format.


Decryption impossible

   An incorrect encryption key has been used to load an encrypted picture.
An encrypted image can only be loaded if the same key used to save the
data is also used to load it. This message can also appear if the disk is
damaged or the picture file has been modified by another program, though
this is very unlikely. Sections 4.1, 4.2 and 8.3.


Disk incompatible

   The format of the disk in the specified drive is not recognized by the
operating system. The disk may be damaged, not formatted or be in a format
not recognized by AmigaDOS. Sections 1.3.4, 4.1 and 10.2.


Disk is not mounted

   The specified disk is not inserted in any drive. Section 10.2.


Disk is write-protected

   Data cannot be written on a disk which is write-protected. The hole at
the corner of the disk must be covered by the write-protect tab. Section
10.2.


Disk not validated

   The Amiga operating system has not yet validated the disk. The
operation may have failed, or still be in progress, if the disk has just
been inserted. If the disk is not successfully validated ("Disk not
validated" system message), no new data can be written to the disk, which
can be read normally. Section 10.2.


Display Mode Selection
Selected image...
Current mode... - ... colors

   The picture selected for a load operation has the same size as the
current image format. However, the selected file would require a different
video mode from the current one (as indicated in the video mode
information contained in the IFF-ILBM file, or calculated by Personal
Paint if there is no such information). This requester allows the user to
decide whether to maintain the current screen mode or to adopt the new
one. Section 4.1.


Error during file I/O

   Personal Paint has several detailed error messages which are used if an
error occurs during a read or write operation. The Amiga operating system
may issue error codes which Personal Paint cannot translate into messages
indicating the exact cause of the error. If this happens during a file
read/write operation, this message is displayed.


Error during printer output

   An error is signalled by the Amiga operating system while data is being
sent to the printer. The most likely causes are: printer is switched off
or is in the off-line (deselected) state; printer is out of paper or the
paper is jammed; the printer's cover is open; the printer cable is not
connected properly; the wrong port (serial vs. parallel) was selected in
the Amiga Printer Preferences. Sections 4.3 and 10.3.


Error: The keys are different

   Personal Paint requires the encryption key to be written twice. This
message is displayed if the first key and the control key are different.
This additional control is useful to prevent an image stored using an
incorrectly typed key from not being loaded any more. Section 8.3.


File is protected from deletion
File is protected from reading
File is write-protected

   The specified file has a software protection which prevents the
operating system from removing, reading or modifying it. The Workbench
Information (or Info) or the Shell/CLI Protect command can be used to
modify the access status of the file.


Format Selection
Requested format...
Current format... - ... colors
Selected image...
Current format... - ... colors

   The current image format (i.e. size and/or number of colors) would be
changed as specified in the Image Format requester or in an IFF-ILBM or
settings file. When an image file is loaded, this requester allows the
user to choose between the new and the current format. The Stretch option
can be set to resize the image, if necessary. Color reduction is always
applied automatically when needed. Sections 4.1, 4.5, 8.6, 8.7 and 8.15.


Icons cannot be loaded

   The "PPaint_Icons" drawer cannot be found, or it does not contain the
correct default icon files. Sections 1.14 and 8.9.2.


Insufficient Chip memory for the requested screen
Insufficient Chip memory to display window

   There is not enough Chip RAM to open a screen, window or requester.
Sections 1.3.2 and 10.1.


Invalid data

   This general purpose message is used if extremely unusual circumstances
are encountered. This may happen, for example, when attempting to load an
image whose size is 0 by 0.


Invalid number of colors for the requested screen

   In most cases, this indicates that the hardware being used does not
support as many colors as specified in the picture or settings file being
loaded. Probably, a particular screen mode was requested in an IFF-ILBM
file written on a computer supporting the same video mode, but with more
colors. Personal Paint automatically selects a different video mode as
close as possible to the requested number of colors.


Invalid parameter in line...

   An error has been encountered in loading a settings file. One or more
parameters of an instruction in the specified line have been found to
contain a value out of the valid range. Sections 8.1, 8.2 and Appendix C.


Invalid window size

   To contain the required text elements, a window would become larger
than the screen. This may happen if requester texts in a "UIText" file are
edited without considering space limitations in lower resolution video
modes. Sections 1.14 and 8.10.


Line too long...

   An error has been encountered in loading a settings file. The line
whose position from the top of the file is indicated is too long (i.e. it
contains too many characters). Sections 8.1, 8.2 and Appendix C.


Memory save mode

   This message indicates that Personal Paint has detected a low-memory
environment and has taken action to reduce the occupation of RAM. This
mode can also be activated by holding the <F1> key down while the program
is starting. If possible, the program does the following things: the audio
functions are not used (the CloantoAudio module is not loaded); the
Workbench screen is closed; the printer driver is not pre-loaded at the
start of the program, and is removed from RAM (expunged) immediately after
each print operation; the directory lists of the file requester are not
stored to speed up the re-display of the same lists. Sections 8.16 and
10.1.


No monitor information for the requested screen mode

   An IFF-ILBM file contains a reference to a video mode which is not
supported by the system hardware or operating system. (Most other file
formats do not contain explicit video mode information.) It may happen
that a given monitor, theoretically supported by the system, was not
activated as indicated in section 10.4.


Object too large

   An internal Amiga error has occurred. The data found is too large to be
handled by the operating system.


Operation impossible

   A function of the Amiga operating system has returned an error, but the
cause of the failure is not specified. Personal Paint cannot complete the
operation.


Path incorrect

   The path (i.e. the set of names of drawers, separated by '/' signs)
which is written in the file requester, does not exist in the requested
unit. One or more of the drawer names are incorrect or too long (maximum
25 characters). Some characters cannot be used in the names of files and
drawers. Sections 1.4, 1.5 and 3.4.


Path too long

   The selected path contains too many levels (i.e. drawers within
drawers), which AmigaDOS cannot handle.


Personal.font cannot be opened

   Personal Paint uses a custom font, which contains symbols especially
designed for the program, for its user interface texts. On startup,
Personal Paint searches for the font in the "FONTS" logical volume or in
"PPaint:Fonts". Section 1.13.


PostScript module cannot be opened

   The "PPaint_PS" file cannot be loaded by Personal Paint. The program
needs to access this external module to output in PostScript mode.
Sections 1.13 and 4.3.3.


Printer device cannot be opened

   Personal Paint cannot activate the printer driver to execute a printing
operation. This may happen if there is not enough RAM available, or if the
"printer.device" file cannot be accessed in the "Printers" drawer in the
"DEVS" logical unit. Sections 1.11, 1.13 and 10.3.


Printing copy ... of ...

   An image or a brush is being printed. The progress indication gives
detailed information on the data which the Amiga printer device has
already sent to the printer, and the amount still to be transmitted.
Sections 4.3, 5.3 and 10.3.


Stencil size does not match

   The operation requested would have required the stencil to be exactly
as wide and as tall as the image over which the stencil would have to be
applied. Section 7.2 and subsections.


Syntax error in line...

   An error has been found in a settings file. In the specified line, a
keyword has not been recognized, or a command parameter is missing or
appears in an incorrect format. Section 8.2 and Appendix C.


The current font has no palette

   The Copy Font Palette command has been executed, but the current font
does not have an associated color palette. Sections 3.1.3.2 and 7.1.8.


The current one is the only brush

   The Next Transparency command (which copies the transparency
information of another brush to the current brush) failed because there is
no other brush. Section 5.8.7.


The file does not contain the required data

   A file has been selected for a read operation, but the data contained
in that file is not of the expected type, or the content of the file has
been damaged. This can happen, for example, if Personal Paint tries to
load a settings file, but discovers that the file specified through the
file requester contains a brush image. In order to reduce the risk of
similar errors, files of different types should not be stored in the same
drawer. It is also advisable to append standard suffixes to file names.
Sections 1.4 and 1.11.


The file does not exist

   A file has been specified for a load operation, but Personal Paint
cannot find a file with the given name following the specified path.
Section 3.4 ("The File Requester") explains how to avoid the risk of
mistyping file and directory names.


The file exists and would be overwritten

   An operation which would overwrite an existing file has been selected.
The Confirm Overwriting option is active (section 8.8.6), so the program
displays this warning message, indicating the file whose content would be
overwritten. The operation is aborted if the Cancel gadget of the
requester containing the message is selected. This makes it possible to
execute the operation again, using a different file name.


The file will be deleted

   The Delete File command has been executed. The operation is aborted if
the Cancel gadget of the requester containing the message is selected.
Section 4.10.


The font cannot be opened

   The Font Requester has failed to load the specified font. This may
happen if an incorrect typeface name is typed, or if the available memory
conditions or a read/write error interrupt the font load operation.
Section 3.1.3.2.


The image has been modified

   The current image has been changed since it was last saved or defined.
A command has been executed which would cause the loss of the current
image (e.g. a Load Image or Quit command).


The image is too large

   The maximum image size supported by Personal Paint is limited by the
Amiga hardware. The original Amiga blitter could not handle images larger
than 1008 by 1024 pixels. ECS and AA chips can process images as large as
32752 by 32767 pixels.


The image will be cut

   An image format smaller than the format of the image currently
displayed (or being loaded) has been selected. Unless the Stretch option
of the Format Selection requester is enabled, this additional warning
requester appears. Sections 4.1 and 4.5.


The other image has been modified

   A Copy to Other command has been executed, but the image in the other
environment has not yet been saved since it was last modified. Proceeding
with the command would cause the other image to be lost. Section 4.8.2.


There is not enough memory
There is not enough memory to load the user interface texts

   There is not enough memory to perform the operation requested. Sections
1.3.2 and 10.1.


The requested screen cannot be used
The requested screen mode requires 2.x O.S. or higher
The requested screen mode requires ECS or higher

   The IFF-ILBM file specified for loading an image also contains a
reference to a screen mode to be used. Due to hardware or operating system
limitations on the machine used to load the image, another screen mode has
to be used by Personal Paint. Sections 4.1 and 10.4.


The screen is not available any more

   A screen selected in the Grab Screen requester was closed before it
could be grabbed. Section 4.4.


The selected image type cannot be loaded

   The selected picture file uses an image encoding format not supported
by Personal Paint. These may include unusual IFF formats and image formats
which could not be edited with the freedom and precision required by
Personal Paint (e.g. Dual-Playfield images).


The size of the following brush does not match

   The Next Transparency command cannot apply the transparency information
of the following brush to the current one, because the two have different
sizes. Section 5.8.7.


The Undo buffer will be freed

   An explicit request to release the Undo buffer has been made (e.g. by
selecting the Undo tool with the right mouse button), or there is not
enough memory to allocate an Undo buffer for the selected operation. If
there is not enough memory to display this message, the buffer is freed
without displaying this request for confirmation. Sections 3.1.10 and
10.1.


The ... user interface text should be shortened
The ... user interface text should be made splittable

   The "UIText" file for the specified language was loaded successfully,
but some texts were found to be too long to be displayed properly in some
video modes. A text can be made splittable by inserting an underscore
character ('_') where Personal Paint may go to a new line if there is not
enough horizontal space. Some texts (e.g. non-"TMS" texts) can only be
displayed in a single line. If these are too long, they must be shortened.
Sections 1.14 and 8.10.


The user interface text file cannot be opened

   The "UIText" file associated to the user interface language which is to
be loaded cannot be found. Personal Paint searches for the files in the
"PPaint_Prefs" drawer of either the "PPaint" volume, or the current
drawer. Sections 1.14 and 8.10.


Title not correct

   A wrong path has been specified for a file read or write function, or
the selected file name is not correct. Sections 1.4, 1.5 and 3.4.


UIText: Error in line...

   A syntax error has been found in a "UIText" user interface file. For
example, a keyboard shortcut was not enclosed in a couple of '<' and '>'
signs, or an unrecognized keyboard qualifier name was used. A line number
greater than the number of lines in the file indicates that one or more
texts are missing. Sections 1.14 and 8.10.


Volume is full

   The unit to which a save operation has been directed is full, and
cannot contain the requested amount of data. The data can still be saved
on any unit which has enough free room to contain it. The disks which come
with Personal Paint are almost completely full. Additional data (e.g. a
picture) should not be saved to these disks. Instead, a new disk should be
formatted, or a new drawer should be created on a hard disk partition
where some space is left, to contain all Personal Paint files. Sections
1.3.4, 1.5, 1.13 and 10.2.


Volume not mounted

   The selected peripheral does not contain any storage unit. There
probably is no disk in the selected drive. This can only happen if the
Expand Path option has been disabled, as Personal Paint's default volume
access mode is by logical name, rather than physical name. Section 8.8.1.


Workbench screen cannot be closed

   Personal Paint cannot close the Workbench screen, since it contains
other windows than those used to display the content of disks and drawers.
Section 8.16.


Workbench screen cannot be opened

   Personal Paint cannot open the Workbench screen, as requested in a
settings file or through a program menu. There is probably not enough free
Chip RAM. Sections 8.16 and 10.1.