"Personal Fonts Maker -  H. PDM Program Messages"


H.         PDM Program Messages

   This appendix lists (in alphabetical order) and explains the most
important messages of the Printer Driver Modifier, like the listing of the
Personal Fonts Maker messages, in appendix G. A more complete description
can be found in the referenced sections.


Content overflow in character...   (D1B)
Content overflow in command...   (D1C)

   The program has detected that the control sequence associated with the
specified character or commmand is too long to fit in the space reserved
for that character or command by the driver. This can only happen in the
"Fixed Locations" encoding mode. The error condition is detected when a
driver is saved or the definitions are checked. As described in section
10.4 ("Save Definitions") it is always better to modify an original
printer driver, rather than one which has already been modified. Sections
9.4.2 ("The Editing Gadget"), 10.2 ("Save Driver"), 10.6 ("Check
Definitions") and 11.5 ("Encoding Mode").


Definition overflow   (D41)

   While loading a printer driver, the Printer Driver Modifier has
encountered a control sequence which is too large to be displayed and
edited in the program's string gadgets. Sections 1.9.6 ("String Gadgets")
and 10.1 ("Load Driver").


Error during file I/O   (D20)

   During a load or save operation the Amiga operating system has issued
an error code. The Printer Driver Modifier cannot complete the operation.
Section 14.1 ("Problems with Disks").


Global character table overflow...   (D3B)
Global command table overflow...   (D3A)

   In the "Floating Locations" encoding mode (section 11.5.2) the Printer
Driver Modifier stores the printer control codes one immediately after the
other. Whenever a control sequence is made shorter than the original
sequence stored in the printer driver, more memory becomes available for
the other codes. Two blocks of memory are used: one for the control
sequences associated with characters, and the other for printer commands.
The size of the blocks depends on the printer driver, and cannot be
increased by the Printer Driver Modifier. If too many control sequences
are made larger, but not enough other sequences are made shorter to create
room for the new codes, this error message is displayed. The message
indicates where the error has occurred (in the character or the command
section), and how many bytes in that section overflow (i.e. the bytes
which are in excess). Some bytes can be saved by disabling the "Strings on
Word Boundary" option (section 11.5.3). As described in section 10.4
("Save Definitions") additional space can be gained by editing an original
printer driver, rather than one which has already been modified. The error
condition is detected when a driver is saved or the definitions are
checked. Sections 9.4.2 ("The Editing Gadget"), 10.2 ("Save Driver"), 10.6
("Check Definitions") and 11.5 ("Encoding Mode").


Illegal code in character...   (D27)

   A NOAV or DLAY code has been encountered in a control sequence
associated with a character. These codes can only be used in the control
sequences associated with printer commands (not characters). After this
error message is displayed, the cursor in the editing gadget appears over
the position where the error was detected. Section 9.4.2 ("The Editing
Gadget").


Illegal parameter in line...   (D22)

   Reading a parameter file (section 10.3, "Load Definitions"), the
parameter following a CHAR or COMM keyword falls outside the valid range.
The CHAR keyword accepts a parameter in the range from 160 to 255, while
the value following the COMM keyword must be in the range 0-75. These
codes are the same which are used in the "Number" gadget (section 9.4.1).


Illegal value in command...   (D28)

   As explained in section 9.4.2 ("The Editing Gadget"), printer drivers
store the codes DLAY, NUL and NOAV internally, using the values 253, 254
and 255 (decimal). This means that the values from 253 to 255 are
reserved, and cannot be used in a control sequence associated with a
printer command. If one of the reserved codes is found in a control
sequence associated with a command, this error message is displayed. The
Printer Driver Modifier automatically searches for these codes when a
driver is saved or the definitions are checked. After this error message
is displayed, the exact position where one of these reserved codes was
found is highlighted by the cursor in the editing gadget. Sections 10.2
("Save Driver"), 10.6 ("Check Definitions") and 11.5 ("Encoding Mode").


Internal name mismatch - Please confirm   (D23)

   Printer drivers have an internal name, in addition to the file name.
The driver for the NEC Pinwriter printers, for example, is called
"Nec_Pinwriter". This name is used both as an internal name and to name
the file containing that printer's driver data. If, when loading a driver
(section 10.1), the Printer Driver Modifier detects that the driver's
internal name is different from the file name which has been selected
through the file requester (section 3.23) it displays this warning
message, asking the user to confirm the load operation. The message itself
does not imply an error. It simply informs the user that the driver which
has been selected may not contain the data the user really wanted to load.
If modified versions of the drivers are always saved with other names than
the original name, this message may be a useful help in distinguishing
original drivers from modified versions. As explained in section 10.4
("Save Definitions") it is preferable to modify an original printer
driver, rather than one which has already been modified.


No errors were found   (D2C)

   After a "Check Definitions" command (section 10.6), the Printer Driver
Modifier has checked all control sequences, without finding any errors.


Printer device will be removed as soon as possible   (D34)

   The "Flush Printer Device" function (section 10.8) has been selected,
but the printer driver is currently being used, and cannot be removed from
the system's RAM. As soon as the program currently using the driver does
not need the driver any more, the memory occupied by the driver will be
freed.


Syntax error in character...   (D29)
Syntax error in command...   (D2A)

   The control sequence associated with the specified character or
commmand contains an error. The error may have been caused by a
non-existing code (e.g. "DELY" written instead of "DLAY"), an open
parentheses ('(') not immediately followed by a number (decimal,
hexadecimal or octal), or a missing close parentheses (')') after the
numerical constant, a backslash ('\') followed by character whose ASCII
code is out of the range 33 to 126. FFDL constant codes and the NOAV and
DLAY codes must be written in upper case. The error is detected when a
driver is saved or the definitions are checked. The program automatically
positions the cursor of the editing gadget where the error was found.
Sections 2.7.1 ("FFDL Constants"), 10.2 ("Save Driver"), 10.6 ("Check
Definitions") and 11.5 ("Encoding Mode") and appendix B ("Hexadecimal,
Decimal, Octal, Binary and ASCII Codes Table").


Syntax error in line...   (D21)

  An error has been encountered during the loading of a file containing
control sequence definitions. Most likely, in the specified line the
initial keyword was other than CHAR or COMM, or the keyword was not
followed by a number and an equal sign. Sections 2.6 ("Program and Font
Parameters") and 10.3 ("Load Definitions").


The current definitions will be lost   (D1D)

   The current set of control sequences has been modified since it was
last loaded or saved. The changes to the sequences would be lost if the
program proceeded as requested (e.g. loading a new driver or definition
file, or terminating the program). This warning message gives the user the
opportunity to abort the selected function to save the definitions. This
can be done either by saving the entire driver, or saving the control
sequences to a definition file. Sections 10.1 ("Load Driver"), 10.3 ("Load
Definitions"), 10.4 ("Save Definitions"), 10.5 ("Clear Definitions") and
10.10 ("Quit").


The driver cannot be modified   (D26)

   A "Load Driver" command has been issued (section 10.1), but the
technique implemented by the Printer Driver Modifier to modify the
driver's control sequences cannot be applied to that driver. This may
happen, for example, if the user tries to modify a driver which has
already been modified by clearing all definitions (or the first ones).


The file cannot be opened   (D1E)

   The file specified in the file requester (section 3.23) cannot be
opened. A wrong path or file name may have been specified. The program
cannot write to a file if another program is accessing the same file. It
is also possible that a software protection is preventing the operating
system from accessing the file. The Workbench "Information" (or "Info") or
the Shell/CLI "Protect" command can be used to modify the access status of
the file.


The file does not contain the required data   (D1F)

   The program has tried to load the data contained in a file, but
discovered that the file did not contain the expected data. For example, a
file other than a printer driver (or a printer driver of an Amiga
operating system version previous to 1.2) may have been specified for the
"Load Driver" function (section 10.1), or the parameter file selected for
the "Load Definitions" operation did not begin with the "PDM DEFS" header.
Sections 3.23 ("The File Requester"), 10.1 ("Load Driver") and 10.3 ("Load
Definitions").


The printer device has been removed   (D33)

   The printer driver has been successfully removed from RAM using the
"Flush Printer Device" function (section 10.8). The printer driver can
stay in RAM even after a program has finished using it (often occupying
precious memory). The operating system should be able to detect a
memory-shortage condition and free the memory occupied by the driver, but
it may sometimes be necessary to remove the driver sooner. A printer
driver may also be flushed if it has been modified with the Printer Driver
Modifier, so that the Amiga operating system is forced to load the updated
version the next time the driver is needed. The driver is also removed
automatically by the "Save Driver" function (section 10.2).


The printer device is not in RAM   (D32)

   The "Flush Printer Device" function (section 10.8) has been selected,
but the driver has not been found in the system's RAM. This may be caused
by the fact that the driver has not yet been used, or the operating system
(or a previous "Flush Printer Device" command) has already removed it.


There is not enough memory   (D25)

   There is not enough memory to perform the operation requested. It may
be useful to close as many Workbench windows as possible and terminate
other programs. If the Personal Fonts Maker is running, the "Free Font
Memory" function (section 4.2) can be used on one of the two font
environments, and the "Free Character Set" function (section 4.7) on the
other font.