SYS
SYS0000H: 
;
;
SYS0001H: 
;
;
SYS0002H: EXPLANATION: The file named in the command does not exist in the
current directory or search path specified or the file name was
entered incorrectly.

ACTION: Retry the command using the correct file name.
;
;
SYS0003H: EXPLANATION: The path named in the command does not exist for the
drive specified or the path was entered incorrectly.

ACTION: Retry the command using the correct path.
;
;
SYS0004H: EXPLANATION: The maximum number of open files has been reached.

ACTION: Wait until another program has ended and then retry the
command.
;
;
SYS0005H: EXPLANATION: One of the following has occurred:
1. The file is marked read-only.
2. The resource (for example, a file or subdirectory) that you tried to
   access is in use or the named pipe, queue, or semaphore is a shared
   resource in use.
3. You tried to access a resource or to perform an action for which you
   do not have sufficient privilege.  You have LAN Server Version 2.0
   or later installed and you tried to access a resource or perform an
   action for which you do not have sufficient privilege.
4. The file name is incorrect.
5. DOS attempted to open a file that has required extended attributes
   associated with it.  The Need EA bit is set on one or more of the
   extended attributes.

ACTION: Do one of the following and then retry the command:
1. Use the ATTRIB command to change the read-only attribute.
2. Try to re-access the resource later.
3. Log on with sufficient privilege.  If you do not have sufficient
   privilege, request it from the administrator who controls access.
4. Correct the file name.
5. Use the appropriate OS/2 utility to process the file.
;
;
SYS0006H: 
;
;
SYS0007H: 
;
;
SYS0008H: EXPLANATION: If segment swapping is active, the swap file may be full
or an input/output (I/O) error may have occurred on the auxiliary
storage device that contains the swap file.

ACTION: Do one of the following and then retry the command:
o  Reduce the number of running programs.
o  Reduce the value of the BUFFERS=, TRACEBUF=, DISKCACHE=, THREADS=,
   RMSIZE=, or DEVICE=VDISK.SYS statement in the CONFIG.SYS file and
   then restart the system.
o  Remove unwanted files from the swap file disk and restart the system.
o  Install additional memory on your system.
o  Check the swap file disk for an I/O error.
;
;
SYS0009H: 
;
;
SYS0010H: 
;
;
SYS0011H: 
;
;
SYS0012H: 
;
;
SYS0013H: 
;
;
SYS0014H: 
;
;
SYS0015H: EXPLANATION: One of the following has occurred:
1. The specified drive does not exist.
2. The drive letter is incorrect.
3. You are trying to RESTORE to a redirected drive.
4. You are trying to RESTORE to a read-only drive.

ACTION: For situations 1 and 2 above, retry the command using
the correct drive letter.  For situations 3 and 4, you are not
allowed to RESTORE to a redirected drive or a read-only drive.
;
;
SYS0016H: EXPLANATION: The directory cannot be removed for one of the following
reasons:
1. It does not exist or is misspelled.
2. It contains files or other subdirectories.
3. It is the current directory in this session or another session that
   is in process, or it is on a drive that is not current in any
   session.
4. It has the same name as an OS/2 reserved device name.

ACTION: Do one of the following and retry the command:
1. Correct the directory name.
2. Remove all files and subdirectories from the directory.
3. Use the CD or CHDIR command to change the current directory in all
   sessions that might be using it.
4. If the directory name is the same as an installed device, remove
   the device.
;
;
SYS0017H: EXPLANATION: The file cannot be moved or renamed to a different disk
drive.

ACTION: Retry the command, specifying the same drive for both the
original and changed file names, or attempt to copy the file.
;
;
SYS0018H: 
;
;
SYS0019H: EXPLANATION: No information can be changed or added to a
write-protected drive.

ACTION: If this is a removable media drive, make sure that the proper
diskette is being used or remove the write protection and retry the
command. If the diskette has been prepared using XDF (eXtended Density Format),
it must be reformatted to remove the write protection.
;
;
SYS0020H: EXPLANATION: An unknown device was specified.

ACTION: Retry the command using a correct device name.
;
;
SYS0021H: EXPLANATION: One of the following errors occurred:
o  The drive is empty.
o  The drive door is open.
o  The drive is in use.

ACTION: Do one of the following and retry the command:
o  Insert a diskette in the drive.
o  Close the drive door.
o  Wait until the drive is available.
;
;
SYS0022H: 
;
;
SYS0023H: EXPLANATION: The operating system cannot read or write the data
correctly.

ACTION: If the error occurred on a hard disk, retry the command.  If
the error occurs again, the hard disk may have to be reformatted.  If
the error occurred on a diskette, insert a formatted diskette or the
backup diskette and retry the command.
;
;
SYS0024H: 
;
;
SYS0025H: EXPLANATION: The disk may be damaged, unformatted, or not compatible
with the operating system.

ACTION: Do one of the following:
o  Make sure the diskette is properly inserted.
o  Check that the disk is not damaged.
o  Format the disk for the operating system.
;
;
SYS0026H: EXPLANATION: The disk or diskette is not properly formatted
for the operating system.

ACTION: Format the disk or diskette for the operating system.
;
;
SYS0027H: EXPLANATION: The disk or diskette may be damaged, unformatted,
or not compatible with the operating system.

ACTION: Do one of the following and retry the command:
o  Make sure the diskette is properly inserted.
o  Use CHKDSK to check that the disk is not damaged.
o  Format the disk or diskette for the operating system.  Warning!
   When you format a disk or diskette, any information that was
   previously on the disk or diskette is erased.
o  Make sure you do not have a high-density diskette in a low-density
   diskette drive.
;
;
SYS0028H: EXPLANATION: One of the following has occurred:
o  There is no paper in the printer.
o  There is not enough disk space to create a spool file.  (If
   printing to a LAN server, the server disk is full.)

ACTION: Do one of the following:
o  Make sure the printer is loaded properly with paper.
o  Make sure the printer is switched on.
o  Make sure the printer is installed and connected.
o  Delete any unnecessary files from the disk that contains the spool
   directory and retry the command.
;
;
SYS0029H: EXPLANATION: The operating system detected an error while writing to
this device.

ACTION: Retry the command after ensuring that the device is:
o  Installed and connected
o  Switched on
o  Not being used by another process
o  In the proper receive mode
o  Formatted if the device is a disk
;
;
SYS0030H: EXPLANATION: The operating system detected an error while reading
from this device.

ACTION: Retry the command after making sure that the device is:
o  Installed and connected
o  Switched on
o  Not being used by another process
o  In the proper send mode
o  Formatted if the device is a disk
;
;
SYS0031H: EXPLANATION: An attached device is not working for one of the
following reasons:
o  It is switched off or connected improperly.
o  The diskette and drive types are incompatible.
o  The diskette is not properly inserted in the drive.
o  The drive door is open.
o  The diskette is not properly formatted.

ACTION: Correct the problem and retry the command.
;
;
SYS0032H: EXPLANATION: The file is already being used by another process.

ACTION: Retry the command later.
;
;
SYS0033H: EXPLANATION: One process has locked a portion of the file and a second
process has attempted to use the same portion of the file.

ACTION: Retry the command later.
;
;
SYS0034H: 
;
;
SYS0035H: EXPLANATION: The program attempted to open a file using File Control
Blocks (FCBs), but the FCB limit was exceeded.

ACTION: Edit the CONFIG.SYS file to increase the value in the
FCBS= statement.  Restart the system and retry the command.
;
;
SYS0036H: EXPLANATION: The maximum number of files in the sharing buffer has
temporarily been exceeded.

ACTION: Retry the command when fewer programs are running.
;
;
SYS0037H: EXPLANATION: You tried to write to a diskette that is write-protected.

ACTION: Make sure that the proper diskette is being used or remove the
write protection.  Retry the command.
If the diskette has been prepared using XDF (eXtended Density Format),
it must be reformatted to remove the write protection.
;
;
SYS0038H: EXPLANATION: An unknown device was specified.

ACTION: Retry the command using a correct device name.
;
;
SYS0039H: EXPLANATION: One of the following has occurred:
1. The device is not ready or is empty.
2. The device driver for COMn is not installed or COMn was
   shut down and further use of it is disabled.

ACTION: Do one of the following and retry the command:
1. Insert a diskette in the drive and close the drive door or
   wait until the drive is available.
2. a. Check the CONFIG.SYS file for the DEVICE=COM.SYS statement.
   b. Shut down the system.  During restart, note and refer to
      any messages regarding COMn.
   c. Issue MODE COMn from a command prompt to see if COMn exists.
3. Be sure there is hardware for COMn.
;
;
SYS0040H: 
;
;
SYS0041H: EXPLANATION: The operating system cannot read or write the data
correctly.

ACTION: If the error occurred on a hard disk, retry the command.  If
the error occurs again, the hard disk may have to be reformatted.  If
the error occurred on a diskette, insert a formatted diskette or the
backup diskette and retry the command.
;
;
SYS0042H: 
;
;
SYS0043H: EXPLANATION: The disk or diskette may be damaged, unformatted, or not
compatible with the operating system.

ACTION: Do one of the following and retry the command:
1. Make sure the diskette is properly inserted.
2. Check that the disk or diskette is not damaged.
3. Format the disk or diskette for the operating system.
;
;
SYS0044H: 
;
;
SYS0045H: EXPLANATION: The disk or diskette may be damaged, unformatted, or not
compatible with the operating system.

ACTION: Do one of the following and retry the command:
1. Make sure the diskette is properly inserted.
2. Check that the disk or diskette is not damaged.
3. Format the disk or diskette for OS/2.
4. Format a damaged optical disc with the /L option.
5. Format the diskette to the proper density for the disk drive.
;
;
SYS0046H: EXPLANATION: There is no paper in the printer.

ACTION: Make sure the printer is:
o  Installed and connected
o  Switched on
o  Loaded properly with paper
;
;
SYS0047H: EXPLANATION: The operating system detected an error while
writing to this device.

ACTION: Retry the command after ensuring that the device is:
o  Installed, connected, and switched on
o  Not being used by another process
o  In the proper receive mode
o  Formatted if the device is a disk
o  Files with extended attributes cannot be written to flash media.
   Use EAUTIL.EXE to split the extended attributes from the named file.
   Then copy both files to the flash media.
;
;
SYS0048H: EXPLANATION: The operating system detected an error while
reading from this device.

ACTION: Retry the command after ensuring that the device is:
o  Installed, connected, and switched on
o  Not being used by another process
o  In the proper send mode
o  Formatted if the device is a disk
;
;
SYS0049H: EXPLANATION: An attached device is not working for one of
these reasons:
o  It is switched off or connected improperly.
o  The diskette and drive types are incompatible.
o  The diskette is not properly inserted in the drive.
o  The drive door is open.
o  The diskette is not properly formatted.

ACTION: Correct the problem and retry the command.
;
;
SYS0050H: EXPLANATION: You attempted an operation that cannot be performed from
your computer or that is not supported on the specified remote server.

ACTION: Verify that you are using the correct server for the command or
task that you want to perform and retry the command.  If you continue
to have problems, contact your network administrator to ensure that the
correct software is installed on your workstation.
;
;
SYS0051H: EXPLANATION: You might have specified the wrong computer name or the
remote computer might be busy or turned off.

ACTION: Perform one of the following actions and retry the operation:
o  Specify the correct remote computer name.
o  Ensure that the specified remote computer is available.

If neither action corrects the problem, contact your network
administrator.
;
;
SYS0052H: EXPLANATION: Another computer or user on the network is already using
this name.  Your computer name must be unique on the network.

ACTION: Choose another name for your computer and retry the command.
;
;
SYS0053H: EXPLANATION: The server that you specified does not exist or has not
been started.

ACTION: Do one of the following and retry the command:
o  Verify that you specified the path name correctly.
o  Verify that the server specified is started.

Contact your network administrator if you continue to have problems.
;
;
SYS0054H: EXPLANATION: The network is currently busy processing other requests
or is out of resources.

ACTION: Retry the command at a later time or verify your network
configuration to be sure enough network resources are specified.
;
;
SYS0055H: EXPLANATION: The computer that shared the resource might have been
turned off or the permissions might have been changed.

ACTION: Do one of the following:
o  Check to see that the computer sharing resources is turned on
   and retry the command.
o  Contact your network administrator to find out how you can use
   the resource.
;
;
SYS0056H: EXPLANATION: The network currently has too many NETBIOS requests
waiting to be processed.

ACTION: Retry the command at a later time.  If you continue to have
problems, contact your network administrator.
;
;
SYS0057H: EXPLANATION: The hardware that connects your computer to the local
area network is experiencing a problem.

ACTION: Make sure that the cable on the back of your computer is
properly connected and then retry the command.  If you continue to
have problems, contact your network administrator or the manufacturer
of the network hardware.
;
;
SYS0058H: EXPLANATION: You are attempting an operation that cannot be performed
by the specified server.

ACTION: Make sure that you have specified the correct computer name
and command, then retry the command.  If you continue to have problems,
contact your network administrator.
;
;
SYS0059H: EXPLANATION: Your workstation received an error from the network that
was not expected in this situation.

ACTION: Retry the operation.  If you continue to have problems, contact
your network administrator.
;
;
SYS0060H: EXPLANATION: Your computer cannot communicate with the specified remote
computer because their hardware adapters are not compatible.

ACTION: Retry the command communicating with a different computer.
If you continue to have problems, contact your network administrator.
;
;
SYS0061H: EXPLANATION: The printer cannot take any additional print requests at
this time.

ACTION: Retry the command at a later time.
;
;
SYS0062H: EXPLANATION: The server that is sharing the printer does not
have space available to store the file waiting to be printed.

ACTION: Retry the command at a later time.
;
;
SYS0063H: EXPLANATION: The file you recently submitted for printing was deleted
by another user on the server.

ACTION: Contact the other user to find out why the file was deleted or
retry the command at a later time.
;
;
SYS0064H: EXPLANATION: The network resource that you specified was either
temporarily taken off-line or is no longer available.  It is possible
that:
o  The share at the server might have been temporarily deleted.
o  The server that shared the resource might have been turned off.
o  The permissions might have been changed.

ACTION: Retry the operation.  If you continue to have difficulty
accessing the resource contact the person who administers the server
to find out why it is no longer available or contact the network
administrator.
;
;
SYS0065H: EXPLANATION: You attempted to access a resource that is not available
to you.  It is possible that:
o  You do not have a valid account on the server sharing the resource.
o  Your account on this server has not been granted the permissions
   necessary to access the resource.

ACTION: Make sure that you specify the correct name of the resource
that you want to use and retry the command.  If you are still denied
access, contact your network administrator.
;
;
SYS0066H: EXPLANATION: The network directory or device name that you specified
is incorrect.

ACTION: Retry the command using the correct network directory or
device name.  Your possible choices are:
  Directory device names          A - Z
  Printer device names            LPT1 - LPT9
  Communications device names     COM1 - COM4
;
;
SYS0067H: EXPLANATION: The specified network name is incorrect.  You attempted
to access a resource that is not shared by the server you specified.

ACTION: Make sure that the network name you specified is correct and
retry the command.  If you continue to have problems, contact your
network administrator.
;
;
SYS0068H: EXPLANATION: The number of names allowed on the network adapter card
for the local computer was exceeded.

ACTION: Perform one of the following actions and retry the operation:
o  Disconnect from any resources that you are not currently using.
o  Reconfigure the network adapter card.

If neither action corrects the problem, contact your network
administrator.
;
;
SYS0069H: EXPLANATION: Your computer network adapter card has too many NETBIOS
sessions currently active.

ACTION: Disconnect from any resources that you are not currently using
and retry the command.  If you continue to have problems, contact your
network administrator.
;
;
SYS0070H: EXPLANATION: The server you attempted to access is either in a paused
state or is still being started.

ACTION: Retry the command at a later time.  If the same error occurs,
contact your network administrator.
;
;
SYS0071H: EXPLANATION: One of the following occurred:
o  The specified server cannot support the network request.
o  The server might have run out of network resources such as memory,
   network buffers, or NETBIOS commands necessary to process your
   request.
o  The maximum number of users for the alias may have been reached.

ACTION: Retry the command at a later time.  If the same error
occurs, contact your network administrator.  Network administrators
should consult the server's documentation.
;
;
SYS0072H: EXPLANATION: The printer or disk device that you specified has
been paused.

ACTION: Use the NET CONTINUE command to reactivate the device and
retry the command.
;
;
SYS0073H: EXPLANATION: No information can be changed or added to a
write-protected diskette.

ACTION: Make sure that the proper diskette is being used or remove
the write protection.  Retry the command.
If the diskette has been prepared using XDF (eXtended Density Format),
it must be reformatted to remove the write protection.
;
;
SYS0074H: EXPLANATION: An attached device is not working for one of these reasons:
o  It is switched off or connected improperly.
o  The diskette and drive types are incompatible.
o  The diskette is not properly inserted in the drive.
o  The drive door is open.
o  The diskette is not properly formatted.

ACTION: Correct the problem and retry the command.
;
;
SYS0075H: EXPLANATION: The XGA virtual device driver requires locked memory to
guarantee successful I/O (input/output) transfer by the XGA coprocessor.

ACTION: To end a program, select it from the Window List and then
close it.
;
;
SYS0076H: 
;
;
SYS0077H: 
;
;
SYS0078H: 
;
;
SYS0079H: 
;
;
SYS0080H: 
;
;
SYS0081H: 
;
;
SYS0082H: EXPLANATION: One of the following errors occurred:
o  The file or directory name already exists.
o  The directory path cannot be found.
o  The root directory is full or there is not enough space on the
   disk for the new file or directory.
o  The directory name contains unacceptable OS/2 characters or is a
   reserved file name.
o  The disk is not properly formatted.

ACTION: Correct the problem and retry the command.
;
;
SYS0083H: 
;
;
SYS0084H: EXPLANATION: The system has more requests to process than it
can currently handle.

ACTION: Retry the request later.
;
;
SYS0085H: EXPLANATION: You specified a resource with a local device
name that is already being used.

ACTION: Retry the request using a different device name.
Your possible choices are:
  Directory device names          A - Z
  Printer device names            LPT1 - LPT9
  Communications device names     COM1 - COM4
;
;
SYS0086H: EXPLANATION: The password that you specified is incorrect for the
account or resource you attempted to access.

ACTION: Specify the correct password.  If you continue to have
problems, contact your network administrator.
;
;
SYS0087H: 
;
;
SYS0088H: EXPLANATION: An error occurred while data was being written to disk.
Data might have been lost.

ACTION: Ensure that the disk that you want to write to has enough
space available, and that you have permission to write to the target
file.  Then retry the command.
;
;
SYS0089H: EXPLANATION: The maximum number of running processes has been reached.

ACTION: End a process or retry the command after the current process
has completed.
;
;
SYS0090H: 
;
;
SYS0091H: 
;
;
SYS0092H: 
;
;
SYS0093H: 
;
;
SYS0094H: 
;
;
SYS0095H: 
;
;
SYS0096H: EXPLANATION: The application attempted to use an illegal DTA value
that would disable the system.  The application will be closed.
ACTION: Contact the supplier of the application.
;
;
SYS0097H: 
;
;
SYS0098H: 
;
;
SYS0099H: EXPLANATION: The device requested is not available.  One of the
following has occurred:
o  The device is being used by another application.
o  The MODE command is attempting to get dedicated access to the
   same DMA channel twice (for example, MODE COM1 TXDMA=ON RXDMA=ON).

ACTION: Do one of the following:
o  Retry the command at a later time.
o  Reconfigure the COM port using the Reference Diskette.  Set the
   Serial Transmit and Serial Receive Arbitration levels to a shared
   or dedicated number that is not in conflict with another port.
;
;
SYS0100H: EXPLANATION: All of the system semaphore slots have been used.
Another system semaphore cannot be created until one has been freed.

ACTION: Try again later.
;
;
SYS0101H: EXPLANATION: This is an exclusive system semaphore (only the owner
can modify it).

ACTION: End your requested operation.
;
;
SYS0102H: EXPLANATION: A semaphore cannot be closed while it is set.

ACTION: Release the semaphore or wait for it to be released
and then close it.
;
;
SYS0103H: EXPLANATION: Semaphores can be set and released in a nested fashion
only a limited number of times.  That limit has been reached.

ACTION: Check semaphore request nesting and make sure that the
semaphore is released before requesting it again.
;
;
SYS0104H: EXPLANATION: Exclusive system semaphores are owned by a task.  The
system checks to make sure that only the owner modifies the semaphore.
It is impossible to determine the requestor at interrupt time, so
exclusive semaphores may not be modified then.

ACTION: End your requested operation.
;
;
SYS0105H: 
;
;
SYS0106H: 
;
;
SYS0107H: 
;
;
SYS0108H: EXPLANATION: A process has exclusive use of this disk or diskette,
prohibiting another process from accessing it at this time.

ACTION: Retry the operation later or try it on another disk or diskette.
;
;
SYS0109H: EXPLANATION: The using process has closed the pipe or (if you are
trying to write to the pipe) there are no available readers.

ACTION: End your requested operation.
;
;
SYS0110H: 
;
;
SYS0111H: EXPLANATION: The new file name exceeds 255 characters.

ACTION: Rename the file using a shorter file name.
;
;
SYS0112H: EXPLANATION: The disk or diskette being written to has no more room.

ACTION: Delete some unwanted files and retry the command.
;
;
SYS0113H: 
;
;
SYS0114H: 
;
;
SYS0115H: 
;
;
SYS0116H: 
;
;
SYS0117H: 
;
;
SYS0118H: 
;
;
SYS0119H: 
;
;
SYS0120H: 
;
;
SYS0121H: 
;
;
SYS0122H: 
;
;
SYS0123H: EXPLANATION: The system does not accept characters displayed using
the keyboard combination ALT plus 0-32 or the following characters:

  \  /  [ ] : |  <  >  +  ; =  .  ?  *  "

ACTION: Correct the file name or volume label and retry the command.
;
;
SYS0124H: 
;
;
SYS0125H: 
;
;
SYS0126H: EXPLANATION: The requested module is not loaded.

ACTION: Check which module is being requested and make sure that it
has been loaded.
;
;
SYS0127H: EXPLANATION: The specified procedure is not in the module being
searched or in the Exitlist routine list.

ACTION: Check which procedure is being requested and make sure that it
is in the module or Exitlist routine list.
;
;
SYS0128H: 
;
;
SYS0129H: 
;
;
SYS0130H: 
;
;
SYS0131H: 
;
;
SYS0132H: 
;
;
SYS0133H: 
;
;
SYS0134H: 
;
;
SYS0135H: 
;
;
SYS0136H: 
;
;
SYS0137H: 
;
;
SYS0138H: 
;
;
SYS0139H: 
;
;
SYS0140H: 
;
;
SYS0141H: 
;
;
SYS0142H: EXPLANATION: The drive specified is being used by another process.

ACTION: Retry the command later.
;
;
SYS0143H: 
;
;
SYS0144H: EXPLANATION: The directory specified in the JOIN command must be a
subdirectory of the root directory.

ACTION: Retry the command specifying a different directory.
;
;
SYS0145H: EXPLANATION: The JOIN command requires that the directory be empty.

ACTION: Retry the command specifying an empty directory.
;
;
SYS0146H: EXPLANATION: An attempt was made to join to a path which is
being used in a substitute.

ACTION: Retry the command specifying a different path.
;
;
SYS0147H: EXPLANATION: All available memory is in use.  If segment swapping is
active, the swap file may be full.

ACTION: Do one of the following and retry the command:
o  Reduce the number of running programs.
o  Reduce the value of the BUFFERS=, TRACEBUF=, DISKCACHE=, THREADS=,
   RMSIZE=, or DEVICE=VDISK.SYS statement in the CONFIG.SYS file and
   restart the system.
o  Remove unwanted files from the swap file disk and restart the system.
o  Install additional memory on your system.
o  Contact the supplier of the application.
;
;
SYS0148H: EXPLANATION: The path specified is being used by the current process
or another process.

ACTION: Retry the command later.
;
;
SYS0149H: 
;
;
SYS0150H: EXPLANATION: The CONFIG.SYS file does not contain a TRACE= or TRACEBUF=
statement or tracing is not allowed by the TRACE utility.

ACTION: If a TRACE= or TRACEBUF= statement is not present in your
CONFIG.SYS file, add the appropriate statement.  If your CONFIG.SYS
file contains one of the statements, use the TRACE utility to allow
tracing.
;
;
SYS0151H: EXPLANATION: Either no event or too many events were specified in a
call to DosMuxSemWait.

ACTION: Correct the event count.
;
;
SYS0152H: EXPLANATION: All system slots for DosMuxSemWait semaphores have been
taken.  Another semaphore cannot be accommodated until a slot is freed.

ACTION: Try again later.
;
;
SYS0153H: EXPLANATION: The list passed to DosMuxSemWait is not in the proper
format.

ACTION: Correct the format of the DosMuxSemWait list.
;
;
SYS0154H: 
;
;
SYS0155H: EXPLANATION: The thread table for the processes is full.  Another
thread cannot be added.

ACTION: Remove some idle threads and try again, or use a different
process.
;
;
SYS0156H: EXPLANATION: The signal sent was not handled by the recipient.

ACTION: Make sure the recipient can handle the signal sent or try a
different signal.
;
;
SYS0157H: 
;
;
SYS0158H: 
;
;
SYS0159H: EXPLANATION: The thread ID address passed to DosCreateThread was
incorrect.

ACTION: Correct the thread ID address.
;
;
SYS0160H: EXPLANATION: The argument (command parameters) string passed to
DosExecPgm was not in the proper format.

ACTION: Correct the argument string.
;
;
SYS0161H: 
;
;
SYS0162H: EXPLANATION: This signal could not be posted because the process
has another signal to process.

ACTION: Try again later.
;
;
SYS0163H: 
;
;
SYS0164H: EXPLANATION: All system slots for threads have been used.  No more
threads can be created until some threads have been released.

ACTION: Free some threads or processes and try again.
;
;
SYS0165H: 
;
;
SYS0166H: EXPLANATION: The operation has failed because the network has not
been installed.

ACTION: Install the appropriate network.
;
;
SYS0167H: 
;
;
SYS0168H: 
;
;
SYS0169H: 
;
;
SYS0170H: 
;
;
SYS0171H: EXPLANATION: The application disabled the interrupts and did not reset
them in a reasonable period of time.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS0172H: 
;
;
SYS0173H: 
;
;
SYS0174H: 
;
;
SYS0175H: 
;
;
SYS0176H: 
;
;
SYS0177H: 
;
;
SYS0178H: 
;
;
SYS0179H: 
;
;
SYS0180H: EXPLANATION: The DLL or EXE file contains a segment number that is
incorrect or the file is unusable.

ACTION: Do one of the following and then retry the command.
o  Restart the system.
o  Replace the DLL or EXE file.
;
;
SYS0181H: 
;
;
SYS0182H: EXPLANATION: The application program cannot run on this version
of the OS/2 operating system.

ACTION: Reinstall the application and retry the command.  If the
error occurs again, contact the supplier of the application.
;
;
SYS0183H: 
;
;
SYS0184H: 
;
;
SYS0185H: 
;
;
SYS0186H: EXPLANATION: The flag passed to the JOIN command or to DosFlagProcess
was incorrect.

ACTION: Correct the flags.
;
;
SYS0187H: EXPLANATION: The specified system semaphore name is incorrect.

ACTION: Make sure the semaphore name is correct and try again.
;
;
SYS0188H: EXPLANATION: The application program does not have a correct
END <label> directive.

ACTION: Contact the supplier of the application.
;
;
SYS0189H: EXPLANATION: The application program does not contain a correct stack
segment.

ACTION: Contact the supplier of the application.
;
;
SYS0190H: EXPLANATION: A dynamic link library (DLL) file cannot be used as an
application program.  An application cannot be used as a DLL.

ACTION: Reinstall the application and retry the command.  If the
error occurs again, contact the supplier of the application program.
;
;
SYS0191H: EXPLANATION: The specified file or program is either a DOS application
program or not compatible with OS/2.

ACTION: If the specified application is a DOS program, switch to a DOS
session and retry the command.  Otherwise, reinstall the application
and retry the command.  If the error occurs again, contact the supplier
of the application program.
;
;
SYS0192H: EXPLANATION: LINK detected errors when this application program was
created.

ACTION: Contact the supplier of the application.
;
;
SYS0193H: EXPLANATION: The specified file or program is either a DOS application
program or not compatible with OS/2.

ACTION: If the specified application is a DOS program, switch to a DOS
session and retry the command.  Otherwise, reinstall the application
and retry the command.  If the error occurs again, contact the supplier
of the application program.
;
;
SYS0194H: EXPLANATION: One of the segments in the specified file contains more
than 64KB of data.

ACTION: Contact the supplier of the application program.
;
;
SYS0195H: EXPLANATION: The minimum storage allocation size of a segment is
specified to be less than the size of the data segment in the file.

ACTION: Contact the supplier of the application.
;
;
SYS0196H: EXPLANATION: Routines that run in ring 2 to utilize I/O privileges
cannot link to dynamic link libraries.

ACTION: Contact the supplier of the application.
;
;
SYS0197H: EXPLANATION: The program requires input/output privilege and the system
is not configured to allow it.

ACTION: Edit the CONFIG.SYS file and add the statement IOPL=YES.  Then
restart the system and retry the command.
;
;
SYS0198H: EXPLANATION: The segment can only have privilege levels of 2 and 3.
The segment specified has an unacceptable privilege level.

ACTION: Contact the supplier of the application.
;
;
SYS0199H: EXPLANATION: The program's autodata segment exceeds 64KB.

ACTION: Contact the supplier of the application.
;
;
SYS0200H: 
;
;
SYS0201H: EXPLANATION: The relocation-chain for a segment exceeds the segment
limit.

ACTION: Contact the supplier of the application program.
;
;
SYS0202H: EXPLANATION: The system has detected an infinite loop in the
relocation-chain segment.

ACTION: Contact the supplier of the application program.
;
;
SYS0203H: 
;
;
SYS0204H: 
;
;
SYS0205H: 
;
;
SYS0206H: EXPLANATION: The length of the file name or the extension is greater
than the maximum length allowed.

ACTION: Correct the file name or the extension and retry the command.
For more information about file names, refer to "file-naming rules" in
the Master Help Index.
;
;
SYS0207H: 
;
;
SYS0208H: 
;
;
SYS0209H: EXPLANATION: The signal number is incorrect or a Presentation Manager
application is trying to set SIGINTR or SIGBREAK, which is not allowed.
Possible signal numbers are:
  1 - Ctrl+C (SIGINTR)
  3 - Program terminated (SIGTERM)
  4 - Ctrl+Break (SIGBREAK)
  5 - Process flag A
  6 - Process flag B
  7 - Process flag C

ACTION: Correct the signal number.
;
;
SYS0210H: EXPLANATION: Signal handlers cannot be set when a process is ending.

ACTION: Allow the process to end without setting a handler.
;
;
SYS0211H: 
;
;
SYS0212H: 
;
;
SYS0213H: 
;
;
SYS0214H: EXPLANATION: The system ran out of space for keeping track of
dynamic-link modules that are attached to the module being executed
or loaded.

ACTION: Remove some dynamic link library dependencies from the program
or module.
;
;
SYS0215H: 
;
;
SYS0216H: 
;
;
SYS0217H: 
;
;
SYS0218H: 
;
;
SYS0219H: EXPLANATION: The Exitlist routine address must be at ring 3.

ACTION: Correct the Exitlist routine address.
;
;
SYS0220H: 
;
;
SYS0221H: 
;
;
SYS0222H: 
;
;
SYS0223H: 
;
;
SYS0224H: EXPLANATION: The specified PM session ID does not appear in the Window
List.  One of the following has occurred:
o  The application window was created without the FCF_TASKLIST style.
o  The application window has not yet been created.
o  The application window has been destroyed.

ACTION: Refer to "WinCreateStdWindow" and "Frame Control Window
Processing" in the Presentation Manager Programming Reference.
;
;
SYS0225H: 
;
;
SYS0226H: 
;
;
SYS0227H: 
;
;
SYS0228H: EXPLANATION: DosWaitChild placed the current thread in a wait state to
allow all child processes to be completed, but no more child processes
exist.

ACTION: Continue your operation.
;
;
SYS0229H: 
;
;
SYS0230H: EXPLANATION: A pipe operation cannot be performed on a file that does
not refer to a pipe.

ACTION: Contact the supplier of the application.
;
;
SYS0231H: EXPLANATION: The pipe cannot be accessed because another process is
using it.

ACTION: Retry the operation later.
;
;
SYS0232H: 
;
;
SYS0233H: EXPLANATION: The specified pipe was disconnected at its other end.

ACTION: Retry the program later.
;
;
SYS0234H: EXPLANATION: A read operation on a pipe has read the requested amount,
but the pipe contains more data to be read.

ACTION: Contact the supplier of the application.
;
;
SYS0235H: 
;
;
SYS0236H: 
;
;
SYS0237H: 
;
;
SYS0238H: 
;
;
SYS0239H: 
;
;
SYS0240H: EXPLANATION: Transmission errors caused the connection to the remote
machine to be disconnected.

ACTION: Run the application again to re-establish the connection.
;
;
SYS0241H: EXPLANATION: The network specified is not registered.

ACTION: Retry this operation using a correct network name.
;
;
SYS0242H: EXPLANATION: You tried to register a name that has already been used.

ACTION: Try another name or contact your system administrator.
;
;
SYS0243H: 
;
;
SYS0244H: 
;
;
SYS0245H: 
;
;
SYS0246H: 
;
;
SYS0247H: 
;
;
SYS0248H: 
;
;
SYS0249H: 
;
;
SYS0250H: EXPLANATION: You cannot move or rename a parent directory to one of its
subdirectories.  Such an action causes a loop in the directory tree.

ACTION: Check that you have chosen the correct directories and retry
the command.
;
;
SYS0251H: EXPLANATION: Possible reasons why the operation is not allowed are:
o  COMMAND.COM or CMD.EXE is at the prompt in the source directory.
o  The source directory specified is in use.
o  The directory is part of a SUBST or JOIN macro.

ACTION: Do one of the following:
o  Determine if COMMAND.COM or CMD.EXE is in the source directory.
   If so, change the directory and retry the command.
o  Check to see if the source directory is being used as a current
   directory by an active program.  If so, wait until the program
   ends and retry the command.
o  Remove the directory from the SUBST or JOIN macro.
;
;
SYS0252H: EXPLANATION: The specified file system name could not be found.

ACTION: Do one of the following:
o  Retry the operation using the correct file system name.
o  Add the IFS= statement (containing the correct file system name)
   to the CONFIG.SYS file and restart your system.
o  Contact the supplier of the application.
;
;
SYS0253H: EXPLANATION: The device name could not be found in the specified path.

ACTION: Retry the operation using the correct device name and path or
contact the supplier of the application.
;
;
SYS0254H: EXPLANATION: The extended-attribute name contains a character that is
incorrect.

ACTION: Correct the extended-attribute name and retry the operation.
;
;
SYS0255H: EXPLANATION: The extended-attribute list size does not match the size
that was specified.

ACTION: Correct the extended-attribute list size and retry the
operation or contact the supplier of the application.
;
;
SYS0256H: EXPLANATION: The extended-attribute list is too long.

ACTION: Use a shorter extended-attribute list or contact the
supplier of the application.
;
;
SYS0257H: 
;
;
SYS0258H: EXPLANATION: The application program timeout did not allow the
requested number of changes to occur.

ACTION: Contact the supplier of the application.
;
;
SYS0259H: 
;
;
SYS0260H: EXPLANATION: A system directory search structure has been reused
and is now no longer valid.

ACTION: End the operation.
;
;
SYS0261H: 
;
;
SYS0262H: EXPLANATION: The stack size indicated in a DevHlp_RegisterStackUsage
call was too large.

ACTION: Request and use a smaller of stack.
;
;
SYS0263H: 
;
;
SYS0264H: EXPLANATION: The starting address for the program being executed is
not at ring 3.

ACTION: Recompile the program with the starting address at ring 3.
;
;
SYS0265H: EXPLANATION: The start routine address for the DLL being loaded is not
at ring 3.

ACTION: Recompile the DLL with the starting address at ring 3.
;
;
SYS0266H: EXPLANATION: Either the source and target files are not in the same
file system or the operating system does not support COPY for this
file system.

ACTION: Check the source and target file names and retry the operation.
;
;
SYS0267H: 
;
;
SYS0268H: 
;
;
SYS0269H: 
;
;
SYS0270H: 
;
;
SYS0271H: 
;
;
SYS0272H: 
;
;
SYS0273H: 
;
;
SYS0274H: 
;
;
SYS0275H: 
;
;
SYS0276H: EXPLANATION: The extended attributes for the specified disk or diskette
are not usable.

ACTION: Run CHKDSK /F on the disk or diskette.
;
;
SYS0277H: EXPLANATION: The number of files containing extended attributes has
reached the system limit.

ACTION: Delete any files containing extended attributes that you no
longer need.
;
;
SYS0278H: EXPLANATION: A file contains a reference to an extended attribute that
does not exist.  Either the disk volume is damaged or the extended
attribute system file has been improperly modified.

ACTION: Run CHKDSK /F on the disk or diskette.
;
;
SYS0279H: EXPLANATION: The system cannot find a cluster in the extended
attribute system file.  The cause might be a disk error or a
damaged extended attribute system file.

ACTION: Run CHKDSK /F on the disk or diskette.
;
;
SYS0280H: EXPLANATION: No free directory entry exists in the root or not enough
space is available on the disk or diskette.

ACTION: Remove a file from the root directory that you do not currently
need and retry the command.
;
;
SYS0281H: EXPLANATION: The file could be missing, in which case you might
not be able to recover it.

ACTION: Run CHKDSK /F on the disk or diskette.
;
;
SYS0282H: EXPLANATION: An attempt was made to save extended attributes using a
file system that does not have the ability to save extended attributes.

ACTION: Save the file or directory using a file system that can save
extended attributes or use the EAUTIL /S command to save the file or
directory without saving the extended attributes.
;
;
SYS0283H: EXPLANATION: An attempt was made to save extended attributes using a
file system that does not have the ability to save extended attributes.
The extended attributes must be saved with the file or directory.

ACTION: Save the file or directory using a file system that can save
extended attributes.
;
;
SYS0284H: 
;
;
SYS0285H: EXPLANATION: You are attempting to create a semaphore, but the name you
specified already exists.  You must specify a unique semaphore name.

ACTION: Specify a different semaphore name and retry the command.
;
;
SYS0286H: EXPLANATION: You cannot issue the call to wait on an empty muxwait
semaphore.

ACTION: Add an event or mutex to the muxwait semaphore and retry the
command.
;
;
SYS0287H: EXPLANATION: You are trying to wait on a muxwait semaphore when one or
more of the muxwait semaphores is owned by the current thread.  This
condition might result in a deadlock.

ACTION: Query the muxwait semaphore and release the owned semaphore
and retry the command.
;
;
SYS0288H: EXPLANATION: You must be the current owner of a mutex semaphore to
release it.

ACTION: Request ownership of the mutex semaphore and retry the command.
;
;
SYS0289H: EXPLANATION: The buffer parameter passed to DosQueryMuxWaitSem is not
large enough to complete the operation.

ACTION: Use the buffer size returned in the pcSemRec field of the
DosQueryMuxWaitSem call.  Then retry the operation.
;
;
SYS0290H: EXPLANATION: The limit for the number of handles allowed in the system
at one time has been reached.

ACTION: Retry the command when a semaphore has been closed out or when
a semaphore has been removed from the system.
;
;
SYS0291H: EXPLANATION: You tried to open a semaphore that has already been opened
the maximum number of times.

ACTION: Wait until the semaphore has been closed at least once and
retry the command.
;
;
SYS0292H: EXPLANATION: You have specified a semaphore that is not the correct
type for the operation requested.

ACTION: Be sure the semaphore type matches the type required by the
operation.  Correct the semaphore type and retry the command.
;
;
SYS0293H: 
;
;
SYS0294H: 
;
;
SYS0295H: 
;
;
SYS0296H: 
;
;
SYS0297H: 
;
;
SYS0298H: EXPLANATION: There is a limited number of times that an event
semaphore can be posted.  You tried to post an event semaphore
that has already been posted the maximum number of times.

ACTION: Retry the call when the event semaphore has been reset.
;
;
SYS0299H: EXPLANATION: The event semaphore was already posted at the time you
called DosPostEventSem.

ACTION: The event semaphore was already posted and remains posted.
No action needs to be taken.
;
;
SYS0300H: EXPLANATION: The event semaphore was reset at the time you called
DosResetEventSem.

ACTION: The event semaphore was already reset and remains reset.
No action needs to be taken.
;
;
SYS0301H: EXPLANATION: You cannot make the final close of a semaphore while
other threads in the current process are waiting for it.

ACTION: Retry the command when all the threads have been awakened.
;
;
SYS0302H: 
;
;
SYS0303H: EXPLANATION: The program passed a process identifier to the operating
system for which no process exists.

ACTION: Contact the supplier of the application.
;
;
SYS0304H: 
;
;
SYS0305H: 
;
;
SYS0306H: 
;
;
SYS0307H: 
;
;
SYS0308H: 
;
;
SYS0309H: 
;
;
SYS0310H: 
;
;
SYS0311H: 
;
;
SYS0312H: 
;
;
SYS0313H: 
;
;
SYS0314H: 
;
;
SYS0315H: 
;
;
SYS0316H: EXPLANATION: The message was truncated because the length of the
buffer passed to the message retriever is not large enough for the
entire message.  The storage area passed to DosGetMessage is too
small to hold the message to be displayed.

ACTION: Contact the supplier of the application.
;
;
SYS0317H: EXPLANATION: The message is not in the message file.

ACTION: Enter the correct message number or reinstall the message
file and retry the command.
;
;
SYS0318H: EXPLANATION: The message file should be in the current directory.

ACTION: Install the message file or specify the location of the
message file using the DPATH command (for OS/2 sessions) or APPEND
(for DOS sessions).  Then, retry the command.
;
;
SYS0319H: EXPLANATION: Another process may be using the message file or the
message file is incorrect.

ACTION: Wait for the other process to finish or reinstall the message
file and retry the command.
;
;
SYS0320H: EXPLANATION: The value of IvCount (count of variable insertion text
strings) cannot exceed 9.

ACTION: Correct the programming error or refer to the manual that
came with the application program.
;
;
SYS0321H: EXPLANATION: The system does not have enough memory to display the
message or a system error occurred.

ACTION: Retry the command later.
;
;
SYS0322H: 
;
;
SYS0323H: 
;
;
SYS0324H: 
;
;
SYS0325H: 
;
;
SYS0326H: 
;
;
SYS0327H: 
;
;
SYS0328H: 
;
;
SYS0329H: 
;
;
SYS0330H: EXPLANATION: A process attempted to read, peek at, or purge a queue
that is owned by another process.

ACTION: Contact the supplier of the application.
;
;
SYS0331H: 
;
;
SYS0332H: EXPLANATION: A process attempted to create a queue with
the same name as an existing queue.

ACTION: Contact the supplier of the application.
;
;
SYS0333H: EXPLANATION: A process attempted to read or peek at an
element that is not in the queue.

ACTION: Contact the supplier of the application.
;
;
SYS0334H: EXPLANATION: The total amount of memory for queues in the system
was exceeded.

ACTION: If you are simultaneously running multiple applications
that use queues, cancel one of the applications.  If you are running
only one application that uses queues, contact the supplier of the
application.
;
;
SYS0335H: 
;
;
SYS0336H: 
;
;
SYS0337H: 
;
;
SYS0338H: 
;
;
SYS0339H: 
;
;
SYS0340H: 
;
;
SYS0341H: 
;
;
SYS0342H: 
;
;
SYS0343H: 
;
;
SYS0344H: 
;
;
SYS0345H: 
;
;
SYS0346H: 
;
;
SYS0347H: 
;
;
SYS0348H: 
;
;
SYS0349H: EXPLANATION: The function masks for the functions to be replaced
contain a binary value of zero or the masks had bits set for
undefined functions.

ACTION: Assign the appropriate bit mask for the functions to be
replaced.  Refer to the OS/2 Toolkit for information about VioRegister
or VioGlobReg.
;
;
SYS0350H: EXPLANATION: The physical address of the video buffer is below that of
the start of the video buffer or the start of the video buffer plus
the input buffer length is beyond the end of the video buffer.

ACTION: Refer to the VioGetPhysBuf section of the OS/2 Toolkit
or any documentation unique to your Video Device Handler/Adapter
for information regarding the valid range of the video buffer.
;
;
SYS0351H: 
;
;
SYS0352H: 
;
;
SYS0353H: 
;
;
SYS0354H: 
;
;
SYS0355H: EXPLANATION: The mode information may contain values that cannot be
supported by the Video Device Handler or the requested VIO function
cannot be completed using the current display mode.

ACTION: Refer to the OS/2 Toolkit or any documentation unique to your
Video Device Handler/Adapter for information regarding which modes are
supported by your video adapter.
;
;
SYS0356H: EXPLANATION: The requested cursor width cannot be set.

ACTION: Refer to the OS/2 Toolkit or any documentation unique to your
Video Device Handler/Adapter for information about the specific cursor
width allowed by your video adapter.
;
;
SYS0357H: 
;
;
SYS0358H: EXPLANATION: The row parameter is beyond the valid range allowed for
the current display mode.

ACTION: Refer to the OS/2 Toolkit or any documentation unique to your
Video Device Handler/Adapter for information about the row or column
configuration for each display mode supported by your video adapter.
;
;
SYS0359H: EXPLANATION: The column parameter specified is beyond the valid range
for the current display mode.

ACTION: Refer to the OS/2 Toolkit or any documentation unique to your
Video Device Handler/Adapter for information about the row or column
configuration for each display mode supported by your video adapter.
;
;
SYS0360H: 
;
;
SYS0361H: 
;
;
SYS0362H: 
;
;
SYS0363H: 
;
;
SYS0364H: 
;
;
SYS0365H: 
;
;
SYS0366H: EXPLANATION: The wait-flag parameter, which indicates whether to wait
or return immediately when attempting to obtain a screen lock through
VioScrLock, is incorrect.  The correct wait-flag parameter values are:
0 - Return immediately if screen I/O is not available.
1 - Wait until screen I/O becomes available.

ACTION: Correct the wait-flag parameter and retry the operation.
;
;
SYS0367H: EXPLANATION: A VioScrLock call must be in effect before VioScrUnlock
is called.

ACTION: Be sure a successful call to VioScrLock is accomplished before
VioScrUnlock is called.  The VioScrUnlock and VioScrLock calls must be
issued from the same process.
;
;
SYS0368H: 
;
;
SYS0369H: EXPLANATION: The specified parameter that indicates which screen
group needs to be set, selected, or stopped is incorrect.

ACTION: Refer to the OS/2 Toolkit under DosSetSession,
DosSelectSession, or DosStopSession for the correct parameter.
;
;
SYS0370H: 
;
;
SYS0371H: EXPLANATION: An internal Session Manager error occurred when the
requested session was not found in the active session queue.

ACTION: Reinstall your system and restart the system.
;
;
SYS0372H: EXPLANATION: The Presentation Manager set title routine is corrupted.

ACTION: Reinstall your system and restart the system.
;
;
SYS0373H: EXPLANATION: One or more of the parameters passed to a keyboard API
function were incorrect.

ACTION: Refer to the OS/2 Toolkit to determine which parameters are
valid for the keyboard API function being issued.
;
;
SYS0374H: 
;
;
SYS0375H: EXPLANATION: The value of the IOWAIT parameter for the keyboard
API function is incorrect.

ACTION: Refer to the OS/2 Toolkit for correct IOWAIT parameter values.
;
;
SYS0376H: EXPLANATION: The parameter value that specifies the keyboard API
function length is invalid.

ACTION: Refer to the OS/2 Toolkit for a definition of accepted
parameter values for the keyboard API function being issued.
;
;
SYS0377H: EXPLANATION: The system detected an error for the value of one or
more of the bitmask parameters that were passed to KbdSetState.

ACTION: Refer to the OS/2 Toolkit for a description of KbdSetState.
;
;
SYS0378H: 
;
;
SYS0379H: EXPLANATION: The specified parameters are incorrect.

ACTION: Perform the following actions:
1. Check the parameters passed to the monitor API call.
2. Correct any parameter error and retry the call.
;
;
SYS0380H: EXPLANATION: The specified device for DosMonOpen is incorrect.

ACTION: Retry the operation using the correct device name.
;
;
SYS0381H: EXPLANATION: The specified device handle for monitor API is incorrect.
The device handle should be the same as the one returned by DosMonOpen.

ACTION: Retry the operation using the correct device handle.
;
;
SYS0382H: EXPLANATION: The monitor buffer length must be greater than or
equal to the device driver monitor-chain buffer plus 20 bytes.

ACTION: Correct the length of the monitor buffer and retry the
operation.
;
;
SYS0383H: EXPLANATION: The monitor application is terminating or there is no
data in the buffer.  DosMonRead was called during one of the following
conditions:
o  A DosMonClose call for the monitor application was in progress.
o  The wait flag parameter on the call was set to 1, indicating
   "DO NOT WAIT", and the monitor buffer was empty.

ACTION: Confirm that DosMonClose was not issued and retry DosMonRead.
;
;
SYS0384H: EXPLANATION: The bytecount parameter passed to DosMonWrite is too large,
causing DosMonWrite to terminate.  The bytecount parameter must be equal
to, or smaller than, the device driver monitor-chain buffer.

ACTION: Correct the value of the bytecount parameter and retry the
operation.
;
;
SYS0385H: EXPLANATION: Mouse API function calls are not valid when the mouse and
pointer-draw device drivers are not loaded.

ACTION: Ensure that the appropriate statements to load the MOUSExxx.SYS
and POINTDD.SYS device drivers are in the CONFIG.SYS file.  Refer to
the DEVICE= command in the Command Reference for more information.
;
;
SYS0386H: EXPLANATION: A process is attempting to close a mouse handle that
it did not open with MouOpen.  Mouse handles obtained from DosOpen
are not valid for the mouse API functions.

ACTION: Refer to the OS/2 Toolkit for a description of MouClose.
;
;
SYS0387H: 
;
;
SYS0388H: 
;
;
SYS0389H: 
;
;
SYS0390H: 
;
;
SYS0391H: 
;
;
SYS0392H: 
;
;
SYS0393H: 
;
;
SYS0394H: 
;
;
SYS0395H: 
;
;
SYS0396H: EXPLANATION: The system cannot find the COUNTRY.SYS file in the
directory specified in the COUNTRY= statement of the CONFIG.SYS file.
OS/2 cannot start the system unless the COUNTRY.SYS file is contained
in the COUNTRY= statement specified in the CONFIG.SYS file.

ACTION: Place the COUNTRY.SYS file in the directory specified by the
COUNTRY= statement in the CONFIG.SYS file and retry the operation.
;
;
SYS0397H: EXPLANATION: The system cannot open the COUNTRY.SYS file to read
its information.

ACTION: Determine if another application has exclusive access to the
COUNTRY.SYS file.  If so, wait until that application is terminated
and retry the operation.
;
;
SYS0398H: EXPLANATION: The system cannot find the specified country
code or code page.
The following list shows valid combinations for country code
and code page, for each country that is supported.

                         CODE PAGES
COUNTRY             CODE SUPPORTED
Albania             355  850, 437
Arabic-speaking     785  864 (Note 1), 850
Asia (English)      099  437, 850
Australia           061  437, 850
Belgium             032  850, 437
Bosnia              387  852, 850
Brazil              055  850, 437
Bulgaria            359  915, 850
Canada (French)     002  863, 850
Croatia             385  852, 850
Czech Republic      421  852, 850
Czechoslavakia      042  852, 850
Denmark             045  850
Estonia             372  922, 850
Finland             358  850, 437
France              033  850, 437
Germany             049  850, 437
Hebrew-speaking     972  862 (Note 1), 850
Hungary             036  852, 850
Iceland             354  850, 861
Italy               039  850, 437
Japan               081  932 (Note 2), 437
Korea               082  949 (Note 2), 437
Latin America       003  437, 850
Latvia              371  921, 850
Lithuania           370  921, 850
FYR Macedonia       389  855, 850
Netherlands         031  850, 437
Norway              047  850
Peoples Rep. China  086  936, (Note 2), 437
Poland              048  852, 850
Portugal            351  850, 860
Romania             040  852, 850
Russia              007  866, 850
Serbia              381  855, 850
Slovakia            422  852, 850
Slovenia            386  852, 850
Rep. of China  (TW) 088  948, (Note 2), 437
Spain               034  850, 437
Sweden              046  850, 437
Switzerland         041  850, 437
Turkey              090  857, 850
United Kingdom      044  850, 437
United States       001  437, 850
Yugoslavia          038  852, 850

   Notes:
      1. This code page is supported only with a
         special version of OS/2.
      2. This code page is supported only with the
         Asian version of OS/2 on Asian hardware.
ACTION: Perform the following actions; then, start the system
again:
1. Check the country code and code page.
2. Edit the CODEPAGE= and COUNTRY= statements in the CONFIG.SYS
   file to correct any errors.
;
;
SYS0399H: EXPLANATION: The buffer length specified on the NLS API call is too
small to contain all of the returned NLS table.
ACTION: Increase the buffer length specified on the NLS API call and
retry the operation.
;
;
SYS0400H: 
;
;
SYS0401H: 
;
;
SYS0402H: 
;
;
SYS0403H: 
;
;
SYS0404H: EXPLANATION: A VioRegister call must be in effect before VioDeRegister
is called.

ACTION: Be sure a successful call to VioRegister is accomplished before
VioDeRegister is called.  The VioDeRegister and VioRegister calls must
be issued from the same process.
;
;
SYS0405H: EXPLANATION: A VioPopup call must be in effect before VioEndPopup is
called.

ACTION: Be sure a successful call to VioPopup is accomplished before
VioEndPopup is called.  The VioEndPopup and VioPopup calls must be
issued from the same process.
;
;
SYS0406H: EXPLANATION: Another VIO pop-up already exists and only one
can be active at a time.

ACTION: Perform one of the following actions:
o  Wait for the existing pop-up process to complete.
o  Repeat the VioPopup call periodically until a successful
   return is obtained.
;
;
SYS0407H: EXPLANATION: The keyboard API function can be called only from the
Session Manager or Workplace Shell processes.

ACTION: Refer to the OS/2 Toolkit to determine which API functions can
be called from your process.
;
;
SYS0408H: EXPLANATION: KbdRegister accepts ASCIIZ strings of certain lengths
only.  ASCIIZ strings with a length of 0 are not accepted.

ACTION: Refer to the OS/2 Toolkit to determine which ASCIIZ string
lengths are accepted by KbdRegister.
;
;
SYS0409H: EXPLANATION: The caller of KbdRegister must attempt to register
replacement functions for existing keyboard API functions only.
The function mask parameter passed to KbdRegister must not be zero.

ACTION: Refer to the OS/2 Toolkit to determine which bits are defined
for the function mask parameter of KbdRegister.
;
;
SYS0410H: EXPLANATION: Only one KbdRegister is allowed between KbdDeRegister
calls.  KbdRegister is valid only from full-screen sessions.

ACTION: If this error occurred in a full-screen session, start your
program in a new full-screen session.  If the current session is not a
full-screen session, start your program in a full-screen session.
;
;
SYS0411H: EXPLANATION: The current session does not have an Alternate Keyboard
Subsystem registered.  KbdDeRegister is used to undo a KbdRegister.

ACTION: Refer to the OS/2 Toolkit to determine when KbdDeRegister
can be issued.
;
;
SYS0412H: EXPLANATION: The mouse API function can be called only from the Session
Manager or Workplace Shell processes.

ACTION: Refer to the OS/2 Toolkit to determine which functions are
allowed for your process.
;
;
SYS0413H: EXPLANATION: MouRegister accepts ASCIIZ strings of certain lengths
only.  ASCIIZ strings of length zero are not accepted.

ACTION: Refer to the OS/2 Toolkit to determine which ASCIIZ string
lengths are accepted by MouRegister.
;
;
SYS0414H: EXPLANATION: The caller of MouRegister must attempt to register
replacement functions for existing mouse API functions only.  The
function mask parameter passed to MouRegister must not be zero.

ACTION: Refer to the OS/2 Toolkit to determine which bits are defined
for the function mask parameter of MouRegister.
;
;
SYS0415H: EXPLANATION: Only one MouRegister is allowed between MouDeRegister
calls.  MouRegister is valid only from full-screen sessions.

ACTION: If this error occurred in a full-screen session, start your
program in a new full-screen session.  If the current session is not a
full-screen session, start your program in a full-screen session.
;
;
SYS0416H: EXPLANATION: The current session does not have an Alternate Mouse
Subsystem registered.  MouDeRegister is used to undo a MouRegister.

ACTION: Refer to the OS/2 Toolkit to determine when MouDeRegister can
be issued.
;
;
SYS0417H: EXPLANATION: The Session Manager detected a parameter error for the
value that specifies if the state of the shell should be saved, or an
internal Session Manager error occurred.

ACTION: Correct the programming error and retry the command.
;
;
SYS0418H: EXPLANATION: Once the Session Manager has been started, device
drivers cannot be registered.

ACTION: Ensure that the specified device driver has requested to be
registered with the Session Manager before the Session Manager starts
its initialization process.
;
;
SYS0419H: 
;
;
SYS0420H: 
;
;
SYS0421H: EXPLANATION: The parameters specified to the VIO call contain values
that are not acceptable to the VIO function.

ACTION: Verify the contents of the parameters and refer to the OS/2
Toolkit for specific information regarding the VIO application in
question.
;
;
SYS0422H: EXPLANATION: When registration of mode or save redraw wait thread
already exists, any subsequent VioModeWait, VioModeUndo,
VioSaveRedrawWait, or VioSaveRedrawUndo call made by a process
other than the current owner is not allowed.

ACTION: Execute your program from a new screen group.
;
;
SYS0423H: 
;
;
SYS0424H: 
;
;
SYS0425H: 
;
;
SYS0426H: EXPLANATION: VioRegister and VioGlobalReg calls are not allowed
from the pop-up screen group.  Also, a call to VioRegister is not
valid if another process has already registered for the current
screen group.

ACTION: Execute your program from a new screen group.
;
;
SYS0427H: 
;
;
SYS0428H: EXPLANATION: A VioSaveRedrawWait call must be in effect before
VioSaveRedrawUndo is called.

ACTION: Be sure a successful call to VioSaveRedrawWait is
accomplished before VioSaveRedrawUndo is called.  VioSaveRedrawUndo
and VioSaveRedrawWait calls must be issued from the same process.
;
;
SYS0429H: EXPLANATION: VioGetPhysBuf can be called only by a process executing
in the foreground screen group.

ACTION: Refer to the OS/2 Toolkit for information regarding the current
and foreground screen group.
;
;
SYS0430H: EXPLANATION: This VIO application is not allowed while the current VIO
pop-up is executing.

ACTION: Refer to the OS/2 Toolkit for the list of VIO application
calls that are allowed during the execution of a VIO pop-up.
;
;
SYS0431H: EXPLANATION: An internal Session Manager error occurred when a function
that is reserved for the shell was requested.

ACTION: Reinstall your system and restart the system.
;
;
SYS0432H: EXPLANATION: An internal Session Manager error occurred when an
application program requested session status.

ACTION: Reinstall your system and restart it.
;
;
SYS0433H: 
;
;
SYS0434H: EXPLANATION: A screen lock is already in effect, preventing the call
to VioScrLock from any other thread executing within the same screen
group.

ACTION: Execute your program from a new screen group or wait until
VioScrUnlock is called by the process that called VioScrLock.
;
;
SYS0435H: EXPLANATION: The value of the IOWAIT parameter is incorrect.

ACTION: Refer to the OS/2 Toolkit for correct IOWAIT parameter values.
;
;
SYS0436H: EXPLANATION: For a full-screen or VIO windowed application, a handle
of zero must be used.  For a Presentation Manager application, the VIO
handle returned from VioCreatePS must be used.

ACTION: Refer to the OS/2 Toolkit for information regarding VIO handle
usage.
;
;
SYS0437H: 
;
;
SYS0438H: EXPLANATION: The length parameter specifies a value that is not
sufficient for the VIO call.

ACTION: Refer to the OS/2 Toolkit for information regarding the
length values allowed for the VIO call.
;
;
SYS0439H: EXPLANATION: The accepted values for a keyboard handle are zero and
any handle obtained from KbdOpen.  Keyboard handles obtained from
DosOpen are not valid for the keyboard API functions.

ACTION: Refer to the OS/2 Toolkit for a definition of accepted
keyboard handle values for the keyboard API function being issued.
;
;
SYS0440H: EXPLANATION: The system has a limited number of handles that
can be used at the same time.  All of the handles are in use
at this time.

ACTION: Stop any programs that you are no longer using and
retry the program.
;
;
SYS0441H: EXPLANATION: The Keyboard device driver returned an allocation
error to the keyboard subsystem because of a problem allocating
a keyboard control block for the new logical keyboard handle.
No more space is available for the keyboard control block.

ACTION: Stop running any programs and sessions that you are
no longer using and restart the program.
;
;
SYS0442H: EXPLANATION: An error was returned from DosRead while the keyboard
subsystem was reading the KEYBOARD.DCP file.  This error most likely
occurred during system initialization.

ACTION: Ensure that your KEYBOARD.DCP file is correct and loads properly
when the system is started.
;
;
SYS0443H: EXPLANATION: One or more of the code-page IDs specified in the CODEPAGE=
statement of the CONFIG.SYS file are incorrect.

ACTION: Refer to CODEPAGE command in the online Command Reference
for more information.
;
;
SYS0444H: EXPLANATION: The CONFIG.SYS file must contain a CODEPAGE= statement at
system startup so that your system can process code-page commands.

ACTION: If code-page support is desired, add the appropriate CODEPAGE=
statement in the CONFIG.SYS file and start the system again.  Refer to
the CODEPAGE command in the Command Reference for more information.
;
;
SYS0445H: EXPLANATION: Logical keyboard handles may only be used between calls
to KbdGetFocus and KbdFreeFocus.  KbdFreeFocus may only be issued while
there is an outstanding KbdGetFocus.

ACTION: Ensure that the thread using logical keyboard handles or
issuing KbdFreeFocus is the same thread that issued KbdGetFocus.
;
;
SYS0446H: EXPLANATION: Only one thread per session can own the focus at a time.

ACTION: Release the focus of the current thread by issuing KbdFreeFocus
and re-issue KbdGetFocus to obtain the keyboard focus for the new
logical handle.  Refer to the OS/2 Toolkit for more information about
KbdOpen, KbdGetFocus, and KbdFreeFocus.
;
;
SYS0447H: EXPLANATION: Another thread owns the KbdGetFocus call or is waiting
for input from the device.

ACTION: Re-issue the call to KbdGetFocus with the wait option or start
your program in another session.
;
;
SYS0448H: EXPLANATION: The code page passed to KbdSetCP must also be specified
in the CODEPAGE= statement of the CONFIG.SYS file during system startup.

ACTION: Add the appropriate statement to the CONFIG.SYS file and restart
the system.  Refer to the CODEPAGE command in the Command Reference for
more information.
;
;
SYS0449H: EXPLANATION: The keyboard handle passed to KbdGetFocus must be either
zero or a non-zero value obtained from KbdOpen.  Keyboard handles
obtained from DosOpen are not valid for use with KbdGetFocus.

ACTION: Re-issue the call to KbdGetFocus using an appropriate
keyboard handle.  Refer to the OS/2 Toolkit for more information
about KbdGetFocus.
;
;
SYS0450H: EXPLANATION: An internal Session Manager error occurred when the
shell attempted to select a session that is not selectable.

ACTION: Reinstall your system and restart it.
;
;
SYS0451H: 
;
;
SYS0452H: EXPLANATION: An internal Session Manager error occurred because the
requesting session was not the parent of the target session.

ACTION: Ensure that the requesting session is the parent of the
target session.  Reinstall your system and restart it.
;
;
SYS0453H: EXPLANATION: The DosStartSession parameter that specifies if the new
session should be started in the foreground or background is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0454H: EXPLANATION: The DosStartSession parameter that specifies if the
created session is related to the calling session is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0455H: EXPLANATION: The DosSetSession parameter that specifies which session
to bring to the foreground the next time the parent session is selected
is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0456H: EXPLANATION: The DosSetSession parameter that specifies if the target
session is selectable is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0457H: 
;
;
SYS0458H: EXPLANATION: The DosStopSession parameter that specifies if a
particular session or all sessions should be ended is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0459H: EXPLANATION: The reserved parameter that is required for the
DosStopSession call must be zero.

ACTION: Change the reserved parameter to 0 and re-issue DosStopSession.
;
;
SYS0460H: EXPLANATION: An internal Session Manager error occurred during a
related session start request because the requesting session was not
the parent of the newly started session.

ACTION: Reinstall your system and restart it.
;
;
SYS0461H: EXPLANATION: The DosSetSession, DosStartSession, or DosSMRegisterDD
parameter that specifies the length of the input data structure is
incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0462H: EXPLANATION: An internal Session Manager error occurred when the
parent session tried to retrieve the child session.

ACTION: Reinstall your system and restart it.
;
;
SYS0463H: EXPLANATION: If segment swapping is active, the swap file might be
full or an input or output error might have occurred on the auxiliary
storage device that contains the swap file.

ACTIONS: Perform one of the following actions:
o  Reduce the number of running programs and retry the command.
o  Reduce the value of the BUFFERS=, TRACEBUF=, DISKCACHE=, THREADS=,
   RMSIZE=, or DEVICE=VDISK.SYS statement in the CONFIG.SYS file.
   Restart the system and retry the command.
o  Remove files that you do not need from the hard disk or diskette
   and restart the system.
o  Install additional memory on your system.
o  If an input or output error occurred on the swap file, check the
   auxiliary storage device that contains the swap file.
;
;
SYS0464H: EXPLANATION: Detached processes are not allowed to make keyboard API
function calls.  The process in error might have been started using
the DETACH command or a RUN= statement that is in the CONFIG.SYS file.

ACTION: Ensure that the detached process makes keyboard API function
calls only between calls to VioPopup and VioEndPopup.
;
;
SYS0465H: EXPLANATION: A detached process can issue VIO calls only to VioPopup
and VioEndPopup, or while a VIO pop-up is in effect.

ACTION: Refer to the OS/2 Toolkit for information regarding which VIO
applications can be called by a detached process or during a VIO pop-up.
;
;
SYS0466H: EXPLANATION: Detached processes cannot make mouse API function calls.
The process in error might have been started using the DETACH command
or a RUN= statement from the CONFIG.SYS file.

ACTION: Ensure that the detached process only make mouse API function
calls only between calls to VioPopup and VioEndPopup.
;
;
SYS0467H: EXPLANATION: The font requested cannot be found in the VIOTBL.DCP file.

ACTION: Check that VIOTBL.DCP contains the font information requested.
;
;
SYS0468H: EXPLANATION: The user loadable font requested cannot be found.

ACTION: Validate the format of the font to be loaded.
;
;
SYS0469H: EXPLANATION: The code page specified on VioSetCP is not one of the
prepared code pages, nor is it set to 0.

ACTION: Edit the CONFIG.SYS file to correct any errors in the
CODEPAGE=, COUNTRY=, and DEVINFO= statements and restart the system.
;
;
SYS0470H: 
;
;
SYS0471H: EXPLANATION: The current video device is not capable of loading the
fonts to support code pages.

ACTION: Switch to a device in your system capable of supporting fonts
or install a new device that can support fonts.
;
;
SYS0472H: 
;
;
SYS0473H: 
;
;
SYS0474H: 
;
;
SYS0475H: 
;
;
SYS0476H: 
;
;
SYS0477H: 
;
;
SYS0478H: EXPLANATION: The DosStartSession parameter that specifies the value of
the tracing options is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0479H: 
;
;
SYS0480H: EXPLANATION: VioPopup cannot occur until the Workplace Shell is
started.

ACTION: Refer to the OS/2 Toolkit for information regarding how to set
up your system CONFIG.SYS file with the appropriate PROTSHELL statement.
;
;
SYS0481H: EXPLANATION: The hard error and print screen handlers could not be
started when the system was initialized.

ACTION: Reinstall your system and restart it.
;
;
SYS0482H: 
;
;
SYS0483H: EXPLANATION: A transparent pop-up cannot occur over a graphics
screen or over a screen group that has previously registered a
VioSaveRedrawWait thread.

ACTION: Issue a standard VIO pop-up instead of the transparent pop-up.
;
;
SYS0484H: 
;
;
SYS0485H: 
;
;
SYS0486H: EXPLANATION: A zero must be specified for the reserved parameter
required by the VIO application call.

ACTION: Change the reserved parameter to 0 and re-issue the VIO call.
;
;
SYS0487H: EXPLANATION: The specified address to store selectors for
DevHlp_AllocateGDTSelectors does not have enough room to store the
selectors or the specified address in DevHlp_PhysToGDTSelector goes
past the end of possible memory.

ACTION: Correct the address.
;
;
SYS0488H: 
;
;
SYS0489H: EXPLANATION: The system does not have enough free GDT selectors to
satisfy the request.

ACTION: Reduce the number of GDT selectors in use by ending processes
that you do not need.
;
;
SYS0490H: EXPLANATION: The selector passed to the system was either incorrect or
it was not allocated from the general selector pool.

ACTION: Specify the correct selector to be passed to the system.
;
;
SYS0491H: EXPLANATION: The DosStartSession parameter that specifies the type of
session to be created for this program is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0492H: EXPLANATION: The DosStartSession parameter that specifies the first
state for a windowed application is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0493H: EXPLANATION: The DosStartSession parameter that specifies if the
started program should inherit the environment and open file handles
of the calling process is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0494H: EXPLANATION: A VIO windowed program is not allowed to call this VIO
application.

ACTION: Refer to the OS/2 Toolkit for information regarding which VIO
calls can be called by a VIO windowed program.
;
;
SYS0495H: EXPLANATION: Only a Presentation Manager program can issue Advanced
VIO calls.

ACTION: Refer to the OS/2 Toolkit for information regarding Advanced
VIO applications.
;
;
SYS0496H: EXPLANATION: VioShieldInit and VioShieldTerm calls can be issued only
by the first process to call VioShieldInit for a specific session.

ACTION: Ensure that the process that will call VioShieldInit executes
first or execute your program from a new session.
;
;
SYS0497H: EXPLANATION: The call to VioCreatePS failed and an additional handle
cannot be allocate to the presentation space.

ACTION: Issue VioDestroyPS before re-issuing VioCreatePS.
;
;
SYS0498H: 
;
;
SYS0499H: 
;
;
SYS0500H: EXPLANATION: An error was returned to the keyboard subsystem when
DosLoadModule was called to load module PMVIOP.DLL.

ACTION: Ensure that the file PMVIOP.DLL is accessible from the LIBPATH
statement as specified in the CONFIG.SYS file and restart the system.
;
;
SYS0501H: 
;
;
SYS0502H: EXPLANATION: The mouse API functions only accept mouse handles
obtained from MouOpen only.  Mouse handles obtained from DosOpen
are not valid for the mouse API functions.

ACTION: Refer to the OS/2 Toolkit for a description of MouOpen.
;
;
SYS0503H: EXPLANATION: The DosStartSession parameter that specifies the
session diagnostic option is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0504H: EXPLANATION: PM sessions cannot issue keyboard API functions.
Keyboard functions are valid only from full-screen and
text-windowed sessions.

ACTION: Refer to the OS/2 Toolkit for an explanation of how to
receive keyboard input for a PM program.
;
;
SYS0505H: EXPLANATION: PM sessions cannot issue mouse API functions.  Mouse
API functions are valid only from full-screen sessions and
text-windowed sessions.

ACTION: Refer to the OS/2 Toolkit for an explanation of how to
receive mouse input for a PM program.
;
;
SYS0506H: 
;
;
SYS0507H: EXPLANATION: The process specified in a RAS trace request
does not exist.

ACTION: Correct the process ID to be passed to the system.
;
;
SYS0508H: EXPLANATION: RAS has been asked to trace-until-error, but a
similar previous request is being processed.

ACTION: Try again after RAS finishes tracing.
;
;
SYS0509H: EXPLANATION: A RAS trace-until-error request was received and
an error was encountered.

ACTION: Request RAS to turn off the trace-until-error function.
;
;
SYS0510H: EXPLANATION: A RAS request to turn off trace-until-error or
increment the error count has been received but no request
to trace-until-error exists.

ACTION: Request a RAS trace-until-error first.
;
;
SYS0511H: 
;
;
SYS0512H: EXPLANATION: RAS tracing is active, but minor code information
will not be recorded.

ACTION: Continue.  (Note that minor code trace information
is not being recorded.)
;
;
SYS0513H: EXPLANATION: An error is in the RAS major or minor code table.

ACTION: Continue.  (Note that some of the trace information
might not be recorded.)
;
;
SYS0514H: EXPLANATION: RAS has been asked to trace-until-error, but the
error count specified was zero.

ACTION: Correct the error count.
;
;
SYS0515H: EXPLANATION: The Session Manager function has too many device
drivers registered with it.

ACTION: Remove one or more device driver statements from the
CONFIG.SYS file.  Restart your system and retry the command.
;
;
SYS0516H: EXPLANATION: The DosSMRegisterDD parameter that specifies
the notification bit map is incorrect.

ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
;
;
SYS0517H: EXPLANATION: The Logging Facility cannot perform the operation you
requested because of the incorrect function code.

ACTION: Correct the function code and retry the operation.
;
;
SYS0518H: EXPLANATION: Statements required to start logging are missing
from the CONFIG.SYS file.

ACTION: Add the following statements to your CONFIG.SYS file and
restart your system:
   DEVICE=C:\OS2\LOG.SYS
   RUN=C:\OS2\SYSTEM\LOGDAEM.EXE
;
;
SYS0519H: EXPLANATION: Your request to log errors cannot be performed
because logging is suspended.

ACTION: To resume logging, go to an OS/2 command prompt and
type:  SYSLOG /R.  Then, retry the operation.
;
;
SYS0520H: EXPLANATION: The number of bytes required for the buffer are
stored in the first DWORD of the buffer.

ACTION: Call LogGetEntries and specify a larger buffer size.
;
;
SYS0521H: EXPLANATION: The Logging Facility buffer is full because the
information is being generated faster than it can be stored.

ACTION: Use SYSLOG to look at the log file and determine what is
causing the problem.
;
;
SYS0522H: EXPLANATION: The Logging Facility stores records in LogAddEntries
until an invalid record is found.  Each record must begin on a DWORD
boundary when multiple records are given in the LogAddEntries buffer.

ACTION: Correct the format of the LogAddEntries buffer.
;
;
SYS0523H: EXPLANATION: Currently, only logging class 1 is supported.

ACTION: Set the logging class to 1 and retry the API call.
;
;
SYS0524H: EXPLANATION: One of the following has occurred:
o  An invalid parameter was given to DosLogRegister.
o  Too many applications called DosLogRegister for
   log-record notification.
o  An invalid buffer was given to LogQueryState.
o  An error occurred in communicating with the Logging Facility
   LOGDAEM program.

ACTION: Do one of the following and then retry the command:
o  Correct the invalid parameter given to DosLogRegister.
o  Ensure that your application registers only once with
   DosLogRegister.
o  Correct the invalid buffer given to LogQueryState.

If the problem occurs again, use the SYSLOG utility to display the
current status of the Logging Facility.
;
;
SYS0525H: EXPLANATION: One or both of the following has occurred:
o  Another process is accessing the specified disk.
o  You have not logged on with sufficient privilege to format
   the disk.

ACTION: Do one or both of the following and retry the command:
o  End the other process or wait until it is complete.
o  Log on with sufficient privilege.
;
;
SYS0526H: EXPLANATION: This error might have been caused by a bad disk, a bad
Disk device driver, or incompatible disk and device driver.

ACTION: Restart your computer and re-run FORMAT with the /L switch
(valid only for the HPFS format).  If your computer will not start from
the hard disk, restart it using OS/2 or DOS from a diskette.  Then,
format the disk for the FAT (File Allocation Table) file system.  If
you can format your hard disk with OS/2 or DOS, the problem is with
the disk device driver that you were using with HPFS.  If you cannot
format the disk, it is probably unusable.
;
;
SYS0527H: EXPLANATION: The FORMAT command organizes the disk and copies
HPFS data to the disk.  The disk you want to format is either
corrupt or too small for the HPFS files.

ACTION: Try running FORMAT again.  If this does not work, use
LVM to increase the size of the volume or format the
volume for the FAT (File Allocation Table) file system used
with OS/2 or DOS.
;
;
SYS0528H: EXPLANATION: An operating system error occurred while the disk was
being formatted.  FORMAT was not able to finish formatting the
specified disk.
ACTION: Restart your computer and run FORMAT again.
;
;
SYS0529H: EXPLANATION: FORMAT requires more memory than your system
currently has available.

ACTION: End any programs that you no longer need that are
running as background processes or that are running in
other sessions and retry the command.
;
;
SYS0530H: EXPLANATION: HPFS (High Performance File System) volumes
can be created only on hard disks.

ACTION: Retry the command, specifying the drive letter
of the hard disk you want formatted.  If you want to format
a diskette, use the DOS or OS/2 FORMAT command to format the
disk for the FAT file system.
;
;
SYS0531H: EXPLANATION: HPFS (High Performance File System) can format
only one hard disk volume at a time.

ACTION: Retry the command using only one drive letter.
;
;
SYS0532H: EXPLANATION: A problem was detected with the UHPFS.DLL file.

ACTION: Copy the UHPFS.DLL file from your backup copy.  Then,
restart your system and retry the command.
;
;
SYS0533H: EXPLANATION: Syntax information can be found in the online
Command Reference.

ACTION: Enter HELP followed by the command name to see the
syntax of the command.
;
;
SYS0534H: 
;
;
SYS0535H: 
;
;
SYS0536H: 
;
;
SYS0537H: 
;
;
SYS0538H: 
;
;
SYS0539H: 
;
;
SYS0540H: EXPLANATION: The disk cannot be formatted for HPFS because
the HPFS file system driver is not loaded.

ACTION: Load the file system driver and retry the command.
;
;
SYS0541H: 
;
;
SYS0542H: 
;
;
SYS0543H: EXPLANATION: The correct parameters are:
drive:   Indicates the drive letter followed by a colon (such as E:),
         specifying which disk to check.
/V       Displays the name of each file as the disk is checked.
/F[:n]   Fixes the errors on the disk to the specified level of
         recovery "n" (n = 1, 2, or 3). The default is 2.

         /F:1   Fixes errors, removes corrupt files to be recovered
                later.
         /F:2   Same as /F:1, also searches orphaned areas.
         /F:3   Same as /F:2, also searches free areas for files.

         If /F is not specified, CHKDSK will only identify disk errors
         but will not correct them.

ACTION: Retry the CHKDSK command using the correct parameters.
;
;
SYS0544H: EXPLANATION: CHKDSK cannot read data from the specified drive.
Either the drive does not exist or some other process is
currently using it.

ACTION: Ensure that you specified the correct drive letter for
the disk volume you want to check.  Also, if you used
the /F parameter with CHKDSK, make sure no other program is
using that disk volume.
;
;
SYS0545H: EXPLANATION: A problem was detected with the UHPFS.DLL file.

ACTION: Copy the UHPFS.DLL file from your backup copy.  Restart
your system and retry the CHKDSK command.
;
;
SYS0546H: EXPLANATION: CHKDSK requires more memory than your system
currently has available.

ACTION: End any programs that you no longer need that are
running as background processes or that are running in other
sessions and retry the command.
;
;
SYS0547H: EXPLANATION: CHKDSK located the lost files but did not write
the recovered information to the disk yet.

ACTION: If the disk is full, delete any files that you do not
currently need and retry the CHKDSK command.
;
;
SYS0548H: EXPLANATION: CHKDSK was instructed to recover lost data but
not enough memory is available.  All of the data cannot be
recovered.

ACTION: End one or more programs that are running in other
sessions or as background processes and retry the CHKDSK command.
;
;
SYS0549H: EXPLANATION: CHKDSK is fixing errors as it finds them but does
not have enough disk space to write recovered data to the disk.

ACTION: Delete from the specified any unwanted files and retry
the command.
;
;
SYS0550H: EXPLANATION: CHKDSK did not recover any data on the disk
because it could not identify any of the directories or files.

ACTION: Restart your system and retry the CHKDSK command.
If the problem continues, restore files from your backup copy.
If this still does not fix the problem, reformat the disk.
;
;
SYS0551H: EXPLANATION: CHKDSK is trying to recover lost data even though
it cannot find the root directory of the disk.  Some of the data
might not be recovered.

ACTION: Examine the disk to see if all files were recovered.
If some files appear to be missing, run CHKDSK /F:3 to recover them.
;
;
SYS0552H: EXPLANATION: CHKDSK detected file system errors on the
specified disk.  The errors have not been corrected.

ACTION: Use the CHKDSK command with the /F parameter
to correct the errors.
;
;
SYS0553H: 
;
;
SYS0554H: 
;
;
SYS0555H: 
;
;
SYS0556H: 
;
;
SYS0557H: 
;
;
SYS0558H: 
;
;
SYS0559H: 
;
;
SYS0560H: 
;
;
SYS0561H: 
;
;
SYS0562H: EXPLANATION: Lost data was detected on the specified disk.

ACTION: Use the CHKDSK command with the /F parameter to recover the
data.
;
;
SYS0563H: 
;
;
SYS0564H: 
;
;
SYS0565H: EXPLANATION: Important!  Do NOT turn your computer off until you create
a backup copy of all files on the disk!  The disk might be unusable and
the file system files unreadable.  Once you turn your computer off, you
probably will not be able to access this volume.  If this is your
boot volume, you probably will not be able to restart your system.

ACTION: Use the OS/2 BACKUP command or another backup program to back
up all files and directories on the disk.  Type FORMAT, specifying the
drive and the /FS:HPFS parameter, to reformat the drive.  Then, restore
your data from the backup copy.
;
;
SYS0566H: EXPLANATION: CHKDSK cannot run on a disk volume while another
process is accessing the volume.

ACTION: End all programs running on the specified disk volume and
retry the CHKDSK command.
;
;
SYS0567H: 
;
;
SYS0568H: 
;
;
SYS0569H: 
;
;
SYS0570H: 
;
;
SYS0571H: 
;
;
SYS0572H: 
;
;
SYS0573H: 
;
;
SYS0574H: 
;
;
SYS0575H: 
;
;
SYS0576H: EXPLANATION: When HPFS cannot write data to its proper place on the
disk, it writes the data to a temporary replacement sector.  Not enough
disk space was available for CHKDSK to move the data that it found in
the temporary replacement sector to its correct location.

ACTION: Delete from the disk any files that you do not currently need
and retry the CHKDSK command.
;
;
SYS0577H: 
;
;
SYS0578H: 
;
;
SYS0579H: EXPLANATION: When HPFS cannot write data to its proper place on the
disk, it writes the data to a temporary replacement sector.  Not enough
disk space was available for CHKDSK to move the data that it found in
the temporary replacement sector to its correct location.

ACTION: Delete from the disk any files that you do not currently need
and retry the CHKDSK command.
;
;
SYS0580H: 
;
;
SYS0581H: 
;
;
SYS0582H: 
;
;
SYS0583H: 
;
;
SYS0584H: 
;
;
SYS0585H: 
;
;
SYS0586H: 
;
;
SYS0587H: 
;
;
SYS0588H: EXPLANATION: When HPFS cannot write data to its proper place on the
disk, it writes the data to a temporary replacement sector.  Not enough
disk space was available for CHKDSK to move the data that it found in
the temporary replacement sector to its correct location.

ACTION: Delete from the disk any files that you do not currently need
and retry the CHKDSK command.
;
;
SYS0589H: 
;
;
SYS0590H: EXPLANATION: Data was found in a temporary relocation sector by CHKDSK.

ACTION: Use the CHKDSK command with the /F parameter to recover the
data.
;
;
SYS0591H: 
;
;
SYS0592H: 
;
;
SYS0593H: EXPLANATION: The only required parameter of the RECOVER command
is the name of the file that you want to recover.

ACTION: Retry the command using a valid path name.  If necessary,
include its drive letter and path.
;
;
SYS0594H: EXPLANATION: RECOVER searched for the file you specified
but could not find it on the disk.

ACTION: Check that you typed the file name correctly.
;
;
SYS0595H: EXPLANATION: A problem was detected with the UHPFS.DLL file.

ACTION: Restart your system and retry the RECOVER command.
If the problem persists, recopy the UHPFS.DLL file from your
backup copy, restart your system, and re-run RECOVER.
;
;
SYS0596H: EXPLANATION: RECOVER requires more memory than your system
currently has available.

ACTION: End any programs that you do not need that are running
as background processes or that are running in other sessions,
and retry the RECOVER command.
;
;
SYS0597H: EXPLANATION: The disk is probably full or bad.  If you can
re-run RECOVER, the information will be recovered.

ACTION: Check if there is any free space left on the disk.  If
the disk is full or nearly full, delete any files that are no
longer needed and retry the RECOVER command.
;
;
SYS0598H: EXPLANATION: RECOVER can create up to 10,000 files named
FILEnnnn.REC (where "nnnn" is a number starting with 0000).
You attempted to exceed the number of files allowed.
ACTION: Delete or rename one or more existing FILEnnnn.REC
files and retry the RECOVER command.
;
;
SYS0599H: EXPLANATION: RECOVER was unable to read a list of extended
attributes.  The list was truncated at the last readable
attribute.

ACTION: No action is required.
;
;
SYS0600H: 
;
;
SYS0601H: 
;
;
SYS0602H: 
;
;
SYS0603H: EXPLANATION: RECOVER was unable to write information about bad
blocks to the disk because another process was accessing the disk.

ACTION: No action is required.  The information is now recovered.
;
;
SYS0604H: EXPLANATION: Duplicate files now exist on your disk.

ACTION: Delete the original file and rename the recovered file.
;
;
SYS0605H: EXPLANATION: Duplicate files now exist on your disk. This
can be caused if the read-only attribute of a file is set,
or if you have insufficient file access permissions.

ACTION: Check the attributes on the original file.  Also
check your own file access permissions.  If you have delete
permission, delete the original file and rename the recovered file.
;
;
SYS0606H: EXPLANATION: RECOVER detected an operating system error.

ACTION: Restart your system and retry the RECOVER command.
;
;
SYS0607H: EXPLANATION: You must specify the drive that you want the system
data transferred to.

ACTION: Retry the SYS command using a valid drive letter.
;
;
SYS0608H: EXPLANATION: The command assumes that the current drive is the
source drive.  The source and target drives cannot be the same.

ACTION: Specify another drive as the target drive.
;
;
SYS0609H: EXPLANATION: You tried to use SYS on a drive that is not
formatted for HPFS.

ACTION: Use this version of SYS only on HPFS formatted drives.
;
;
SYS0610H: EXPLANATION: The system files cannot be written to the target
disk.  This might be caused by one of the following:
o  There is no room on the disk.
o  The target disk is write-protected.
o  A file has a read-only attribute that is set.

ACTION: Do one of the following:
o  If the disk is full, delete any files that are no longer needed.
o  Determine if the disk is write-protected.  If so, remove
   the write-protection.
o  Disallow any read-only attributes on your files.

Then, if you have permission to write to the disk, retry the SYS
command.
;
;
SYS0611H: 
;
;
SYS0612H: EXPLANATION: The IFS= statement contains illegal characters.

ACTION: Edit the CONFIG.SYS file to correct the IFS= statement
and restart the system.
;
;
SYS0613H: EXPLANATION: The cache requires a minimum of 64KB to start.  This
minimum amount was not available.

ACTION: Reinstall a new version of HPFS (High Performance File System).
;
;
SYS0614H: 
;
;
SYS0615H: 
;
;
SYS0616H: 
;
;
SYS0617H: 
;
;
SYS0618H: 
;
;
SYS0619H: 
;
;
SYS0620H: 
;
;
SYS0621H: 
;
;
SYS0622H: 
;
;
SYS0623H: 
;
;
SYS0624H: 
;
;
SYS0625H: 
;
;
SYS0626H: EXPLANATION: An error was found on the HPFS volume in the
specified drive.  A possible cause for the error is that
the disk is not formatted correctly.

ACTION: Reformat the HPFS volume and try again.
;
;
SYS0627H: EXPLANATION: A HPFS drive returns this message if the system lost power
or was turned off before the Shutdown choice in the desktop was used.

ACTION: From the OS/2 command prompt, run CHKDSK with the /F parameter
on the specified drive.  (If you receive this message after your system
is started, you need only follow step 5.)

1. Insert the Installation diskette in drive A.
2. Press Ctrl+Alt+Del.
3. At the logo screen, press the Esc key to display the OS/2 command
   prompt.
4. Replace the Installation diskette with Diskette 1.
5. Type CHKDSK %1: /F at the command prompt, press the Enter key,
   and follow the instructions on the screen.
6. When CHKDSK finishes, remove Diskette 1.
7. Press Ctrl+Alt+Del to restart the system.

To prevent this message from appearing each time you start the
system, always use the Shutdown choice in the desktop pop-up menu
before turning off the computer.
;
;
SYS0628H: 
;
;
SYS0629H: EXPLANATION: The following parameters can be used for FORMAT:
drive:       Indicates the drive letter followed by a colon (such as
             E:), specifying which hard disk volume to format.
/V[:label]   Puts the volume label on your disk.
/FS:xxxx     xxxx indicates file system type (FAT or HPFS) to be used.

ACTION: Retry the FORMAT command using the correct parameters.
;
;
SYS0630H: EXPLANATION: When a volume is formatted for HPFS, the IFS= statement
in the CONFIG.SYS file is modified.  Your CONFIG.SYS file was not
modified because the drive or drives formatted for HPFS were not
included with the /AUTOCHECK: parameter in the IFS= statement.

ACTION: Make sure that the letter of all drives that are formatted for
HPFS are included with the /AUTOCHECK: parameter in the IFS= statement
of the CONFIG.SYS file.  For example, the following statement modifies
the CONFIG.SYS file for HPFS drives D and F:
   IFS=C:\OS2\HPFS.IFS /C:64 /AUTOCHECK:DF
;
;
SYS0631H: 
;
;
SYS0632H: 
;
;
SYS0633H: 
;
;
SYS0634H: 
;
;
SYS0635H: 
;
;
SYS0636H: EXPLANATION: You entered a volume label that does not match the
current label.

ACTION: Use the VOL command to determine the current volume
label on the hard disk.  Run FORMAT again and type the current
volume label for the disk volume when prompted.
;
;
SYS0637H: EXPLANATION: Too many FORMAT commands are running concurrently.

ACTION: Wait until one of your current formatting processes
has ended and retry the command.
;
;
SYS0638H: EXPLANATION: The DOS application is trying to access a function
that is not supported by the virtual device driver.

ACTION: Take the following steps:
1. Save your data.
2. End the application.
3. AT DOS prompt, type: EXIT  (this will end the virtual DOS
   machine session).
;
;
SYS0639H: EXPLANATION: KP.COM and other keyboard-lockup utility programs are
not supported in DOS mode in this version of OS/2.

ACTION: To set the keyboard and mouse lockup password, display the
desktop pop-up menu, select Lockup now, then type a password.
;
;
SYS0640H: 
;
;
SYS0641H: EXPLANATION: The target drive was formatted in "fast format" mode,
which does not erase all data areas.  CHKDSK /F:3 searches data
areas for "lost" files.  If a file existed on this drive before
the last format, CHKDSK may find it, and attempt to recover it.

ACTION: Use CHKDSK /F:2 to check this drive.  If you use /F:3,
be aware that files recovered to the FOUND directories may be
old files.  Also, if you format a drive using FORMAT /L, FORMAT
will completely erase all old files, and avoid this warning.
;
;
SYS0642H: 
;
;
SYS0643H: 
;
;
SYS0644H: 
;
;
SYS0645H: 
;
;
SYS0646H: 
;
;
SYS0647H: 
;
;
SYS0648H: 
;
;
SYS0649H: 
;
;
SYS0650H: 
;
;
SYS0651H: EXPLANATION: DOS support was specified in the CONFIG.SYS file
(PROTECTONLY was set to NO), but the virtual %1 device driver was
not specified.  This device driver must be specified for DOS support.

ACTION: Continue with start-up, add the DEVICE= statement for the
virtual %1 device driver to CONFIG.SYS, and restart the system.
;
;
SYS0652H: EXPLANATION: The drive letter you want to access is currently in use
and cannot be remapped or deregistered at this time.

ACTION: Change the current drive letter and retry the command.
;
;
SYS0653H: EXPLANATION: You used the mapping symbol (=) in the command, but did
not specify the two drive letters to map.

ACTION: Correct the syntax and retry the command.  For example:
[DOS letter = OS/2 drive].
;
;
SYS0654H: EXPLANATION: You used a sequence symbol (-) in the command, but did
not specify the first and last letters of the sequence.

ACTION: Correct the syntax and retry the command.  For example:
[DOS letter - DOS letter].
;
;
SYS0655H: EXPLANATION: You used a deregistration symbol (!) in the command,
but did not specify the following DOS drive letter to deregister.

ACTION: Correct the syntax and retry the command.
;
;
SYS0656H: EXPLANATION: The FSACCESS utility requires the installation of the
FSFILTER.SYS device driver.

ACTION: Edit the Virtual Machine (VM) Boot CONFIG.SYS file and add
as the first device driver statement: DEVICE=FSFILTER.SYS.  Close
the VM Boot session and restart the session.
;
;
SYS0657H: EXPLANATION: The FSACCESS command requires a drive letter.
You must specify the drive letter you want to register.

ACTION: Specify the letter of a drive and retry the command.
;
;
SYS0658H: 
;
;
SYS0659H: EXPLANATION: Additional disk space on the target disk is required to
complete this operation.

ACTION: To increase disk space, do one of the following:
o  Delete unnecessary files.
o  Move some files to another disk or diskette.
;
;
SYS0660H: 
;
;
SYS0661H: 
;
;
SYS0662H: 
;
;
SYS0663H: EXPLANATION: To load the EMM386 device driver in a DOS session, you
must install the OS/2 VEMM.SYS device driver.

ACTION: Make sure there is a DEVICE= statement in the OS/2 CONFIG.SYS
file that loads the VEMM.SYS device driver.  If the statement is not
found, reinstall OS/2 and select DOS Support as an installation option.
;
;
SYS0664H: EXPLANATION: To load the HIMEM device driver in a DOS session, you
must install the OS/2 VXMS.SYS device driver.

ACTION: Make sure there is a DEVICE= statement in the OS/2 CONFIG.SYS
file that loads the VXMS.SYS device driver.  If the statement is not
found, reinstall OS/2 and select DOS Support as an installation option.
;
;
SYS0665H: EXPLANATION: To load MOUSE.COM in a DOS session, the OS/2
VMOUSE.SYS device driver must be present.

ACTION: Make sure there is a DEVICE= statement in the OS/2 CONFIG.SYS
file that loads the VMOUSE.SYS device driver.  If the statement is not
found, reinstall OS/2 and select DOS Support as an installation option.
;
;
SYS0666H: EXPLANATION: The OS/2 EMM386.SYS device driver does not provide
services for any versions of OS/2 prior to OS/2 2.0.

ACTION: Replace EMM386.SYS with the DOS version of the EMS driver.
;
;
SYS0667H: EXPLANATION: OS/2 HIMEM.SYS device driver does not provide XMS
services in any version of OS/2 prior to OS/2 2.0 or later.

ACTION: Replace HIMEM.SYS with the DOS version of the XMS driver.
;
;
SYS0668H: EXPLANATION: OS/2 MOUSE.COM does not provide services in any version
of OS/2 prior to OS/2 2.0.

ACTION: Replace MOUSE.COM with the DOS version of the MOUSE device
support.
;
;
SYS0669H: EXPLANATION: There is no memory range available to allocate an EMS
page frame.  All memory ranges are allocated to option adapters.

ACTION: Use the "Include regions" property to reallocate a
memory range away from an option adapter.  This makes the memory
range available for the EMS operation.
;
;
SYS0670H: EXPLANATION: The disk or diskette specified by the VM boot path DOS
setting is not able to start in a VM Boot session.  One of the
following errors has been found:
o  The disk or diskette is not formatted for startup.
o  The startup program is trying to start invalid instructions.

ACTION: Be sure that the VM boot path DOS setting is set to a disk
or diskette drive that contains a startable DOS system.
;
;
SYS0671H: 
;
;
SYS0672H: 
;
;
SYS0673H: 
;
;
SYS0674H: 
;
;
SYS0675H: 
;
;
SYS0676H: 
;
;
SYS0677H: 
;
;
SYS0678H: 
;
;
SYS0679H: 
;
;
SYS0680H: 
;
;
SYS0681H: 
;
;
SYS0682H: 
;
;
SYS0683H: 
;
;
SYS0684H: 
;
;
SYS0685H: 
;
;
SYS0686H: 
;
;
SYS0687H: 
;
;
SYS0688H: 
;
;
SYS0689H: 
;
;
SYS0690H: 
;
;
SYS0691H: 
;
;
SYS0692H: 
;
;
SYS0693H: EXPLANATION: HPFS encountered a disk error while updating the
system's temporary and reserved allocation pool.  This might
have left the system in an inconsistent state.

ACTION: Backup critical files from the affected drive and run
CHKDSK /F on the drive as soon as possible.
;
;
SYS0694H: EXPLANATION: The HPFS encountered an error while reading
the file's FNODE. The file's FNODE may or may not be corrupted on the disk.
Possibly only an in-RAM copy of the file's FNODE may be corrupted. The problem
may have one of several causes,
 1. HPFS
 2. Errant hardware (I/O device) may be installed on the system
 3. Errant device driver may be installed on the system

ACTION: Run CHKDSK /F on the drive as a possible solution.
You should reboot your system as soon as possible.
;
;
SYS0695H: 
;
;
SYS0696H: 
;
;
SYS0697H: 
;
;
SYS0698H: 
;
;
SYS0699H: 
;
;
SYS0700H: EXPLANATION: The baud rate had the correct syntax, but the serial port
hardware does not support the baud rate you specified.

ACTION: Specify a different baud rate and retry the command.  To view
other asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS0701H: 
;
;
SYS0702H: 
;
;
SYS0703H: 
;
;
SYS0704H: 
;
;
SYS0705H: 
;
;
SYS0706H: 
;
;
SYS0707H: 
;
;
SYS0708H: 
;
;
SYS0709H: 
;
;
SYS0710H: 
;
;
SYS0711H: 
;
;
SYS0712H: 
;
;
SYS0713H: 
;
;
SYS0714H: 
;
;
SYS0715H: 
;
;
SYS0716H: 
;
;
SYS0717H: EXPLANATION: When ENHANCED=OFF is specified or when it is the current
setting, the parameters RXDMA= and TXDMA= are not supported.

ACTION: If you want to use RXDMA= or TXDMA=, specify ENHANCED=ON at
this time.  To view other asynchronous communications MODE command
parameters, type: HELP 1625 | more
;
;
SYS0718H: EXPLANATION: The parameters ENHANCED=, RXDMA=, and TXDMA= cannot be
specified because the serial port hardware does not support DMA.

ACTION: Delete the parameters and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS0719H: 
;
;
SYS0720H: EXPLANATION: The specified parameter is not supported on the serial
port.

ACTION: Do one of the following:
o  Delete the parameter and retry the command.
o  Specify a different port and retry the command.

To view other asynchronous communications MODE command parameters,
type: HELP 1625 | more
;
;
SYS0721H: EXPLANATION: The specified parameter is not supported on the serial
port.

ACTION: Do one of the following:
o  Delete the parameter and retry the command.
o  Specify a different port and retry the command.

To view other asynchronous communications MODE command parameters,
type: HELP 1625 | more
;
;
SYS0722H: EXPLANATION: The baud parameter must be specified.

ACTION: Specify a baud rate and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS0723H: EXPLANATION: One of the following has occurred:
o  The parameter was misspelled.
o  The parameter is not supported.
o  The specified positional parameter is in the wrong position.

ACTION: Correct the parameter specified and retry the command.  To
view other asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS0724H: EXPLANATION: The combination of DATABITS and STOPBITS you specified is
invalid.  If 5 databits were specified, 2 stopbits are not allowed.
If 1.5 stopbits were specified, only 5 databits are allowed.

ACTION: Correct the parameter and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS0725H: EXPLANATION: The value specified is not supported.

ACTION: Correct the value and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS0726H: EXPLANATION: A parameter was specified without an equal sign (=).

ACTION: Include an equal sign (=) in the specified parameter and
retry the command.  To view other asynchronous communications MODE
command parameters, type: HELP 1625 | more
;
;
SYS0727H: EXPLANATION: One of the following has occurred:
o  The parameter was misspelled.
o  The specified positional parameter is in the wrong position.

ACTION: Correct the parameter specified and retry the command.  To
view other asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS0728H: EXPLANATION: The value specified also might be in the wrong position.

ACTION: Correct the value or position of the specified parameter and
retry the command.  To view other asynchronous communications MODE
command parameters, type: HELP 1625 | more
;
;
SYS0729H: 
;
;
SYS0730H: EXPLANATION: A header in a monitor buffer has been changed.  The
change created a general protection fault (Trap D) condition.

ACTION: Contact the supplier of the application.
;
;
SYS0731H: EXPLANATION: An error occurred while the module was being replaced.  An
attempt was made to back out the changes but the attempt failed.

ACTION: Check the backup copy of the module.  It should contain a
valid copy of the module.  Use it to manually restore the file.
;
;
SYS0732H: EXPLANATION: OS/2 cannot operate the disk or diskette from which you
are starting OS/2.  This may indicate that:
1. An incompatibility exists between OS/2 and the hard-disk drive
   controller, or diskette drive controller, on your system.
2. A hard-disk drive controller or diskette drive might have an
   additional device (such as a tape backup) attached to it.
3. There might be an interrupt request (IRQ) level conflict between the
   hard-disk drive controller or diskette drive and other devices
   installed on your system.
4. The hard-disk partition on which you are installing OS/2 has been
   compressed with a DOS data compression program.
ACTION: Do one of the following and retry the operation:
1. Edit the CONFIG.SYS file on the hard disk or diskette from which
   you are starting OS/2.  Remove all BASEDEV=xxxxxxxx.ADD (where
   xxxxxxxx is the name of the device driver).  Add the following
   two statements, save the CONFIG.SYS file, and restart the system:
      BASEDEV=ibm1flpy.add
      BASEDEV=ibmint13.i13
2. Disconnect any additional devices, if possible.
3. Change the IRQ levels to eliminate any conflicts.
4. Use the data compression program to decompress the partition.
;
;
SYS0733H: 
;
;
SYS0734H: 
;
;
SYS0735H: 
;
;
SYS0736H: 
;
;
SYS0737H: 
;
;
SYS0738H: 
;
;
SYS0739H: 
;
;
SYS0740H: 
;
;
SYS0741H: 
;
;
SYS0742H: 
;
;
SYS0743H: 
;
;
SYS0744H: 
;
;
SYS0745H: 
;
;
SYS0746H: 
;
;
SYS0747H: 
;
;
SYS0748H: 
;
;
SYS0749H: 
;
;
SYS0750H: 
;
;
SYS0751H: 
;
;
SYS0752H: 
;
;
SYS0753H: 
;
;
SYS0754H: 
;
;
SYS0755H: 
;
;
SYS0756H: 
;
;
SYS0757H: 
;
;
SYS0758H: 
;
;
SYS0759H: 
;
;
SYS0760H: 
;
;
SYS0761H: 
;
;
SYS0762H: 
;
;
SYS0763H: 
;
;
SYS0764H: 
;
;
SYS0765H: 
;
;
SYS0766H: 
;
;
SYS0767H: 
;
;
SYS0768H: 
;
;
SYS0769H: 
;
;
SYS0770H: 
;
;
SYS0771H: 
;
;
SYS0772H: 
;
;
SYS0773H: 
;
;
SYS0774H: 
;
;
SYS0775H: 
;
;
SYS0776H: 
;
;
SYS0777H: 
;
;
SYS0778H: 
;
;
SYS0779H: 
;
;
SYS0780H: 
;
;
SYS0781H: 
;
;
SYS0782H: 
;
;
SYS0783H: 
;
;
SYS0784H: 
;
;
SYS0785H: 
;
;
SYS0786H: 
;
;
SYS0787H: 
;
;
SYS0788H: 
;
;
SYS0789H: 
;
;
SYS0790H: 
;
;
SYS0791H: 
;
;
SYS0792H: 
;
;
SYS0793H: 
;
;
SYS0794H: 
;
;
SYS0795H: 
;
;
SYS0796H: 
;
;
SYS0797H: 
;
;
SYS0798H: 
;
;
SYS0799H: 
;
;
SYS0800H: 
;
;
SYS0801H: 
;
;
SYS0802H: 
;
;
SYS0803H: 
;
;
SYS0804H: 
;
;
SYS0805H: 
;
;
SYS0806H: 
;
;
SYS0807H: 
;
;
SYS0808H: 
;
;
SYS0809H: 
;
;
SYS0810H: 
;
;
SYS0811H: 
;
;
SYS0812H: 
;
;
SYS0813H: 
;
;
SYS0814H: 
;
;
SYS0815H: 
;
;
SYS0816H: 
;
;
SYS0817H: 
;
;
SYS0818H: 
;
;
SYS0819H: 
;
;
SYS0820H: 
;
;
SYS0821H: 
;
;
SYS0822H: 
;
;
SYS0823H: 
;
;
SYS0824H: 
;
;
SYS0825H: 
;
;
SYS0826H: 
;
;
SYS0827H: 
;
;
SYS0828H: 
;
;
SYS0829H: 
;
;
SYS0830H: 
;
;
SYS0831H: 
;
;
SYS0832H: 
;
;
SYS0833H: 
;
;
SYS0834H: 
;
;
SYS0835H: 
;
;
SYS0836H: 
;
;
SYS0837H: 
;
;
SYS0838H: 
;
;
SYS0839H: 
;
;
SYS0840H: 
;
;
SYS0841H: 
;
;
SYS0842H: 
;
;
SYS0843H: 
;
;
SYS0844H: 
;
;
SYS0845H: 
;
;
SYS0846H: 
;
;
SYS0847H: 
;
;
SYS0848H: 
;
;
SYS0849H: 
;
;
SYS0850H: EXPLANATION: An error was detected when trying to replace the Master
Boot Record on the fixed disk.

ACTION: Record this message number along with the error code and
contact your service representative.
;
;
SYS0851H: 
;
;
SYS0852H: 
;
;
SYS0853H: 
;
;
SYS0854H: 
;
;
SYS0855H: 
;
;
SYS0856H: 
;
;
SYS0857H: 
;
;
SYS0858H: 
;
;
SYS0859H: 
;
;
SYS0860H: 
;
;
SYS0861H: 
;
;
SYS0862H: 
;
;
SYS0863H: 
;
;
SYS0864H: 
;
;
SYS0865H: 
;
;
SYS0866H: 
;
;
SYS0867H: 
;
;
SYS0868H: 
;
;
SYS0869H: 
;
;
SYS0870H: 
;
;
SYS0871H: 
;
;
SYS0872H: 
;
;
SYS0873H: 
;
;
SYS0874H: 
;
;
SYS0875H: 
;
;
SYS0876H: 
;
;
SYS0877H: 
;
;
SYS0878H: 
;
;
SYS0879H: 
;
;
SYS0880H: 
;
;
SYS0881H: 
;
;
SYS0882H: 
;
;
SYS0883H: 
;
;
SYS0884H: 
;
;
SYS0885H: 
;
;
SYS0886H: 
;
;
SYS0887H: 
;
;
SYS0888H: EXPLANATION: The file named in the command does not exist or was
entered incorrectly.

ACTION: Retry the command using the correct file name.
;
;
SYS0889H: EXPLANATION: The number of partitions found matching the requested
command is not 1.  The command may have missing or extra parameters,
or no partition exists which satisfy this command.

ACTION: Correct the parameters and retry the command.
;
;
SYS0890H: EXPLANATION: The FDISK message file MBS001.TXT contains an error.  It
is probably caused by a message not starting or ending with the caret
(^) character.

ACTION: Record this message number and contact your service
representative.
;
;
SYS0891H: EXPLANATION: The value specified is an invalid restrictor.

ACTION: Correct the value and retry the command.
;
;
SYS0892H: EXPLANATION: This command cannot be done to Boot Manager.

ACTION: Remove the BOOTMGR restrictor and retry the command.
;
;
SYS0893H: EXPLANATION: Only one Boot Manager partition is allowed.

ACTION: Delete the existing Boot Manager partition and retry the
command.
;
;
SYS0894H: EXPLANATION: A boot name cannot be given to this partition.
Either this is the Boot Manager partition or it does not reside
entirely within the first gigabyte of the hard file.

ACTION: Check the partition type and location.
;
;
SYS0895H: EXPLANATION: A boot name cannot be given to this partition.  Either
this is the Boot Manager partition or it does not reside entirely
within the first 1024 megabytes of the hard file.

ACTION: Remove the name option from the parameter /CREATE:name.
;
;
SYS0896H: EXPLANATION: Boot Manager must reside within area which can be
accessed by CBIOS, which is the first 1024 cylinders of the hard file.

ACTION: Correct the command to specify the free space within the
first 1024 cylinders.
;
;
SYS0897H: EXPLANATION: An error has occurred in a partition table entry on the
specified file.

ACTION: Record this message number and contact your service
representative.
;
;
SYS0898H: EXPLANATION: A boot name cannot be assigned to a volume without
Boot Manager support installed.

ACTION: Install Boot Manager or do not assign a name to this volume.
;
;
SYS0899H: 
;
;
SYS0900H: 
;
;
SYS0901H: 
;
;
SYS0902H: 
;
;
SYS0903H: 
;
;
SYS0904H: 
;
;
SYS0905H: 
;
;
SYS0906H: 
;
;
SYS0907H: 
;
;
SYS0908H: 
;
;
SYS0909H: 
;
;
SYS0910H: 
;
;
SYS0911H: 
;
;
SYS0912H: 
;
;
SYS0913H: 
;
;
SYS0914H: 
;
;
SYS0915H: 
;
;
SYS0916H: 
;
;
SYS0917H: 
;
;
SYS0918H: 
;
;
SYS0919H: 
;
;
SYS0920H: 
;
;
SYS0921H: 
;
;
SYS0922H: 
;
;
SYS0923H: 
;
;
SYS0924H: 
;
;
SYS0925H: 
;
;
SYS0926H: 
;
;
SYS0927H: 
;
;
SYS0928H: 
;
;
SYS0929H: 
;
;
SYS0930H: 
;
;
SYS0931H: 
;
;
SYS0932H: 
;
;
SYS0933H: 
;
;
SYS0934H: 
;
;
SYS0935H: 
;
;
SYS0936H: 
;
;
SYS0937H: 
;
;
SYS0938H: 
;
;
SYS0939H: 
;
;
SYS0940H: 
;
;
SYS0941H: 
;
;
SYS0942H: 
;
;
SYS0943H: 
;
;
SYS0944H: 
;
;
SYS0945H: 
;
;
SYS0946H: 
;
;
SYS0947H: 
;
;
SYS0948H: 
;
;
SYS0949H: 
;
;
SYS0950H: 
;
;
SYS0951H: 
;
;
SYS0952H: 
;
;
SYS0953H: 
;
;
SYS0954H: 
;
;
SYS0955H: 
;
;
SYS0956H: 
;
;
SYS0957H: 
;
;
SYS0958H: 
;
;
SYS0959H: 
;
;
SYS0960H: 
;
;
SYS0961H: 
;
;
SYS0962H: 
;
;
SYS0963H: 
;
;
SYS0964H: 
;
;
SYS0965H: 
;
;
SYS0966H: 
;
;
SYS0967H: 
;
;
SYS0968H: 
;
;
SYS0969H: 
;
;
SYS0970H: 
;
;
SYS0971H: 
;
;
SYS0972H: 
;
;
SYS0973H: 
;
;
SYS0974H: 
;
;
SYS0975H: 
;
;
SYS0976H: 
;
;
SYS0977H: 
;
;
SYS0978H: 
;
;
SYS0979H: 
;
;
SYS0980H: 
;
;
SYS0981H: 
;
;
SYS0982H: 
;
;
SYS0983H: 
;
;
SYS0984H: 
;
;
SYS0985H: 
;
;
SYS0986H: 
;
;
SYS0987H: 
;
;
SYS0988H: 
;
;
SYS0989H: 
;
;
SYS0990H: 
;
;
SYS0991H: 
;
;
SYS0992H: 
;
;
SYS0993H: 
;
;
SYS0994H: 
;
;
SYS0995H: 
;
;
SYS0996H: 
;
;
SYS0997H: 
;
;
SYS0998H: 
;
;
SYS0999H: 
;
;
SYS1000H: 
;
;
SYS1001H: EXPLANATION: A parameter was entered that is not recognized by
the command.

ACTION: Check the parameters and retry the command.
;
;
SYS1002H: EXPLANATION: The specified parameter is not recognized by the command.

ACTION: Check the parameter and retry the command.
;
;
SYS1003H: EXPLANATION: One of the following occurred:
o  An incorrect parameter was specified.
o  An incorrect separator was specified.
o  A required parameter is missing.
o  Too many parameters were entered.
o  The parameters were entered in the wrong order.

ACTION: Check the syntax of the command and retry the command.
;
;
SYS1004H: 
;
;
SYS1005H: 
;
;
SYS1006H: EXPLANATION: A file larger than 63KB cannot be sorted.

ACTION: No action can be taken.
;
;
SYS1007H: 
;
;
SYS1008H: 
;
;
SYS1009H: 
;
;
SYS1010H: EXPLANATION: The number of lines in a file cannot exceed
(file size + 768) / 4.

ACTION: Reduce the number of lines in the file or split
the file into smaller files.  Then retry the command.
;
;
SYS1011H: EXPLANATION: The system tried to rewrite extended attributes to a
readable cluster, but no readable clusters are available on the
volume specified.

ACTION: To free clusters, erase unneeded files and retry the command.
;
;
SYS1012H: 
;
;
SYS1013H: 
;
;
SYS1014H: 
;
;
SYS1015H: 
;
;
SYS1016H: 
;
;
SYS1017H: 
;
;
SYS1018H: 
;
;
SYS1019H: EXPLANATION: An incorrect drive letter was used.

ACTION: Retry the command using the correct drive letter.
;
;
SYS1020H: 
;
;
SYS1021H: 
;
;
SYS1022H: 
;
;
SYS1023H: 
;
;
SYS1024H: EXPLANATION: The root directory is full and cannot store the files
requested.

ACTION: Remove some of the files from the root directory of the disk.
Then retry the command.
;
;
SYS1025H: 
;
;
SYS1026H: 
;
;
SYS1027H: 
;
;
SYS1028H: 
;
;
SYS1029H: 
;
;
SYS1030H: 
;
;
SYS1031H: 
;
;
SYS1032H: 
;
;
SYS1033H: 
;
;
SYS1034H: EXPLANATION: The system cannot find CMD.EXE in the specified path.

ACTION: Ensure that CMD.EXE is in the path specified.  If required,
change the PROTSHELL= statement in your CONFIG.SYS file and restart
the system.
;
;
SYS1035H: EXPLANATION: An incorrect path or file name was entered with the
RENAME, TYPE, MKDIR, MOVE, or RMDIR command.

ACTION: Retry the command using a correct path or file name.
;
;
SYS1036H: EXPLANATION: An incorrect date format was entered.

ACTION: Retry the command using a correct date format.  For
example, mm/dd/yy, mm-dd-yy, mm.dd.yy or yy.dd.mm.
;
;
SYS1037H: 
;
;
SYS1038H: 
;
;
SYS1039H: EXPLANATION: The label specified in the GOTO command does not
exist in the batch file.

ACTION: Remove the GOTO command or edit the batch file and
put the desired label in the correct location.
;
;
SYS1040H: 
;
;
SYS1041H: EXPLANATION: The name specified should be one of the following:
o  The name of a batch file whose file extension is .CMD or .BAT.
o  The name of an executable program whose file extension
   is .EXE or .COM.
o  The name of an OS/2 or DOS external command.
o  The name of an OS/2 internal command.

For the first 3 cases (if a path for the command was not specified at
the command prompt), the file must reside in the current directory or
in one of the directories specified by the PATH environment variable.

ACTION: Retry the command using a correct name or path.
;
;
SYS1042H: 
;
;
SYS1043H: 
;
;
SYS1044H: EXPLANATION: An incorrect time format was entered.

ACTION: Enter the time using the correct time format.
;
;
SYS1045H: EXPLANATION: The program requires a different version of the operating
system.

ACTION: Use OS/2 Warp and restart the system or
install the proper version of the application program on the
system.  Then retry the command.
;
;
SYS1046H: 
;
;
SYS1047H: 
;
;
SYS1048H: 
;
;
SYS1049H: 
;
;
SYS1050H: 
;
;
SYS1051H: 
;
;
SYS1052H: 
;
;
SYS1053H: 
;
;
SYS1054H: 
;
;
SYS1055H: 
;
;
SYS1056H: EXPLANATION: The operating system cannot accept the SET, PATH, DPATH,
or PROMPT command issued because it cannot expand the area in which
the environment information is kept.

ACTION: Remove an environment string and retry the command.
;
;
SYS1057H: EXPLANATION: The DOS application could not be started because the file
or path name is not valid in a DOS session.  The file name and all the
path names must be limited to the DOS 8.3 file-name format (FAT).

ACTION: Rename the file or path using DOS file naming conventions
or move the file to a path whose name is valid in a DOS session.
;
;
SYS1058H: EXPLANATION: An area of your hard disk is defective.

ACTION: Retrieve the data in the HOTFIX.DAT file.  Backup and reformat
the specified drive.
;
;
SYS1059H: EXPLANATION: The operating system encountered an unknown
error while attempting to start up the program.

ACTION: Contact the supplier of the program.
;
;
SYS1060H: 
;
;
SYS1061H: EXPLANATION: One of the following errors occurred:
o  The file you tried to write to is read-only.
o  The directory is full.

ACTION: Do one of the following:
o  If the file is read-only, you can use the ATTRIB
   command to change the read-only attribute.
o  If the directory is full, no action can be taken
   unless files are deleted.
;
;
SYS1062H: 
;
;
SYS1063H: 
;
;
SYS1064H: 
;
;
SYS1065H: EXPLANATION: The line exceeds 128 characters or the command is greater
than 80 characters in length.

ACTION: Shorten the length of the input line.
;
;
SYS1066H: EXPLANATION: When the destination file and one of the source files
share the same name, the shared name must be the same as the first
source file listed for the COPY command.

ACTION: There is no action available.
;
;
SYS1067H: 
;
;
SYS1068H: 
;
;
SYS1069H: EXPLANATION: A Uniform Naming Convention (UNC) network path name
cannot be used with this command.

ACTION: Use a different command that supports UNC path names or
correct the path name and retry the command.
;
;
SYS1070H: 
;
;
SYS1071H: EXPLANATION: The handle specified for redirection was in use by another
process or there were too many open handles to complete the redirection.

ACTION: Wait for the other processes to end and retry the command.
;
;
SYS1072H: 
;
;
SYS1073H: 
;
;
SYS1074H: 
;
;
SYS1075H: 
;
;
SYS1076H: 
;
;
SYS1077H: 
;
;
SYS1078H: EXPLANATION: The target file has the same name as the source file.

ACTION: Ensure that the file-name specifications for the target
and source files are not the same.
;
;
SYS1079H: EXPLANATION: The command is missing required keywords.

ACTION: Retry the command correctly.
;
;
SYS1080H: 
;
;
SYS1081H: EXPLANATION: A permanent copy of CMD.EXE was running and one
of the following situations occurred:
o  Another program tried to cancel this copy of CMD.EXE.
o  CMD.EXE was started using a redirected input file
   and the end of the file was reached.

ACTION: No action can be taken.
;
;
SYS1082H: 
;
;
SYS1083H: EXPLANATION: The target file name specified with the RENAME or MOVE
command already exists, is in use, or cannot be created, or the source
file cannot be found.

ACTION: Check the target and source file names used or wait until the
file is no longer in use and retry the command.
;
;
SYS1084H: 
;
;
SYS1085H: 
;
;
SYS1086H: EXPLANATION: A single command name or argument was entered that is too
long to be processed.

ACTION: Revise and retry the command.
;
;
SYS1087H: 
;
;
SYS1088H: 
;
;
SYS1089H: 
;
;
SYS1090H: 
;
;
SYS1091H: 
;
;
SYS1092H: EXPLANATION: Too many handles prevent handle duplication during a
pipe operation.

ACTION: Wait for the other processes to end and retry the command.
;
;
SYS1093H: 
;
;
SYS1094H: 
;
;
SYS1095H: 
;
;
SYS1096H: 
;
;
SYS1097H: 
;
;
SYS1098H: 
;
;
SYS1099H: 
;
;
SYS1100H: 
;
;
SYS1101H: 
;
;
SYS1102H: EXPLANATION: The JOIN command was unable to create the specified
directory.

ACTION: Ensure that the directory name is correct and retry the
command.
;
;
SYS1103H: EXPLANATION: The directory specified does not exist on your system.

ACTION: Create the directory and retry the command.
;
;
SYS1104H: 
;
;
SYS1105H: 
;
;
SYS1106H: 
;
;
SYS1107H: EXPLANATION: The command specified is either a file that can be run
in a DOS session only or is an invalid executable file.
ACTION: If the file is a DOS file, switch to a DOS session and then
retry the command.  If the file is an invalid executable file, correct
the problem and then retry the command in an OS/2 session.
;
;
SYS1108H: 
;
;
SYS1109H: 
;
;
SYS1110H: 
;
;
SYS1111H: 
;
;
SYS1112H: 
;
;
SYS1113H: 
;
;
SYS1114H: 
;
;
SYS1115H: 
;
;
SYS1116H: 
;
;
SYS1117H: 
;
;
SYS1118H: EXPLANATION: There is no more help available for this message.

ACTION: No further action can be supplied for this error.
;
;
SYS1119H: 
;
;
SYS1120H: 
;
;
SYS1121H: 
;
;
SYS1122H: 
;
;
SYS1123H: 
;
;
SYS1124H: 
;
;
SYS1125H: 
;
;
SYS1126H: 
;
;
SYS1127H: 
;
;
SYS1128H: 
;
;
SYS1129H: 
;
;
SYS1130H: 
;
;
SYS1131H: 
;
;
SYS1132H: 
;
;
SYS1133H: 
;
;
SYS1134H: 
;
;
SYS1135H: 
;
;
SYS1136H: 
;
;
SYS1137H: EXPLANATION: A source path must be specified with this command.

ACTION: Retry the command using the following source path syntax:
[d:] [path] filename[.ext]
;
;
SYS1138H: 
;
;
SYS1139H: 
;
;
SYS1140H: 
;
;
SYS1141H: EXPLANATION: The source path specified does not contain the files
requested.

ACTION: Retry the command using the correct source path or the current
file specification.
;
;
SYS1142H: 
;
;
SYS1143H: 
;
;
SYS1144H: 
;
;
SYS1145H: EXPLANATION: The specified file is currently being used by another
process or the specified target file is read-only.

ACTION: If the file is being used by another process, wait for the
process to release the file.  If the target file is read-only, retry
the command with the /R parameter.
;
;
SYS1146H: 
;
;
SYS1147H: 
;
;
SYS1148H: 
;
;
SYS1149H: 
;
;
SYS1150H: 
;
;
SYS1151H: 
;
;
SYS1152H: 
;
;
SYS1153H: 
;
;
SYS1154H: 
;
;
SYS1155H: 
;
;
SYS1156H: 
;
;
SYS1157H: 
;
;
SYS1158H: 
;
;
SYS1159H: 
;
;
SYS1160H: 
;
;
SYS1161H: 
;
;
SYS1162H: 
;
;
SYS1163H: 
;
;
SYS1164H: 
;
;
SYS1165H: 
;
;
SYS1166H: 
;
;
SYS1167H: 
;
;
SYS1168H: 
;
;
SYS1169H: 
;
;
SYS1170H: 
;
;
SYS1171H: EXPLANATION: The path specified is incorrect.

ACTION: Retry the command using the correct path.
;
;
SYS1172H: 
;
;
SYS1173H: 
;
;
SYS1174H: EXPLANATION: The device requested is being used by another
application.

ACTION: Complete one of the following actions.
o  Select END to terminate the DOS session.  This will terminate the
   DOS application and the DOS session.
o  Select RETRY to suspend the application.  When the hardware becomes
   available, the application will be restarted automatically.
o  Select IGNORE to continue.  This is often the desired action when
   starting a WIN-OS/2 session because multimedia drivers are loaded
   even if the application does not require Audio/Video hardware.
;
;
SYS1175H: EXPLANATION: The Win32s application has used a function
not supported by the Win32s virtual device driver.
Possible cause: an unsupported version of Win32s.
Continuing the application may produce errors.

ACTION: Record this message number and contact your
OS/2 Technical Support team.
;
;
SYS1176H: 
;
;
SYS1177H: 
;
;
SYS1178H: 
;
;
SYS1179H: 
;
;
SYS1180H: 
;
;
SYS1181H: 
;
;
SYS1182H: 
;
;
SYS1183H: 
;
;
SYS1184H: EXPLANATION: The source and target files cannot have the same name.

ACTION: Retry the command using a different target file name.
;
;
SYS1185H: EXPLANATION: An unexpected error occurred during XCOPY processing.

ACTION: Restart the system before trying XCOPY.
;
;
SYS1186H: EXPLANATION: One of the following conditions exists:
o  A Cyclic Redundancy Check error.
o  The file is in use by another process.
o  Too many files are open.
o  The diskette is not a DOS diskette.

ACTION: Correct the problem or wait until the file is not in use,
then retry the command.
;
;
SYS1187H: EXPLANATION: One of the following conditions exists:
o  The disk is full.
o  The file or drive is in use or locked by another process.
o  Too many files are open.
o  The target file is a read-only file.
o  A disk error occurred.

ACTION: Correct the problem or wait until the file is not in use,
then retry the command.
;
;
SYS1188H: 
;
;
SYS1189H: EXPLANATION: The file requested cannot be closed because a disk error
occurred.

ACTION: Retry XCOPY later.
;
;
SYS1190H: 
;
;
SYS1191H: 
;
;
SYS1192H: EXPLANATION: One of the following conditions exists:
o  The disk is in use or locked by another process.
o  A disk error occurred.

ACTION: Do one of the following:
o  Retry XCOPY later.
o  If the error is with a diskette, make sure it is properly inserted.
o  Format the diskette for the operating system.
o  Check that the diskette is not damaged.
;
;
SYS1193H: EXPLANATION: OS/2 does not support the 80386 processor with the 80287
math coprocessor.

ACTION: To realize the full performance of the math coprocessor, you
should upgrade to a 80387 math coprocessor.
;
;
SYS1194H: EXPLANATION: The 80387 coprocessor has been disabled because OS/2 has
found a 80386-level B1 stepping machine with a 80387 math coprocessor
present.

ACTION: To realize the full performance from your installed math
coprocessor running with OS/2, your system may require an IBM
no-cost modification.  Please contact your point-of-sale personnel
to have them resolve the possible 80386/80387 conflict.
;
;
SYS1195H: EXPLANATION: The statement specified is not a recognized configuration
command.

ACTION: Do one of the following and restart your system:
1. Edit the CONFIG.SYS file to correct or remove the incorrect
   statement.
2. Install the Serviceablilty Kernel to support the statement.
;
;
SYS1196H: EXPLANATION: The specified parameter is not a correct keyword or
numeric value for the configuration command.

ACTION: Edit the CONFIG.SYS file to correct or remove the incorrect
statement.  Restart the system.
;
;
SYS1197H: EXPLANATION: The specified statement requires a parameter.

ACTION: Edit the CONFIG.SYS file to correct or remove the incorrect
statement.  Restart the system.
;
;
SYS1198H: EXPLANATION: The specified DOS device driver has executed an INT 21
function during initialization.  This is not compatible with the
operating system.

ACTION: Edit the CONFIG.SYS file to remove the incorrect statement.
Then restart the system.
;
;
SYS1199H: 
;
;
SYS1200H: EXPLANATION: DOS initialization failed. The specified
error code was returned by a DOS function while the system
tried to create the DOS environment.

ACTION: Refer to the OS/2 Toolkit to determine the
nature of the error.  Correct the problem and restart the system.
;
;
SYS1201H: EXPLANATION: None of the device drivers contained in the specified
file are installed successfully.

ACTION: Edit the CONFIG.SYS file to correct or remove the incorrect
statement.  Then restart the system.
;
;
SYS1202H: 
;
;
SYS1203H: EXPLANATION: I/O privilege level 2 is required.

ACTION: Add to your CONFIG.SYS file the statement:  IOPL=YES
Then restart the system.
;
;
SYS1204H: EXPLANATION: I/O privilege level 2 is required.

ACTION: Add to your CONFIG.SYS file the statement: IOPL=YES
Then restart the system.
;
;
SYS1205H: 
;
;
SYS1206H: EXPLANATION: There is not enough available memory to load the
specified program or device driver.

ACTION: Perform one of the following actions and restart the system:
o  Edit the CONFIG.SYS file to remove the specified statement.
o  Edit the CONFIG.SYS file to increase the amount of available
   memory by:
   -  Reducing the value in the BUFFERS statement
   -  Removing unnecessary DEVICE= and/or RUN statements
   -  Reducing the value in the DISKCACHE statement
   -  Reducing the value in the TRACEBUF statement
   -  Reducing the size of the virtual disk specified in
      the DEVICE=VDISK statement
o  If the failing command is the SHELL command or a DEVICE= statement
   for a DOS device driver, edit the CONFIG.SYS file to increase the
   value in the RMSIZE statement.
o  If the failing command is the PROTSHELL, RUN, or DEVICE= statement
   used for both DOS and OS/2, edit the CONFIG.SYS file to decrease the
   value in the RMSIZE statement or add the PROTECTONLY=YES statement.
o  Install another memory option in your system unit.
;
;
SYS1207H: 
;
;
SYS1208H: 
;
;
SYS1209H: 
;
;
SYS1210H: EXPLANATION: The version of the operating system in your system is not
the correct level.

ACTION: Use the VER command to determine the level of OS/2 you are
using.  You should be using OS/2 2.0 or later.
;
;
SYS1211H: 
;
;
SYS1212H: 
;
;
SYS1213H: 
;
;
SYS1214H: 
;
;
SYS1215H: 
;
;
SYS1216H: 
;
;
SYS1217H: EXPLANATION: A file must be decompressed with the same version of OS/2
that was used to compress it.

ACTION: Correct the problem and retry the command.
;
;
SYS1218H: 
;
;
SYS1219H: 
;
;
SYS1220H: 
;
;
SYS1221H: 
;
;
SYS1222H: 
;
;
SYS1223H: EXPLANATION: One of the following errors occurred:
o  The group code is incorrect.
o  The group code table is damaged or set up incorrectly.

ACTION: Do one of the following:
o  Correct the group code and retry the command.
o  Create a new group code table and retry the command.
;
;
SYS1224H: EXPLANATION: The valid group code range is 0 to 255.

ACTION: Correct the value and retry the command.
;
;
SYS1225H: 
;
;
SYS1226H: 
;
;
SYS1227H: 
;
;
SYS1228H: 
;
;
SYS1229H: 
;
;
SYS1230H: 
;
;
SYS1231H: EXPLANATION: An incorrect drive specification was entered or a hard
disk was specified.  A hard disk is not an acceptable drive for this
program.

ACTION: Retry the command using a correct drive specification.
;
;
SYS1232H: 
;
;
SYS1233H: 
;
;
SYS1234H: EXPLANATION: The diskette and drive type are incompatible with each
other or the diskette is unusable.

ACTION: Make sure the diskette drives are the same type or that the
correct type of diskette is in the drive.  For example, high-capacity
diskettes in a high-capacity drive can only be copied to high-capacity
diskettes in a high-capacity drive.
;
;
SYS1235H: EXPLANATION: The diskette or drive type are incompatible with each
other or the diskette is unusable.

ACTION: Make sure the diskette drives are the same type or that the
correct type of diskette is in the drive.  For example, high-capacity
diskettes in a high-capacity drive can only be copied to high-capacity
diskettes in a high-capacity drive.
;
;
SYS1236H: 
;
;
SYS1237H: 
;
;
SYS1238H: 
;
;
SYS1239H: 
;
;
SYS1240H: EXPLANATION: The wrong type of diskette was inserted in the drive.

ACTION: Make sure the diskette and diskette drive are the same type
and retry the command.
;
;
SYS1241H: 
;
;
SYS1242H: 
;
;
SYS1243H: 
;
;
SYS1244H: 
;
;
SYS1245H: 
;
;
SYS1246H: 
;
;
SYS1247H: 
;
;
SYS1248H: EXPLANATION: A subdirectory or file with the same name already exists
in the target directory.

ACTION: Choose a new name and retry the command.
;
;
SYS1249H: 
;
;
SYS1250H: 
;
;
SYS1251H: EXPLANATION: The DISKCOPY command cannot be used on diskettes that
have been formatted for eXtended Density Format (XDF).

ACTION: Use the XDFCOPY command to copy this type of diskette.  For
more information on this command, refer to the Command Reference.
;
;
SYS1252H: 
;
;
SYS1253H: 
;
;
SYS1254H: 
;
;
SYS1255H: 
;
;
SYS1256H: 
;
;
SYS1257H: 
;
;
SYS1258H: 
;
;
SYS1259H: 
;
;
SYS1260H: 
;
;
SYS1261H: EXPLANATION: The system detected a read error.  The function will
attempt to proceed normally.

ACTION: No action is required by the user.
;
;
SYS1262H: EXPLANATION: The system detected a write error.  The function will
attempt to proceed normally.

ACTION: Try reformatting the target diskette and using the DISKCOPY
command, or use another formatted diskette.
;
;
SYS1263H: EXPLANATION: The system detected a read error.  The function will
attempt to proceed normally.

ACTION: No action is required by the user.  %2 sectors per track,
%3 side(s).
;
;
SYS1264H: 
;
;
SYS1265H: 
;
;
SYS1266H: 
;
;
SYS1267H: EXPLANATION: The system detected an error while attempting to
determine the type of optical disc that is present in the optical
disc drive.

ACTION: Reinsert the optical disc and retry the operation.
;
;
SYS1268H: EXPLANATION: The system is unable to format optical read-only memory
(O-ROM) discs in any optical drive and only able to format programmable
read-only memory (P-ROM) discs in drives that support this function.

ACTION: Retry the FORMAT command using another optical disc or another
optical disc drive.
;
;
SYS1269H: EXPLANATION: The system found an error while attempting to copy ITB
information on a programmable read-only memory (P-ROM) disc.

ACTION: Retry the FORMAT command using another P-ROM disc or another
optical disc drive.
;
;
SYS1270H: 
;
;
SYS1271H: 
;
;
SYS1272H: 
;
;
SYS1273H: 
;
;
SYS1274H: EXPLANATION: The OS/2 FAT file system can only support volumes up
to 2,048MB.

ACTION: Re-partition your hard disk and retry the command.
;
;
SYS1275H: EXPLANATION: The /S parameter has been removed from the FORMAT command
in this release of the operating system.

ACTION: Run system installation using the Installation diskette.
;
;
SYS1276H: EXPLANATION: The correct parameters are:
drive       Specifies the drive to be formatted.
/ONCE       Specifies 1 disk, diskette, or disc is to be formatted.
            Inhibits the first and last prompt from a diskette format.
/4          Formats 360KB diskettes in a 1.2 MB drive.
/T:tracks   Formats a diskette to the specified number of tracks and
            sectors.
/N:sectors  Formats a diskette to the specified number of sectors.
/F:xxxx     Specifies size to which the diskette is to be formatted.
/FS:xxxxx   Replaces xxxxx with the file-system type that you are
            using for the hard disk.
/L          Specifies that the long format procedure is to be used.
/V[:label]  Specifies the volume label used to identify your disk.

ACTION: Retry the command using the correct parameters.
;
;
SYS1277H: 
;
;
SYS1278H: 
;
;
SYS1279H: EXPLANATION: A disk error occurred while the target disk was being
formatted.

ACTION: Review the error messages displayed and follow the corrective
action.
;
;
SYS1280H: EXPLANATION: The area on the disk where the system information is
stored is unusable.

ACTION: Retry the FORMAT command using another diskette or re-partition
the hard disk.
;
;
SYS1281H: EXPLANATION: Track 0 is defective or the diskette and drive type are
incompatible.

ACTION: Make sure the diskette and drive type are compatible and take
appropriate action.  If track 0 is defective, discard the diskette or
re-partition the hard disk.
;
;
SYS1282H: 
;
;
SYS1283H: 
;
;
SYS1284H: 
;
;
SYS1285H: 
;
;
SYS1286H: 
;
;
SYS1287H: 
;
;
SYS1288H: 
;
;
SYS1289H: EXPLANATION: This version of the operating system will no longer
permit leading blanks in volume labels.

ACTION: No further action is required.
;
;
SYS1290H: 
;
;
SYS1291H: EXPLANATION: FORMAT was unable to read the files required for a
system transfer.

ACTION: Try the FORMAT command from another OS/2 diskette or recopy
the system files to your default disk and retry the command.
;
;
SYS1292H: 
;
;
SYS1293H: 
;
;
SYS1294H: 
;
;
SYS1295H: EXPLANATION: HPFS (High Performance File System) data cannot be written
to a volume greater than 64 Gigabytes.  The volume you specified is too large.

ACTION: Resize your volume using the LVM utility and then reformat the volume.
Alternatively, format the original volume with JFS (Journaled File System).
;
;
SYS1296H: EXPLANATION: The area on the disk where the system information is
stored is unusable.

ACTION: Retry the FORMAT command using another diskette or re-partition
the hard disk.
;
;
SYS1297H: EXPLANATION: A parameter was given that is only used for formatting
diskettes and cannot be used for formatting a hard disk.

ACTION: Retry the FORMAT command using the correct parameter.
;
;
SYS1298H: EXPLANATION: FORMAT parameters were entered that cannot be used
together.

ACTION: Retry the FORMAT command using the correct parameters.
;
;
SYS1299H: 
;
;
SYS1300H: 
;
;
SYS1301H: 
;
;
SYS1302H: 
;
;
SYS1303H: EXPLANATION: The system cannot support the device as
configured.  A virtual disk (VDISK.SYS) is already formatted.

ACTION: If you have replaced the default Disk device driver, check
its DEVICE= statement in the CONFIG.SYS file and restart the system.
;
;
SYS1304H: 
;
;
SYS1305H: 
;
;
SYS1306H: 
;
;
SYS1307H: 
;
;
SYS1308H: 
;
;
SYS1309H: 
;
;
SYS1310H: EXPLANATION: The FORMAT command was entered without a drive letter.

ACTION: Retry the FORMAT command and include the letter of the drive
to be formatted.
;
;
SYS1311H: EXPLANATION: The system transfer option (/S) was used with the FORMAT
command, but the system files cannot be found on the default drive.

ACTION: Retry the FORMAT command using another disk as the default
drive.
;
;
SYS1312H: 
;
;
SYS1313H: EXPLANATION: The volume table of the hard disk does not have an
OS/2 volume or the volume is unusable.

ACTION: Re-partition the hard disk using the LVM command.
;
;
SYS1314H: 
;
;
SYS1315H: 
;
;
SYS1316H: EXPLANATION: The format of the extended attributes on this disk or
diskette is incorrect for this version of OS/2.

ACTION: Install the correct version of OS/2 and retry the command.
;
;
SYS1317H: 
;
;
SYS1318H: 
;
;
SYS1319H: EXPLANATION: An incorrect volume label for the hard disk to be
formatted was used.

ACTION: Use the VOL command to determine the current volume label on
the hard disk.  Use this label when prompted by the FORMAT command.
;
;
SYS1320H: EXPLANATION: FORMAT reads the file names in FORMATS.TBL and copies
these files to the target disk.  FORMATS.TBL is expected to be in the
root directory of the default drive.  If FORMAT is unable to read
FORMATS.TBL, it will only transfer OS2LDR and OS2KRNL.

ACTION: Copy the files listed in FORMATS.TBL to the target disk to
create an OS/2 startup disk.
;
;
SYS1321H: 
;
;
SYS1322H: 
;
;
SYS1323H: 
;
;
SYS1324H: EXPLANATION: The extended attribute for this file or directory is
already in use by another file or directory on this disk.

ACTION: Do one of the following:
o  Make copies of the specified files (use the COPY command).
o  Delete the original files (use the ERASE command).
o  Check the files that you copied for validity and edit them, if
   necessary.
;
;
SYS1325H: EXPLANATION: The diskette drive determined that the diskette is too
large for the drive.

ACTION: Do one of the following:
o  Insert the diskette in the drive that has the same capacity as the
   diskette.
o  Check to see if the diskette is the correct size.
o  Retry the command using the /F parameter.  For more information
   about formatting, refer to the online Command Reference.
;
;
SYS1326H: 
;
;
SYS1327H: 
;
;
SYS1328H: 
;
;
SYS1329H: 
;
;
SYS1330H: EXPLANATION: One or more of the parameters entered for the CHKDSK
command are incorrect.  The correct parameters are:
/F and /V   For FAT (File Allocation Table) formatted disk.
/F and /C   For HPFS (High Performance File System) formatted disk.

ACTION: Specify the correct parameter and retry the command.
;
;
SYS1331H: 
;
;
SYS1332H: 
;
;
SYS1333H: EXPLANATION: The drive specified is incorrect, the diskette is not in
the OS/2 format, or the diskette is unusable.

ACTION: Retry the CHKDSK command using a correct drive specification.
If this error occurs again, format a diskette with the operating
system, copy the files from the old diskette to the new one, and retry
the command.
;
;
SYS1334H: 
;
;
SYS1335H: EXPLANATION: The file had a different size than the number of clusters
associated with the file.  The file size was adjusted.

ACTION: No action is required.
;
;
SYS1336H: EXPLANATION: The table indicated is incorrect.  This can be caused by
a power failure while a file is open.

ACTION: If this message appears for both Tables 1 and 2, format the
disk.  If FORMAT fails, the disk is unusable.
;
;
SYS1337H: EXPLANATION: A disk error was encountered while attempting to update
FAT on the specified drive.  The table number will be 1 or 2,
depending on which of the two copies of FAT could not be written.

ACTION: If this message appears for both Tables 1 and 2, format the
disk.  If FORMAT fails, the disk is unusable.
;
;
SYS1338H: 
;
;
SYS1339H: 
;
;
SYS1340H: EXPLANATION: The file %1 contains an incorrect pointer
to a data block.

ACTION: Use the /F option to truncate the file at the last valid data
block.  No corrective action occurs if CHKDSK is used without the /F
option.
;
;
SYS1341H: EXPLANATION: CHKDSK attempted to read the current directory.  It found
an unrecoverable error on the disk.

ACTION: No action can be taken.  The disk is unusable.
;
;
SYS1342H: EXPLANATION: The file has a different size than the number of clusters
associated with the file.

ACTION: To correct the file size, type: CHKDSK /F.
;
;
SYS1343H: EXPLANATION: The File Allocation Table (FAT) points to the same data
block for the specified files, which are assigned to the same space on
the disk or diskette.

ACTION: Do one of the following:
o  Make copies of the specified files (use the COPY command).
o  Delete the original files (use the ERASE command).
o  Review the files for validity and edit as necessary.
;
;
SYS1344H: 
;
;
SYS1345H: 
;
;
SYS1346H: 
;
;
SYS1347H: EXPLANATION: A subdirectory was found that does not properly contain
a .  or ..  entry.  This usually happens when the operating system is
not given a chance to update the disk properly.  During the updating
process, the system may have shut down or you may have reloaded the
system before the operating system finished the update.

ACTION: Use the RECOVER command to try to recover files on the damaged
disk.
;
;
SYS1348H: 
;
;
SYS1349H: EXPLANATION: Incorrect information was detected in
subdirectory %1.

ACTION: CHKDSK attempts to correct the error if you have used the /F
option.  For more information about the error, run CHKDSK with the /V
option.
;
;
SYS1350H: EXPLANATION: A subdirectory was found that did not properly contain
a . entry.  This usually happens when the operating system is not
given a chance to update the disk properly.  During the updating
process, the system may have shut down or you may have reloaded the
system before the operating system finished the update.

ACTION: Use the RECOVER command to try to recover files on the damaged
disk.
;
;
SYS1351H: EXPLANATION: A subdirectory was found that did not properly contain
a .. entry.  This usually happens when the operating system is not
given a chance to update the disk properly.  During the updating
process, the system may have shut down or you may have reloaded the
system before the operating system finished the update.

ACTION: Use the RECOVER command to try to recover files on the damaged
disk.
;
;
SYS1352H: EXPLANATION: The path listed can end with one or two dots.  One dot
indicates the current directory is in error.  Two dots indicate the
parent directory is in error.  If you did not use the /F option, no
corrective action is taken.

ACTION: Type: CHKDSK /F.  CHKDSK will attempt to correct the error.
;
;
SYS1353H: 
;
;
SYS1354H: EXPLANATION: The system could not format the diskette into a capacity
other than the default one. For example, it can not format a 1.44MB
diskette into a 720KB one. The is because the floppy device driver does
support it.

ACTION: Remove the /F option and reformat it.

;
;
SYS1355H: 
;
;
SYS1356H: 
;
;
SYS1357H: 
;
;
SYS1358H: 
;
;
SYS1359H: EXPLANATION: Disk space is marked as allocated and is not associated
with any file.  Using CHKDSK without the /F option does not free up
any space.

ACTION: Use the /F option to free up and make available space that is
currently marked as allocated but not associated to any file.
;
;
SYS1360H: EXPLANATION: CHKDSK was instructed to create files from the lost
data blocks it has found, but the root directory is full and the
lost chains could not be recovered into files.

ACTION: Copy some of the recovered files to another disk for
examination.  Delete the recovered files from the disk you are
checking.  Retry the CHKDSK command to recover the remainder
of the lost data.
;
;
SYS1361H: 
;
;
SYS1362H: 
;
;
SYS1363H: 
;
;
SYS1364H: 
;
;
SYS1365H: 
;
;
SYS1366H: 
;
;
SYS1367H: 
;
;
SYS1368H: 
;
;
SYS1369H: 
;
;
SYS1370H: 
;
;
SYS1371H: 
;
;
SYS1372H: 
;
;
SYS1373H: 
;
;
SYS1374H: EXPLANATION: Multiple errors occurred while writing to a disk drive.
The disk may be unusable.

ACTION: Reformat the disk.
;
;
SYS1375H: 
;
;
SYS1376H: EXPLANATION: A disk error was encountered while CHKDSK (with the /F
option) was attempting to update the directory entry.

ACTION: Directory entry %1 may not be usable.  No action is
required.
;
;
SYS1377H: EXPLANATION: A disk error was encountered while CHKDSK (with the /F
option) was attempting to update the root directory.

ACTION: Check the following:
o  The diskette is inserted correctly.
o  The diskette is not write protected.
o  The diskette is formatted.
;
;
SYS1378H: 
;
;
SYS1379H: 
;
;
SYS1380H: EXPLANATION: A disk error was encountered while CHKDSK was attempting
to read subdirectory %1.

ACTION: Directory %1 may not be usable.  No action is required.
;
;
SYS1381H: 
;
;
SYS1382H: 
;
;
SYS1383H: EXPLANATION: There is an error on the diskette.  This diskette cannot
be used as a memory dump diskette until it is reformatted.

ACTION: Insert another formatted diskette in drive A and continue.
;
;
SYS1384H: 
;
;
SYS1385H: 
;
;
SYS1386H: EXPLANATION: The utility has detected a return code error.  Some data
may be written on the diskette.

ACTION: Restart the program using another diskette.
;
;
SYS1387H: EXPLANATION: The diskette drive specification is either missing,
incorrect, or not a drive that is configured for the system.

ACTION: Retry the command using a correct diskette drive specification.
;
;
SYS1388H: 
;
;
SYS1389H: 
;
;
SYS1390H: 
;
;
SYS1391H: 
;
;
SYS1392H: EXPLANATION: The system could not write the CREATEDD information to
the diskette.

ACTION: Restart the program using another diskette.
;
;
SYS1393H: 
;
;
SYS1394H: 
;
;
SYS1395H: 
;
;
SYS1396H: 
;
;
SYS1397H: EXPLANATION: The CONFIG.SYS file does not contain a TRACE= or
TRACEBUF= statement.

ACTION: Edit your CONFIG.SYS file.  Enter the necessary information
for system trace, restart the system, and retry the command.
;
;
SYS1398H: 
;
;
SYS1399H: EXPLANATION: The TRACE utility's ON/OFF parameter is missing,
incorrect, or is not in the correct position.

ACTION: Check the command keyword and retry the command using
either ON or OFF.
;
;
SYS1400H: 
;
;
SYS1401H: EXPLANATION: The TRACE utility detected that all major event codes
and corresponding minor codes are incorrect.

ACTION: Correct the major event code and syntax of the command and
retry the command.
;
;
SYS1402H: 
;
;
SYS1403H: 
;
;
SYS1404H: EXPLANATION: The TRACE utility was unable to interpret the command.

ACTION: Correct the error and retry the command.
;
;
SYS1405H: EXPLANATION: The trace definition file (.TDF) exceeds the maximum
size of 65535 bytes.

ACTION: A smaller .TDF file must be used with the TRACE utility.
;
;
SYS1406H: 
;
;
SYS1407H: EXPLANATION: The .TDF file is an incorrect level or contains a syntax
error.

ACTION: Correct the syntax error or replace the .TDF file.
;
;
SYS1408H: EXPLANATION: The utility failed to locate the specified file for one
of the following reasons:
o  The DLL does not exist.
o  The DLL does not contain its corresponding .TDF file.
o  The DLL was not loaded.

ACTION: Do one of the following:
o  Ensure that the proper DLL file and corresponding .TDF file are
   located in the same directory.
o  Load the DLL using DosLoadModule.
;
;
SYS1409H: EXPLANATION: One or more opcodes in the .TDF and DLL files do not
match at the trace point.

ACTION: Ensure that the opcodes match.
;
;
SYS1410H: EXPLANATION: TRACE was unable to convert one or more of the
segment numbers into selectors.

ACTION: Correct the segment number.
;
;
SYS1411H: 
;
;
SYS1412H: 
;
;
SYS1413H: EXPLANATION: There is an error on the diskette.  This diskette
cannot be used as a memory dump diskette until it is reformatted.

ACTION: Insert another formatted diskette in drive A and continue.
;
;
SYS1414H: 
;
;
SYS1415H: 
;
;
SYS1416H: 
;
;
SYS1417H: EXPLANATION: The resources for the application (for example, bitmaps
and text strings) could not be found.

ACTION: The resources of the application should reside in a dynamic
link library (DLL).  Do one of the following:
o  Copy this file to the C:\OS2\DLL directory and retry the command.
o  Contact the supplier of this application.
;
;
SYS1418H: 
;
;
SYS1419H: 
;
;
SYS1420H: 
;
;
SYS1421H: 
;
;
SYS1422H: 
;
;
SYS1423H: 
;
;
SYS1424H: 
;
;
SYS1425H: 
;
;
SYS1426H: 
;
;
SYS1427H: 
;
;
SYS1428H: 
;
;
SYS1429H: 
;
;
SYS1430H: 
;
;
SYS1431H: 
;
;
SYS1432H: 
;
;
SYS1433H: EXPLANATION: An incorrect input device name was entered.

ACTION: Retry the command using a correct input device name.
;
;
SYS1434H: EXPLANATION: An incorrect device name was entered.

ACTION: Retry the command using a correct output device name.
;
;
SYS1435H: 
;
;
SYS1436H: 
;
;
SYS1437H: 
;
;
SYS1438H: 
;
;
SYS1439H: 
;
;
SYS1440H: 
;
;
SYS1441H: 
;
;
SYS1442H: 
;
;
SYS1443H: 
;
;
SYS1444H: 
;
;
SYS1445H: 
;
;
SYS1446H: 
;
;
SYS1447H: 
;
;
SYS1448H: 
;
;
SYS1449H: 
;
;
SYS1450H: 
;
;
SYS1451H: 
;
;
SYS1452H: 
;
;
SYS1453H: 
;
;
SYS1454H: EXPLANATION: Supported languages are:
AR     (Arabic)             LA (Latin America)
BE     (Belgium)            NO (Norway)
BR     (Brazil)             NL (Netherlands)
CF     (Canada Fr.)         PL (Poland)
CS 243 (Czechoslovakia)     PO (Portugal)
CS 245 (Czech - Slovak)     SP (Spain)
DK     (Denmark)            SV (Sweden)
SU     (Finland)            SF (Switzerland, Fr.)
FR     (France)             SG (Switzerland, Ger.)
GR     (Germany)            TR (Turkey)
HE     (Hebrew)             TW (Republic of China)
HU     (Hungary)            UK (United Kingdom)
IS     (Iceland)            US (United States)
IT     (Italy)              YU (Yugoslavia)

ACTION: Enter the correct keyboard code and retry the command.
;
;
SYS1455H: 
;
;
SYS1456H: EXPLANATION: An unexpected error occurred when the system attempted to
copy the operating system files.

ACTION: Retry the installation using the FORMAT option.
;
;
SYS1457H: EXPLANATION: There is an insufficient amount of memory available to
transfer the operating system files.

ACTION: Wait for another process to end and retry the command.
;
;
SYS1458H: EXPLANATION: The operating system files do not exist on the
default drive.

ACTION: Retry the command using the default drive that contains
the operating system files.
;
;
SYS1459H: 
;
;
SYS1460H: 
;
;
SYS1461H: EXPLANATION: An incorrect target drive was entered, no drive was
specified, or the disk was not formatted.

ACTION: Retry the command using a correct target drive or format the
target disk.
;
;
SYS1462H: 
;
;
SYS1463H: 
;
;
SYS1464H: 
;
;
SYS1465H: EXPLANATION: The DEVICE=VDISK statement in the CONFIG.SYS file
contains incorrect parameters.

ACTION: Correct the DEVICE=VDISK statement in the CONFIG.SYS file
and restart the system.
;
;
SYS1466H: EXPLANATION: VDISK requires more memory than the system has available.

ACTION: Do one of the following and then restart the system:
o  Decrease the amount of memory requested in any of the DEVICE=VDISK
   statements in the CONFIG.SYS file.
o  Edit the CONFIG.SYS file to reduce the value specified in the
   BUFFERS=, TRACEBUF=, DISKCACHE=, or THREADS= statement.
o  Install another memory option in your system unit.
;
;
SYS1467H: 
;
;
SYS1468H: 
;
;
SYS1469H: 
;
;
SYS1470H: EXPLANATION: The drive must be a single letter followed by a colon.
The drive letter must be the name of a disk on your system.

ACTION: Check the SWAPPATH= statement in the CONFIG.SYS file.
Then restart the system.
;
;
SYS1471H: EXPLANATION: The path specified is incorrect.  It must be the name of
a subdirectory that exists on the specified disk.

ACTION: To use a specific path for the swap file, correct the
SWAPPATH= statement in the CONFIG.SYS file and restart the system.
;
;
SYS1472H: EXPLANATION: The hard disk or diskette may be full (swapping requires
a minimum of 512KB free space) or the diskette is write-protected.

ACTION: Do one of the following and then restart the system:
o  Make additional space available on the hard disk or diskette.
o  Insert a formatted diskette that is not write-protected.
o  Change the SWAPPATH= statement in CONFIG.SYS to specify a
   different drive.
;
;
SYS1473H: 
;
;
SYS1474H: EXPLANATION: There is not enough system or disk memory available.

ACTION: Try one of the following and then restart the system:
o  Edit the CONFIG.SYS file to reduce the value specified in the
   BUFFERS=, TRACEBUF=, DISKCACHE=, THREADS=, or RMSIZE= statement or
   reduce the size allocated for a virtual disk in a DEVICE=VDISK.SYS
   statement.
o  Install another memory option in your system unit.
o  Use the ERASE command to delete unwanted files on the swap disk or
   use the COPY command to copy them to a different disk.
;
;
SYS1475H: EXPLANATION: This is a hidden system file and must reside in the root directory
of the drive from which the operating system is started, or the OS2BOOT file
might be missing.
ACTION: Exit the installation program to a command prompt.  Use the installation
diskette or CD-ROM to restart your computer.
;
;
SYS1476H: EXPLANATION: The path specified is incorrect.  It must be the name of
a subdirectory that exists on the specified disk.

ACTION: To use a specific path for the swap file, correct the
SWAPPATH= statement in the CONFIG.SYS file and restart the system.
;
;
SYS1477H: EXPLANATION: The system requires additional virtual memory, but
cannot expand the size of the swap file to satisfy this request.

ACTION: Reduce the virtual memory requirement by closing applications
or increase the amount of available space on the volume by deleting
unwanted files.  If the SWAPPER.DAT file is full (message reoccurs),
you may need to change the default location of your swap file.  Refer
to the SWAPPATH command in the online Command Reference for additional
information.
;
;
SYS1478H: 
;
;
SYS1479H: 
;
;
SYS1480H: 
;
;
SYS1481H: 
;
;
SYS1482H: 
;
;
SYS1483H: 
;
;
SYS1484H: 
;
;
SYS1485H: 
;
;
SYS1486H: 
;
;
SYS1487H: 
;
;
SYS1488H: 
;
;
SYS1489H: 
;
;
SYS1490H: EXPLANATION: The file name is incorrect or does not exist.

ACTION: Check the file name and retry the command.
;
;
SYS1491H: 
;
;
SYS1492H: 
;
;
SYS1493H: 
;
;
SYS1494H: 
;
;
SYS1495H: 
;
;
SYS1496H: 
;
;
SYS1497H: 
;
;
SYS1498H: EXPLANATION: The VIEW command does not exist in the current directory
or path specified or the Command Reference might not be installed.

ACTION: Add the subdirectory in which VIEW exists to the path
environment variable or install the Command Reference.
;
;
SYS1499H: 
;
;
SYS1500H: 
;
;
SYS1501H: 
;
;
SYS1502H: EXPLANATION: A portion of the swap file is mapped to a bad sector on
the hard disk.  The system cannot read the specific segment in this
area of the swap file.

ACTION: Depending on the location of the swap file (SWAPPER.DAT),
do one of the following:

If the swap file is located on the C: volume (the default location
for the swap file):
  1. Restart the system using an OS/2 or DOS startup diskette.
  2. Backup to diskette non-OS/2 system files located on the C:
     volume.
  3. Reinstall OS/2, then select the option to format the C: volume.
  4. Restore the files you backed up in Step 2.

If the swap file is located on a volume other than C:
  1. Restart the system using an OS/2 or DOS startup diskette.
  2. Edit the CONFIG.SYS file and change the SWAPPATH statement so that
     the swap file is located on the C: volume.  (For example,
     SWAPPATH=C:\OS2\SYSTEM 512)
  3. Restart OS/2 from the hard disk (the usual way).
  4. If required, perform an error recovery.  You might need to
     reformat the volume that contained the bad sector.
OPTIONAL:
  5. Backup to diskette all files on the volume containing the bad
     sector.
  6. Reformat that volume.
  7. Restore the files you backed up in Step 5.

If the above procedure fails, then:
  1. Use the Hardware Reference Diskette and select the format option.
  2. Perform a low-level format of the entire hard disk.
  3. Reinstall OS/2.

If this procedure fails, then:
  1. Replace the hard disk.
  2. Install OS/2.
  3. Restore all files you backed up.
;
;
SYS1503H: 
;
;
SYS1504H: 
;
;
SYS1505H: EXPLANATION: There are not enough drive letters available to install
a virtual disk.

ACTION: Determine if drive letters can be made available by modifying
the disk volumes.  Use LVM or delete DEVICE=VDISK statements in
the CONFIG.SYS file.
;
;
SYS1506H: 
;
;
SYS1507H: 
;
;
SYS1508H: 
;
;
SYS1509H: EXPLANATION: The operating system detected an error when starting
the program.  The usual cause of this type of error is:
o  The program cannot be found.
o  There is not enough memory available to start the program.
o  The file system program specified in the /FS parameter of the
   FORMAT command cannot be found.
o  The final installation diskette must be replaced with the OS/2
   Diskette 1.

ACTION: Do one of the following and retry the command:
o  Check that the program name in the current path is correct.
o  Reduce the number of running programs.
o  Check that the file system name is correct.
o  Remove the final installation diskette and insert OS/2 Diskette 1
   in drive A.
;
;
SYS1510H: 
;
;
SYS1511H: EXPLANATION: A function needed by the program is not available or is
in use.

ACTION: Wait awhile and retry the command.
;
;
SYS1512H: EXPLANATION: The specified file system does not work with the disk or
diskette being used.

ACTION: Do one of the following and retry the command:
o  Specify a different file system name.
o  Use a different disk or diskette.
;
;
SYS1513H: 
;
;
SYS1514H: 
;
;
SYS1515H: 
;
;
SYS1516H: 
;
;
SYS1517H: 
;
;
SYS1518H: 
;
;
SYS1519H: EXPLANATION: There is not enough available memory to load the
specified system program or device driver.

ACTION: Perform one of the following actions and restart the system:
o  Edit the CONFIG.SYS file to increase the amount of available
   memory by:
   -  Reducing the value on the BUFFERS statement.
   -  Removing unnecessary DEVICE and/or RUN statements.
   -  Reducing the value on the DISKCACHE statement.
   -  Reducing the value on the TRACEBUF statement.
   -  Reducing the size of the virtual disk specified on the
      DEVICE=VDISK statement.
o  If the failing program is COMMAND.COM, edit the CONFIG.SYS file to
   increase the value on the RMSIZE statement.
o  If the failing program is not COMMAND.COM, edit the CONFIG.SYS file
   to decrease the value on the RMSIZE statement or add the statement
   PROTECTONLY=YES.
o  Install another memory option in your system unit.
;
;
SYS1520H: EXPLANATION: All drive letters are being used by the hard disks.

ACTION: Delete any logical volumes that are not needed.
;
;
SYS1521H: EXPLANATION: The specified statement in the CONFIG.SYS file has more
parameters than are expected.

ACTION: Edit the CONFIG.SYS file to correct or remove the incorrect
statement and restart the system.
;
;
SYS1522H: 
;
;
SYS1523H: EXPLANATION: The required symbol has been left out or is misplaced.

ACTION: Edit the CONFIG.SYS file to correct or remove the incorrect
statement and restart the system.
;
;
SYS1524H: EXPLANATION: The file that you are trying to copy is being used by
another process.  The COPY command will copy the file.  If the other
process writes to the file during the COPY command, the target file
might be corrupted.  The COPY command is permitted to continue only
for DOS compatibility reasons.

ACTION: End the process using the source file and use the COPY command
to recopy the file.
;
;
SYS1525H: EXPLANATION: An option was selected that does not exist.  /B, /C, /T,
and /D are the only options the system accepts.

ACTION: Retry the command using a correct option.
;
;
SYS1526H: EXPLANATION: The parameters selected cannot appear together or no
parameter was specified.  The correct syntax is:
  PRINT /C [/D:device]
  PRINT /T [/D:device]
  PRINT [/D:device] [/B] pathname...

ACTION: Enter the parameters correctly and retry the command.
;
;
SYS1527H: 
;
;
SYS1528H: 
;
;
SYS1529H: EXPLANATION: Correct printer device names are PRN, LPT1, LPT2, and LPT3.

ACTION: Retry the PRINT command using a correct printer device name.
;
;
SYS1530H: 
;
;
SYS1531H: EXPLANATION: A /C or /T option was requested but the spooler is not
running.

ACTION: Retry the command without the /C or /T option.
;
;
SYS1532H: EXPLANATION: The /C or /T parameter can only be used in OS/2 sessions.

ACTION: Switch to an OS/2 session and retry the command.
;
;
SYS1533H: EXPLANATION: The file named in the command does not exist
in the current directory or search path specified, or the
file name was entered incorrectly.

ACTION: Retry the command using the correct file name.
;
;
SYS1534H: 
;
;
SYS1535H: 
;
;
SYS1536H: 
;
;
SYS1537H: 
;
;
SYS1538H: 
;
;
SYS1539H: 
;
;
SYS1540H: 
;
;
SYS1541H: 
;
;
SYS1542H: 
;
;
SYS1543H: 
;
;
SYS1544H: 
;
;
SYS1545H: 
;
;
SYS1546H: 
;
;
SYS1547H: 
;
;
SYS1548H: 
;
;
SYS1549H: 
;
;
SYS1550H: 
;
;
SYS1551H: 
;
;
SYS1552H: 
;
;
SYS1553H: 
;
;
SYS1554H: 
;
;
SYS1555H: 
;
;
SYS1556H: 
;
;
SYS1557H: 
;
;
SYS1558H: 
;
;
SYS1559H: 
;
;
SYS1560H: 
;
;
SYS1561H: 
;
;
SYS1562H: 
;
;
SYS1563H: 
;
;
SYS1564H: 
;
;
SYS1565H: 
;
;
SYS1566H: 
;
;
SYS1567H: 
;
;
SYS1568H: 
;
;
SYS1569H: 
;
;
SYS1570H: 
;
;
SYS1571H: 
;
;
SYS1572H: 
;
;
SYS1573H: 
;
;
SYS1574H: 
;
;
SYS1575H: EXPLANATION: The PATCH command can be used as follows:

To patch a file interactively:
   PATCH filename.ext
where "filename.ext" identifies the file to be patched

To patch a file automatically:
   PATCH /A filename.ext
where "filename.ext" identifies a patch instruction file

ACTION: Check the PATCH parameters and retry the command.
;
;
SYS1576H: EXPLANATION: A VER or CHA command was specified without the necessary
fields.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1577H: 
;
;
SYS1578H: 
;
;
SYS1579H: 
;
;
SYS1580H: 
;
;
SYS1581H: 
;
;
SYS1582H: 
;
;
SYS1583H: 
;
;
SYS1584H: 
;
;
SYS1585H: 
;
;
SYS1586H: 
;
;
SYS1587H: 
;
;
SYS1588H: EXPLANATION: The requested offset is greater than the size of the file.

ACTION: Make sure you entered the correct offset.
;
;
SYS1589H: EXPLANATION: PATCH could not allocate enough storage to save all the
patch information.

ACTION: Split the patch request into two or more PATCH sessions.
;
;
SYS1590H: EXPLANATION: PATCH could not find instructions for patching a
file in the patch instruction file.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1591H: EXPLANATION: A VER or CHA command was found in the patch instruction
file without a previous FILE command specifying the file to patch.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1592H: EXPLANATION: An incorrect offset was found in the patch instruction
file.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1593H: EXPLANATION: A correct hexadecimal string consists of up to 32
hexadecimal digits with optional imbedded hyphens.  There must be
an even number of hexadecimal digits.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1594H: EXPLANATION: A verify offset in the patch instruction file was too
close to the end or past the end of the file being patched.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1595H: EXPLANATION: The file being patched is already patched or is not the
right file.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1596H: 
;
;
SYS1597H: EXPLANATION: A change offset in the patch instruction file was past
the end of the file being patched.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1598H: EXPLANATION: An unknown command or a comment without a preceding
semicolon (;) was found in the patch instruction file.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1599H: EXPLANATION: The file to be appended cannot be opened for reading.

ACTION: Make sure the file exists and the file name is spelled
correctly.
;
;
SYS1600H: EXPLANATION: No CHA commands were found in the patch instruction file
for the file to be patched.

ACTION: Check the patch instruction file for errors or contact the
supplier of the patch instruction file.
;
;
SYS1601H: EXPLANATION: The MODE command accepts the parameters that follow.

To set parallel printer modes:
   MODE LPTn chars,lines,P
   MODE PRN chars,lines,P

To set video modes:
   MODE CONn display,rows

To set asynchronous modes for DOS sessions:
   MODE COMn:baud,parity,databits,stopbits

To set asynchronous modes for OS/2 sessions:
   MODE COMn:baud,parity,databits,stopbits,
        TO,XON,IDSR,ODSR,OCTS,DTR,RTS,BUFFER

To set diskette verification:
   MODE DSKT VER=ON or VER=OFF

ACTION: Check the MODE parameters and retry the command.  For more
information about MODE, refer to the online Command Reference.
;
;
SYS1602H: 
;
;
SYS1603H: 
;
;
SYS1604H: 
;
;
SYS1605H: 
;
;
SYS1606H: 
;
;
SYS1607H: 
;
;
SYS1608H: 
;
;
SYS1609H: 
;
;
SYS1610H: 
;
;
SYS1611H: 
;
;
SYS1612H: 
;
;
SYS1613H: EXPLANATION: Valid values are:  PRN or LPTn (where n = 1, 2, or 3)

ACTION: Correct the value and retry the command.
;
;
SYS1614H: EXPLANATION: Valid values for chars are:  80 or 132.

ACTION: Correct the value and retry the command.
;
;
SYS1615H: EXPLANATION: Valid values for lines are:  6 or 8.

ACTION: Correct the value and retry the command.
;
;
SYS1616H: EXPLANATION: Valid values for COMn are:  1, 2, 3, or 4

ACTION: Correct the value and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS1617H: EXPLANATION: Valid values for baud are:
110, 150, 300, 600, 1200, 1800, 2400, 3600, 4800, 7200, 9600,
14400, 19200, 38400, or 57600

Note: Rates higher than 57600 are only valid on certain systems.

ACTION: Correct the value and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS1618H: 
;
;
SYS1619H: EXPLANATION: You are operating in the DOS environment, but the
parameter specified is for an OS/2 session.  The following MODE
parameters can be used in OS/2 sessions only:
   TO=
  XON=
 IDSR=
 ODSR=
 OCTS=
  DTR=
  RTS=

ACTION: Specify the correct DOS parameter or switch to an OS/2
session and retry the command.
;
;
SYS1620H: EXPLANATION: MODE detected a COM port that is not installed.

ACTION: Specify an installed COM port and retry the command.
;
;
SYS1621H: 
;
;
SYS1622H: EXPLANATION: Valid values for rows are:
25, 43, or 50   For DOS and OS/2 sessions.
>1              For OS/2 windowed sessions.

ACTION: Correct the value and retry the command.
;
;
SYS1623H: EXPLANATION: Valid values for display are:
40, 80, 132, BW40, BW80, BW132, CO40, CO80, C132, or MONO

ACTION: Correct the value and retry the command.
;
;
SYS1624H: EXPLANATION: When you specify a rows parameter for the MODE command,
you must also specify a display parameter.  Valid values for display
are:  40, 80, 132, BW40, BW80, BW132, CO40, CO80, C132, or MONO

ACTION: Specify a display and rows parameter and retry the command.
;
;
SYS1625H: EXPLANATION: Valid values for the asynchronous communications MODE
parameters are:
   COMn    -  1-4
   baud    -  110, 150, 300, 600, 1200, 1800, 2400, 3600,
              4800, 7200, 9600, 14400, 19200, 38400, 57600
              (Higher rates are valid only on certain systems)
   parity   - N (none), O (odd), E (even), M (1), S (0)
   databits - 5, 6, 7, 8
   stopbits - 1, 1.5 (only if databits is 5), 2
   P        - Specifies a timeout of about 30 seconds
   TO       - ON, OFF
   XON      - ON, OFF
   IDSR     - ON, OFF
   ODSR     - ON, OFF
   OCTS     - ON, OFF
   DTR      - ON, OFF, HS
   RTS      - ON, OFF, HS, TOG
   BUFFER   - ON, OFF, AUTO

ACTION: Correct the value and retry the command.  To view the correct
format for entering  the MODE command and its parameters, type:
HELP 1601 | more
;
;
SYS1626H: 
;
;
SYS1627H: EXPLANATION: Valid values for the diskette verification parameter are:
DSKT VER=ON  or  DSKT VER=OFF

ACTION: Correct the value and retry the command.
;
;
SYS1628H: 
;
;
SYS1629H: EXPLANATION: The display or rows parameter is incorrect for the
type of video device specified.  Valid values are:
display - MONO              (for EGA, VGA, or XGA)
          132, BW132, C132  (for XGA)
          80, BW80, CO80    (for XGA, VGA, EGA, CGA, or MPA)
          40, BW40, CO40    (for XGA, VGA, EGA, or CGA)
                            (not valid in a VIO window)
rows    - 25  (for XGA, VGA, EGA, CGA, or MPA)
          43  (for XGA, VGA, or EGA)
          50  (for XGA or VGA)

ACTION: Correct the value and retry the command.
;
;
SYS1630H: EXPLANATION: Valid values for databits are:  5, 6, 7, or 8

ACTION: Correct the value and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS1631H: EXPLANATION: Valid values for stopbits are:  1, 1.5, or 2
Note: 1.5 is valid only if databits is set to 5.

ACTION: Correct the value and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS1632H: EXPLANATION: Valid values for parity are:
N (none), O (odd), E (even), M (1), or S (0)

ACTION: Correct the value and retry the command.  To view other
asynchronous communications MODE command parameters, type:
HELP 1625 | more
;
;
SYS1633H: EXPLANATION: The MODE parameter is not recognized.

ACTION: Correct the value and retry the command.  To view the correct
format for entering the MODE command and its parameters, type:
HELP 1601 | more
;
;
SYS1634H: 
;
;
SYS1635H: 
;
;
SYS1636H: 
;
;
SYS1637H: 
;
;
SYS1638H: 
;
;
SYS1639H: 
;
;
SYS1640H: 
;
;
SYS1641H: 
;
;
SYS1642H: EXPLANATION: A disk cannot be restored onto itself.

ACTION: Retry the command using the correct source
and target drive letters.
;
;
SYS1643H: EXPLANATION: More than 11 parameters or less than 2 parameters
were entered.

ACTION: Retry the command using the correct number of parameters.
;
;
SYS1644H: 
;
;
SYS1645H: EXPLANATION: All of the backup diskettes were searched and no
files were found to match the path and file specification.

ACTION: Insert the correct diskette and retry the command.
;
;
SYS1646H: 
;
;
SYS1647H: 
;
;
SYS1648H: 
;
;
SYS1649H: 
;
;
SYS1650H: 
;
;
SYS1651H: EXPLANATION: The diskettes used in a restore must be inserted in
the same order in which they were backed up.

ACTION: Retry the RESTORE command inserting the diskettes in the
correct order.
;
;
SYS1652H: 
;
;
SYS1653H: 
;
;
SYS1654H: 
;
;
SYS1655H: 
;
;
SYS1656H: 
;
;
SYS1657H: 
;
;
SYS1658H: 
;
;
SYS1659H: 
;
;
SYS1660H: 
;
;
SYS1661H: 
;
;
SYS1662H: 
;
;
SYS1663H: 
;
;
SYS1664H: EXPLANATION: The /L parameter was specified but there is
not enough room to create the log file.

ACTION: Press Ctrl+Break to end the BACKUP log file procedure or
press Enter to continue without adding more entries to the log
file.  Delete unwanted files from the disk and retry the command.
;
;
SYS1665H: EXPLANATION: No drive letter was entered for the BACKUP command.

ACTION: Retry the command specifying a correct drive letter.
;
;
SYS1666H: 
;
;
SYS1667H: EXPLANATION: A source drive must be specified for the BACKUP command.

ACTION: Retry the command specifying a source drive.
;
;
SYS1668H: EXPLANATION: A target drive must be specified for the BACKUP command.

ACTION: Retry the command specifying a target drive.
;
;
SYS1669H: 
;
;
SYS1670H: 
;
;
SYS1671H: EXPLANATION: A disk cannot be backed up onto itself.

ACTION: Retry the command using the correct source and target drive
letters.
;
;
SYS1672H: EXPLANATION: Either the system cannot find the FORMAT.COM
file or there is not enough memory in the system.

ACTION: Insert a formatted diskette and backup will continue.
;
;
SYS1673H: 
;
;
SYS1674H: 
;
;
SYS1675H: EXPLANATION: A non-existent drive specification was entered for the
command or one of its parameters.

ACTION: Retry the command using a correct drive specifier.
;
;
SYS1676H: EXPLANATION: The FORMAT utility is not in the current directory or is
not accessible through the path specified.

ACTION: Copy the FORMAT utility to a location that can be found through
the PATH specified.
;
;
SYS1677H: EXPLANATION: One of the following errors occurred:
o  The path specified is incorrect.
o  The log file is read-only.
o  The log file is being used by another process.

ACTION: Choose the appropriate action and retry the command:
o  Specify the correct path.
o  Use the ATTRIB command to remove the read-only attribute of the file.
o  Wait until the log file is no longer in use.
o  Use a different file name for the log file.
;
;
SYS1678H: EXPLANATION: The /F parameter cannot be used to format a hard disk.

ACTION: Retry the command without the /F parameter or specify a
diskette drive.
;
;
SYS1679H: 
;
;
SYS1680H: 
;
;
SYS1681H: 
;
;
SYS1682H: 
;
;
SYS1683H: 
;
;
SYS1684H: 
;
;
SYS1685H: 
;
;
SYS1686H: 
;
;
SYS1687H: 
;
;
SYS1688H: EXPLANATION: The file is being used by another process.

ACTION: Retry the command later and use the /M parameter.
;
;
SYS1689H: 
;
;
SYS1690H: EXPLANATION: The system cannot create files on the target disk.

ACTION: If you are using a diskette drive, replace the diskette.
If not, back up files on a different drive.
;
;
SYS1691H: 
;
;
SYS1692H: 
;
;
SYS1693H: EXPLANATION: One of the following errors occurred:
1. The directory cannot be created because it already exists.
2. The directory path cannot be found.
3. The root directory is full.
4. A file with that name already exists.
5. The directory name contains unacceptable characters or is an
   OS/2 reserved file name.

ACTION: Do one of the following:
1. Ensure that a directory by that name exists in the current directory.
2. Ensure that a directory by that name exists in the current directory.
3. Use the CHKDSK command to see if the directory is full.
4. Use another name for the directory.
5. Use the correct characters.
;
;
SYS1694H: EXPLANATION: The path specified is greater than 63 characters.

ACTION: Specify a path name with up to 63 characters.
;
;
SYS1695H: 
;
;
SYS1696H: 
;
;
SYS1697H: 
;
;
SYS1698H: 
;
;
SYS1699H: 
;
;
SYS1700H: 
;
;
SYS1701H: EXPLANATION: The /S option cannot be used when copying to a
subdirectory belonging to a source directory.

ACTION: Delete the /S option or copy the files to a directory outside
of the source directory.
;
;
SYS1702H: EXPLANATION: One or more of the specified parameters are not
valid, a valid parameter was entered more than once, or a
parameter was not specified.

The allowed parameters are:

  /DOS     Prepares your system to start DOS from drive C.
  /OS2     Prepares your system to start the OS/2 operating
           system from drive C.
  /NOBOOT  Disables the automatic system restart after
           preparing the system for the new operating system.
  /QUERY   Queries the system to determine which operating
           system will start next.
ACTION: Specify the correct parameter or parameters; then,
try the command again.
;
;
SYS1703H: EXPLANATION: The file contains errors or it is in use by
another process.

ACTION: Do one of the following and retry the command:
o  Correct the errors in the file.
o  Wait until the process using the file finishes.
;
;
SYS1704H: EXPLANATION: Either the source directory was not specified or a
parameter was entered more than once.

ACTION: Correct the parameters and retry the command.
;
;
SYS1705H: 
;
;
SYS1706H: 
;
;
SYS1707H: EXPLANATION: This utility requires DOS Version 3.20 or higher.

ACTION: Install the appropriate version of DOS and retry the command.
;
;
SYS1708H: 
;
;
SYS1709H: 
;
;
SYS1710H: 
;
;
SYS1711H: EXPLANATION: The file might be missing or the Dual Boot feature
might not be installed.

ACTION: Ensure that the file is present at the location specified
in this message.  If the file is in the correct location, reinstall
the Dual Boot feature and retry the command.
;
;
SYS1712H: EXPLANATION: The requested operating system is the same as the current
operating system.  The BOOT command should be used to switch from the
startup operating system to the other operating system.  You can switch
from the OS/2 operating system to DOS or from DOS to OS/2.

ACTION: Specify the other operating system and retry the command.
;
;
SYS1713H: EXPLANATION: An error occurred during the attempt to change
the startup operating system.

ACTION: Reinstall the DOS and OS/2 operating systems.
;
;
SYS1714H: EXPLANATION: The BOOT utility will make changes to your hard disk
and replace the C:\CONFIG.SYS and C:\AUTOEXEC.BAT files, and then
restart your system automatically.

Note that if the system is restarted while programs are running,
those programs will be ended and no changes will be saved.
ACTION: End all programs that you have running (so that the
changes will be saved) before using the BOOT utility.
;
;
SYS1715H: EXPLANATION: The specified file was not copied.  The file might not
exist, contain errors, or be in use by another process.

ACTION: Do one of the following and then retry the command:
o  Copy the file to the startup drive.
o  Correct any errors in the file.
o  Wait until the process using the file finishes.
;
;
SYS1716H: EXPLANATION: The program made changes to your hard disk and
replaced files C:\CONFIG.SYS and C:\AUTOEXEC.BAT in
preparation for the next reset.
ACTION: Restart your system by selecting Shutdown from the
desktop, or pressing Ctrl+Alt+Del.
;
;
SYS1717H: 
;
;
SYS1718H: EXPLANATION: The file containing the specified device driver, program,
or data file cannot be found.

ACTION: Install the specified file and restart the system.
;
;
SYS1719H: EXPLANATION: The file specified does not contain a valid device driver
or file system driver, or contains a valid DOS device driver when a
DOS session was not started.

ACTION: Perform one of the following actions and restart the system:
o  Edit the CONFIG.SYS file to correct or remove the incorrect
   statement.
o  Edit the CONFIG.SYS file to remove the PROTECTONLY=YES statement.
o  Install the correct device driver or file system driver in the
   specified file.
o  Install all dynamic link libraries required by the specified device
   driver.
;
;
SYS1720H: 
;
;
SYS1721H: 
;
;
SYS1722H: 
;
;
SYS1723H: 
;
;
SYS1724H: 
;
;
SYS1725H: 
;
;
SYS1726H: 
;
;
SYS1727H: EXPLANATION: There is not enough memory available for the memory
specified by the DISKCACHE statement.

ACTION: Try one of the following and restart the system:
o Edit the CONFIG.SYS file to reduce the value specified in the
  DISKCACHE=, BUFFERS=, TRACEBUF=, THREADS=, or RMSIZE= statement or
  reduce the size allocated for a  virtual disk in a DEVICE=VDISK.SYS
  statement.
o  Install another memory option in your system unit.
;
;
SYS1728H: EXPLANATION: The value is too small for the amount of total DASD
(hard-disk size) in your system.

ACTION: Edit the CONFIG.SYS file to increase the value on the
DISKCACHE command and restart the system.  For more information about
the minimum value needed, refer to DISKCACHE in the Command Reference.
;
;
SYS1729H: EXPLANATION: The specified code page is not defined in the
font file for the display or no DEVINFO command was specified
for device type SCR.

ACTION: Perform one of the following actions and restart the system:
o  Edit the CONFIG.SYS file to correct or remove the CODEPAGE statement.
o  Edit the CONFIG.SYS file to correct or add the DEVINFO=SCR statement.
o  Install the correct font file for the display.
;
;
SYS1730H: EXPLANATION: One or more of the specified code pages are not defined
in the translation table file for the keyboard or no DEVINFO command
was specified for device type KBD.

ACTION: Perform one of the following actions and restart the system:
o  Edit the CONFIG.SYS file to correct or remove the CODEPAGE statement.
o  Edit the CONFIG.SYS file to correct or add the DEVINFO=KBD statement.
o  Install the correct keyboard translation file.
;
;
SYS1731H: EXPLANATION: An error occurred that prevented the BOOT command from
automatically restarting the system.  If you are running OS/2, the
C:\OS2 directory might not contain the DOS.SYS file or, if you have
just run BOOT /DOS, your OS/2 CONFIG.SYS file might not contain the
correct DEVICE= statement.

ACTION: Do one of the following and restart the system:
o  If you are running OS/2 and the C:\OS2 directory does not contain
   the DOS.SYS file, use the UNPACK command to copy the DOS.SYS file
   from the OS/2 Installation Diskette to the C:\OS2 directory.
o  If you have just run BOOT /DOS, make sure that the OS/2 CONFIG.SYS
   file contains the DEVICE=C:\OS2\DOS.SYS statement.
;
;
SYS1732H: 
;
;
SYS1733H: EXPLANATION: The specified file is not a valid country information
file or the file has been destroyed.

ACTION: Install the correct country information file and restart the
system.
;
;
SYS1734H: 
;
;
SYS1735H: 
;
;
SYS1736H: EXPLANATION: The BOOT command cannot access a function of the DOS.SYS
device driver.  The device driver is either missing or is not in the
correct directory.

ACTION: Do one of the following, restart the system, and retry the
command:
o  If the DOS.SYS device driver is not in the C:\OS2 directory,
   use the UNPACK command to copy it from the OS/2 Installation
   Diskette to the C:\OS2 directory.
o  Ensure that the OS/2 CONFIG.SYS file contains the
   DEVICE=C:\OS2\DOS.SYS statement.
;
;
SYS1737H: 
;
;
SYS1738H: EXPLANATION: The memory in the system cannot be allocated or a
hardware error occurred.

ACTION: Check the storage size and run the diagnostics diskette to
determine the cause of the problem.
;
;
SYS1739H: 
;
;
SYS1740H: EXPLANATION: The BOOT utility replaces system files on the hard disk with
DOS system files when OS/2 was installed.  If DOS was not installed on C:
when you installed OS/2, these files will not exist.  In this case, the
BOOT utility can save the OS/2 system files, allow you to install DOS, and
when you return to OS/2, the DOS system files will be saved.
ACTION: Continue the BOOT utility, then shut down OS/2 and install DOS.
When DOS is installed, you may return to OS/2 with the command: BOOT /OS2.
;
;
SYS1741H: EXPLANATION: The translation table file does not exist or the path is
not given in your DEVINFO= statement.

ACTION: Unpack the translation table file to your disk.  Put the path
and file name in the DEVINFO= statement in the CONFIG.SYS file and
restart the system.
;
;
SYS1742H: EXPLANATION: An error occurred while reading the translation table file.

ACTION: Reinstall the translate table file using the same file name
and path name and restart the system.
;
;
SYS1743H: 
;
;
SYS1744H: EXPLANATION: An external error has occurred and the system cannot
continue with the operation.

ACTION: Retry the command.
;
;
SYS1745H: 
;
;
SYS1746H: EXPLANATION: The translate table file listed in the DEVINFO= statement
in the CONFIG.SYS file does not have a default translate table entry
that matches the country code and the keyboard you are using.

ACTION: Do one of the following and retry the command:
o  Edit the DEVINFO= statement in the CONFIG.SYS file to use the
   system provided translate table file (KEYBOARD.DCP).
o  Correct the translate table file.
;
;
SYS1747H: 
;
;
SYS1748H: EXPLANATION: The operating system detected an error opening the
keyboard.  Too many files or programs might be open.

ACTION: Do one of the following and retry the command:
o  Reduce the number of running programs.
o  Reduce the number of open files.
;
;
SYS1749H: 
;
;
SYS1750H: EXPLANATION: The keyboard that is installed for the system is not a
compatible type.  Compatible types of keyboards are Personal Computer
AT and Personal Computer Enhanced keyboards.

ACTION: Install a compatible keyboard and retry the command.
;
;
SYS1751H: EXPLANATION: The system cannot continue to load the translate table
because it has detected an error.

ACTION: Retry the command.
;
;
SYS1752H: 
;
;
SYS1753H: 
;
;
SYS1754H: 
;
;
SYS1755H: 
;
;
SYS1756H: 
;
;
SYS1757H: 
;
;
SYS1758H: 
;
;
SYS1759H: 
;
;
SYS1760H: 
;
;
SYS1761H: EXPLANATION: Too few or too many parameters were entered.  The CHCP
command accepts only one parameter and that parameter must represent
a specific code-page number.

ACTION: Retry the CHCP command using the correct parameter.
;
;
SYS1762H: EXPLANATION: The country information file was not present
during system startup.

ACTION: If the CONFIG.SYS file specifies a country information
file, make sure that it exists.  If CONFIG.SYS does not specify
this file, make sure that the COUNTRY.SYS file exists in the root
directory of the startup drive.  Correct the problem and restart
the system.
;
;
SYS1763H: 
;
;
SYS1764H: 
;
;
SYS1765H: 
;
;
SYS1766H: 
;
;
SYS1767H: EXPLANATION: The code page specified has not been defined by a
CODEPAGE= statement in the CONFIG.SYS file.

ACTION: Define the CODEPAGE= statement in the CONFIG.SYS file
using a valid code page and restart the system.
;
;
SYS1768H: 
;
;
SYS1769H: 
;
;
SYS1770H: 
;
;
SYS1771H: 
;
;
SYS1772H: 
;
;
SYS1773H: EXPLANATION: The START command has a wrong parameter or combination
of parameters.

ACTION: Check the command syntax and retry the command.
;
;
SYS1774H: 
;
;
SYS1775H: 
;
;
SYS1776H: 
;
;
SYS1777H: 
;
;
SYS1778H: EXPLANATION: The spooler option was not started.

ACTION: Start the spooler by using the Spooler object in the
System Setup folder.
;
;
SYS1779H: EXPLANATION: Presentation Manager detected an error while trying to
write to this device.
ACTION: Retry the command after ensuring that the device is:
o  Installed and connected
o  Switched on
o  Not being used by another process
o  In the proper receive mode
;
;
SYS1780H: EXPLANATION: The PRINT command received a return code it did not
understand.

ACTION: Retry the command.  If the error occurs again, it might
be necessary to reconfigure the component and restart the system.
;
;
SYS1781H: 
;
;
SYS1782H: 
;
;
SYS1783H: 
;
;
SYS1784H: 
;
;
SYS1785H: 
;
;
SYS1786H: 
;
;
SYS1787H: 
;
;
SYS1788H: 
;
;
SYS1789H: 
;
;
SYS1790H: 
;
;
SYS1791H: 
;
;
SYS1792H: 
;
;
SYS1793H: 
;
;
SYS1794H: 
;
;
SYS1795H: 
;
;
SYS1796H: 
;
;
SYS1797H: 
;
;
SYS1798H: EXPLANATION: A communications port can be used by only one application
at a time.

ACTION: You may end a program by selecting it from the PM Window List
and then closing it.
;
;
SYS1799H: EXPLANATION: A parallel port can be used by only one application at
a time.

ACTION: You may end a program by selecting it from the PM Window List
and then closing it.
;
;
SYS1800H: 
;
;
SYS1801H: EXPLANATION: The REXX command file was not processed because
OS/2 Procedures Language 2/REXX is not installed.

ACTION: Install OS/2 Procedures Language 2/REXX on your system
and retry the command.
;
;
SYS1802H: EXPLANATION: A Presentation Manager application cannot
be executed using the DETACH command.

ACTION: Try executing the program using the START command.
;
;
SYS1803H: EXPLANATION: CMD.EXE does not support chaining from REXX batch files.

ACTION: Check your REXX batch file for other batch files names.
Precede the batch file name that you want started with the REXX
keyword CALL.
;
;
SYS1804H: EXPLANATION: The file does not exist or is in a different directory.

ACTION: Check the spelling of the file name and its location and
retry the command.
;
;
SYS1805H: EXPLANATION: The process tried to write to a pipe that could
not be created or no longer exists.

ACTION: Check that the program you are trying to pipe to exists
and retry the command.
;
;
SYS1806H: EXPLANATION: The START command was specified using the /F parameter,
but CMD.EXE was not able to start the program in the foreground.
The session is started, but it is not in the foreground session.

ACTION: Switch to the session created by the command to make it
the foreground session.
;
;
SYS1807H: 
;
;
SYS1808H: EXPLANATION: The program generated an exception that the system cannot
resolve.  The soft ware diagnostic code allows determination of what
type of exception was generated.

ACTION: Correct the problem or try a different version of the program.
;
;
SYS1809H: 
;
;
SYS1810H: EXPLANATION: The process ended when it tried to divide a number by zero.

ACTION: Correct the problem or try a different version of the program.
;
;
SYS1811H: EXPLANATION: The program attempted to perform an instruction that the
system cannot perform.  The software diagnostic code allows
determination of what type of instruction was attempted.

ACTION: Correct the problem or try a different version of the program.
;
;
SYS1812H: EXPLANATION: A math coprocessor is not present in the system.

ACTION: Obtain a version of the program that does not require a
math coprocessor or obtain a math coprocessor.
;
;
SYS1813H: 
;
;
SYS1814H: 
;
;
SYS1815H: EXPLANATION: The device name is incorrect.

ACTION: Check the device name or spelling and retry the command.
;
;
SYS1816H: EXPLANATION: The batch file that was running cannot be found or has
been deleted.

ACTION: Replace or reconstruct the batch file and retry the command.
;
;
SYS1817H: 
;
;
SYS1818H: EXPLANATION: CHKDSK requires more memory to examine the EA chains for
this file or directory.  All EA chains on this disk will be ignored.

ACTION: Do one of the following, restart the system, and retry the
command:
o  Reduce the number of running programs.
o  Reduce the value of BUFFERS=, TRACEBUF=, DISKCACHE=, THREADS=,
   RMSIZE=, or DEVICE=VDISK.SYS statement in the CONFIG.SYS file.
o  Remove unwanted swap files from the hard disk or diskette.
o  Install additional memory.
;
;
SYS1819H: 
;
;
SYS1820H: 
;
;
SYS1821H: 
;
;
SYS1822H: 
;
;
SYS1823H: 
;
;
SYS1824H: 
;
;
SYS1825H: 
;
;
SYS1826H: 
;
;
SYS1827H: 
;
;
SYS1828H: 
;
;
SYS1829H: EXPLANATION: One or more EAs already exist on the target directory
or file.  The EA join operation is not allowed when EAs already
exist, unless the override switch is selected.

ACTION: Use the /O parameter on the EAUTIL command to select
the override switch.
;
;
SYS1830H: 
;
;
SYS1831H: 
;
;
SYS1832H: 
;
;
SYS1833H: 
;
;
SYS1834H: 
;
;
SYS1835H: 
;
;
SYS1836H: 
;
;
SYS1837H: 
;
;
SYS1838H: 
;
;
SYS1839H: 
;
;
SYS1840H: 
;
;
SYS1841H: 
;
;
SYS1842H: 
;
;
SYS1843H: 
;
;
SYS1844H: 
;
;
SYS1845H: 
;
;
SYS1846H: 
;
;
SYS1847H: 
;
;
SYS1848H: 
;
;
SYS1849H: 
;
;
SYS1850H: 
;
;
SYS1851H: 
;
;
SYS1852H: 
;
;
SYS1853H: 
;
;
SYS1854H: 
;
;
SYS1855H: 
;
;
SYS1856H: 
;
;
SYS1857H: 
;
;
SYS1858H: 
;
;
SYS1859H: 
;
;
SYS1860H: 
;
;
SYS1861H: 
;
;
SYS1862H: 
;
;
SYS1863H: 
;
;
SYS1864H: 
;
;
SYS1865H: 
;
;
SYS1866H: 
;
;
SYS1867H: 
;
;
SYS1868H: 
;
;
SYS1869H: 
;
;
SYS1870H: 
;
;
SYS1871H: 
;
;
SYS1872H: 
;
;
SYS1873H: 
;
;
SYS1874H: 
;
;
SYS1875H: 
;
;
SYS1876H: 
;
;
SYS1877H: 
;
;
SYS1878H: 
;
;
SYS1879H: 
;
;
SYS1880H: 
;
;
SYS1881H: 
;
;
SYS1882H: 
;
;
SYS1883H: 
;
;
SYS1884H: 
;
;
SYS1885H: 
;
;
SYS1886H: 
;
;
SYS1887H: 
;
;
SYS1888H: 
;
;
SYS1889H: 
;
;
SYS1890H: 
;
;
SYS1891H: 
;
;
SYS1892H: 
;
;
SYS1893H: 
;
;
SYS1894H: 
;
;
SYS1895H: 
;
;
SYS1896H: 
;
;
SYS1897H: 
;
;
SYS1898H: EXPLANATION: The maximum number of OS/2 mode sessions has been reached.

ACTION: Wait until an OS/2 mode session ends and then retry the command.
;
;
SYS1899H: 
;
;
SYS1900H: 
;
;
SYS1901H: EXPLANATION: The system can establish the status of the
COM port only from an OS/2 session.

ACTION: Switch to an OS/2 session and retry the command.
;
;
SYS1902H: EXPLANATION: The ASYNC parameter P has been specified in the
OS/2 session but is only valid in the DOS session.

ACTION: Do one of the following and retry the command:
o  Set the infinite timeout setting to TO=ON in the OS/2 session.
o  Switch to a DOS session.
;
;
SYS1903H: EXPLANATION: This port supports enhanced mode (DMA), but the
COMDMA.SYS device driver cannot use enhanced mode because the
Arbitration Levels are set incorrectly.

ACTION: Do the following:
1. Restart the system using the Hardware Reference Diskette.
2. Select Set Configuration.
3. Set the Arbitration Levels of the COM port to DEDICATED.
4. Be sure that the Arbitration Levels for Serial Receive and
   Serial Transmit are different.
;
;
SYS1904H: 
;
;
SYS1905H: 
;
;
SYS1906H: 
;
;
SYS1907H: 
;
;
SYS1908H: 
;
;
SYS1909H: 
;
;
SYS1910H: 
;
;
SYS1911H: 
;
;
SYS1912H: 
;
;
SYS1913H: 
;
;
SYS1914H: EXPLANATION: The specified drive letter cannot be reserved because it is
already assigned to a hard disk volume or to another block device.

ACTION: Edit your CONFIG.SYS file and change the RESERVEDRIVELETTER= statement
to specify a higher drive letter than those already specified in the BASEDEV=
statement.  Restart your computer.
;
;
SYS1915H: 
;
;
SYS1916H: 
;
;
SYS1917H: 
;
;
SYS1918H: 
;
;
SYS1919H: EXPLANATION: The file specified does not contain a startable program.

ACTION: Perform one of the following actions and restart the system:
o  Edit CONFIG.SYS to correct or remove the incorrect statement.
o  Install the correct program file.
o  Install all DLLs required by the specified program.
;
;
SYS1920H: 
;
;
SYS1921H: 
;
;
SYS1922H: 
;
;
SYS1923H: EXPLANATION: While processing within a system call, OS/2 generated a
fatal page fault.  This is probably the result of an invalid parameter
or a parameter that points to memory that has been freed.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS1924H: EXPLANATION: The application disabled interrupts and did not reset
them.  An error in a ring 2 subroutine is causing it to return to
ring 3 without resetting the interrupts.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS1925H: EXPLANATION: The file specified does not contain a startable program.

ACTION: Perform one of the following actions and restart the system:
o  Install the correct program file.
o  Install all DLLs required by the specified program.
;
;
SYS1926H: 
;
;
SYS1927H: EXPLANATION: A DOS program has changed an interrupt vector
that is exclusively owned by the system.

ACTION: Correct the program and retry the command.
;
;
SYS1928H: EXPLANATION: A code or data segment was either discarded or
swapped out.  There is not enough available memory to reload it.

ACTION: Retry the command.
;
;
SYS1929H: 
;
;
SYS1930H: EXPLANATION: One of the following occurred:
o  A program tried to divide a number by zero.
o  The result of a division operation was too large and a divide
   overflow exception handler was not registered.

ACTION: Correct the program and retry the command.
;
;
SYS1931H: EXPLANATION: A program enabled the single step interrupt when it was
not being run by a debugger.

ACTION: Correct the program and retry the command.
;
;
SYS1932H: 
;
;
SYS1933H: EXPLANATION: A program started an INT 3 instruction when it was not
being run by a debugger.

ACTION: Correct the program and retry the command.
;
;
SYS1934H: EXPLANATION: A program started an INTO instruction without registering
an overflow exception handler.

ACTION: Correct the program and retry the command.
;
;
SYS1935H: EXPLANATION: A program started a BOUND instruction without registering
a bound exception handler.

ACTION: Correct the program and retry the command.
;
;
SYS1936H: EXPLANATION: A program started an invalid instruction
without registering an invalid opcode exception handler.

ACTION: Correct the program and retry the command.
;
;
SYS1937H: EXPLANATION: A program started a numeric coprocessor instruction
without a coprocessor present in the system and without registering a
processor extension not available exception handler.

ACTION: Obtain a copy of the program that does not require a numeric
coprocessor.
;
;
SYS1938H: EXPLANATION: The system caused a double fault exception.

ACTION: Restart the system and retry the command.
;
;
SYS1939H: EXPLANATION: A program ran a numeric coprocessor instruction that
tried to read or write to memory that is past the end of a storage
segment.

ACTION: Correct the program and retry the command.
;
;
SYS1940H: EXPLANATION: The system caused an invalid task state segment exception.

ACTION: Restart the system and retry the command.
;
;
SYS1941H: EXPLANATION: A program attempted to reference a memory segment that is
not currently in memory and was not previously discarded or swapped out.

ACTION: Correct the program and retry the command.
;
;
SYS1942H: EXPLANATION: One of the following occurred:
o  A program attempted to push more data onto the stack than the
   stack could hold.
o  A program called too many subroutines.
o  A program attempted to take more data off the stack than was
   pushed onto the stack.
o  A program tried to return more subroutines than were called.

ACTION: Correct the program and retry the command.
;
;
SYS1943H: EXPLANATION: The errors include (but are not limited to) a memory
object that is:
o  Referring to storage that is outside the limits of memory,
   restricted to privileged code, or has a selector object of zero.
o  Writing to a read-only segment or a code segment.
o  Reading from an execute-only code segment.
o  Loading an invalid value into a selector register.
o  Causing a 80286 or 80386 General Protection Fault.

ACTION: Correct the program and retry the command.
;
;
SYS1944H: 
;
;
SYS1945H: EXPLANATION: A memory parity error occurred on a 4096-byte page.
The system code or data contained in that page cannot be recreated.
The physical location is useful in isolating the failing element.

ACTION: Contact your service representative and have the failing
memory element replaced.
;
;
SYS1946H: 
;
;
SYS1947H: 
;
;
SYS1948H: 
;
;
SYS1949H: EXPLANATION: The errors include (but are not limited to) a
memory object that is:
o  Referring to storage outside the limits of a memory or
   restricted to privileged code.
o  Writing to a read-only memory object.
o  Writing to a code object.

ACTION: Correct the program and retry the command.
;
;
SYS1950H: EXPLANATION: A program ran a numeric coprocessor instruction
that specified one or more incorrect operands.

ACTION: Correct the program and retry the command.
;
;
SYS1951H: EXPLANATION: A program started a numeric coprocessor instruction
that specified one or more incorrect operands.

ACTION: Correct the program and retry the command.
;
;
SYS1952H: EXPLANATION: A number cannot be divided by zero.

ACTION: Correct the program and retry the command.
;
;
SYS1953H: EXPLANATION: A program started a numeric coprocessor
instruction that generated a numeric overflow condition.

ACTION: Correct the program and retry the command.
;
;
SYS1954H: EXPLANATION: A program ran a numeric coprocessor instruction
that generated a numeric overflow condition.

ACTION: Correct the program and retry the command.
;
;
SYS1955H: EXPLANATION: A program started a numeric coprocessor instruction
that generated a precision error.

ACTION: Correct the program and retry the command.
;
;
SYS1956H: 
;
;
SYS1957H: EXPLANATION: A program called DosRaiseException to raise a
floating-point exception, but the coprocessor status word provided
in the exception structure was invalid.  Either none of the 6
exception flags in the status word was set or more than one was set.

ACTION: Make sure only one of the bits is set and that the bit
corresponds to the floating-point exception you want to raise.
Correct the program and retry the command.
;
;
SYS1958H: EXPLANATION: A memory-parity error occurred on a 4096-byte page.
The memory-parity error page has been removed, but your data has
been recovered and the operation will continue.  The physical
location is useful in isolating the failing memory element.

ACTION: The failing memory element should be replaced (physical
location).  Contact your service representative.
;
;
SYS1959H: EXPLANATION: A memory parity error occurred on a 4096-byte page.
The application data contained in that page is not recoverable.
The application identified has ended.  The memory-parity error page
has been removed so that system operation can continue.  The physical
location is useful in isolating the failing memory element.

ACTION: Contact your service representative and have the failing
memory element (physical location) replaced.
;
;
SYS1960H: 
;
;
SYS1961H: 
;
;
SYS1962H: 
;
;
SYS1963H: 
;
;
SYS1964H: 
;
;
SYS1965H: 
;
;
SYS1966H: 
;
;
SYS1967H: 
;
;
SYS1968H: 
;
;
SYS1969H: EXPLANATION: One of the following occurred:
o  The wrong name was entered.
o  A file is missing from the application.

ACTION: Do one of the following:
o  Check the instructions on how the application should be run.
o  Reinstall the application and retry the command.

Press any key to continue...
;
;
SYS1970H: 
;
;
SYS1971H: 
;
;
SYS1972H: 
;
;
SYS1973H: 
;
;
SYS1974H: 
;
;
SYS1975H: 
;
;
SYS1976H: 
;
;
SYS1977H: 
;
;
SYS1978H: 
;
;
SYS1979H: 
;
;
SYS1980H: 
;
;
SYS1981H: EXPLANATION: The device that is to receive the information
is not working.

ACTION: Check the device.  If it is a disk,  make sure there
is enough space available.
;
;
SYS1982H: EXPLANATION: The selected process IDs are not in the system.

ACTION: Use the PSTAT command prior to executing the TRACE
command to find out which process IDs are in the system.
;
;
SYS1983H: 
;
;
SYS1984H: 
;
;
SYS1985H: EXPLANATION: Only .PIP is an acceptable file extension.

ACTION: Check the file extension to be sure it is PIP.
;
;
SYS1986H: 
;
;
SYS1987H: 
;
;
SYS1988H: 
;
;
SYS1989H: 
;
;
SYS1990H: 
;
;
SYS1991H: EXPLANATION: The command or program in use requires a different
version of OS/2.

ACTION: Use OS/2 2.0 or later and restart the system, or install the
proper version of the command or program on the system and retry the
command.
;
;
SYS1992H: 
;
;
SYS1993H: EXPLANATION: EDLIN was entered without the name of the file to be
edited.

ACTION: Enter EDLIN followed by the file name.
;
;
SYS1994H: EXPLANATION: One or more of the parameters entered are incorrect or
placed in the wrong order.

ACTION: Make sure the parameter following the slash (/) is correct
for the program being run.  The program expects a drive specifier.
Enter a colon following the drive letter.
;
;
SYS1995H: 
;
;
SYS1996H: EXPLANATION: The system has too many open files.

ACTION: Wait for a program to end or increase the value of the
FILES= statement in the CONFIG.SYS file and restart the system.
;
;
SYS1997H: EXPLANATION: An error occurred while the file was being read
into memory.

ACTION: Copy the file or a backup of the file to a different disk
and retry the command.
;
;
SYS1998H: EXPLANATION: Files with the extension .BAK are considered to
be backup files, with more up-to-date versions of the files
assumed to exist.  Therefore, .BAK files will not be edited.

ACTION: If it is necessary to edit the .BAK file, rename
the file and give it an extension other than .BAK or copy
the file and give the copy a different file-name extension.
;
;
SYS1999H: EXPLANATION: The E (end edit) command ended because the disk
does not contain enough free space to save the entire file.
Any editing of the file has been lost.

ACTION: Copy the files to a different disk or erase files
from the full disk.  Then start editing again.
;
;
SYS2000H: 
;
;
SYS2001H: EXPLANATION: Except for the line# (edit line) command, all
EDLIN commands are a single letter usually preceded by and/or
followed by parameters.

ACTION: Correct the syntax error and retry the command.
;
;
SYS2002H: 
;
;
SYS2003H: 
;
;
SYS2004H: 
;
;
SYS2005H: EXPLANATION: The replacement of a string caused the line to expand
beyond the limit.  The R (replace text) command ended abnormally.

ACTION: Split the long line into shorter lines and re-issue the R
command.
;
;
SYS2006H: 
;
;
SYS2007H: 
;
;
SYS2008H: EXPLANATION: A destination line number is missing from a M (move lines)
or C (copy lines) command.

ACTION: Retry the command with a destination line number.
;
;
SYS2009H: EXPLANATION: The T (transfer lines) command could not merge the entire
contents of the file because of insufficient memory.  Only part of the
file was merged.

ACTION: Reduce the size of the specified file or the file being edited.
;
;
SYS2010H: 
;
;
SYS2011H: 
;
;
SYS2012H: 
;
;
SYS2013H: 
;
;
SYS2014H: 
;
;
SYS2015H: 
;
;
SYS2016H: 
;
;
SYS2017H: 
;
;
SYS2018H: 
;
;
SYS2019H: 
;
;
SYS2020H: 
;
;
SYS2021H: 
;
;
SYS2022H: 
;
;
SYS2023H: 
;
;
SYS2024H: 
;
;
SYS2025H: 
;
;
SYS2026H: 
;
;
SYS2027H: 
;
;
SYS2028H: 
;
;
SYS2029H: 
;
;
SYS2030H: 
;
;
SYS2031H: 
;
;
SYS2032H: 
;
;
SYS2033H: 
;
;
SYS2034H: EXPLANATION: You are trying to start the Logging Facility.
ACTION: Check your CONFIG.SYS file and make sure you have only one
RUN=C:\OS2\SYSTEM\LOGDAEM.EXE statement.
;
;
SYS2035H: 
;
;
SYS2036H: EXPLANATION: The invalid parameter is specified in the CONFIG.SYS file.

ACTION: Correct the line in the CONFIG.SYS file that contains
the error and retry the operation.
;
;
SYS2037H: 
;
;
SYS2038H: EXPLANATION: The LOGDAEM.EXE program tried to resume logging, but the
file previously logged to no longer has a valid header.

ACTION: Use the SYSLOG command to redirect logging to a new log file.
;
;
SYS2039H: EXPLANATION: The LOGDAEM.EXE program tried to run without LOG.SYS.

ACTION: Add the following statement to your CONFIG.SYS file and
restart the system:
   DEVICE=C:\OS2\LOG.SYS
;
;
SYS2040H: 
;
;
SYS2041H: EXPLANATION: One of the following has occurred:
o  The /E: parameter in the RUN=LOGDAEM.EXE statement contains an
   invalid file name in the CONFIG.SYS file.
o  The LOGDAEM.EXE program was not able to open the default log file.

ACTION: Correct the RUN=LOGDAEM.EXE statement in your CONFIG.SYS file.
;
;
SYS2042H: EXPLANATION: The LOGDAEM.EXE program cannot write to the redirected
log file.  The local log file will store log records.

ACTION: Type HELP followed by the return code (for example, HELP 4)
to determine the cause of the failure and use the SYSLOG command if you
want to redirect logging to another log file.
;
;
SYS2043H: EXPLANATION: The LOGDAEM.EXE program could not write to the log file.
Log records may be lost.

ACTION: Type HELP followed by the return code (for example, HELP 4)
to determine the cause of the failure and use the SYSLOG command to
redirect logging to another log file.
;
;
SYS2044H: 
;
;
SYS2045H: EXPLANATION: LOGDAEM.EXE was unable to increase the size of the
current log file.  The file will begin wrapping at its current size.

ACTION: If wrapping is not desired, free some space on your disk and
then redirect logging to a new log file.
;
;
SYS2046H: 
;
;
SYS2047H: 
;
;
SYS2048H: 
;
;
SYS2049H: 
;
;
SYS2050H: 
;
;
SYS2051H: 
;
;
SYS2052H: 
;
;
SYS2053H: 
;
;
SYS2054H: EXPLANATION: The device driver LOG.SYS could not allocate your log
buffer.  Logging is not enabled.

ACTION: If logging is not needed, remove the DEVICE=C:\OS2\LOG.SYS
statement from your CONFIG.SYS file.
;
;
SYS2055H: EXPLANATION: The LOGDAEM.EXE program may not have been able to
process your request within one minute.

ACTION: Issue LogQueryState or use SYSLOG to determine if your
request was satisfied.  If not, issue it again.
;
;
SYS2056H: EXPLANATION: This command expected more information than the input
file contained.  There is not enough data to complete the process.

ACTION: Ensure that all the information necessary for this command to
complete normally is entered in the input file and retry the command.
;
;
SYS2057H: 
;
;
SYS2058H: 
;
;
SYS2059H: 
;
;
SYS2060H: EXPLANATION: The Logging Facility failed to redirect logging to the
specified log file.  Examine the return code for a specific explanation.
To get help for a return code, type HELP followed by the return code
(for example, HELP 4).

ACTION: Correct the problem and retry the log-file redirection using
the SYSLOG command.
;
;
SYS2061H: 
;
;
SYS2062H: 
;
;
SYS2063H: EXPLANATION: Not enough memory is available to create the DOS
environment or the specified DOS environment size is too large.

ACTION: Perform one of the following actions and restart the system:
o  Edit the CONFIG.SYS file to decrease the value in the RMSIZE
   statement.
o  Edit the CONFIG.SYS file to add the PROTECTONLY=YES statement.
;
;
SYS2064H: EXPLANATION: There is not enough memory available to create the DOS
environment or the specified DOS environment size is too small.

ACTION: Perform one of the following actions and restart the system:
o  Edit the CONFIG.SYS file to remove unnecessary DEVICE= statements.
o  Edit the CONFIG.SYS file to increase the value in the RMSIZE
   statement.
o  Edit the CONFIG.SYS file to add the PROTECTONLY=NO statement.
;
;
SYS2065H: 
;
;
SYS2066H: 
;
;
SYS2067H: 
;
;
SYS2068H: EXPLANATION: The system had more error messages than could
be saved to be displayed at the end of system initialization.

ACTION: Correct the errors for the messages that were
displayed and restart the system.
;
;
SYS2069H: EXPLANATION: The specified file is not a valid country information
file or the file has been damaged.

ACTION: Perform one of the following actions and restart the system:
o  Edit the CONFIG.SYS file to correct or remove the COUNTRY statement.
o  Install the correct country information file.
;
;
SYS2070H: EXPLANATION: The system delayed the loading of some of the
application's code until it was needed.  Now there is a problem
loading the needed code segment.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS2071H: EXPLANATION: Either the file does not exist or it is not in your path.

ACTION: Copy SYSLOGPM.EXE into your path and retry the command.
For more information about SYSLOG, refer to the Command Reference.
;
;
SYS2072H: EXPLANATION: SYSLOG found an incorrect parameter in the command syntax.
Type HELP SYSLOG to see the correct syntax and examples.

ACTION: Retype the command with the correct parameter.
;
;
SYS2073H: EXPLANATION: The SYSLOG suspend command did not succeed.

ACTION: Type HELP followed by the return code (for example, HELP 4)
to determine the cause of the failure.
;
;
SYS2074H: EXPLANATION: The SYSLOG resume command did not succeed.

ACTION: Type HELP followed by the return code (for example, HELP 4)
to determine the cause of the failure.
;
;
SYS2075H: 
;
;
SYS2076H: 
;
;
SYS2077H: 
;
;
SYS2078H: 
;
;
SYS2079H: 
;
;
SYS2080H: 
;
;
SYS2081H: 
;
;
SYS2082H: 
;
;
SYS2083H: 
;
;
SYS2084H: 
;
;
SYS2085H: EXPLANATION: This command performs no required function in this
version of the OS/2 operating system.
ACTION: It is not necessary to execute this command.  You may remove
it from your batch files.
;
;
SYS2086H: 
;
;
SYS2087H: EXPLANATION: One of the following errors occurred:
1. The port is not installed.
2. The port is malfunctioning.
3. A DEVICE= statement for a COMn device driver is not
   included in the CONFIG.SYS file.

ACTION: Do the one of the following and restart the system:
1. Install the port.
2. Repair the port.
3. Put a DEVICE=COMn statement in the CONFIG.SYS file.
;
;
SYS2088H: 
;
;
SYS2089H: 
;
;
SYS2090H: EXPLANATION: The system encountered an error while loading the program.

ACTION: Do one of the following, restart the system, and retry the
program:
o  Retry loading the program using a backup copy of the program.
o  Try running the program when nothing else is running in the system.
o  Change the RMSIZE= statement in the CONFIG.SYS file to a larger size.
;
;
SYS2091H: EXPLANATION: One of the following occurred:
o  You specified a hard-disk drive letter.
o  You specified an incorrect number of parameters for this command.

ACTION: Do one of the following:
o  Specify a diskette drive letter.
o  Correct the number of parameters for this command.
;
;
SYS2092H: EXPLANATION: The MODE command accepts the parameters that follow.

To set parallel printer modes:
   MODE LPTn chars,lines,P
   MODE PRN chars,lines,P

To set video modes:
   MODE CONn display,rows

To set asynchronous modes in DOS sessions:
   MODE COMn:baud,parity,databits,stopbits

To set asynchronous modes in OS/2 sessions:
   MODE COMn:baud,parity,databits,stopbits,
   TO,XON,IDSR,ODSR,OCTS,DTR,RTS,BUFFER

To set diskette verification:
   MODE DSKT VER=ON or VER=OFF

ACTION: Check the MODE parameters and retry the command.
;
;
SYS2093H: 
;
;
SYS2094H: 
;
;
SYS2095H: 
;
;
SYS2096H: 
;
;
SYS2097H: 
;
;
SYS2098H: 
;
;
SYS2099H: 
;
;
SYS2100H: 
;
;
SYS2101H: 
;
;
SYS2102H: EXPLANATION: Either the network is not started or your CONFIG.SYS
file is incorrect.

ACTION: Start the network.  If the problem is not corrected,
contact your network administrator.
;
;
SYS2103H: 
;
;
SYS2104H: 
;
;
SYS2105H: 
;
;
SYS2106H: 
;
;
SYS2107H: 
;
;
SYS2108H: 
;
;
SYS2109H: 
;
;
SYS2110H: 
;
;
SYS2111H: 
;
;
SYS2112H: 
;
;
SYS2113H: 
;
;
SYS2114H: 
;
;
SYS2115H: 
;
;
SYS2116H: 
;
;
SYS2117H: EXPLANATION: The device you specified is assigned to a shared resource.

ACTION: To perform the operation on this device, you must disconnect
the device from the shared resource.
;
;
SYS2118H: 
;
;
SYS2119H: 
;
;
SYS2120H: 
;
;
SYS2121H: 
;
;
SYS2122H: 
;
;
SYS2123H: EXPLANATION: The program you are running created a buffer that is
too small for the data being used.

ACTION: The program should correct this problem.  If it does not,
contact your system administrator or the supplier of the program.
;
;
SYS2124H: 
;
;
SYS2125H: 
;
;
SYS2126H: 
;
;
SYS2127H: 
;
;
SYS2128H: 
;
;
SYS2129H: 
;
;
SYS2130H: 
;
;
SYS2131H: 
;
;
SYS2132H: 
;
;
SYS2133H: 
;
;
SYS2134H: 
;
;
SYS2135H: 
;
;
SYS2136H: 
;
;
SYS2137H: 
;
;
SYS2138H: EXPLANATION: You specified an operation that requires the network
to be running.

ACTION: Start the network and retry this operation.
;
;
SYS2139H: 
;
;
SYS2140H: 
;
;
SYS2141H: 
;
;
SYS2142H: EXPLANATION: The server does not support the request that was sent to
it.  This can happen if two or more versions of the requester or the
server are on the network.  However, no program included with the
requester or the server should cause this error.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS2143H: 
;
;
SYS2144H: 
;
;
SYS2145H: 
;
;
SYS2146H: 
;
;
SYS2147H: 
;
;
SYS2148H: 
;
;
SYS2149H: 
;
;
SYS2150H: EXPLANATION: The queue that you specified is invalid.

ACTION: Verify that the spelling of the queue name is correct.
;
;
SYS2151H: EXPLANATION: There is no print job matching the print job
identification number you specified.  Either the job has completed
printing or may have been deleted from the print queue.

ACTION: Make sure that you specified the correct print job ID
number.  Check the printer to which you sent this job.
;
;
SYS2152H: EXPLANATION: This printer given is not defined on the system.

ACTION: Verify the spelling of the print device given.
;
;
SYS2153H: 
;
;
SYS2154H: EXPLANATION: You tried to create a print queue with a name that is
already in use.

ACTION: Assign the new queue with a different name.
;
;
SYS2155H: EXPLANATION: The system does not have enough memory available to add
another print queue.

ACTION: To free memory, delete an existing print queue and then
create the new queue.
;
;
SYS2156H: EXPLANATION: The system does not have enough memory available to
add another print job.

ACTION: Wait a while, then re-send the print job.
;
;
SYS2157H: EXPLANATION: The system does not have enough memory available to add
another printer.

ACTION: To free memory, delete an existing printer and then create
the new printer.
;
;
SYS2158H: EXPLANATION: The specified printer is not in use.

ACTION: Make sure that you are referring to the correct printer.
;
;
SYS2159H: EXPLANATION: The control function given is invalid.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS2160H: 
;
;
SYS2161H: EXPLANATION: The spooler has not been started.

ACTION: Start the OS/2 Spooler.
;
;
SYS2162H: EXPLANATION: The requested change cannot be made because the port is
already assigned to a printer or a job is active on the printer.

ACTION: Wait until there are no jobs printing or disassociate the
port from the other printer.
;
;
SYS2163H: 
;
;
SYS2164H: EXPLANATION: The requested change cannot be made because of the state
of the job.  It may be printing or paused already.

ACTION: Wait until the job status changes, then retry the command.
;
;
SYS2165H: EXPLANATION: The spooler is out of memory.

ACTION: To free memory for the spooler, delete one or more print
queues or print jobs, or remove one or more printers from all print
queues on the server.
;
;
SYS2166H: EXPLANATION: The printer driver you specified has not been installed
for the print queue.

ACTION: Verify your spelling.  To use a new printer driver with this
print queue, you must use the Print Destination object to install the
printer driver.
;
;
SYS2167H: EXPLANATION: The data type of the print job is not supported by the
queue driver of the queue.

ACTION: Use a different queue driver for jobs that have this data type
or rewrite the application so that it uses a data type that the queue
driver can recognize.
;
;
SYS2168H: EXPLANATION: The specified queue driver has not been installed.

ACTION: Use the Print Destination object to install the queue driver.
;
;
SYS2169H: 
;
;
SYS2170H: 
;
;
SYS2171H: 
;
;
SYS2172H: 
;
;
SYS2173H: 
;
;
SYS2174H: 
;
;
SYS2175H: 
;
;
SYS2176H: 
;
;
SYS2177H: 
;
;
SYS2178H: 
;
;
SYS2179H: 
;
;
SYS2180H: 
;
;
SYS2181H: 
;
;
SYS2182H: 
;
;
SYS2183H: 
;
;
SYS2184H: 
;
;
SYS2185H: 
;
;
SYS2186H: 
;
;
SYS2187H: 
;
;
SYS2188H: 
;
;
SYS2189H: 
;
;
SYS2190H: 
;
;
SYS2191H: 
;
;
SYS2192H: 
;
;
SYS2193H: 
;
;
SYS2194H: 
;
;
SYS2195H: 
;
;
SYS2196H: 
;
;
SYS2197H: 
;
;
SYS2198H: 
;
;
SYS2199H: 
;
;
SYS2200H: 
;
;
SYS2201H: 
;
;
SYS2202H: 
;
;
SYS2203H: 
;
;
SYS2204H: 
;
;
SYS2205H: 
;
;
SYS2206H: 
;
;
SYS2207H: 
;
;
SYS2208H: 
;
;
SYS2209H: 
;
;
SYS2210H: 
;
;
SYS2211H: 
;
;
SYS2212H: 
;
;
SYS2213H: 
;
;
SYS2214H: 
;
;
SYS2215H: EXPLANATION: The server required to access the network may be off line.

ACTION: Retry the request.  If this problem persists, contact your
system administrator.
;
;
SYS2216H: 
;
;
SYS2217H: 
;
;
SYS2218H: 
;
;
SYS2219H: 
;
;
SYS2220H: 
;
;
SYS2221H: 
;
;
SYS2222H: 
;
;
SYS2223H: 
;
;
SYS2224H: 
;
;
SYS2225H: 
;
;
SYS2226H: 
;
;
SYS2227H: 
;
;
SYS2228H: 
;
;
SYS2229H: 
;
;
SYS2230H: 
;
;
SYS2231H: 
;
;
SYS2232H: 
;
;
SYS2233H: 
;
;
SYS2234H: 
;
;
SYS2235H: 
;
;
SYS2236H: 
;
;
SYS2237H: EXPLANATION: You have an application attempting to use the numeric
coprocessor, but no coprocessor is present on this system.

ACTION: Install a numeric coprocessor and retry the application.
;
;
SYS2238H: EXPLANATION: Installable DOS device drivers are occupying too much
memory and the DOS_RMSIZE setting is too low.

ACTION: Increase the DOS_RMSIZE or reduce the number of installed
DOS device drivers.
;
;
SYS2239H: EXPLANATION: Installable DOS device drivers have corrupted the DOS
memory allocation chain.  The VDM session cannot start with memory
corrupted.

ACTION: Remove the installed DOS device drivers and contact the
supplier of the device drivers.
;
;
SYS2240H: EXPLANATION: You have attempted to install a block DOS device driver
or a block virtual device driver (VDD).  Block drivers are only
permitted with the DOS_STARTUP_DRIVE setting.

ACTION: Remove the block driver from the CONFIG.SYS file and the
DOS_DEVICE setting, or use the DOS_STARTUP_DRIVE setting.
;
;
SYS2241H: EXPLANATION: The DOS setting specified is invalid.  A VDM
session cannot be started until this value is corrected.

ACTION: Correct the DOS setting value and restart the VDM session.
;
;
SYS2242H: EXPLANATION: The password specified is no longer valid.

ACTION: Contact your system administrator to obtain a new password.
;
;
SYS2243H: 
;
;
SYS2244H: 
;
;
SYS2245H: 
;
;
SYS2246H: 
;
;
SYS2247H: 
;
;
SYS2248H: 
;
;
SYS2249H: 
;
;
SYS2250H: EXPLANATION: This network connection does not exist.

ACTION: Verify your active connections.
;
;
SYS2251H: 
;
;
SYS2252H: 
;
;
SYS2253H: 
;
;
SYS2254H: 
;
;
SYS2255H: 
;
;
SYS2256H: 
;
;
SYS2257H: 
;
;
SYS2258H: 
;
;
SYS2259H: 
;
;
SYS2260H: 
;
;
SYS2261H: 
;
;
SYS2262H: 
;
;
SYS2263H: 
;
;
SYS2264H: 
;
;
SYS2265H: 
;
;
SYS2266H: 
;
;
SYS2267H: 
;
;
SYS2268H: 
;
;
SYS2269H: 
;
;
SYS2270H: 
;
;
SYS2271H: 
;
;
SYS2272H: 
;
;
SYS2273H: 
;
;
SYS2274H: 
;
;
SYS2275H: 
;
;
SYS2276H: 
;
;
SYS2277H: 
;
;
SYS2278H: 
;
;
SYS2279H: 
;
;
SYS2280H: 
;
;
SYS2281H: 
;
;
SYS2282H: 
;
;
SYS2283H: 
;
;
SYS2284H: 
;
;
SYS2285H: 
;
;
SYS2286H: 
;
;
SYS2287H: 
;
;
SYS2288H: 
;
;
SYS2289H: 
;
;
SYS2290H: 
;
;
SYS2291H: 
;
;
SYS2292H: 
;
;
SYS2293H: 
;
;
SYS2294H: 
;
;
SYS2295H: 
;
;
SYS2296H: 
;
;
SYS2297H: 
;
;
SYS2298H: 
;
;
SYS2299H: 
;
;
SYS2300H: 
;
;
SYS2301H: 
;
;
SYS2302H: 
;
;
SYS2303H: 
;
;
SYS2304H: 
;
;
SYS2305H: 
;
;
SYS2306H: 
;
;
SYS2307H: 
;
;
SYS2308H: 
;
;
SYS2309H: 
;
;
SYS2310H: 
;
;
SYS2311H: 
;
;
SYS2312H: 
;
;
SYS2313H: 
;
;
SYS2314H: 
;
;
SYS2315H: 
;
;
SYS2316H: 
;
;
SYS2317H: 
;
;
SYS2318H: 
;
;
SYS2319H: 
;
;
SYS2320H: 
;
;
SYS2321H: 
;
;
SYS2322H: 
;
;
SYS2323H: 
;
;
SYS2324H: 
;
;
SYS2325H: 
;
;
SYS2326H: 
;
;
SYS2327H: 
;
;
SYS2328H: 
;
;
SYS2329H: 
;
;
SYS2330H: 
;
;
SYS2331H: 
;
;
SYS2332H: 
;
;
SYS2333H: 
;
;
SYS2334H: 
;
;
SYS2335H: 
;
;
SYS2336H: 
;
;
SYS2337H: 
;
;
SYS2338H: 
;
;
SYS2339H: 
;
;
SYS2340H: 
;
;
SYS2341H: EXPLANATION: The device given does not represent a known print device.

ACTION: Verify your spelling and retry the command.
;
;
SYS2342H: 
;
;
SYS2343H: EXPLANATION: This device is used with a serial device queue.  You
cannot use a device with both serial device queues and print queues.

ACTION: To use this device with a print queue, you must disconnect
all serial device queues from it.
;
;
SYS2344H: 
;
;
SYS2345H: 
;
;
SYS2346H: 
;
;
SYS2347H: 
;
;
SYS2348H: 
;
;
SYS2349H: 
;
;
SYS2350H: 
;
;
SYS2351H: EXPLANATION: Check the syntax of the computer name.

ACTION: Correct the syntax of the computer name and retry the
operation.  If the problem persists, contact your system administrator.
;
;
SYS2352H: 
;
;
SYS2353H: 
;
;
SYS2354H: 
;
;
SYS2355H: 
;
;
SYS2356H: 
;
;
SYS2357H: 
;
;
SYS2358H: 
;
;
SYS2359H: 
;
;
SYS2360H: 
;
;
SYS2361H: 
;
;
SYS2362H: 
;
;
SYS2363H: 
;
;
SYS2364H: 
;
;
SYS2365H: 
;
;
SYS2366H: 
;
;
SYS2367H: 
;
;
SYS2368H: 
;
;
SYS2369H: 
;
;
SYS2370H: 
;
;
SYS2371H: 
;
;
SYS2372H: 
;
;
SYS2373H: 
;
;
SYS2374H: 
;
;
SYS2375H: 
;
;
SYS2376H: 
;
;
SYS2377H: 
;
;
SYS2378H: 
;
;
SYS2379H: 
;
;
SYS2380H: 
;
;
SYS2381H: 
;
;
SYS2382H: 
;
;
SYS2383H: 
;
;
SYS2384H: 
;
;
SYS2385H: 
;
;
SYS2386H: 
;
;
SYS2387H: 
;
;
SYS2388H: 
;
;
SYS2389H: 
;
;
SYS2390H: 
;
;
SYS2391H: 
;
;
SYS2392H: 
;
;
SYS2393H: 
;
;
SYS2394H: 
;
;
SYS2395H: 
;
;
SYS2396H: 
;
;
SYS2397H: 
;
;
SYS2398H: 
;
;
SYS2399H: 
;
;
SYS2400H: 
;
;
SYS2401H: EXPLANATION: You tried to delete an active connection.  There are
open files or requests pending on this connection.

ACTION: Close all files and end all programs related to the connection
before you try to delete it.
;
;
SYS2402H: 
;
;
SYS2403H: 
;
;
SYS2404H: 
;
;
SYS2405H: EXPLANATION: You tried to assign a local drive letter to a shared
resource.

ACTION: Use a drive letter that does not correspond to a local drive.
;
;
SYS2406H: 
;
;
SYS2407H: 
;
;
SYS2408H: 
;
;
SYS2409H: 
;
;
SYS2410H: 
;
;
SYS2411H: 
;
;
SYS2412H: 
;
;
SYS2413H: 
;
;
SYS2414H: 
;
;
SYS2415H: 
;
;
SYS2416H: 
;
;
SYS2417H: 
;
;
SYS2418H: 
;
;
SYS2419H: 
;
;
SYS2420H: 
;
;
SYS2421H: 
;
;
SYS2422H: 
;
;
SYS2423H: 
;
;
SYS2424H: 
;
;
SYS2425H: 
;
;
SYS2426H: 
;
;
SYS2427H: 
;
;
SYS2428H: 
;
;
SYS2429H: 
;
;
SYS2430H: 
;
;
SYS2431H: 
;
;
SYS2432H: 
;
;
SYS2433H: 
;
;
SYS2434H: 
;
;
SYS2435H: 
;
;
SYS2436H: 
;
;
SYS2437H: 
;
;
SYS2438H: 
;
;
SYS2439H: 
;
;
SYS2440H: 
;
;
SYS2441H: 
;
;
SYS2442H: 
;
;
SYS2443H: 
;
;
SYS2444H: 
;
;
SYS2445H: 
;
;
SYS2446H: 
;
;
SYS2447H: 
;
;
SYS2448H: 
;
;
SYS2449H: 
;
;
SYS2450H: 
;
;
SYS2451H: 
;
;
SYS2452H: 
;
;
SYS2453H: 
;
;
SYS2454H: 
;
;
SYS2455H: 
;
;
SYS2456H: 
;
;
SYS2457H: 
;
;
SYS2458H: 
;
;
SYS2459H: 
;
;
SYS2460H: 
;
;
SYS2461H: 
;
;
SYS2462H: 
;
;
SYS2463H: 
;
;
SYS2464H: 
;
;
SYS2465H: 
;
;
SYS2466H: 
;
;
SYS2467H: 
;
;
SYS2468H: 
;
;
SYS2469H: 
;
;
SYS2470H: 
;
;
SYS2471H: 
;
;
SYS2472H: 
;
;
SYS2473H: 
;
;
SYS2474H: 
;
;
SYS2475H: 
;
;
SYS2476H: 
;
;
SYS2477H: 
;
;
SYS2478H: 
;
;
SYS2479H: 
;
;
SYS2480H: 
;
;
SYS2481H: 
;
;
SYS2482H: 
;
;
SYS2483H: 
;
;
SYS2484H: 
;
;
SYS2485H: 
;
;
SYS2486H: 
;
;
SYS2487H: 
;
;
SYS2488H: 
;
;
SYS2489H: 
;
;
SYS2490H: 
;
;
SYS2491H: 
;
;
SYS2492H: 
;
;
SYS2493H: 
;
;
SYS2494H: 
;
;
SYS2495H: 
;
;
SYS2496H: 
;
;
SYS2497H: 
;
;
SYS2498H: 
;
;
SYS2499H: 
;
;
SYS2500H: 
;
;
SYS2501H: 
;
;
SYS2502H: 
;
;
SYS2503H: 
;
;
SYS2504H: 
;
;
SYS2505H: 
;
;
SYS2506H: 
;
;
SYS2507H: 
;
;
SYS2508H: 
;
;
SYS2509H: 
;
;
SYS2510H: 
;
;
SYS2511H: 
;
;
SYS2512H: 
;
;
SYS2513H: 
;
;
SYS2514H: 
;
;
SYS2515H: 
;
;
SYS2516H: 
;
;
SYS2517H: 
;
;
SYS2518H: 
;
;
SYS2519H: 
;
;
SYS2520H: 
;
;
SYS2521H: 
;
;
SYS2522H: 
;
;
SYS2523H: 
;
;
SYS2524H: 
;
;
SYS2525H: 
;
;
SYS2526H: 
;
;
SYS2527H: 
;
;
SYS2528H: 
;
;
SYS2529H: 
;
;
SYS2530H: 
;
;
SYS2531H: 
;
;
SYS2532H: 
;
;
SYS2533H: 
;
;
SYS2534H: 
;
;
SYS2535H: 
;
;
SYS2536H: 
;
;
SYS2537H: 
;
;
SYS2538H: 
;
;
SYS2539H: 
;
;
SYS2540H: 
;
;
SYS2541H: 
;
;
SYS2542H: 
;
;
SYS2543H: 
;
;
SYS2544H: 
;
;
SYS2545H: 
;
;
SYS2546H: 
;
;
SYS2547H: 
;
;
SYS2548H: 
;
;
SYS2549H: 
;
;
SYS2550H: 
;
;
SYS2551H: 
;
;
SYS2552H: 
;
;
SYS2553H: 
;
;
SYS2554H: 
;
;
SYS2555H: 
;
;
SYS2556H: 
;
;
SYS2557H: 
;
;
SYS2558H: 
;
;
SYS2559H: 
;
;
SYS2560H: 
;
;
SYS2561H: 
;
;
SYS2562H: 
;
;
SYS2563H: 
;
;
SYS2564H: 
;
;
SYS2565H: 
;
;
SYS2566H: 
;
;
SYS2567H: 
;
;
SYS2568H: 
;
;
SYS2569H: 
;
;
SYS2570H: 
;
;
SYS2571H: 
;
;
SYS2572H: 
;
;
SYS2573H: 
;
;
SYS2574H: 
;
;
SYS2575H: 
;
;
SYS2576H: 
;
;
SYS2577H: 
;
;
SYS2578H: 
;
;
SYS2579H: 
;
;
SYS2580H: 
;
;
SYS2581H: 
;
;
SYS2582H: 
;
;
SYS2583H: 
;
;
SYS2584H: 
;
;
SYS2585H: 
;
;
SYS2586H: 
;
;
SYS2587H: 
;
;
SYS2588H: 
;
;
SYS2589H: 
;
;
SYS2590H: 
;
;
SYS2591H: 
;
;
SYS2592H: 
;
;
SYS2593H: 
;
;
SYS2594H: 
;
;
SYS2595H: 
;
;
SYS2596H: 
;
;
SYS2597H: 
;
;
SYS2598H: 
;
;
SYS2599H: 
;
;
SYS2600H: 
;
;
SYS2601H: 
;
;
SYS2602H: 
;
;
SYS2603H: 
;
;
SYS2604H: 
;
;
SYS2605H: 
;
;
SYS2606H: 
;
;
SYS2607H: 
;
;
SYS2608H: 
;
;
SYS2609H: 
;
;
SYS2610H: 
;
;
SYS2611H: 
;
;
SYS2612H: 
;
;
SYS2613H: 
;
;
SYS2614H: 
;
;
SYS2615H: 
;
;
SYS2616H: 
;
;
SYS2617H: 
;
;
SYS2618H: 
;
;
SYS2619H: 
;
;
SYS2620H: 
;
;
SYS2621H: 
;
;
SYS2622H: 
;
;
SYS2623H: 
;
;
SYS2624H: 
;
;
SYS2625H: 
;
;
SYS2626H: 
;
;
SYS2627H: 
;
;
SYS2628H: 
;
;
SYS2629H: 
;
;
SYS2630H: 
;
;
SYS2631H: 
;
;
SYS2632H: 
;
;
SYS2633H: 
;
;
SYS2634H: 
;
;
SYS2635H: 
;
;
SYS2636H: 
;
;
SYS2637H: 
;
;
SYS2638H: 
;
;
SYS2639H: 
;
;
SYS2640H: 
;
;
SYS2641H: 
;
;
SYS2642H: 
;
;
SYS2643H: 
;
;
SYS2644H: 
;
;
SYS2645H: 
;
;
SYS2646H: 
;
;
SYS2647H: 
;
;
SYS2648H: 
;
;
SYS2649H: 
;
;
SYS2650H: 
;
;
SYS2651H: 
;
;
SYS2652H: 
;
;
SYS2653H: 
;
;
SYS2654H: 
;
;
SYS2655H: 
;
;
SYS2656H: 
;
;
SYS2657H: 
;
;
SYS2658H: 
;
;
SYS2659H: 
;
;
SYS2660H: 
;
;
SYS2661H: 
;
;
SYS2662H: 
;
;
SYS2663H: 
;
;
SYS2664H: 
;
;
SYS2665H: 
;
;
SYS2666H: 
;
;
SYS2667H: 
;
;
SYS2668H: 
;
;
SYS2669H: 
;
;
SYS2670H: 
;
;
SYS2671H: 
;
;
SYS2672H: 
;
;
SYS2673H: 
;
;
SYS2674H: 
;
;
SYS2675H: 
;
;
SYS2676H: 
;
;
SYS2677H: 
;
;
SYS2678H: 
;
;
SYS2679H: 
;
;
SYS2680H: 
;
;
SYS2681H: 
;
;
SYS2682H: 
;
;
SYS2683H: 
;
;
SYS2684H: 
;
;
SYS2685H: 
;
;
SYS2686H: 
;
;
SYS2687H: 
;
;
SYS2688H: 
;
;
SYS2689H: 
;
;
SYS2690H: 
;
;
SYS2691H: 
;
;
SYS2692H: 
;
;
SYS2693H: 
;
;
SYS2694H: 
;
;
SYS2695H: 
;
;
SYS2696H: 
;
;
SYS2697H: 
;
;
SYS2698H: 
;
;
SYS2699H: 
;
;
SYS2700H: 
;
;
SYS2701H: 
;
;
SYS2702H: 
;
;
SYS2703H: 
;
;
SYS2704H: 
;
;
SYS2705H: 
;
;
SYS2706H: 
;
;
SYS2707H: 
;
;
SYS2708H: 
;
;
SYS2709H: 
;
;
SYS2710H: 
;
;
SYS2711H: 
;
;
SYS2712H: 
;
;
SYS2713H: 
;
;
SYS2714H: 
;
;
SYS2715H: 
;
;
SYS2716H: 
;
;
SYS2717H: 
;
;
SYS2718H: 
;
;
SYS2719H: 
;
;
SYS2720H: 
;
;
SYS2721H: 
;
;
SYS2722H: 
;
;
SYS2723H: 
;
;
SYS2724H: 
;
;
SYS2725H: 
;
;
SYS2726H: 
;
;
SYS2727H: 
;
;
SYS2728H: 
;
;
SYS2729H: 
;
;
SYS2730H: 
;
;
SYS2731H: 
;
;
SYS2732H: 
;
;
SYS2733H: 
;
;
SYS2734H: 
;
;
SYS2735H: 
;
;
SYS2736H: 
;
;
SYS2737H: 
;
;
SYS2738H: 
;
;
SYS2739H: 
;
;
SYS2740H: 
;
;
SYS2741H: 
;
;
SYS2742H: 
;
;
SYS2743H: 
;
;
SYS2744H: 
;
;
SYS2745H: 
;
;
SYS2746H: 
;
;
SYS2747H: 
;
;
SYS2748H: 
;
;
SYS2749H: 
;
;
SYS2750H: 
;
;
SYS2751H: 
;
;
SYS2752H: 
;
;
SYS2753H: 
;
;
SYS2754H: 
;
;
SYS2755H: 
;
;
SYS2756H: 
;
;
SYS2757H: 
;
;
SYS2758H: 
;
;
SYS2759H: 
;
;
SYS2760H: 
;
;
SYS2761H: 
;
;
SYS2762H: 
;
;
SYS2763H: 
;
;
SYS2764H: 
;
;
SYS2765H: 
;
;
SYS2766H: 
;
;
SYS2767H: 
;
;
SYS2768H: 
;
;
SYS2769H: 
;
;
SYS2770H: 
;
;
SYS2771H: 
;
;
SYS2772H: 
;
;
SYS2773H: 
;
;
SYS2774H: 
;
;
SYS2775H: 
;
;
SYS2776H: 
;
;
SYS2777H: 
;
;
SYS2778H: 
;
;
SYS2779H: 
;
;
SYS2780H: 
;
;
SYS2781H: 
;
;
SYS2782H: 
;
;
SYS2783H: 
;
;
SYS2784H: 
;
;
SYS2785H: 
;
;
SYS2786H: 
;
;
SYS2787H: 
;
;
SYS2788H: 
;
;
SYS2789H: 
;
;
SYS2790H: 
;
;
SYS2791H: 
;
;
SYS2792H: 
;
;
SYS2793H: 
;
;
SYS2794H: 
;
;
SYS2795H: 
;
;
SYS2796H: 
;
;
SYS2797H: 
;
;
SYS2798H: 
;
;
SYS2799H: 
;
;
SYS2800H: 
;
;
SYS2801H: 
;
;
SYS2802H: 
;
;
SYS2803H: 
;
;
SYS2804H: 
;
;
SYS2805H: 
;
;
SYS2806H: 
;
;
SYS2807H: 
;
;
SYS2808H: 
;
;
SYS2809H: 
;
;
SYS2810H: 
;
;
SYS2811H: 
;
;
SYS2812H: 
;
;
SYS2813H: 
;
;
SYS2814H: 
;
;
SYS2815H: 
;
;
SYS2816H: 
;
;
SYS2817H: 
;
;
SYS2818H: 
;
;
SYS2819H: 
;
;
SYS2820H: 
;
;
SYS2821H: 
;
;
SYS2822H: 
;
;
SYS2823H: 
;
;
SYS2824H: 
;
;
SYS2825H: 
;
;
SYS2826H: 
;
;
SYS2827H: 
;
;
SYS2828H: 
;
;
SYS2829H: 
;
;
SYS2830H: 
;
;
SYS2831H: 
;
;
SYS2832H: 
;
;
SYS2833H: 
;
;
SYS2834H: 
;
;
SYS2835H: 
;
;
SYS2836H: 
;
;
SYS2837H: 
;
;
SYS2838H: 
;
;
SYS2839H: 
;
;
SYS2840H: 
;
;
SYS2841H: 
;
;
SYS2842H: 
;
;
SYS2843H: 
;
;
SYS2844H: 
;
;
SYS2845H: 
;
;
SYS2846H: 
;
;
SYS2847H: 
;
;
SYS2848H: 
;
;
SYS2849H: 
;
;
SYS2850H: 
;
;
SYS2851H: 
;
;
SYS2852H: 
;
;
SYS2853H: 
;
;
SYS2854H: 
;
;
SYS2855H: 
;
;
SYS2856H: 
;
;
SYS2857H: 
;
;
SYS2858H: 
;
;
SYS2859H: 
;
;
SYS2860H: 
;
;
SYS2861H: 
;
;
SYS2862H: 
;
;
SYS2863H: 
;
;
SYS2864H: 
;
;
SYS2865H: 
;
;
SYS2866H: 
;
;
SYS2867H: 
;
;
SYS2868H: 
;
;
SYS2869H: 
;
;
SYS2870H: 
;
;
SYS2871H: 
;
;
SYS2872H: 
;
;
SYS2873H: 
;
;
SYS2874H: 
;
;
SYS2875H: 
;
;
SYS2876H: 
;
;
SYS2877H: 
;
;
SYS2878H: 
;
;
SYS2879H: 
;
;
SYS2880H: 
;
;
SYS2881H: 
;
;
SYS2882H: 
;
;
SYS2883H: 
;
;
SYS2884H: 
;
;
SYS2885H: 
;
;
SYS2886H: 
;
;
SYS2887H: 
;
;
SYS2888H: 
;
;
SYS2889H: 
;
;
SYS2890H: 
;
;
SYS2891H: 
;
;
SYS2892H: 
;
;
SYS2893H: 
;
;
SYS2894H: 
;
;
SYS2895H: 
;
;
SYS2896H: 
;
;
SYS2897H: 
;
;
SYS2898H: 
;
;
SYS2899H: 
;
;
SYS2900H: 
;
;
SYS2901H: 
;
;
SYS2902H: 
;
;
SYS2903H: 
;
;
SYS2904H: 
;
;
SYS2905H: 
;
;
SYS2906H: 
;
;
SYS2907H: 
;
;
SYS2908H: 
;
;
SYS2909H: 
;
;
SYS2910H: 
;
;
SYS2911H: 
;
;
SYS2912H: 
;
;
SYS2913H: 
;
;
SYS2914H: 
;
;
SYS2915H: 
;
;
SYS2916H: 
;
;
SYS2917H: 
;
;
SYS2918H: 
;
;
SYS2919H: 
;
;
SYS2920H: 
;
;
SYS2921H: 
;
;
SYS2922H: 
;
;
SYS2923H: 
;
;
SYS2924H: 
;
;
SYS2925H: 
;
;
SYS2926H: 
;
;
SYS2927H: 
;
;
SYS2928H: 
;
;
SYS2929H: 
;
;
SYS2930H: 
;
;
SYS2931H: 
;
;
SYS2932H: 
;
;
SYS2933H: 
;
;
SYS2934H: 
;
;
SYS2935H: 
;
;
SYS2936H: 
;
;
SYS2937H: 
;
;
SYS2938H: 
;
;
SYS2939H: 
;
;
SYS2940H: 
;
;
SYS2941H: 
;
;
SYS2942H: 
;
;
SYS2943H: 
;
;
SYS2944H: 
;
;
SYS2945H: 
;
;
SYS2946H: 
;
;
SYS2947H: 
;
;
SYS2948H: 
;
;
SYS2949H: 
;
;
SYS2950H: 
;
;
SYS2951H: 
;
;
SYS2952H: 
;
;
SYS2953H: 
;
;
SYS2954H: 
;
;
SYS2955H: 
;
;
SYS2956H: 
;
;
SYS2957H: 
;
;
SYS2958H: 
;
;
SYS2959H: 
;
;
SYS2960H: 
;
;
SYS2961H: 
;
;
SYS2962H: 
;
;
SYS2963H: 
;
;
SYS2964H: 
;
;
SYS2965H: 
;
;
SYS2966H: 
;
;
SYS2967H: 
;
;
SYS2968H: 
;
;
SYS2969H: 
;
;
SYS2970H: 
;
;
SYS2971H: 
;
;
SYS2972H: 
;
;
SYS2973H: 
;
;
SYS2974H: 
;
;
SYS2975H: 
;
;
SYS2976H: 
;
;
SYS2977H: 
;
;
SYS2978H: 
;
;
SYS2979H: 
;
;
SYS2980H: 
;
;
SYS2981H: 
;
;
SYS2982H: 
;
;
SYS2983H: 
;
;
SYS2984H: 
;
;
SYS2985H: 
;
;
SYS2986H: 
;
;
SYS2987H: 
;
;
SYS2988H: 
;
;
SYS2989H: 
;
;
SYS2990H: 
;
;
SYS2991H: 
;
;
SYS2992H: 
;
;
SYS2993H: 
;
;
SYS2994H: 
;
;
SYS2995H: 
;
;
SYS2996H: 
;
;
SYS2997H: 
;
;
SYS2998H: 
;
;
SYS2999H: 
;
;
SYS3000H: 
;
;
SYS3001H: EXPLANATION: You are trying to access through
the prompt a drive that no longer exists.

ACTION: Specify a valid drive.
;
;
SYS3002H: 
;
;
SYS3003H: EXPLANATION: In COMMAND.COM, the correct syntax for specifying the
environment size in bytes is /E:n, where n is from 160 to 32768.
One of the following has occurred:
o  You specified a number that is too large (above 32768) or
   too small (below 160).
o  You specified a character other than a number, for example,
   /E:1024a.

ACTION: Change the call to COMMAND.COM to a valid environment size
for future use.  Because COMMAND.COM started, no immediate action is
needed.
;
;
SYS3004H: EXPLANATION: OS/2 does not support redirecting of standard input,
standard output, and standard error to any device other than the
console (default).

ACTION: If CTTY was used to start a new copy of COMMAND.COM, then the
call to COMMAND.COM needs to be changed.
;
;
SYS3005H: EXPLANATION: One of the following has occurred:
1. You tried to add a new variable or change an existing one
   with the SET command, but not enough space is available
   in the current environment to perform the operation.
2. Too small an environment space was specified with the
   COMMAND.COM /E option.

ACTION: Do one of the following:
1. Eliminate environment variables that are not needed.
2. Start COMMAND.COM and specify a larger environment size.
;
;
SYS3006H: EXPLANATION: A new copy of COMMAND.COM was started with the default
COMSPEC=\COMMAND.COM.  Also, the new COMMAND.COM does not inherit any
environment settings.

ACTION: Change the call to COMMAND.COM to a valid drive or path for
future use.  Because COMMAND.COM started, no immediate action is
needed.
;
;
SYS3007H: EXPLANATION: PATH= contains a reference to an invalid drive or path.

ACTION: Type PATH to display the current PATH= setting.  Correct the
invalid path or drive specification and retry the command.
;
;
SYS3008H: 
;
;
SYS3009H: 
;
;
SYS3010H: EXPLANATION: One of the following has occurred:
o  There is not enough memory to load COMMAND.COM.
o  The memory control blocks have been corrupted.

ACTION: Type EXIT to end the current copy of COMMAND.COM and retry the
operation.
;
;
SYS3011H: EXPLANATION: There is an internal error in the format of the .EXE file.
The program cannot be run as it now exists.

ACTION: Contact the supplier of the application.
;
;
SYS3012H: EXPLANATION: Not enough memory is available to process this command.

ACTION: Type EXIT to end the current copy of COMMAND.COM and retry the
operation.
;
;
SYS3013H: EXPLANATION: The attempt to start the .EXE or .COM file failed.
The problem is NOT one of the following error conditions:
o  File not found.
o  Access denied.
o  Insufficient memory.
o  Bad load module format.

The program cannot be run as it now exists.

ACTION: Contact the supplier of the application.
;
;
SYS3014H: EXPLANATION: The name specified should be for one of the following:
o  A DOS internal command.
o  A DOS external command.
o  An executable program with file extension .EXE or .COM.
o  A batch file whose file extension is .BAT.

Except for DOS internal commands, if a path for the command was not
specified at the command prompt, the file must reside in the current
directory or in one of the directories specified by PATH.

ACTION: Retry the command using a correct name or path.
;
;
SYS3015H: EXPLANATION: One of the following has occurred:
1. The COMMAND.COM specified by the COMSPEC environment variable
   cannot be found.
2. The COMMAND.COM specified by the COMSPEC environment variable is
   the wrong version of COMMAND.COM.
3. An error occurred while trying to read COMMAND.COM from disk.

ACTION: Do the following:
1. Type SET to display the current environment variables.
2. Ensure that the COMSPEC variable is specifying a valid version of
   COMMAND.COM.
3. Ensure that COMMAND.COM is the version loaded when the virtual
   DOS machine was started.

Note: You cannot change copies of COMMAND.COM by changing COMSPEC.
      You must load a secondary copy into memory.
;
;
SYS3016H: EXPLANATION: COMMAND.COM cannot be loaded from a permanent DOS session
using the /P option.  The session was halted because there is no
permanent copy of COMMAND.COM to return to.

ACTION: Close the DOS session.  No other activity can be performed.
Correct the COMSPEC variable to prevent this from occurring again.

Note: You cannot change copies of COMMAND.COM by changing COMSPEC.
      You must load a secondary copy into memory.
;
;
SYS3017H: EXPLANATION: COMMAND.COM could not be reloaded from a DOS session.  The
session was either a secondary copy of COMMAND.COM or a single command
option (/C).  In either case, the copy of COMMAND.COM is ended and you
are returned to the caller of COMMAND.COM.

ACTION: Correct the COMSPEC variable to prevent this from occurring
again.  Note that you cannot change copies of COMMAND.COM by changing
COMSPEC.  You must load a secondary copy into memory.
;
;
SYS3018H: 
;
;
SYS3019H: EXPLANATION: The BREAK, ECHO, or VER command tried to use a parameter
other than ON or OFF.

ACTION: Retry the command with the correct parameter.
;
;
SYS3020H: EXPLANATION: One or more devices failed during the selection of a
code page.

ACTION: Be sure the correct code page file is specified in the
CONFIG.SYS file.  You must restart the system to make the revised
CONFIG.SYS file active.
;
;
SYS3021H: EXPLANATION: You cannot use the binary option (/B) on a device.
Copying from devices only uses ASCII files.

ACTION: Retry the COPY command without /B after the source device name.
;
;
SYS3022H: EXPLANATION: The device cannot handle the number of bytes requested.

ACTION: Change the amount of data in the file and retry the operation.
;
;
SYS3023H: 
;
;
SYS3024H: EXPLANATION: A FOR statement cannot be used inside another FOR
statement.

ACTION: Remove the nested FOR and retry the operation.
;
;
SYS3025H: EXPLANATION: An invalid number of parameters was given to the command.

ACTION: Correct the number of parameters and retry the command.
Refer to the Command Reference for the correct number of parameters.
;
;
SYS3026H: 
;
;
SYS3027H: 
;
;
SYS3028H: 
;
;
SYS3029H: 
;
;
SYS3030H: EXPLANATION: The ASSIGN command requires two drive letters.
No action was taken because the second drive letter was missing.

ACTION: Retry ASSIGN and specify a second drive letter.
;
;
SYS3031H: EXPLANATION: The character is not valid as a drive specification
because it is not a letter or the drive is not available on this system.

ACTION: Retry ASSIGN and specify a valid drive letter.
;
;
SYS3032H: EXPLANATION: The character is not valid as a separator.  The only valid
separators are space, tab, line feed, and the following characters:
+  ,  =  ;

ACTION: Retry the ASSIGN command and specify a valid separator.
;
;
SYS3033H: EXPLANATION: The character specified is not valid with this command.

ACTION: Retry the command with a valid switch character.  For more
information about switches, refer to the Command Reference or go to
an OS/2 command prompt and type: HELP xxxxxx, where "xxxxxx" is the
name of the command you tried using with the switch.
;
;
SYS3034H: 
;
;
SYS3035H: 
;
;
SYS3036H: 
;
;
SYS3037H: 
;
;
SYS3038H: EXPLANATION: A drive cannot have its label altered if any of the
real-mode drive redirection commands (JOIN, SUBST, or ASSIGN) are
acting upon the drive.

ACTION: If you want to use LABEL, change the drive back to its default
setting and retry the LABEL command.
;
;
SYS3039H: 
;
;
SYS3040H: 
;
;
SYS3041H: 
;
;
SYS3042H: 
;
;
SYS3043H: 
;
;
SYS3044H: 
;
;
SYS3045H: 
;
;
SYS3046H: 
;
;
SYS3047H: 
;
;
SYS3048H: 
;
;
SYS3049H: 
;
;
SYS3050H: 
;
;
SYS3051H: 
;
;
SYS3052H: 
;
;
SYS3053H: 
;
;
SYS3054H: 
;
;
SYS3055H: 
;
;
SYS3056H: 
;
;
SYS3057H: 
;
;
SYS3058H: 
;
;
SYS3059H: 
;
;
SYS3060H: 
;
;
SYS3061H: 
;
;
SYS3062H: 
;
;
SYS3063H: 
;
;
SYS3064H: 
;
;
SYS3065H: 
;
;
SYS3066H: 
;
;
SYS3067H: 
;
;
SYS3068H: 
;
;
SYS3069H: 
;
;
SYS3070H: EXPLANATION: An internal memory-allocation strategy error occurred
when the system tried to use the LH or LOADHIGH command.

ACTION: Delete the command from the command line and retry the command.
;
;
SYS3071H: EXPLANATION: The path named in the command does not exist
for the drive specified or the path was entered incorrectly.

ACTION: Retry the command using the correct path.
;
;
SYS3072H: EXPLANATION: The required value following the switch character is
incorrect or missing.

ACTION: Correct the switch-character value and retry the command.
;
;
SYS3073H: EXPLANATION: DBCS characters are invalid switch-character values.

ACTION: Correct the switch-character value and retry the command.
;
;
SYS3074H: EXPLANATION: Read-only files cannot be deleted or altered in any
way, unless the read-only attribute is removed.

ACTION: To delete this file, use the ATTRIB command to remove the
read-only attribute.  Then, retry the ERASE or DEL command.
;
;
SYS3075H: EXPLANATION: The RENAME command cannot change the path of a file.

ACTION: Remove the path specified in the second parameter and retry
the command.
;
;
SYS3076H: EXPLANATION: The RENAME command cannot change the drive of a file.

ACTION: Remove the drive specified in the second parameter and retry
the command.
;
;
SYS3077H: 
;
;
SYS3078H: EXPLANATION: You must specify a file name when using the following
commands: RENAME, ERASE, or VMDISK.

ACTION: Specify a file name and retry the command.
;
;
SYS3079H: 
;
;
SYS3080H: 
;
;
SYS3081H: EXPLANATION: The file named in the command does not exist
in the current directory or search path specified, or the
file name was entered incorrectly.

ACTION: Retry the command using the correct file name.
;
;
SYS3082H: 
;
;
SYS3083H: EXPLANATION: Your request to add or modify a macro exceeds the buffer
space available.  To increase the buffer space, use the /BUFSIZE
option when starting a copy of DOSKEY.  The default buffer size is
512 bytes.

ACTION: To start a new buffer, type: DOSKEY /REINSTALL /BUFSIZE=n
where n equals the size of the buffer.  This will discard all command
history and macro definitions.
;
;
SYS3084H: EXPLANATION: A copy of DOSKEY is already installed in this DOS session.
However, it does not match the version of DOSKEY previously installed.

ACTION: To use this version of DOSKEY, you can force a reinstallation
with the DOSKEY /REINSTALL command.  Otherwise, you must use the
version of DOSKEY already installed in this DOS session.
;
;
SYS3085H: EXPLANATION: There is already a copy of DOSKEY installed in this
DOS session.  The BUFSIZE option can only be used the first time
DOSKEY is installed in memory or when DOSKEY is reinstalled.  The
default buffer size is 512 bytes.  If you reinstall, all command
history and macro definitions will be lost.

ACTION: To create a new DOSKEY buffer and specify a larger size, type:
  DOSKEY /REINSTALL /BUFSIZE=n
where n equals the size of the buffer.
;
;
SYS3086H: EXPLANATION: The DOSKEY command requires that an equal sign
be used in the following cases:
o  DOSKEY /BUFSIZE=n
o  DOSKEY macroname=text

ACTION: Retry the command using an equal sign.
;
;
SYS3087H: 
;
;
SYS3088H: EXPLANATION: The name specified should be for one of the following:
o  A DOS internal command.
o  A DOS external command.
o  An executable program with file extension .EXE or .COM.
o  A batch file whose file extension is .BAT.

Except for DOS internal commands, if a path for the command was not
specified at the command prompt, the file must reside in the current
directory or in one of the directories specified by PATH.

ACTION: Retry the command using a correct name or path.
;
;
SYS3089H: 
;
;
SYS3090H: 
;
;
SYS3091H: 
;
;
SYS3092H: 
;
;
SYS3093H: 
;
;
SYS3094H: 
;
;
SYS3095H: 
;
;
SYS3096H: 
;
;
SYS3097H: 
;
;
SYS3098H: 
;
;
SYS3099H: 
;
;
SYS3100H: 
;
;
SYS3101H: 
;
;
SYS3102H: 
;
;
SYS3103H: 
;
;
SYS3104H: 
;
;
SYS3105H: 
;
;
SYS3106H: 
;
;
SYS3107H: 
;
;
SYS3108H: 
;
;
SYS3109H: 
;
;
SYS3110H: 
;
;
SYS3111H: 
;
;
SYS3112H: 
;
;
SYS3113H: 
;
;
SYS3114H: 
;
;
SYS3115H: 
;
;
SYS3116H: 
;
;
SYS3117H: 
;
;
SYS3118H: 
;
;
SYS3119H: 
;
;
SYS3120H: 
;
;
SYS3121H: 
;
;
SYS3122H: 
;
;
SYS3123H: 
;
;
SYS3124H: 
;
;
SYS3125H: 
;
;
SYS3126H: 
;
;
SYS3127H: 
;
;
SYS3128H: 
;
;
SYS3129H: 
;
;
SYS3130H: 
;
;
SYS3131H: 
;
;
SYS3132H: 
;
;
SYS3133H: 
;
;
SYS3134H: 
;
;
SYS3135H: 
;
;
SYS3136H: 
;
;
SYS3137H: 
;
;
SYS3138H: 
;
;
SYS3139H: 
;
;
SYS3140H: 
;
;
SYS3141H: 
;
;
SYS3142H: 
;
;
SYS3143H: 
;
;
SYS3144H: 
;
;
SYS3145H: 
;
;
SYS3146H: EXPLANATION: The system cannot locate the OS2LDR.MSG file.

ACTION: If your system has stopped, contact either your system
administrator or your service representative.  The OS2LDR.MSG file can
be replaced with a valid non-corrupted version found on the
Installation diskette.
;
;
SYS3147H: EXPLANATION: The file was not of the correct form or has an incorrect
number of messages.

ACTION: The OS2LDR.MSG file will have to be replaced with a valid,
non-corrupted version found on the Installation diskette.
;
;
SYS3148H: 
;
;
SYS3149H: 
;
;
SYS3150H: 
;
;
SYS3151H: 
;
;
SYS3152H: 
;
;
SYS3153H: EXPLANATION: The number of files in this directory has exceeded the
internal structural limit for sorting.

ACTION: Create some subdirectories to reduce the number of files
in this directory.
;
;
SYS3154H: EXPLANATION: The specified environment variable contains an invalid
file specification or command option.

ACTION: Use the SET command to change the value of the environment
variable and retry the operation.
;
;
SYS3155H: 
;
;
SYS3156H: 
;
;
SYS3157H: 
;
;
SYS3158H: 
;
;
SYS3159H: 
;
;
SYS3160H: 
;
;
SYS3161H: 
;
;
SYS3162H: 
;
;
SYS3163H: 
;
;
SYS3164H: 
;
;
SYS3165H: 
;
;
SYS3166H: 
;
;
SYS3167H: 
;
;
SYS3168H: 
;
;
SYS3169H: 
;
;
SYS3170H: EXPLANATION: The process was ended because the program generated
an unhandled fatal user (non-system) exception through DosRaiseException.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3171H: EXPLANATION: The process was terminated without running exception
handlers because there was not enough room left on the stack to
dispatch the exception.  This is typically caused by exceptions
occurring in exception handlers.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3172H: EXPLANATION: The process was terminated without running exception
handlers because the system could not successfully dispatch the
exception.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3173H: EXPLANATION: A breakpoint exception occurred when a breakpoint
instruction was executed.  This exception is intended for use by
debuggers.

ACTION: If you purchased this program, contact the supplier of the
program. If you are the developer of this program, refer to the
information in the register.
;
;
SYS3174H: EXPLANATION: A single-step exception was generated when a trace trap
or other single instruction execution mechanism signaled that one
instruction was executed.  This exception is intended for use by
debuggers.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3175H: EXPLANATION: An access violation exception occurred and was generated
when an attempt was made either to load or store data in an inaccessible
location or to execute an inaccessible instruction.  This exception
corresponds to both the Intel 80386 processor general protection fault
(#13), caused by an invalid access attempt, and the page fault (#14),
caused by an attempt to access an uncommitted page or a page with
incorrect attributes for the desired operation.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3176H: EXPLANATION: An illegal instruction exception was generated when an
attempt was made to execute an instruction whose operation was not
defined for the host machine architecture.  On the Intel 80386**
processor, this corresponds to the invalid opcode fault (#6), caused
by an invalid instruction.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3177H: EXPLANATION: A denormalized operand exception occurred when the
80387 NPX** processor attempted an arithmetic operation on a denormal
operand, and the user had not masked off denormal operations.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3178H: EXPLANATION: A floating divide-by-zero exception was generated
when at attempt was made to divide a floating-point dividend by
a floating-point divisor of zero.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3179H: EXPLANATION: A loss of precision exception occurred when the result
of an operation was not exactly representable in the destination
format.  For example, the fraction 1/3 cannot be exactly represented
in binary form.  For the Intel 80386** and 80387** processors, this
corresponds to one of the class of exceptions for which the 80387
processor signals the 80386 processor to raise trap #16.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3180H: EXPLANATION: This exception usually indicates a programming error
corresponding to the invalid floating-point operations defined in IEEE
Standard 754.  The Intel 80386** processor raises trap #16.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3181H: EXPLANATION: A floating overflow exception was generated when the
resulting exponent of a floating-point operation was greater than the
magnitude allowed for the respective floating point data type.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3182H: EXPLANATION: An invalid floating-point stack check was raised when a
floating-point processor attempted an illegal operation on a private
stack.  This is one of the class of exceptions for which the Intel
80387** processor signals the Intel 80386** processor to raise trap #16.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3183H: EXPLANATION: A floating underflow exception was generated when the
resulting exponent of a floating-point operation was less than the
magnitude provided for the respective floating-point data type.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3184H: EXPLANATION: An integer divide-by-zero exception was generated when
an attempt was made to divide an integer dividend by an integer divisor
of zero.  On the Intel 80387** processor, this is a divide by zero
fault (#0) caused by a DIV or IDIV by zero operation.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3185H: EXPLANATION: An integer overflow exception was generated when the
result of an integer operation caused a carry-out of the most
significant bit of the result, which was not the same as the carry-into
of the most significant bit of the result.  For example, the addition
of two positive integers produces a negative result.  On the Intel
80387** processor, this corresponds to overflow trap (#4) caused by
executing an INTO instruction with the OF flag set.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3186H: EXPLANATION: A privileged instruction exception was generated when an
attempt was made to execute an instruction whose operation is not
allowed in the current machine mode.  For example, an attempt was made
to execute an instruction in user mode that is only allowed in kernel
mode.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3187H: EXPLANATION: A page read error exception was generated when an attempt
was made to read a page into memory and an I/O error was encountered.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3188H: EXPLANATION: This exception was raised when an exception handler
returned XCPT_CONTINUE_EXECUTION in response to a noncontinuable
exception.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3189H: EXPLANATION: This exception was raised when an exception handler
returned something besides XCPT_CONTINUE_EXECUTION or
XCPT_CONTINUE_SEARCH.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3190H: EXPLANATION: An invalid lock sequence exception was generated when an
attempt was made to execute an operation within an interlocked section
of code and the sequence was invalid for the host machine architecture.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3191H: EXPLANATION: The bounds check exception corresponds to the Intel
80386** bounds check fault (#5) caused by a BOUND instruction that
fails.

ACTION: If you purchased this program, contact the supplier of the
program.  If you are the developer of this program, refer to the
information in the register.
;
;
SYS3192H: EXPLANATION: An invalid path or an unrecognized parameter was entered
on the UNDELETE command line.

ACTION: Correct the path specification or refer to the Command
Reference for more information about the correct UNDELETE parameters.
;
;
SYS3193H: 
;
;
SYS3194H: EXPLANATION: The DELDIR environment variable specifies a temporary
storage directory for each drive that supports the UNDELETE command.
If this environment variable is not present or is entered incorrectly,
the UNDELETE command will not be active for the affected drive.

ACTION: To activate the UNDELETE command for a drive, add the
appropriate DELDIR environment parameters to your CONFIG.SYS file.
Refer to the Command Reference for more information.
;
;
SYS3195H: 
;
;
SYS3196H: 
;
;
SYS3197H: EXPLANATION: UNDELETE found an unrecognized version of the system
control file in the temporary storage directory of the specified disk.

ACTION: Use the appropriate version of UNDELETE to process files on
this disk.
;
;
SYS3198H: 
;
;
SYS3199H: 
;
;
SYS3200H: EXPLANATION: An error occurred while trying to restore a deleted file
to its original path.

ACTION: Make sure that the disk or diskette is not damaged and retry
the command.
;
;
SYS3201H: EXPLANATION: An error occurred while trying to permanently discard a
file in the temporary storage directory.

ACTION: Make sure that the disk or diskette is not damaged and retry
the command.
;
;
SYS3202H: 
;
;
SYS3203H: EXPLANATION: No files matching the specified path were found.

ACTION: For a list of recoverable files on the desired disk, type:
UNDELETE [drive:]\* /L /S
;
;
SYS3204H: 
;
;
SYS3205H: 
;
;
SYS3206H: EXPLANATION: An error occurred while trying to restore the
path of a previously deleted file.  The file cannot be processed.

ACTION: Do one of the following and retry the command:
o  Check that the disk or diskette is not damaged.
o  Make sure that the disk is not full.
o  Make sure that the you have not reached the maximum number of
   directories.
;
;
SYS3207H: 
;
;
SYS3208H: 
;
;
SYS3209H: 
;
;
SYS3210H: 
;
;
SYS3211H: 
;
;
SYS3212H: 
;
;
SYS3213H: 
;
;
SYS3214H: 
;
;
SYS3215H: 
;
;
SYS3216H: 
;
;
SYS3217H: 
;
;
SYS3218H: 
;
;
SYS3219H: 
;
;
SYS3220H: 
;
;
SYS3221H: 
;
;
SYS3222H: 
;
;
SYS3223H: 
;
;
SYS3224H: 
;
;
SYS3225H: 
;
;
SYS3226H: 
;
;
SYS3227H: 
;
;
SYS3228H: 
;
;
SYS3229H: 
;
;
SYS3230H: 
;
;
SYS3231H: 
;
;
SYS3232H: 
;
;
SYS3233H: 
;
;
SYS3234H: 
;
;
SYS3235H: 
;
;
SYS3236H: 
;
;
SYS3237H: 
;
;
SYS3238H: 
;
;
SYS3239H: 
;
;
SYS3240H: 
;
;
SYS3241H: 
;
;
SYS3242H: 
;
;
SYS3243H: 
;
;
SYS3244H: 
;
;
SYS3245H: 
;
;
SYS3246H: 
;
;
SYS3247H: 
;
;
SYS3248H: 
;
;
SYS3249H: 
;
;
SYS3250H: 
;
;
SYS3251H: 
;
;
SYS3252H: 
;
;
SYS3253H: 
;
;
SYS3254H: 
;
;
SYS3255H: 
;
;
SYS3256H: 
;
;
SYS3257H: 
;
;
SYS3258H: 
;
;
SYS3259H: 
;
;
SYS3260H: 
;
;
SYS3261H: 
;
;
SYS3262H: 
;
;
SYS3263H: 
;
;
SYS3264H: 
;
;
SYS3265H: 
;
;
SYS3266H: 
;
;
SYS3267H: 
;
;
SYS3268H: 
;
;
SYS3269H: 
;
;
SYS3270H: 
;
;
SYS3271H: 
;
;
SYS3272H: 
;
;
SYS3273H: 
;
;
SYS3274H: 
;
;
SYS3275H: 
;
;
SYS3276H: 
;
;
SYS3277H: 
;
;
SYS3278H: 
;
;
SYS3279H: 
;
;
SYS3280H: 
;
;
SYS3281H: 
;
;
SYS3282H: 
;
;
SYS3283H: 
;
;
SYS3284H: 
;
;
SYS3285H: 
;
;
SYS3286H: 
;
;
SYS3287H: 
;
;
SYS3288H: 
;
;
SYS3289H: 
;
;
SYS3290H: 
;
;
SYS3291H: 
;
;
SYS3292H: 
;
;
SYS3293H: 
;
;
SYS3294H: 
;
;
SYS3295H: 
;
;
SYS3296H: 
;
;
SYS3297H: 
;
;
SYS3298H: 
;
;
SYS3299H: 
;
;
SYS3300H: 
;
;
SYS3301H: 
;
;
SYS3302H: 
;
;
SYS3303H: 
;
;
SYS3304H: 
;
;
SYS3305H: 
;
;
SYS3306H: 
;
;
SYS3307H: 
;
;
SYS3308H: 
;
;
SYS3309H: 
;
;
SYS3310H: 
;
;
SYS3311H: 
;
;
SYS3312H: 
;
;
SYS3313H: 
;
;
SYS3314H: 
;
;
SYS3315H: 
;
;
SYS3316H: 
;
;
SYS3317H: 
;
;
SYS3318H: 
;
;
SYS3319H: 
;
;
SYS3320H: 
;
;
SYS3321H: 
;
;
SYS3322H: EXPLANATION: Configuration memory does not contain the correct
information for your hardware configuration (setup).

ACTION: Insert into drive A either the Reference or System
Configuration diskette that came with your hardware.  This
should restart your system.  If this error continues,
contact your hardware sales or service representative.
;
;
SYS3323H: 
;
;
SYS3324H: 
;
;
SYS3325H: 
;
;
SYS3326H: 
;
;
SYS3327H: 
;
;
SYS3328H: 
;
;
SYS3329H: 
;
;
SYS3330H: 
;
;
SYS3331H: 
;
;
SYS3332H: 
;
;
SYS3333H: 
;
;
SYS3334H: 
;
;
SYS3335H: 
;
;
SYS3336H: 
;
;
SYS3337H: 
;
;
SYS3338H: 
;
;
SYS3339H: 
;
;
SYS3340H: 
;
;
SYS3341H: 
;
;
SYS3342H: 
;
;
SYS3343H: 
;
;
SYS3344H: 
;
;
SYS3345H: 
;
;
SYS3346H: 
;
;
SYS3347H: 
;
;
SYS3348H: 
;
;
SYS3349H: 
;
;
SYS3350H: 
;
;
SYS3351H: 
;
;
SYS3352H: 
;
;
SYS3353H: 
;
;
SYS3354H: 
;
;
SYS3355H: 
;
;
SYS3356H: 
;
;
SYS3357H: 
;
;
SYS3358H: EXPLANATION: The drive specified in the TRAPDUMP statement in
CONFIG.SYS specifies an invalid volume or a volume
which resides beyond cylinder 1023 on your disk.

ACTION: Edit the TRAPDUMP statement in CONFIG.SYS and specify
a valid volume which resides below cylinder 1024.
;
;
SYS3359H: 
;
;
SYS3360H: 
;
;
SYS3361H: 
;
;
SYS3362H: 
;
;
SYS3363H: 
;
;
SYS3364H: 
;
;
SYS3365H: 
;
;
SYS3366H: 
;
;
SYS3367H: 
;
;
SYS3368H: 
;
;
SYS3369H: 
;
;
SYS3370H: 
;
;
SYS3371H: 
;
;
SYS3372H: 
;
;
SYS3373H: 
;
;
SYS3374H: 
;
;
SYS3375H: 
;
;
SYS3376H: 
;
;
SYS3377H: 
;
;
SYS3378H: 
;
;
SYS3379H: 
;
;
SYS3380H: 
;
;
SYS3381H: 
;
;
SYS3382H: 
;
;
SYS3383H: 
;
;
SYS3384H: 
;
;
SYS3385H: 
;
;
SYS3386H: 
;
;
SYS3387H: 
;
;
SYS3388H: 
;
;
SYS3389H: 
;
;
SYS3390H: 
;
;
SYS3391H: 
;
;
SYS3392H: 
;
;
SYS3393H: 
;
;
SYS3394H: 
;
;
SYS3395H: 
;
;
SYS3396H: EXPLANATION: KEYBGK only works for code pages 813 and 869.  It is intended
for use only with Greek keyboards and code pages.
ACTION: Change code page and retry the command.
;
;
SYS3397H: EXPLANATION: The system has detected that KEYBGK is already installed.
ACTION: No action needed, KEYBGK already installed.
;
;
SYS3398H: 
;
;
SYS3399H: 
;
;
SYS3400H: 
;
;
SYS3401H: 
;
;
SYS3402H: 
;
;
SYS3403H: 
;
;
SYS3404H: 
;
;
SYS3405H: 
;
;
SYS3406H: 
;
;
SYS3407H: 
;
;
SYS3408H: 
;
;
SYS3409H: 
;
;
SYS3410H: 
;
;
SYS3411H: 
;
;
SYS3412H: 
;
;
SYS3413H: 
;
;
SYS3414H: 
;
;
SYS3415H: 
;
;
SYS3416H: 
;
;
SYS3417H: 
;
;
SYS3418H: 
;
;
SYS3419H: 
;
;
SYS3420H: 
;
;
SYS3421H: 
;
;
SYS3422H: 
;
;
SYS3423H: 
;
;
SYS3424H: 
;
;
SYS3425H: 
;
;
SYS3426H: 
;
;
SYS3427H: 
;
;
SYS3428H: 
;
;
SYS3429H: 
;
;
SYS3430H: 
;
;
SYS3431H: 
;
;
SYS3432H: 
;
;
SYS3433H: 
;
;
SYS3434H: 
;
;
SYS3435H: 
;
;
SYS3436H: 
;
;
SYS3437H: 
;
;
SYS3438H: 
;
;
SYS3439H: 
;
;
SYS3440H: 
;
;
SYS3441H: 
;
;
SYS3442H: 
;
;
SYS3443H: 
;
;
SYS3444H: 
;
;
SYS3445H: 
;
;
SYS3446H: 
;
;
SYS3447H: 
;
;
SYS3448H: 
;
;
SYS3449H: 
;
;
SYS3450H: 
;
;
SYS3451H: 
;
;
SYS3452H: 
;
;
SYS3453H: 
;
;
SYS3454H: 
;
;
SYS3455H: 
;
;
SYS3456H: 
;
;
SYS3457H: 
;
;
SYS3458H: 
;
;
SYS3459H: 
;
;
SYS3460H: 
;
;
SYS3461H: 
;
;
SYS3462H: 
;
;
SYS3463H: 
;
;
SYS3464H: 
;
;
SYS3465H: 
;
;
SYS3466H: 
;
;
SYS3467H: 
;
;
SYS3468H: 
;
;
SYS3469H: 
;
;
SYS3470H: 
;
;
SYS3471H: 
;
;
SYS3472H: 
;
;
SYS3473H: 
;
;
SYS3474H: 
;
;
SYS3475H: 
;
;
SYS3476H: 
;
;
SYS3477H: 
;
;
SYS3478H: 
;
;
SYS3479H: 
;
;
SYS3480H: 
;
;
SYS3481H: 
;
;
SYS3482H: 
;
;
SYS3483H: 
;
;
SYS3484H: 
;
;
SYS3485H: 
;
;
SYS3486H: 
;
;
SYS3487H: 
;
;
SYS3488H: 
;
;
SYS3489H: 
;
;
SYS3490H: 
;
;
SYS3491H: 
;
;
SYS3492H: 
;
;
SYS3493H: 
;
;
SYS3494H: 
;
;
SYS3495H: 
;
;
SYS3496H: 
;
;
SYS3497H: 
;
;
SYS3498H: 
;
;
SYS3499H: 
;
;
SYS3500H: 
;
;
SYS3501H: 
;
;
SYS3502H: 
;
;
SYS3503H: 
;
;
SYS3504H: 
;
;
SYS3505H: 
;
;
SYS3506H: %0
