Liren Large Software Subsidy 14/14.iso/s/s003/5.ddi/BUNDLE/OS2_SYSTEM_OSO001H.MSG

OS/2 Message File | 1992-03-30 | 231.6 KB | 4,433 lines

MKMSGF
oso001h.msg
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The maximum number of open files
has been reached.
ACTION: Wait until another program has ended.
Then retry the command.
HEXPLANATION:  One of the following has occurred:
1. The file is marked read-only.
2. The resource, such as 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 installed and you tried
   to access a resource or perform an action for which you do
   not have sufficient privilege.
4. The filename is incorrect.
ACTION:  Do one of the following; then, retry the command:
1. Use the ATTRIB command to change the read-only attribute.
2. Try to access the resource again 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 filename.
HEXPLANATION: 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:
1. Reduce the number of running programs.
2. Reduce the value of the BUFFERS=, TRACEBUF=, DISKCACHE=,
   THREADS=, RMSIZE=, or DEVICE=VDISK.SYS statement
   in the CONFIG.SYS file. Then restart the system.
3. Remove unwanted files from the swap file disk and restart
   the system.
4. Install additional memory on your system.
5. Check the swap file disk for an I/O error.
HEXPLANATION: One of the following has occurred:
1. The drive specified 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 situation 3, you are not
allowed to RESTORE to a redirected drive.
HEXPLANATION: 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, then retry the command:
1. Correct the directory name.
2. Remove all files and subdirectories from the directory.
3. Use the 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.
HEXPLANATION: 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.
HEXPLANATION: 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; then, retry the command.
HEXPLANATION: An unknown device was specified.
ACTION: Retry the command using a correct
device name.
HEXPLANATION: One of the following errors occurred:
1. The drive is empty.
2. The drive door is open.
3. The drive is in use.
ACTION: Do one of the following:
1. Insert a diskette in the drive and retry the command.
2. Close the drive door and retry the command.
3. Wait until the drive is available and retry the command.
HEXPLANATION: 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.
HEXPLANATION: The disk may be damaged, unformatted,
or not compatible with the operating system.
ACTION: Do one of the following:
1. Make sure the diskette is properly inserted.
2. Check that the disk is not damaged.
3. Format the disk for the operating system.
HEXPLANATION: The disk or diskette is not properly formatted
for the operating system.
ACTION: Format the disk or diskette for the operating system.
HEXPLANATION: The disk/diskette may be damaged, unformatted,
or not compatible with the operating system.
ACTION: Retry the command after you do one of the following:
1. Make sure the diskette is properly inserted.
2. Use CHKDSK to check that the disk is not damaged.
3. Format the disk/diskette for the operating system.
   Warning: When you format a disk/diskette, any information
   that was previously on the disk/diskette is erased.
4. Check to be sure you do not have a high density diskette
   in a low density diskette drive.
HEXPLANATION: One of the following has occurred:
1. There is no paper in the printer.
2. There is not enough disk space to create a spool file.
   NOTE: If printing to a LAN server, the server's disk
         is full.
ACTION: Do one of the following:
1. Make sure the printer is loaded properly with paper.
2. Make sure the printer is switched on.
3. Make sure the printer is installed and connected.
4. Delete any unnecessary files from the disk that
   contains the spool directory; then, retry the command.
HEXPLANATION: The operating system detected an
error while writing to this device.
ACTION: Make sure the device is:
1. Installed and connected
2. Switched on
3. Not being used by another process
4. In the proper receive mode
5. Formatted if the device is a disk.
Retry the command.
HEXPLANATION: The operating system detected an
error while reading from this device.
ACTION: Make sure the device is:
1. Installed and connected
2. Switched on
3. Not being used by another process
4. In the proper send mode
5. Formatted if the device is a disk.
Retry the command.
HEXPLANATION: An attached device is not working for one of
these reasons:
1.  It is switched off, or connected improperly
2.  The diskette and drive types are incompatible.
3.  The diskette is not properly inserted in the drive.
4.  The drive door is open.
5.  The diskette is not properly formatted.
ACTION: Correct the problem and retry the command.
HEXPLANATION: The file is already being used by another process.
ACTION: Retry the command later.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The maximum number of files in the sharing buffer
has temporarily been exceeded.
ACTION: Retry the command when fewer programs are running.
HEXPLANATION: You tried to write to a diskette, but it is
write-protected.
ACTION: Make sure that the proper diskette is being used,
or remove the write protection. Retry the command.
HEXPLANATION: An unknown device was specified.
ACTION: Retry the command using a correct device name.
HEXPLANATION: One of the following has occurred:
1. The device is not ready or is empty.
2. The device driver for COMx is not installed or COMx was
shut down, and further use of COMx is disabled.
ACTION: Do one of the following and retry the command:
1. Insert a diskette in the drive; close the drive door; or, wait
   until the drive is available.
2. a. Check the CONFIG.SYS file for the COMx DEVICE= statement.
   b. Shut down the system; during restart, note and refer to any
      messages regarding COMx.
   d. Issue MODE COMx from a command prompt to see if COMx exists.
3. Be sure there is hardware for COMx.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: There is no paper in the printer.
ACTION: Make sure the printer is:
1. Loaded properly with paper.
2. Switched on.
3. Installed and connected.
HEXPLANATION: The operating system detected an error while
writing to this device.
ACTION: Make sure the device is:
1. Installed, connected, and switched on
2. Not being used by another process
3. In the proper receive mode
4. Formatted if the device is a disk.
Retry the command.
HEXPLANATION: The operating system detected an error while reading
from this device.
ACTION: Make sure the device is:
1. Installed, connected, and switched on
2. Not being used by another process
3. In the proper send mode
4. Formatted if the device is a disk.
Retry the command.
HEXPLANATION: An attached device is not working for one of these
reasons:
1.  It is switched off, or connected improperly.
2.  The diskette and drive types are incompatible.
3.  The diskette is not properly inserted in the drive.
4.  The drive door is open.
5.  The diskette is not properly formatted.
ACTION: Correct the problem and retry the command.
HEXPLANATION: 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, then retry the
command.
If you continue to have problems, contact your network
administrator to ensure that the correct software is
installed on your workstation.
HEXPLANATION: 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 then retry the
operation:
1. Specify the correct remote computer name.
2. Ensure that the specified remote computer is available.
If none of the above actions correct the problem, contact
your network administrator.
HEXPLANATION: 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, then retry the
command.
HEXPLANATION: The server that you specified does not exist or
has not been started.
ACTION: Do one of the following:
1. Verify that you specified the path name correctly,
   then retry the command.
2. Verify that the server specified is started, then retry the
   command.
3. Contact your network administrator if you continue to have
   problems.
HEXPLANATION: 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.
HEXPLANATION: The specified resource is not available.
The computer that shared the resource might have been turned
off, or the permissions might have been changed.
ACTION: Do one of the following:
1. Check to see that the computer sharing resources is turned
   on, then retry the command.
2. Contact your network administrator to find out how
   you can use the resource.
HEXPLANATION: 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.
HEXPLANATION: 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, then retry the command.
If you continue to have problems, contact your network
administrator or the manufacturer of the network hardware.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The printer cannot take any additional print
requests at this time.
ACTION: Retry the command at a later time.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The network resource that you specified was either
temporarily taken off-line or is no longer available.
It is possible that:
1. The share at the server might have been temporarily deleted.
2. The server that shared the resource might have been turned off.
3. The permissions might have been changed.
ACTION: Retry the operation.  If you continue to have difficulty accessing
the resource:
1. Contact the person who administers the server to find
   out why it is no longer available.
2. Contact the network administrator.
HEXPLANATION: You attempted to access a resource that is not
available to you. It is possible that:
1. You do not have a valid account on the server sharing the
   resource.
2. 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, then retry the command.
If you are still denied access, contact your network
administrator.
HEXPLANATION: The network directory or device name that you
specified is not correct.
ACTION: Retry the command using the correct network
directory or device name. Your possible choices are:
o  Directory Device Names:         A: through Z:
o  Printer Device Names:           LPT1: through LPT9:
o  Communications Device Names:    COM1: through COM9:
HEXPLANATION: The specified network name is not correct.
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, then retry the command.
If you continue to have problems, contact your network
administrator.
HEXPLANATION: The number of names allowed on the network
adapter card for the local computer was exceeded.
ACTION: Perform one of the following actions, and then retry the
operation:
1. Disconnect from any resources that you are not
   currently using.
2. Reconfigure the network adapter card.
If none of the above actions correct the problem, contact
your network administrator.
HEXPLANATION: Your computer network adapter card has too
many NETBIOS sessions currently active.
ACTION: Disconnect from any resources that you are not
currently using; then retry the command. Contact your
network administrator if you continue to have problems.
HEXPLANATION: 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.
HEXPLANATION: One of the following occurred:
1. The specified server cannot support the network
   request.
2. The server might have run out of network resources
   such as memory, network buffers, or netbios commands necessary
   to process your request.
3. 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.
HEXPLANATION: The printer or disk device that you specified has
been paused.
ACTION: Use the NET CONTINUE command to reactivate the device;
then, retry the command.
HEXPLANATION: 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.
HEXPLANATION: An attached device is not working for one of
these reasons:
1.  It is switched off, or connected improperly
2.  The diskette and drive types are incompatible.
3.  The diskette is not properly inserted in the drive.
4.  The drive door is open.
5.  The diskette is not properly formatted.
ACTION: Correct the problem and retry the command.
HEXPLANATION: 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;
then, close it.
HEXPLANATION: One of the following errors occurred:
1.  The file or directory name already exists.
2.  The directory path cannot be found.
3.  The root directory is full or there is not enough
    space on the disk for the new file or directory.
4.  The directory name contains unacceptable OS/2
    characters or is a reserved file name.
5.  The disk is not properly formatted.
ACTION: Correct the problem and retry the command.
HEXPLANATION: The system has more requests to process than it
can currently handle.
ACTION: Try the request again later.
HEXPLANATION: You specified a resource with a local device
name that is already being used.
ACTION: Try the request again, using a different device name.
Your possible choices are:
o  Directory Device Names:         A: through Z:
o  Printer Device Names:           LPT1: through LPT9:
o  Communications Device Names:    COM1: through COM9:
HEXPLANATION: The password that you specified is not correct
for the account or resource you attempted to access.
ACTION: Specify the correct password. Contact your network
administrator if you continue to have problems.
HEXPLANATION: 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.
HEXPLANATION: The maximum number of running processes
has been reached.
ACTION: End a process or retry the command after the
current process has completed.
HEXPLANATION: The device requested is not available.
One of the following has occurred:
1. The device is already being used by another application.
2. 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:
1. Retry the command at a later time.
2. Reconfigure the COM port using the Reference Diskette.
   Set the Serial Transmit and Serial Receive Arbitration Levels
   to a shared number or dedicated number that is not in conflict
   with another port.
HEXPLANATION: All of the system semaphore slots have been used.
Another system semaphore cannot be created until
one has been freed.
ACTION: Try again later.
HEXPLANATION: This is an exclusive system semaphore, and only
the owner can modify it.
ACTION: End your requested operation.
HEXPLANATION: A semaphore cannot be closed while it is set.
ACTION: Release the semaphore, or wait for it to be
released; then, close it.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The new file name exceeds 255 characters.
ACTION: Rename the file using a shorter file name.
HEXPLANATION: The disk or diskette being
written to has no more room.
ACTION: Delete some unwanted files and
retry the command.
HEXPLANATION: 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 try the
command again.
HEXPLANATION: The requested module is not loaded.
ACTION: Check which module is being requested, and make
sure that it has been loaded.
HEXPLANATION: 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.
HEXPLANATION: The drive specified is being used by
another process.
ACTION: Retry the command later.
HEXPLANATION: The directory specified in the JOIN
command must be a subdirectory of the root directory.
ACTION: Retry the command specifying a different directory.
HEXPLANATION: The JOIN command requires that
the directory be empty.
ACTION: Retry the command specifying an empty
directory.
HEXPLANATION: An attempt was made to join to a
path which is being used in a substitute.
ACTION: Retry the command specifying a different path.
HEXPLANATION: All available storage is in use.
If segment swapping is active, the swap file may be full.
ACTION: Do one of the following and retry the command:
1. Reduce the number of running programs.
2. Reduce the value of the BUFFERS=, TRACEBUF=, DISKCACHE=,
   THREADS=, RMSIZE=, or DEVICE=VDISK.SYS statement
   in the CONFIG.SYS file. Then restart the system.
3. Remove unwanted files from the swap file disk and restart
   the system.
4. Install additional memory on your system.
5. Contact the supplier of the application.
HEXPLANATION: The path specified is being used
by the current process or another process.
ACTION: Retry the command later.
HEXPLANATION: The CONFIG.SYS file does not contain a TRACE= or
TRACEBUF= statement, or tracing is disallowed by the trace
utility.
ACTION: Check your CONFIG.SYS file to determine if the statement
for either the TRACE= or TRACEBUF= is present. If neither is
present, add the appropriate statement to your CONFIG.SYS file.
If the CONFIG.SYS contains one of the statements, use the TRACE
utility to allow tracing.
HEXPLANATION: Either no event or too many events were
specified in a call to DosMuxSemWait.
ACTION: Correct the event count.
HEXPLANATION: All of the system slots for DosMuxSemWait
semaphores have been taken. Another semaphore cannot be
accommodated until a slot is freed.
ACTION: Try again later.
HEXPLANATION: The list passed to DosMuxSemWait is not in the
proper format.
ACTION: Correct the format of the DosMuxSemWait list.
HEXPLANATION: 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.
HEXPLANATION: The signal sent was not handled by the recipient.
ACTION: Make sure the recipient can handle the signal sent,
or try a different signal.
HEXPLANATION: The thread ID address passed to DosCreateThread
was not correct.
ACTION: Correct the thread ID address.
HEXPLANATION: The argument (command parameters) string passed to
DosExecPgm was not in the proper format.
ACTION: Correct the argument string.
HEXPLANATION: This signal could not be posted because the process
has another signal to process.
ACTION: Try again at a later time.
HEXPLANATION: 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.
HEXPLANATION: The operations has failed because the network has not been
installed.
ACTION: Install the appropriate network.
HEXPLANATION: 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.
HEXPLANATION: The DLL or EXE file contains a segment number that is
not correct, or the file is unusable.
ACTION: Do one of the following; then retry the command.
1. Restart the system.
2. Replace the DLL or EXE file.
HEXPLANATION: 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.
HEXPLANATION: The flag passed to the JOIN command or to
DosFlagProcess was not correct.
ACTION: Correct the flags.
HEXPLANATION: The specified system semaphore name was not found.
ACTION: Make sure the semaphore name is correct and try again.
HEXPLANATION: The application program does not
have a correct END <label> directive.
ACTION: Contact the supplier of the application.
HEXPLANATION: The application program does not
contain a correct stack segment.
ACTION: Contact the supplier of the application.
HEXPLANATION: A dynamic link library file cannot
be used as an application program . An application
cannot be used as a dynamic link library.
ACTION: Reinstall the application and retry the command.
If the error occurs again, contact the supplier of the
application program.
HEXPLANATION: 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.
HEXPLANATION: LINK detected errors when this
application program was created.
ACTION: Contact the supplier of the application.
HEXPLANATION: 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.
HEXPLANATION: One of the segments in the specified
file contains more than 64KB of data.
ACTION: Contact the supplier of the application
program.
HEXPLANATION: 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.
HEXPLANATION: Routines that run in ring 2 to utilize
I/O privileges cannot link to dynamic link libraries.
ACTION: Contact the supplier of the application.
HEXPLANATION: The program requires input/output
privilege and the system is not configured to
allow it.
ACTION: Edit the CONFIG.SYS file to contain
the statement IOPL=YES.  Restart the system and
try the command again.
HEXPLANATION: 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.
HEXPLANATION: The program's autodata segment
exceeds 64KB.
ACTION: Contact the supplier of the application.
HEXPLANATION: The relocation-chain for a segment
exceeds the segment limit.
ACTION: Contact the supplier of the application
program.
HEXPLANATION: The system has detected an infinite loop
in the relocation-chain segment.
ACTION: Contact the supplier of the application
program.
HEXPLANATION: The length of the file name or the extension
is greater than the maximum length allowed.
ACTION: Correct the file name or the extension; then retry
the command.  For more information about file names, refer
Naming Files in the Master Index.
HEXPLANATION: The signal number is not correct or a Presentation
Manager application is trying to set SIGINTR or SIGBREAK, which
is not allowed. Possible signal numbers are:
   1     (SIGINTR)  Ctrl C
   3     (SIGTERM)  Program terminated
   4     (SIGBREAK) Ctrl Break
   5     Process flag A
   6     Process flag B
   7     Process flag C
ACTION: Correct the signal number.
HEXPLANATION: Signal handlers cannot be set when a process is
ending.
ACTION: Allow the process to end without setting a handler.
HEXPLANATION: 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.
HEXPLANATION: The Exitlist routine address must be at ring 3.
ACTION: Correct the Exitlist routine address.
HEXPLANATION: The specified PM session ID does not appear in the
Window List.  One of the following has occurred:
  1. The application window was created without the FCF_TASKLIST style.
  2. The application window has not yet been created.
  3. The application window has been destroyed.
ACTION: Refer to WinCreateStdWindow and Frame Control Window
Processing in the Presentation Manager Technical Reference.
HEXPLANATION: DosCwait 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.
HEXPLANATION: A pipe operation cannot be performed on a
file that does not refer to a pipe.
ACTION: Contact the supplier of the application.
HEXPLANATION: The pipe cannot be accessed because
another process is using it.
ACTION: Try the operation again later.
HEXPLANATION: The specified pipe was disconnected
at its other end.
ACTION: Try the program again later.
HEXPLANATION: 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.
HEXPLANATION: Transmission errors caused the connection
to the remote machine to be disconnected.
ACTION: Run the application again to re-establish the
connection.
HEXPLANATION: The network specified is not registered.
ACTION: Retry this operation using a correct network name.
HEXPLANATION: You attempted to register a name that has already been
used.
ACTION: Try another name, or contact your system administrator.
HEXPLANATION: You cannot move or rename a parent directory to
one of its subdirectories. Such an action would cause a loop in the
directory tree.
ACTION: Check that you have chosen the correct directories. Then,
retry the command.
HEXPLANATION: The move or rename operation is not allowed.
Possible reasons why the operation is not allowed are:
1. COMMAND.COM or CMD.EXE is at the prompt in the source directory.
2. The source directory specified is in use.
3. The directory is part of a SUBST or JOIN macro.
ACTION: Do one of the following:
1. Determine if COMMAND.COM or CMD.EXE is in the source directory.
   If so, change the directory then retry the command.
2. 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 then retry the command.
3. Remove the directory from the SUBST or JOIN macro.
HEXPLANATION: The specified file system name could not be found.
ACTION: Do one of the following:
1. Try the operation again using the correct file system name.
2. Add the IFS= statement (containing the correct file system name)
   to the CONFIG.SYS file and restart your system.
3. Contact the supplier of the application.
HEXPLANATION: The device name could not be found in the specified
path.
ACTION: Try the operation again using the correct device name and
path, or contact the supplier of the application.
HEXPLANATION: The extended attribute name contains character that
is not correct.
ACTION: Correct the extended attribute name and try the operation
again.
HEXPLANATION: The extended attribute list size does not match the
size that was specified.
ACTION: Correct the extended attribute list size and try the
operation again, or contact the supplier of the application.
HEXPLANATION: The extended attribute list is too long.
ACTION: Use a shorter extended attribute list, or contact the
supplier of the application.
HEXPLANATION: The application program timeout did not allow the
requested number of changes to occur.
ACTION: Contact the supplier of the application.
HEXPLANATION: A system directory search structure has been reused
and is now no longer valid.
ACTION: End the operation.
HEXPLANATION: The stack size indicated in a DevHlp_RegisterStackUsage
call was too large.
ACTION: Request and use a smaller of stack.
HEXPLANATION: The attributes of the installable file system are not
acceptable to your system.
ACTION: Contact the supplier of file system.
HEXPLANATION: The starting address for the program being executed
is not at ring 3.
ACTION: Recompile the program with the starting address at ring 3.
HEXPLANATION: The start routine address for the dynamic link library
being loaded is not at ring 3.
ACTION: Recompile the dynamic link library with the starting address
at ring 3.
HEXPLANATION: The specified file was not copied. 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.
HEXPLANATION: The extended attributes for the specified disk
or diskette are not usable.
ACTION: Run CHKDSK /F on the disk or diskette.
HEXPLANATION: The number of files containing extended
attributes has reached the system limit.
ACTION: Delete any files containing extended attributes that
you no longer need.
HEXPLANATION: A file contains a reference to an extended
attribute that does not exist. Either the disk partition
is damaged or the extended attribute system file has been
improperly modified.
ACTION: Run CHKDSK /F on the disk or diskette.
HEXPLANATION: 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.
HEXPLANATION: Extended attributes could not be placed on this
disk or diskette because 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; then, try the command again.
HEXPLANATION: The system was not successful in opening the
extended attribute system file. 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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; then, retry the command.
HEXPLANATION: You cannot issue the call to wait on an empty
muxwait semaphore.
ACTION:  Add an event or mutex to the muxwait semaphore;
then, retry the command.
HEXPLANATION: 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; then, retry the command.
HEXPLANATION: You must be the current owner of a
mutex semaphore in order to release it.
ACTION: Request ownership of the mutex semaphore;
then, retry the command.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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;
then, retry the command.
HEXPLANATION:  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; then,
retry the command.
HEXPLANATION: 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: Try the call again when the event semaphore has been reset.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The program passed a process identifier to the
operating system for which no process exists.
ACTION: Contact the supplier of the application.
HEXPLANATION: 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.
HEXPLANATION: The message is not in the
message file.
ACTION: Enter the correct message number or
reinstall the message file, and retry the command.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The system does not have enough storage
to display the message or a system error occurred.
ACTION: Retry the command later.
HEXPLANATION:  A process attempted to read, peek at, or purge a queue
that is owned by another process.
ACTION: Contact the supplier of the application.
HEXPLANATION: A process attempted to create a queue with
the same name as an existing queue.
ACTION: Contact the supplier of the application.
HEXPLANATION: A process attempted to read or peek at an
element that is not in the queue.
ACTION: Contact the supplier of the application.
HEXPLANATION: 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.
HEXPLANATION: The function masks for the function(s) 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 function(s)
to be replaced. Refer to the OS/2 Toolkit
for information regarding VioRegister or VioGlobReg.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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 regarding the specific cursor width allowed by
your video adapter.
HEXPLANATION: 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 regarding the row or column configuration for
each display mode supported by your video adapter.
HEXPLANATION: 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 regarding the row or column configuration
for each display mode supported by your video adapter.
HEXPLANATION: The wait flag parameter, which indicates
whether to wait or return immediately when attempting to
obtain a screen lock through VioScrlock, is not correct.
The correct wait flag parameter values are:
  0   for immediate return if screen I/O is not available
  1   to wait until screen I/O becomes available
ACTION: Correct the wait flag parameter and try the operation
again.
HEXPLANATION: 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.
HEXPLANATION: The specified parameter that indicates which
screen group needs to be set, selected, or stopped is not
correct.
ACTION: Refer to the OS/2 Toolkit under
DosSetSession, DosSelectSession, or DosStopSession for the
correct parameter.
HEXPLANATION: An internal Session Manager error occurred when the
requested session was not found in the active session queue.
ACTION: Reinstall your system; then, start the system again.
HEXPLANATION: The Presentation Manager set title routine is corrupted.
ACTION: Reinstall your system; then, start the system again.
HEXPLANATION: One or more of the parameters passed to a
keyboard API function call were not correct.
ACTION: Refer to the OS/2 Toolkit to determine which
parameters are valid for the keyboard API function being
issued.
HEXPLANATION: The value of the IOWAIT parameter for the keyboard
API function is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct IOWAIT
parameter values.
HEXPLANATION: The parameter value that specifies the keyboard
API function length is not valid.
ACTION: Refer to the OS/2 Toolkit for a definition of accepted
parameter values for the keyboard API function being issued.
HEXPLANATION: 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 the
KbdSetState function.
HEXPLANATION: The specified parameters are not correct.
ACTION: Perform the following actions:
1. Check the parameters passed to the monitor API call.
2. Correct any parameter error and try the call again.
HEXPLANATION: The specified device for the DosMonOpen call
is not correct.
ACTION: Try the operation again using the correct device
name.
HEXPLANATION: The specified device handle for the monitor
call is not correct. The device handle should be the same
as the one returned by the DosMonOpen call.
ACTION: Try the operation again using the correct device handle.
HEXPLANATION: The monitor buffer length is too small. 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 try the
operation again.
HEXPLANATION: The monitor application is terminating, or there
is no data in the buffer.
DosMonRead was called during one of the following conditions:
1. A DosMonClose call for the monitor application was in progress.
2. 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; then, try
DosMonRead again.
HEXPLANATION: The bytecount parameter passed to the DosMonWrite
call is too large, causing the DosMonWrite call 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 try
the operation again.
HEXPLANATION: 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 appropriate DEVICE statements
in the Command Reference for more information.
HEXPLANATION: 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.
HEXPLANATION: The NLS.DLL 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; then try the operation again.
HEXPLANATION: The NLS.DLL API 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; then try the operation again.
HEXPLANATION: The system cannot find the specified country
code or code page. The country code and code page specified
to the NLS.DLL are not correct, or they do not match each other.
The following list shows valid combinations for country code
and code page, for each country that is supported.
                         COUNTRY   CODE PAGES
COUNTRY                  CODE      SUPPORTED
Arabic-speaking          785       864 (Note 1), 850
Australia                061       437, 850
Belgium                  032       850, 437
Canada (French-speaking) 002       863, 850
Czechoslavakia           042       852, 850
Denmark                  045       850, 865
Finland                  358       850, 437
France                   033       437, 850
Germany                  049       437, 850
Hebrew-speaking          972       862 (Note 1), 850
Hungary                  042       852, 850
Iceland                  354       850, 861
Italy                    039       437, 850
Japan                    081       932 (Note 2), 437
Korea                    082       934 (Note 2), 437
Latin America            003       437, 850
Netherlands              031       050, 860
Norway                   047       850, 865
Poland                   048       852, 850
Portugal                 351       850, 860
Simplified Chinese       086       936 (Note 2), 437
Spain                    034       437, 850
Sweden                   046       437, 850
Switzerland              041       850, 437
Turkey                   090       857, 850
Traditional Chinese      088       938, (Note 2), 437
United Kingdom           044       437, 850
United States            001       437, 850
Yugoslavia               038       852, 850
   Notes:
      1. This code page is supported only with a
         country supplement.
      2. This code page is supported only with the
         Asian version of OS/2 on Asian hardware.
      3. If your country is not listed, select the
         country that is most similar to yours.
ACTION: Perform the following actions; then, start the system
again:
1. Check the country code and code page parameters passed to
   the NLS.DLL.
2. Edit the CODEPAGE= statement in the CONFIG.SYS file to
   correct any errors.
HEXPLANATION: The buffer length specified on the NLS API call
is too small to contain the returned NLS table. The returned
NLS table is truncated.
ACTION: Increase the buffer length specified on the NLS API
call and retry the operation.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: Another VIO pop-up already exists and only one
can be active at a time.
ACTION: Perform one of the following actions:
1. Wait for the existing pop-up process to complete.
2. Repeat the VioPopup call periodically until a successful
   return is obtained.
HEXPLANATION: The keyboard API function can be called only
from the Session Manager or Shell processes.
ACTION: Refer to the OS/2 Toolkit to determine which API
functions can be called from your process.
HEXPLANATION: KbdRegister accepts ASCIIZ strings of certain
lengths only. ASCIIZ strings with a length of zero are not accepted.
ACTION: Refer to the OS/2 Toolkit to determine which ASCIIZ string lengths
are accepted by KbdRegister.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The mouse API function can be called only from
the Session Manager or Shell processes.
ACTION: Refer to the OS/2 Toolkit to determine which functions are
allowed for your process.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The Session Manager detected a parameter error
for the value that specifies whether or not the state of the
shell should be saved, or an internal Session Manager error
occurred.
ACTION: Reinstall your system; then, start it again, or correct
the programming error and try the command again.
HEXPLANATION: 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.
HEXPLANATION: The parameter(s) 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.
HEXPLANATION:  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.
HEXPLANATION: 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.
HEXPLANATION: 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. The
VioSaveRedrawUndo and VioSaveRedrawWait calls must be issued
from the same process.
HEXPLANATION:  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.
HEXPLANATION: 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.
HEXPLANATION: An internal Session Manager error occurred when
a function that is reserved for the shell was requested.
ACTION: Reinstall your system; then, start the system again.
HEXPLANATION: An internal Session Manager error occurred when
an application program requested session status.
ACTION: Reinstall your system; then, start the system again.
HEXPLANATION: 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.
HEXPLANATION: The value of the IOWAIT parameter for the
mouse API function is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct IOWAIT
parameter values.
HEXPLANATION: 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 Toolit for information regarding
VIO handle usage.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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
try the program again.
HEXPLANATION: 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 start the program again.
HEXPLANATION: 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.
HEXPLANATION: One or more of the code page IDs specified in
the CODEPAGE= statement of the CONFIG.SYS file are not correct.
ACTION: Refer to CODEPAGE statement in the Command Reference
for more information.
HEXPLANATION: 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 statement in the
Command Reference for more information.
HEXPLANATION: 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.
HEXPLANATION: Only one thread per session can own the focus at
any given time.
ACTION: Release the focus of the current thread by issuing
KbdFreeFocus; then, issue KbdGetFocus again to obtain the
keyboard focus for the new logical handle. Refer to the
OS/2 Toolkit for more information about KbdOpen, KbdGetFocus,
and KbdFreeFocus.
HEXPLANATION: Another thread owns the KbdGetFocus call or is
waiting for input from the device.
ACTION: Issue the call to KbdGetFocus again with the wait
option, or start your program in another session.
HEXPLANATION: 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 statements to the CONFIG.SYS file
and start the system again. Refer to the CODEPAGE statement
in the Command Reference for more information.
HEXPLANATION: 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: Issue the call to KbdGetFocus again using an
appropriate keyboard handle. Refer to the OS/2 Toolkit
for more information about KbdGetFocus.
HEXPLANATION: An internal Session Manager error occurred when the
shell attempted to select a session that is not selectable.
ACTION: Reinstall your system; then, start the system again.
HEXPLANATION: 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; then, start the system again.
HEXPLANATION: The DosStartSession parameter that specifies
if the new session should be started in the foreground or
the background is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: The DosStartSession parameter that specifies if the
created session is related to the calling session is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: The DosSetSession parameter that specifies which
session to bring to the foreground the next time the parent
session is selected is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: The DosSetSession parameter that specifies if the
target session is selectable is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: The DosStopSession parameter that specifies if a
particular session or all sessions should be ended is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: The reserved parameter that is required for the
DosStopSession call must be zero (0).
ACTION: Change the reserved parameter to zero (0) and issue the
DosStopSession call again.
HEXPLANATION: 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; then, start the system again.
HEXPLANATION: The DosSetSession, DosStartSession, or
DosSMRegisterDD parameter that specifies the length
of the input data structure is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: An internal Session Manager error occurred
when the parent session tried to retrieve the child
session.
ACTION: Reinstall your system; then, start the system again.
HEXPLANATION: Not enough storage is available. 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:
1. Reduce the number of running programs and try the
   command again.
2. Reduce the value of the BUFFERS=, TRACEBUF=, DISKCACHE=,
   THREADS=, RMSIZE=, or DEVICE=VDISK.SYS statement in the
   CONFIG.SYS file. Then restart the system and try the command
   again.
3. Remove files that you do not need from the hard disk or
   diskette; then, restart the system.
4. Install additional memory on your system.
5. If an input or output error occurred on the swap file,
   check the auxiliary storage device that contains the swap
   file.
HEXPLANATION: Detached processes are not allowed to make
keyboard API function calls. The process in error might
have been started using the DETACH command or the
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.
HEXPLANATION: 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.
HEXPLANATION: Detached processes cannot make mouse API function
calls. The process in error might have been started using the
DETACH command or the 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.
HEXPLANATION: The font requested cannot be found in the
VIOTBL.DCP file.
ACTION: Check that the VIOTBL.DCP file contains the font
information requested.
HEXPLANATION: The user loadable font requested cannot be found.
ACTION: Validate the format of the font to be loaded.
HEXPLANATION: The code page specified on VioSetCP is not one
of the prepared code pages, nor is it set to 0.
To view a list of valid country code and code page
combinations, type:  HELP 398
ACTION: Edit the CONFIG.SYS file to correct any errors in
the following three statements:
    CODEPAGE=, COUNTRY=, and DEVINFO=
Then, restart the system.
HEXPLANATION: 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.
HEXPLANATION: The DosStartSession parameter that specifies
the value of the tracing options is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: VioPopup cannot occur until the 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.
HEXPLANATION: The hard error and print screen handlers could
not be started when the system was initialized
ACTION: Reinstall your system; then, start the system again.
HEXPLANATION: A transparent pop-up cannot occur over a graphics
screen or over a screen group that has previously registered
a VioSavRedrawWait thread.
ACTION: Issue a standard VIO pop-up instead of the transparent
popup.
HEXPLANATION: A zero (0) must be specified for the reserved
parameter required by the VIO application call.
ACTION: Change the reserved parameter to zero (0) and issue
the VIO call again.
HEXPLANATION: The specified address to store selectors for a
DevHlp_AllocateGDTSelectors call does not have enough room to store
the selectors, or the specified address in a DevHlp_PhysToGDTSelector
call goes past the end of possible memory.
ACTION: Correct the address.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The DosStartSession parameter that specifies the
type of session to be created for this program is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: The DosStartSession parameter that specifies
the first state for a windowed application is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: The DosStartSession parameter that specifies if the
started program should inherit the environment and open file
handles of the calling process is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: 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.
HEXPLANATION: Only a Presentation Manager program can issue
Advanced VIO calls.
ACTION: Refer to the OS/2 Toolkit for information regarding
Advanced VIO applications.
HEXPLANATION: 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.
HEXPLANATION: The call to VioCreatePS failed and an additional
handle cannot be allocate to the Presentation Space.
ACTION: Issue VioDestroyPS before issuing VioCreatePS again.
HEXPLANATION: 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 start the system again.
HEXPLANATION: 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.
HEXPLANATION: The DosStartSession parameter that specifies the
session diagnostic option is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: A Presentation Manager session is not
allowed to issue keyboard API function calls. Keyboard
function calls 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 Presentation Manager program.
HEXPLANATION: Presentation Manager sessions cannot issue mouse
API function calls. 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 Presentation Manager program.
HEXPLANATION: The process specified in a RAS trace request does
not exist.
ACTION: Correct the process ID to be passed to the system.
HEXPLANATION: RAS has been asked to trace-until-error, but a
similar previous request is being processed.
ACTION: Try again after RAS finishes tracing.
HEXPLANATION: A RAS trace-until-error request was received and
an error was encountered; RAS tracing has been suspended.
ACTION: Request RAS to turn off the trace-until-error function.
HEXPLANATION: 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.
HEXPLANATION: RAS tracing is active, but minor code information
will not be recorded.
ACTION: Continue. But, realize that minor code trace information
is not being recorded.
HEXPLANATION: An error is in the RAS major or minor code table.
ACTION: Continue. But, realize that some of the trace information
might not be recorded.
HEXPLANATION: RAS has been asked to trace-until-error, but the
error count specified was zero.
ACTION: Correct the error count.
HEXPLANATION: 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; then, restart your system and try the command
again.
HEXPLANATION: The DosSMRegisterDD parameter that specifies
the notification bit map is not correct.
ACTION: Refer to the OS/2 Toolkit for the correct parameter value.
HEXPLANATION: The Logging Facility cannot perform the operation you
requested because of the incorrect function code.
ACTION: Correct the function code and retry the operation.
HEXPLANATION: Statements required to start logging are missing
from the CONFIG.SYS file.
ACTION: Add the following statements to your CONFIG.SYS file, then restart
your system.
      DEVICE=C:\OS2\LOG.SYS
      RUN=C:\OS2\SYSTEM\LOGDAEM.EXE
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: Currently, only logging class 1 is supported.
ACTION: Set the logging class to 1; then, retry the API call.
HEXPLANATION: One of the following has occurred:
1. An invalid parameter was given to DosLogRegister.
2. Too many applications called DosLogRegister for
   log-record notification.
3. An invalid buffer was given to LogQueryState.
4. An error occurred in communicating with the Logging Facility
   LOGDAEM program.
ACTION:  Do one of the following; then, retry the command.
1. Correct the invalid parameter given to DosLogRegister.
2. Be sure that your application registers only once with DosLogRegister.
3. 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.
HEXPLANATION: One or both of the following has occurred.
  Another process is accessing the specified disk.
  You have not logged on with sufficient privilege to format the disk.
ACTION: Do one or both of the following; then, retry the command.
  End the other process or wait until it is complete.
  Log on with sufficient privilege.
HEXPLANATION: 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 try running FORMAT again.
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.
HEXPLANATION: 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
FDISK to increase the size of the partition, or format the
partition for the FAT (File Allocation Table) file system used
with OS/2 or DOS.
HEXPLANATION: 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, then run FORMAT again.
HEXPLANATION: 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; then, try the command again.
HEXPLANATION: HPFS (High Performance File System) partitions
can be created only on hard disks.
ACTION: Try the command again, 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.
HEXPLANATION: HPFS (High Performance File System) can format
only one hard disk partition at a time.
ACTION: Try the command again using only one drive letter.
HEXPLANATION: A problem was detected with the UHPFS.DLL file.
ACTION: Copy the UHPFS.DLL file from your backup copy. Then,
restart your system and try the command again.
HEXPLANATION: 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.
HEXPLANATION: The disk cannot be formatted for HPFS because
the HPFS File System Driver is not loaded.
ACTION: Load the File System Driver; then, try the command
again.
HEXPLANATION: The correct parameters are:
 drive:        is the drive letter followed by a colon (such as
               E:), specifying which disk to check.
 /V            display 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  is the same as /F:1; also searches orphaned
                       areas.
                 /F:3  is the 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: Try the CHKDSK command again using the correct
parameters.
HEXPLANATION: 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 partition you want to check.  Also, if you used
the /F parameter with FORMAT, make sure no other program is
using that disk partition.
HEXPLANATION: A problem was detected with the UHPFS.DLL file.
ACTION: Copy the UHPFS.DLL file from your backup copy. Restart
your system; then, run the CHKDSK command again.
HEXPLANATION: 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; then, try the command again.
HEXPLANATION: 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; then, run the CHKDSK command again.
HEXPLANATION: 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; then, run the CHKDSK
command again.
HEXPLANATION: 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; then,
try the command again.
HEXPLANATION: 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 try the CHKDSK command again.
If the problem continues, restore files from your backup copy.
If this still does not fix the problem, format the disk again.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: Lost data was detected on the specified disk.
ACTION: Use the CHKDSK command with the /F parameter to
recover the data.
HEXPLANATION: 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 partition. If this is your primary partition,
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
with the /FS:HPFS parameter to reformat the drive. Then, restore
your data from the backup copy.
HEXPLANATION: CHKDSK cannot run on a disk partition while
another process is accessing the partition.
ACTION: End all programs running on the specified disk
partition; then, try the CHKDSK command again.
HEXPLANATION: 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; then, try the CHKDSK command again.
HEXPLANATION: 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; then, try the CHKDSK command again.
HEXPLANATION: 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; then, try the CHKDSK command again.
HEXPLANATION: Data was found in a temporary relocation sector
by the CHKDSK command.
ACTION: Use the CHKDSK command with the /F parameter to
recover the data.
HEXPLANATION: The only required parameter of the RECOVER command
is the name of the file that you want to recover.
ACTION: Try the command again using a valid path name. If
necessary, include its drive letter and path.
HEXPLANATION: RECOVER searched for the file you specified
but could not find it on the disk.
ACTION: Check that you typed the file name correctly.
HEXPLANATION: A problem was detected with the UHPFS.DLL file.
ACTION: Restart your system and run the RECOVER command again.
If the problem persists, recopy the UHPFS.DLL file from your
backup copy; then, restart your system and run RECOVER again.
HEXPLANATION: 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;
then, try the RECOVER command again.
HEXPLANATION: The disk is probably full or bad. If you can
run RECOVER again, 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 than are no
longer needed; then, try the RECOVER command again.
HEXPLANATION: RECOVER can create up to 10,000 files named
FILEnnnn.REC (where "nnnn" is a number). You attempted to
exceed the number of files allowed.
ACTION: Delete or rename one or more existing FILEnnnn.REC
files; then, try the RECOVER command again.
HEXPLANATION: RECOVER was unable to read a list of extended
attributes.  The list was truncated at the last readable
attribute.
ACTION: No action is required.
HEXPLANATION: 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.
HEXPLANATION: Duplicate files now exist on your disk.
ACTION: Delete the original file; then, rename the
recovered file.
HEXPLANATION: 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; then, rename the
recovered file.
HEXPLANATION: RECOVER detected an operating system error.
ACTION: Restart your system; then, try the RECOVER command
again.
HEXPLANATION: You must specify the drive that you want the system
data transferred to.
ACTION: Try the SYS command again using a valid drive letter.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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:
1. If the disk is full, delete any files that are no longer
   needed.
2. Determine if the disk is write-protected. If so, remove
   the write-protection.
3. Disallow any read-only attributes on your files.
Then, if you have permission to write to the disk, try the SYS
command again.
HEXPLANATION: The IFS= statement contains illegal characters.
ACTION: Edit the CONFIG.SYS file to correct the IFS= statement;
then, restart the system.
HEXPLANATION: The cache requires a minimum of 64K to start. This
minimum amount was not available.
ACTION: Reinstall a new version of HPFS (High Performance
File System).
HEXPLANATION: 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.
HEXPLANATION: A High Performance File System (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.
Example: CHKDSK D: /F
Note: 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; then, 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
before turning off the computer.
HEXPLANATION: The only parameters that can be used are:
 drive:        is the drive letter followed by a colon (such as
               E:), that specifies which hard disk partition
               to format.
 /V[:label]    puts the volume label on your disk
 /FS:xxxx      xxxx indicates the file system type
               (FAT or HPFS) to be used.
ACTION: Try the FORMAT command again using the correct
parameters.
HEXPLANATION: 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 modifies the CONFIG.SYS file for
HPFS drives D and F:
IFS=C:\OS2\HPFS.IFS -C:64 /AUTOCHECK:DF
HEXPLANATION: 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 partition when prompted.
HEXPLANATION: Too many FORMAT commands are running concurrently.
ACTION: Wait until one of your current formatting processes
has ended; then, retry the command.
HEXPLANATION: 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 data.
2. End application.
3. AT DOS prompt, type: exit
   this will end the virtual DOS machine session.
HEXPLANATION: 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.
 ; DCR 1131.2 CP20, msg. fixed 2/18/91 to conform to standalone app.
HEXPLANATION: 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: Do the following:
  1.  Continue with start-up.
  2.  Add the DEVICE statement for the Virtual %1 device driver
      to the CONFIG.SYS file; then, restart the system.
HEXPLANATION: 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; then, retry the command.
HEXPLANATION: You used the mapping symbol (=) in the command,
but did not specify the two drive letters to map.
ACTION: Correct the syntax; then, retry the command.
Example: [DOS letter = OS/2 drive].
HEXPLANATION: 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.
Example:  [DOS letter - DOS letter].
HEXPLANATION: 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.
HEXPLANATION: 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; then, restart the session.
HEXPLANATION: The FSACCESS command requries a drive letter.
You must specify the drive letter you want to register.
ACTION: Specify the letter of a drive; then retry the command.
HEXPLANATION: Additional disk space on the target disk
is required to complete this operation.
ACTION: To increase disk space, do one of the following:
1. Delete unnecessary files.
2. Move some files to another disk or diskette.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: OS/2 HIMEM.SYS device driver does not provide XMS services
in any version of OS/2 prior to OS/2 2.0.
ACTION: Replace the HIMEM.SYS with the DOS version of the XMS driver.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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:
1. The disk or diskette is not formatted for startup.
2. The startup program will try to start invalid instructions.
ACTION: Be sure that the VM boot path setting is set to a disk or
diskette drive that contains a startable DOS system.
HEXPLANATION: The HPFS encountered a disk error while updating
the system 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.
HEXPLANATION: 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; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: When the ENHANCED=OFF statement 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.
HEXPLANATION: The parameters ENHANCED=, RXDMA=, and TXDMA= cannot be
specified because the serial port hardware does not support DMA.
ACTION: Delete the parameters; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: The specified parameter is not supported on the serial port.
ACTION: Do one of the following:
        1. Delete the parameter; then, retry the command.
        2. Specify a different port; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: The specified parameter is not supported on the
serial port.
ACTION: Do one of the following:
        1. Delete the parameter; then, retry the command.
        2. Specify a different port; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: The baud rate is a required parameter that must be specified.
ACTION: Specify a baud rate; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: One of the following has occurred:
        1.  The parameter was misspelled.
        2.  The parameter is not supported.
        3.  The specified positional parameter is in the wrong position.
ACTION: Correct the parameter specified; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: The combination of DATABITS and STOPBITS you specified is
invalid.  If 5 databits were specified, then 2 stopbits are not
allowed.  If 1.5 stopbits were specified, then only 5 databits are
allowed.
ACTION: Correct the parameter; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: The value specified is not supported.
ACTION: Correct the value; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: A parameter was specified without an equal sign (=).
ACTION: Include an equal sign (=) in the specified parameter; then,
retry the command.  To view other asynchronous communications MODE command
parameters, type: Help 1625.
HEXPLANATION: One of the following has occurred:
        1.  The parameter was misspelled.
        2.  The specified positional parameter is in the wrong position.
ACTION: Correct the parameter specified; then, retry the command.
To view other asynchronous communications MODE command parameters,
type: Help 1625.
HEXPLANATION: The value specified is out of range, or it might be in the
wrong position.
ACTION: Correct the value or position of the specified parameter; then,
retry the command.  To view other asynchronous communications MODE command
parameters, type: Help 1625.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The FDISK syntax specified is incorrect.
ACTION: To see the correct syntax of the command, type: Fdisk /help.
HEXPLANATION: The input value specified is either missing or not valid
for this command.
ACTION: Correct the value; then, retry the command.
To see values for the command, type: Fdisk /help.
HEXPLANATION: The value specified is not valid restrictor.
ACTION: Correct the value; then, retry the command.
To see values for the command, type: Fdisk /help.
HEXPLANATION: The value specified is not valid restrictor.
ACTION: Correct the value; then, retry the command.
To see values for the command, type: Fdisk /help.
HEXPLANATION: The value specified is not valid restrictor.
ACTION: Correct the value; then, retry the command.
To see values for the command, type: Fdisk /help.
HEXPLANATION: The value specified is not valid restrictor.
ACTION: Correct the value; then, retry the command.
To see values for the command, type: Fdisk /help.
HEXPLANATION: The specified FDISK command is not a valid command.
ACTION: To see the correct syntax of the command, type: Fdisk /help.
HEXPLANATION: The restrictor specified is not a valid restrictor.
ACTION: To see the correct syntax of the command, type: Fdisk /help.
HEXPLANATION: The restrictor specified has already been set as shown.
ACTION: Correct the restrictor; then, retry the command.
HEXPLANATION: The specified restrictor requires a value.
ACTION: To see the correct syntax of the command, type: Fdisk /help.
HEXPLANATION: This command requires the restrictor specified.
ACTION: To see the correct syntax of the command, type: Fdisk /help.
HEXPLANATION: The file named in the command does not exist or was entered
incorrectly.
ACTION: Retry the command using the correct file name.
HEXPLANATION: 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; then, retry the command.
HEXPLANATION: 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.
HEXPLANATION: The value specified is not valid restrictor.
ACTION: Correct the value; then, retry the command.
HEXPLANATION: This command cannot be done to the Boot Manager.
ACTION: Remove the BOOTMGR restrictor and retry the command.
HEXPLANATION: Only one Boot Manager partitions is allowed.
ACTION: Delete the existing Boot Manager partition and then retry the command.
HEXPLANATION:  A boot name cannot be given to this partition.
Either the partition is the Boot Manager, or it does not reside
entirely within the first gigabyte of the hardfile.
ACTION: Check the partition type and location.
HEXPLANATION:  A boot name cannot be given to this partition.  Either the
partition is the Boot Manager, or it does not reside entirely within the
first 1024 megabytes of the hardfile.
ACTION:  Remove the name option from the command "/created[:name]".
HEXPLANATION:  The boot manager must reside within the first 1024 megabytes
on the first hard file.
ACTION:  Correct the command to specify the freespace within the first
1024 megabytes.
HEXPLANATION:  An error has occurred in a partition table entry on the
specified file.
ACTION:  Record this message number and contact your Service Representative.
HEXPLANATION:  A boot name cannot be assigned to a partition without boot
manager support installed.
ACTION:  Install the boot manager, or do not assign a name to this partition.
HEXPLANATION: A parameter was entered
that is not recognized by the command.
ACTION: Check the parameters and retry
the command.
HEXPLANATION: The specified parameter
is not recognized by the command.
ACTION: Check the parameter and retry the command.
HEXPLANATION: One of the following occurred:
1. An incorrect parameter was specified.
2. An incorrect separator was specified.
3. A required parameter is missing.
4. Too many parameters were entered.
5. The parameters were entered in the wrong order.
ACTION: Check the syntax of the command. Then retry
the command.
HEXPLANATION: A file larger than 63KB cannot
be sorted.
ACTION: No action can be taken.
HEXPLANATION: The number of lines in a file
cannot exceed (file size + 768) / 4.
ACTION: You can reduce the number of lines in
the file or split the file into smaller files.
Then retry the command.
HEXPLANATION: 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; then retry
the command.
HEXPLANATION: An incorrect disk drive letter
was used.
ACTION: Retry the command using the correct
disk drive letter.
HEXPLANATION: 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.
HEXPLANATION: 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= parameter in your CONFIG.SYS
file and restart the system.
HEXPLANATION: 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.
HEXPLANATION: An incorrect date format was
entered.
ACTION: Retry the command using a correct
date format.  For example, mm/dd/yy,
mm-dd-yy, or mm.dd.yy.
HEXPLANATION: 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.
HEXPLANATION: The name specified should be one of the following:
1. The name of an OS/2 internal command.
2. The name of an OS/2 external command.
3. The name of an executable program whose file extension
   is .EXE or .COM.
4. The name of a batch file whose file extension is .CMD.
For cases 2, 3 and 4 (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.
HEXPLANATION: An incorrect time format
was entered.
ACTION: Enter the time using the correct
time format.
HEXPLANATION: The program requires a different
version of the operating system.
ACTION: Use Operating System/2 Version 2.0
and restart the system, or install the proper version
of the application program on the system.
Then retry the command.
HEXPLANATION: 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.
HEXPLANATION:  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 (FAT), or move the file to a path
whose name is valid in a DOS session.
HEXPLANATION: An area of your hard disk is defective.
ACTION: Retrieve the data in the HOTFIX.DAT file.
Backup, then reformat the specified drive.
HEXPLANATION: The operating system encountered an unknown
error while attempting to start up the program.
ACTION: Contact the supplier of the program.
HEXPLANATION: One of the following errors
occurred:
1. The file you tried to write to is read-only.
2. The directory is full.
ACTION: Do one of the following:
1. If the file is read-only, you may use the ATTRIB
   command to change the read-only attribute.
2. If the directory is full, no action can be
   taken unless files are deleted.
HEXPLANATION: The line exceeds
128 characters, or the command is
greater than 80 characters in length.
ACTION: Shorten the length
of the input line.
HEXPLANATION: 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.
HEXPLANATION: 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; then retry the command.
HEXPLANATION: Either 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.
HEXPLANATION: You named the target file
the same as the source file.
ACTION: Ensure that the file name specifications
for the target and source files are not the same.
HEXPLANATION: The command is missing
required keywords.
ACTION: Retry the command correctly.
HEXPLANATION: A permanent copy of CMD.EXE was
running, and one of the following situations occurred:
1. Another program tried to cancel this copy of CMD.EXE.
2. CMD.EXE was started using a redirected input file
   and the end of the file was reached.
ACTION: No action can be taken.
HEXPLANATION: The target file name specified with the
RENAME or MOVE command already exists, is in use, 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; then, retry the command.
HEXPLANATION: A single command name or argument
was entered that is too long to be processed.
ACTION: Revise and retry the command.
HEXPLANATION: Too many handles prevent handle
duplication during a pipe operation.
ACTION: Wait for the other processes to end and
retry the command.
HEXPLANATION: The JOIN command was unable
to create the specified directory.
ACTION: Retry the command making sure
the directory name is correct.
HEXPLANATION: The directory specified
does not exist on your system.
ACTION: Create the directory and retry the command.
HEXPLANATION: 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.
HEXPLANATION:  There is no further help available for this message.
ACTION: No further action can be supplied for this error.
HEXPLANATION: A source path must be specified
with this command.
ACTION: Retry the command using the following source
path syntax: [d:] [path] filename[.ext]
HEXPLANATION: The source path specified
does not contain the files requested.
ACTION: Retry the command using the correct
source path or the current file specification.
HEXPLANATION: 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.
HEXPLANATION: The path specified is incorrect.
ACTION: Retry the command using the correct path.
HEXPLANATION: The source and target
files cannot have the same name.
ACTION: Retry the command using a different
target file name.
HEXPLANATION: An unexpected error occurred
during XCOPY processing.
ACTION: Restart the system before trying XCOPY.
HEXPLANATION: One of the following conditions exists:
     1. A Cyclic Redundancy Check error.
     2. The file is in use by another
        process.
     3. Too many files are open.
     4. The diskette is not a DOS diskette.
ACTION: Correct the problem or wait until the
file is not in use, then retry the command.
HEXPLANATION: One of the following conditions exists:
1. The disk is full.
2. The file or drive is in use or locked
   by another process.
3. Too many files are open.
4. The target file is a read-only file.
5. A disk error occurred.
ACTION: Correct the problem or wait until the
file is not in use, then retry the command.
HEXPLANATION: The file requested cannot be
closed because a disk error occurred.
ACTION: Retry XCOPY later.
HEXPLANATION: One of the following conditions exists:
1. The disk is in use or locked by another process.
2. A disk error occurred.
ACTION: Do one of the following:
1. Retry XCOPY later.
2. If the error is with a diskette, make sure it is properly inserted.
3. Format the diskette for the operating system.
4. Check that the diskette is not damaged.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The command specified is not a recognized
configuration command.
ACTION: Edit the CONFIG.SYS file to correct or remove
the incorrect command. Restart the system.
HEXPLANATION: 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 command. Restart the system.
HEXPLANATION: The specified command requires a parameter.
ACTION: Edit the CONFIG.SYS file to correct or remove
the incorrect command. Restart the system.
HEXPLANATION: The specified DOS device driver
has executed an INT 21 function call 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: Input/Output privilege level 2 is required.
ACTION: Add to your CONFIG.SYS file the statement: IOPL=YES.
Then restart the system.
HEXPLANATION: Input/Output privilege level 2 is required.
ACTION: Add to your CONFIG.SYS file the statement: IOPL=YES.
Then restart the system.
HEXPLANATION: There is not enough available storage to load
the specified program or device driver.
ACTION: Perform one of the following actions, then restart
the system:
1. Edit the CONFIG.SYS file to remove the specified command.
2. Edit the CONFIG.SYS file to increase the amount of
   storage available by:
   a. Reducing the value on the BUFFERS command
   b. Removing unnecessary DEVICE and/or RUN commands
   c. Reducing the value on the DISKCACHE command
   d. Reducing the value on the TRACEBUF command
   e. Reducing the size of the virtual disk specified on
      the DEVICE=VDISK command
3. If the failing command is the SHELL command or a DEVICE
   command for a DOS device driver, edit the CONFIG.SYS
   file to increase the value on the RMSIZE command.
4. If the failing command is the PROTSHELL command, a RUN
   command, or a DEVICE command used for both DOS and OS/2,
   edit the CONFIG.SYS file to decrease the value on the
   RMSIZE command or add the PROTECTONLY=YES command.
5. Install another memory option in your system unit.
HEXPLANATION: The version of the operating system in your system
is not the correct level.
ACTION: Use the VER command to determine the level of
Operating System/2 you are using. You should be using
Operating System/2 Version 2.0.
HEXPLANATION: A file must be decompressed with the same
version of OS/2 that was used to compress it.
ACTION: Correct the problem; then, retry the command.
HEXPLANATION: One of the following errors occurred:
1. The group code is incorrect.
2. The group code table is damaged or set up incorrectly.
ACTION: Do one of the following:
1. Correct the group code; then, retry the command.
2. Create a new group code table; then, retry the command.
HEXPLANATION: The group code exceeds the maximum value of 255. The
valid group code range is 0 to 255.
ACTION: Correct the value; then, retry the command.
HEXPLANATION: 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.
HEXPLANATION: 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).
HEXPLANATION: 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).
HEXPLANATION: 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.
HEXPLANATION: A subdirectory or file with the same name
already exists in the target directory.
ACTION: Choose a new name and retry the command.
HEXPLANATION: The system detected an error while reading from the
source diskette. The function will attempt to proceed normally.
ACTION: No action is required by the user.
HEXPLANATION: The system detected an error while writing to the
target diskette. The function will attempt to proceed normally.
ACTION: Try reformatting the target diskette and entering the
DISKCOPY command again, or use another formatted diskette.
HEXPLANATION: The system detected an error while reading from the
target diskette. The function will attempt to proceed normally.
ACTION: No action is required by the user. %2 sectors per track, %3 side(s).
HEXPLANATION: The OS/2 FAT file system can only support
partitions up to 2,048 MB and/or before cylinder 1023.
ACTION: Partition your hard disk again; then retry the command.
HEXPLANATION: 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.
HEXPLANATION: The correct parameters are:
 /4          formats 360KB diskettes in a 1.2 MB drive
 /F:xxxx     formats diskettes to the specified capacity
 /V[:label]  puts the volume label on your disk
 /N:9        formats 720KB diskettes in a 1.44 MB drive
 /FS:xxxx    replace xxxx with the file system type
             (FAT or HPFS) that you are using for the hard disk
 /ONCE       inhibits first and last prompt from a diskette format
ACTION: Retry the command using the correct parameters.
HEXPLANATION: A disk error occurred while the target disk
was being formatted.
ACTION: Review the error messages displayed, and follow
the corrective action.
HEXPLANATION: The area on the disk where the system
information is stored is unusable.
ACTION: Retry the FORMAT command using another
diskette or repartition the hard disk.
HEXPLANATION: Either 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 repartition the hard disk.
HEXPLANATION: This version of the operating system will no longer
permit leading blanks in volume labels.
ACTION: No further action is required.
HEXPLANATION: 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.
HEXPLANATION: The area on the disk where the system
information is stored is unusable.
ACTION: Retry the FORMAT command using another
diskette or repartition the hard disk.
HEXPLANATION: 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.
HEXPLANATION: FORMAT parameters were entered
that cannot be used together.
ACTION: Retry the FORMAT command using the
correct parameters.
HEXPLANATION: 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 the DEVICE= command in the CONFIG.SYS file.
Restart the system.
HEXPLANATION: The FORMAT command was entered
without a drive letter.
ACTION: Try the FORMAT command again and include
the letter of the drive to be formatted.
HEXPLANATION: 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.
HEXPLANATION: The partition table of the hard
disk does not have an OS/2 partition, or the
partition is unusable.
ACTION: Repartition the hard disk using
the FDISK command.
HEXPLANATION: The format of the extended attributes on this
disk or diskette is not correct for this version of OS/2.
ACTION: Install the correct version of OS/2; then, try the
command again.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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:
1. Make copies of the specified files (use the COPY command).
2. Delete the original files (use the ERASE command).
3. Check the files that you copied for validity, and edit them
   if necessary.
HEXPLANATION: The diskette drive determined that the diskette is too large
for the drive.
ACTION: Do one of the following:
  1.  Insert the diskette in the drive with the same capacity as the
      diskette.
  2.  Check to see if the diskette is the correct size.
  3.  Retry the command using the /F parameter.  For more information
      about formatting, refer to the Command Reference.
HEXPLANATION: One or more of the parameters
entered for the CHKDSK command are not correct.
The correct parameters for CHKDSK are:
 /F and /V  for a FAT (File Allocation Table) formatted disk
 /F and /C  for an HPFS (High Performance File System) formatted disk
ACTION: Specify the correct parameter; then, try the command again.
HEXPLANATION: The drive specified is not correct, 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.
HEXPLANATION: 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.
HEXPLANATION: 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 table 1
and 2, format the disk.  If FORMAT fails, the
disk is unusable.
HEXPLANATION: A disk error was encountered
while attempting to update the File Allocation Table
on the specified drive. The table number will be 1 or 2,
depending on which of the two copies of the
File Allocation Table could not be written.
ACTION: If this message appears for both table 1
and 2, format the disk.  If FORMAT fails, the
disk is unusable.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The file has a different size
than the number of clusters associated with the
file.
ACTION: To correct the file size enter CHKDSK /F.
HEXPLANATION: The File Allocation Table points to
the same data block for the specified  files. The files
are assigned to the same space on the disk or diskette.
ACTION: Do one of the following:
1. Make copies of the specified files (use the COPY
   command).
2. Delete the original files (use the ERASE command).
3. Review the files for validity and edit as necessary.
HEXPLANATION: 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.
HEXPLANATION: Incorrect information was
detected in the 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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
enter the /F option, no corrective action is
taken.
ACTION: Enter CHKDSK /F.  CHKDSK will
attempt to correct the error.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: Multiple errors occurred while
writing to a disk drive.  The disk may be
unusable.
ACTION: Format the disk again.
HEXPLANATION: A disk error was encountered
while CHKDSK with the /F option was attempting
to update the directory entry.
ACTION: The directory entry %1 may not
be usable. No action required.
HEXPLANATION: A disk error was encountered
while CHKDSK with the /F option was attempting
to update the root directory.
ACTION: Check the following:
1. The diskette is inserted correctly.
2. The diskette is not write protected.
3. The diskette is formatted.
HEXPLANATION: A disk error was encountered
while CHKDSK was attempting to read
subdirectory %1.
ACTION: The directory %1 may not be usable.
No action is required.
HEXPLANATION: There is an error on the
diskette.  This diskette cannot be used as a
storage dump diskette until it
is reformatted.
ACTION: Insert another formatted diskette
in drive A and continue.
HEXPLANATION: The utility has detected a return code
error.  Some data may be written on the diskette.
ACTION: Restart the program using another diskette.
HEXPLANATION: The diskette drive specification is either
missing, incorrect, or not a drive which is configured for
the system.
ACTION: Retry the command using a correct diskette drive
specification.
HEXPLANATION: The system could not write the
CREATEDD information to the diskette.
ACTION: Restart the program using another
diskette.
HEXPLANATION: The CONFIG.SYS file does not
contain a TRACE= or TRACEBUF= statement.
ACTION: Check your CONFIG.SYS file.  Enter the
necessary information for system trace,
restart the system, and retry the command.
HEXPLANATION: The TRACE utility has detected
that the ON/OFF parameter is either missing or
incorrect, or is not in the correct position.
ACTION: Check the command keyword and retry the
command using either ON or OFF.
HEXPLANATION: The TRACE utility detected that
all major event codes and corresponding minor codes
are not correct.
ACTION: Correct the major event code and syntax of the
command; then retry the command.
HEXPLANATION: The Trace Utility was unable to interpret the
command.
ACTION: Correct the error and retry the command.
HEXPLANATION: The Trace Definition File exceeds the maximum
size of 65535 bytes.
ACTION: A smaller Trace Definition File must be used with the Trace Utility.
HEXPLANATION: The Trace Definition File is an incorrect level,
or contains a syntax error.
ACTION: Correct the syntax error or replace the Trace
Definition File.
HEXPLANATION:   The utility failed to locate the specified file for one of
the following reasons:
1.  The Dynamic Link Library (.DLL) does not exist.
2.  The Dynamic Link Library does not contain its corresponding Trace
    Definition File (.TDF)
3.  The Dynamic Link Library was not loaded.
ACTION: Do one of the following:
1.  Ensure that the proper Dynamic Link Library file and
    corresponding Trace Definition File are located in the same directory.
2.  Load the Dynamic Link Library using DosLoadModule.
HEXPLANATION: One or more opcodes in the TDF and DLL files do not
match at the trace point.
ACTION: Ensure that the opcodes match.
HEXPLANATION: Trace was unable to convert one or more of the
segment numbers into selectors.
ACTION: Correct the segment number.
HEXPLANATION: There is an error on the
diskette.  This diskette cannot be used as a
storage dump diskette until it
is reformatted.
ACTION: Insert another formatted diskette
in drive A and continue.
HEXPLANATION: 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.  Do one of the following:
  1. Copy this file to the C:\OS2\DLL directory; then, retry the command.
  2. Contact the supplier of this application.
HEXPLANATION: An incorrect input
device name was entered.
ACTION: Retry the command using a correct
input device name.
HEXPLANATION: An incorrect device
name was entered.
ACTION: Retry the command using a correct
output device name.
HEXPLANATION: Supported languages are:
      BE     (Belgium)                    NO (Norway)
      CF     (Canada Fr.)                 PL (Poland)
      CS 243 (Czechoslovakia - Czech)     PO (Portugal)
      CS 245 (Czechoslovakia - Slovak)    SF (Switzerland, Fr.)
      DK     (Denmark)                    SG (Switzerland, Ger.)
      GR     (Germany)                    SP (Spain)
      FR     (France)                     SU (Finland)
      HU     (Hungary)                    SV (Sweden)
      IS     (Iceland)                    TR (Turkey)
      IT     (Italy)                      UK (United Kingdom)
      LA     (Latin America)              US (United States)
      NL     (Netherlands)                YU (Yugoslavia)
ACTION: Enter the correct keyboard code and retry the command.
HEXPLANATION: An unexpected error occurred when the system
attempted to copy the operating system files.
ACTION: Retry the installation using the FORMAT option.
HEXPLANATION: There is an insufficient amount of
storage available to transfer the operating system files.
ACTION: Wait for another process to end and retry
the command.
HEXPLANATION: The operating system files do not exist on the
default drive.
ACTION: Retry the command using a correct default drive
that contains the operating system files.
HEXPLANATION: 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.
HEXPLANATION: The DEVICE=VDISK statement in the
CONFIG.SYS file contains incorrect parameters.
ACTION: Correct the DEVICE=VDISK statement in the
CONFIG.SYS file. Then restart the system.
HEXPLANATION: VDISK requires more storage
than the system has available.
ACTION: Do one of the following:
1. Decrease the amount of storage requested
   in any or more of the  DEVICE=VDISK
   statements in the CONFIG.SYS file.
2. Edit the CONFIG.SYS file to reduce the value specified
   in the BUFFERS=, TRACEBUF=, DISKCACHE=, or THREADS=
   statement.
3. Install another memory option in your system unit.
Then restart the system.
HEXPLANATION: 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.
HEXPLANATION: The path specified is incorrect.
The path must be the name of a subdirectory
that exists on the specified disk.
ACTION: If you want to use a specific path for
the swap file, correct the SWAPPATH= statement
in the CONFIG.SYS file.  Restart the system.
HEXPLANATION: 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:
1. Make additional space available on the
   hard disk or diskette.
2. Insert a formatted diskette that is not
   write-protected.
3. Change the SWAPPATH= statement in CONFIG.SYS
   to specify a different drive.
Then restart the system.
HEXPLANATION: There is not enough system memory or disk
storage available.
ACTION: Try one of the following:
1. 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.
2. Install another memory option in your system unit.
3. Use the ERASE command to delete unwanted files on the
   swap disk or use the COPY command to copy them to a
   different disk.
Then restart the system.
HEXPLANATION: The path specified is incorrect.
The path must be the name of a subdirectory
that exists on the specified disk.
ACTION: If you want to use a specific path for
the swap file, correct the SWAPPATH= statement
in the CONFIG.SYS file.  Restart the system.
HEXPLANATION: The system requires additional virtual memory,
but cannot expand the size of the swapfile to satisfy this
request.
ACTION: Reduce the virtual memory requirement by closing
applications, or increase the amount of available space on
the partition by deleting unwanted files.
HEXPLANATION: The file name is incorrect or
does not exist.
ACTION: Check the file name and retry the
command.
HEXPLANATION: 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.
HEXPLANATION: 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: partition (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: partition.
 3. Reinstall OS/2, then select the option to format the C: partition.
 4. Restore the files you backed up in Step 2.
If the swap file is located on a partition 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: partition.
    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.  It may be possible that
    you will need to reformat the partition that contained
    the bad sector.
OPTIONAL
 4. Backup to diskette all files on the partition containing the bad sector.
 5. Reformat that partition.
 6. Restore the files you backed up in Step 4.
If the above procedure fails, then:
 1. Use the Hardware Reference Diskette, and select the format option.
    Perform a low-level format of the entire hard disk.
 2. Reinstall OS/2.
If this procedure fails, then:
 1. Replace the hard disk.
 2. Install OS/2.
 3. Restore all files you backed up.
HEXPLANATION: 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 partitions. Use
FDISK or delete DEVICE=VDISK statements in the
CONFIG.SYS file.
HEXPLANATION: The operating system detected an error when starting
the program. The usual cause of this type of error is:
1. The program cannot be found.
2. There is not enough storage available to start the program.
3. The file system program specified in the /FS parameter of the
   FORMAT command cannot be found.
4. The final installation diskette must be replaced with the
   Operating System/2 Diskette 1.
ACTION: Do one of the following; then, retry the command.
1. Check that the program name in the current path is correct.
2. Reduce the number of running programs.
3. Check that the file system name is correct.
4. Remove the final installation diskette and insert
   Operating System/2 Diskette 1 in drive A.
HEXPLANATION: A function needed by the program is not available
or is in use.
ACTION: Wait awhile; then retry the command.
HEXPLANATION: The specified file system does not work with
the disk or diskette being used.
ACTION: Do one of the following; then retry the command.
1. Specify a different file system name.
2. Use a different disk or diskette.
HEXPLANATION: There is not enough available storage to load
the specified system program or device driver.
ACTION: Perform one of the following actions, then restart
the system:
1. Edit the CONFIG.SYS file to increase the amount of
   storage available by:
   a. Reducing the value on the BUFFERS command
   b. Removing unnecessary DEVICE and/or RUN commands
   c. Reducing the value on the DISKCACHE command
   d. Reducing the value on the TRACEBUF command
   e. Reducing the size of the virtual disk specified on
      the DEVICE=VDISK command
2. If the failing program is COMMAND.COM, edit the
   CONFIG.SYS file to increase the value on the RMSIZE
   command.
3. If the failing program is not COMMAND.COM, edit the
   CONFIG.SYS file to decrease the value on the RMSIZE
   command or add the PROTECTONLY=YES command.
4. Install another memory option in your system unit.
HEXPLANATION: All drive letters are being used by the hard
disks.
ACTION: Delete any logical partitions that are not needed.
HEXPLANATION: The specified command in the CONFIG.SYS file
has more parameters than are expected.
ACTION: Edit the CONFIG.SYS file to correct or remove
the incorrect command. Then restart the system.
HEXPLANATION: The required symbol has been left out or is
misplaced.
ACTION: Edit the CONFIG.SYS file to correct or remove
the incorrect command. Then restart the system.
HEXPLANATION: An option was selected that
does not exist.  Options /B, /C, /T, and /D:
are the only options the system accepts.
ACTION: Retry the command using a correct
option.
HEXPLANATION: The parameters selected cannot
appear together or no parameter was specified.
The correct syntax is:
  PRINT /C [/D:device]
  PRINT /T [/D:device]
  PRINT pathname... [/D:device] [/B]
ACTION: Enter the parameters correctly and
retry the command.
HEXPLANATION: Correct printer device names
are PRN, LPT1, LPT2, and LPT3.
ACTION: Retry the PRINT command using a
correct printer device.
HEXPLANATION: A /C or /T option was requested
but the spooler is not running.
ACTION: Retry the command without the /C or
/T option.
HEXPLANATION: The /C or /T parameter can only be used
while in an OS/2 session.
ACTION: Switch to an OS/2 session and try the command again.
HEXPLANATION: 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.
HEXPLANATION: The parameter specified is not valid for the FDISK
command. /D is the only parameter that you can use.
ACTION: To perform the delete operation, type FDISK /D.
HEXPLANATION: The PATCH command accepts the
following parameters:
To patch a file interactively:
   PATCH filename
where filename identifies the file to be patched
To patch a file automatically:
   PATCH /A filename
where filename identifies a patch instruction file
ACTION: Check the PATCH parameters and retry the command.
HEXPLANATION: 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.
HEXPLANATION: The requested offset is greater
than the size of the file.
ACTION: Make sure you entered the correct
offset.
HEXPLANATION: PATCH could not allocate enough
storage to save all the patch information.
ACTION: Split the patch request into two or
more PATCH sessions.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION:  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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The file to be appended cannot
be opened for reading.
ACTION: Make sure the file exists and the
file name is spelled correctly.
HEXPLANATION: 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.
HEXPLANATION: The MODE command accepts the
following parameters:
To set parallel printer modes:
   MODE LPT# chars,lines,P
   MODE PRN  chars,lines,P
To set video modes:
   MODE display,rows
To set asynchronous modes for DOS sessions:
   MODE COM#:baud,parity,databits,stopbits
To set asynchronous modes for OS/2 sessions:
   MODE COM#:baud,parity,databits,stopbits,
   TO=ON|OFF,XON=ON|OFF,IDSR=ON|OFF,ODSR=ON|OFF,
   OCTS=ON|OFF,DTR=ON|OFF|HS,RTS=ON|OFF|HS|TOG
To set diskette verification:
   MODE DSKT VER=ON|OFF
ACTION: Check the MODE parameters and retry the command.
For more information about MODE, refer to the Command Reference.
HEXPLANATION: The value for the printer parameter is not correct.
Only the following values can be used:
   LPT# or PRN (# can equal 1, 2, or 3)
ACTION: Correct the value; then, retry the command.
HEXPLANATION: The value for the printer parameter is not correct.
Only the following values can be used:
   CHARS - 80, 132
ACTION: Correct the value; then, retry the command.
HEXPLANATION: The value for the printer parameter is not correct.
Only the following values can be used:
   LINES - 6, 8
ACTION: Correct the value; then, retry the command.
HEXPLANATION: The value for the COM# parameter is not correct.
Only the following values can be used:
   COM#    -  1-8
ACTION: Correct the value; then, retry the command.
To view other asynchronous communications MODE command parameters,
enter: HELP 1625
HEXPLANATION: The value for the BAUD parameter is not correct.
Only the following values can be used:
   BAUD    -  110, 150, 300, 600, 1200, 1800, 2400, 3600,
              4800, 7200, 9600, 19200, 38400, 57600, 76800, 115200,
              138240, 172800, 230400, 345600
   NOTE: Rates higher than 19200 are only valid on certain systems.
ACTION: Correct the value; then, retry the command.
To view other asynchronous communications MODE command parameters,
enter: HELP 1625
HEXPLANATION: 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;
then, retry the command.
HEXPLANATION: MODE detected a COM port that is not installed.
ACTION: Specify an installed COM port; then, retry the command.
HEXPLANATION: The value for the video mode parameter is not correct.
Only the following values can be used:
ROWS - 25
       43
       50
ACTION: Correct the value; then, retry the command.
HEXPLANATION: The value for the video mode parameter is not correct.
Only the following values can be used:
DISPLAY - 40
          80
          BW40
          BW80
          CO40
          CO80
          MONO
ACTION: Correct the value; then, retry the command.
HEXPLANATION: When you specify a ROWS parameter for the MODE
command, you must also specify a DISPLAY parameter. The
following DISPLAY parameters can be used:
ACTION: Specify a DISPLAY and ROW parameter; then, retry the command.
HEXPLANATION: The values for the asynchronous communications MODE
parameters are not correct. Only the following values can be used:
   COM#    -  1-8
   BAUD    -  110, 150, 300, 600, 1200, 1800, 2400, 3600,
              4800, 7200, 9600, 19200, 38400, 57600, 76800, 115200,
              138240, 172800, 230400, 345600
   PARITY   - N(one), O(dd), E(ven), M(ark), S(pace)
   DATABITS - 5, 6, 7, 8
   STOPBITS - 1, 1.5, 2
              (1.5 STOPBITS is correct only if DATABITS is set to 5)
   TO   - ON, OFF
   XON  - ON, OFF
   IDSR - ON, OFF
   ODSR - ON, OFF
   OCTS - ON, OFF
   DTR  - ON, OFF, HS
   RTS  - ON, OFF, HS, TOG
   NOTE: Rates higher than 19200 are only valid on certain systems.
ACTION: Correct the value; then, retry the command.
To view the correct format for entering the MODE command and its
parameters, enter: HELP 1601
HEXPLANATION: The value for the diskette verification parameter is not
correct. Only the following values can be used:
   DSKT VER=ON, OFF
ACTION: Correct the value; then, retry the command.
HEXPLANATION: The DISPLAY or ROW parameter is not correct for the
type of video device specified. The following are the correct
combinations of DISPLAY and video device:
DISPLAY:
   80, BW80, CO80 - XGA, VGA, EGA, CGA, MPA
   40, BW40, CO40 - XGA, VGA, EGA, CGA
                    (Not valid in a VIO window)
   MONO - EGA, VGA, XGA
ROWS:
   25 - XGA, VGA, EGA, CGA, MPA
   43 - XGA, VGA, EGA
   50 - XGA, VGA
ACTION: Correct the value; then, retry the command.
HEXPLANATION: The value for the DATABITS parameter is not correct.
Only the following values can be used:
   DATABITS -  5-8
ACTION: Correct the value; then, retry the command.
To view other asynchronous communications MODE command parameters,
enter: HELP 1625
HEXPLANATION: The value for the STOPBITS parameter is not correct.
Only the following values can be used:
   STOPBITS - 1, 1.5, 2
              (1.5 STOPBITS is correct only if DATABITS is set to 5)
ACTION: Correct the value; then, retry the command.
To view other asynchronous communications MODE command parameters,
enter: HELP 1625
HEXPLANATION: The value for the PARITY parameter is not correct.
Only the following values can be used:
   PARITY   - N(one), O(dd), E(ven), M(ark), S(pace)
ACTION: Correct the value; then, retry the command.
To view other asynchronous communications MODE command parameters,
enter: HELP 1625
HEXPLANATION: The MODE parameter is not recognized.
ACTION: Correct the value; then, retry the command.
To view the correct format for entering the MODE command and its
parameters, enter: HELP 1601
HEXPLANATION: A disk cannot be restored onto itself.
ACTION: Retry the command using the correct
source and target drive letters.
HEXPLANATION: More than 11 parameters or less
than 2 parameters were entered.
ACTION: Retry the command using the correct
number of parameters.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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 any
unwanted files from the disk and retry the command.
HEXPLANATION: No drive letter was entered for
the BACKUP command.
ACTION: Retry the command specifying a
correct drive letter.
HEXPLANATION: A source drive must be
specified for the BACKUP command.
ACTION: Retry the command specifying
a source drive.
HEXPLANATION: A target drive must be
specified for the BACKUP command.
ACTION: Retry the command specifying
a target drive.
HEXPLANATION: A disk cannot be backed up onto itself.
ACTION: Retry the command using the correct
source and target drive letters.
HEXPLANATION: Either the system cannot find FORMAT.COM
file or there is not enough storage in the system.
ACTION: Insert a formatted diskette and
backup will continue.
HEXPLANATION: A non-existent drive
specification was entered for the command or
one of its parameters.
ACTION: Retry the command using a correct
drive specifier.
HEXPLANATION: 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.
HEXPLANATION: One of the following errors occurred:
1. The path specified is incorrect.
2. The logfile is read-only.
3. The logfile is being used by another process.
ACTION: Choose the appropriate ACTION:
1. Specify the correct path.
2. Use the ATTRIB command to remove the read-only
   attribute of the file.
3. Wait until the logfile is no longer in use.
4. Use a different file name for the logfile.
Then retry the command.
HEXPLANATION: The /F parameter cannot be used
to format a hard disk.
ACTION: Retry the command without the /F
parameter, or specify a diskette drive.
HEXPLANATION: The file is being used by another process.
ACTION: Retry the command later and use the /M parameter.
HEXPLANATION: 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.
HEXPLANATION: 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: To correct problems 1 and 2, check to
see if a directory by that name exists in the
current directory.  To correct problem 3,
use the CHKDSK command to see if the directory
is full.  To correct problem 4, use another
name for the directory.  To correct problem 5,
be sure to use the correct characters.
HEXPLANATION: The path specified is greater
than 63 characters.
ACTION: Specify a path name with up to
63 characters.
HEXPLANATION: 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.
HEXPLANATION: 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.
  /Q       Queries the system to determine which operating
           system will start next.
ACTION: Specify the correct parameter or parameters; then,
try the command again.
HEXPLANATION: The file contains errors, or the file is in use
by another process.
ACTION: Do one of the following:
  1. Correct the errors in the file.
  2. Wait until the process using the file finishes.
Then try the command again.
HEXPLANATION: Either the source directory was not
specified, or a parameter was entered more than once.
ACTION: Correct the parameters and retry the command.
HEXPLANATION: This utility requires DOS version 3.20 or higher.
ACTION: Install the appropriate version of DOS; then, try the
command again.
HEXPLANATION: 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 try the
command again.
HEXPLANATION: The requested operating system is the same as
the current operating system. The BOOT command should be
used when you want 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; then, try the
command again.
HEXPLANATION: An error occurred during the attempt to change
the startup operating system.
ACTION: Reinstall the DOS and OS/2 operating systems.
HEXPLANATION: The BOOT utility made changes to your hard disk
and replaced the C:\CONFIG.SYS and C:\AUTOEXEC.BAT files in
preparation for the next reset.
Note that if you restart the system 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) and start your system again.
HEXPLANATION: The specified file was not copied. The file
might not exist, or it might contain errors or be in use
by another process.
ACTION: Do one of the following. Then, try the command again:
1. Copy the file to the startup drive.
2. Correct any errors in the file.
3. Wait until the process using the file finishes.
HEXPLANATION: 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: Start your system again by pressing Ctrl+Alt+Del.
HEXPLANATION: The file containing the specified device
driver, program, or data file cannot be found.
ACTION: Install the specified file. Then restart the system.
HEXPLANATION: 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, then
restart the system:
1. Edit the CONFIG.SYS file to correct or remove the
   incorrect command.
2. Edit the CONFIG.SYS file to remove the PROTECTONLY=YES
   command.
3. Install the correct device driver or file system driver in the specified
   file.
4. Install all dynamic link libraries required by the
   specified device driver.
HEXPLANATION: There is not enough storage available for the
storage specified by the DISKCACHE statement.
ACTION: Try one of the following:
1. 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.
2. Install another memory option in your system unit.
Then restart the system.
HEXPLANATION: The value specified in the DISKCACHE statement in
the CONFIG.SYS file 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. Then restart the system.
For more information about the minumum value needed, refer to
DISKCACHE in the Command Reference.
HEXPLANATION: 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, then restart
the system:
1. Edit the CONFIG.SYS file to correct or remove the
   CODEPAGE command.
2. Edit the CONFIG.SYS file to correct or add the
   DEVINFO=SCR command.
3. Install the correct font file for the display.
HEXPLANATION: One or more of the specified code page(s) 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, then restart
the system:
1. Edit the CONFIG.SYS file to correct or remove the
   CODEPAGE command.
2. Edit the CONFIG.SYS file to correct or add the
   DEVINFO=KBD command.
3. Install the correct keyboard translation file.
HEXPLANATION: 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:
1. 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.
2. If you have just run BOOT /DOS, make sure that the OS/2
   CONFIG.SYS file contains the DEVICE=C:\OS2\DOS.SYS statement.
Then, press Ctrl+Alt+Del to restart the system.
HEXPLANATION: The specified file is not a valid country
information file or the file has been destroyed.
ACTION: Install the correct country information file. Then
restart the system.
HEXPLANATION: 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:
1. 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.
2. Ensure that the OS/2 CONFIG.SYS file contains the
   DEVICE=C:\OS2\DOS.SYS statement.
Press Ctrl+Alt+Del to restart the system; then, try the command
again.
HEXPLANATION: The storage 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: An external error has occurred and
the system cannot continue with the operation.
ACTION: Retry the command.
HEXPLANATION: The translate table file that is 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; then retry the command.
1. Edit the DEVINFO= statement in the CONFIG.SYS file to use
   the system provided translate table file (KEYBOARD.DCP).
2. Correct the translate table file.
HEXPLANATION: The operating system detected an error opening
the keyboard. The usual cause of this error is too many files
or programs are open.
ACTION: Do one of the following; then retry the command.
1. Reduce the number of running programs.
2. Reduce the number of open files.
HEXPLANATION: 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.
HEXPLANATION: The system cannot continue to load
the translate table because it has detected an error.
ACTION: Retry the command.
HEXPLANATION: 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.
HEXPLANATION: 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 the CONFIG.SYS file does not specify
a country information file, make sure that the
COUNTRY.SYS file exists in the root directory of the
startup drive. Correct the problem and restart the system.
HEXPLANATION: The code page specified has not
been defined by a CODEPAGE= command in the
CONFIG.SYS file.
ACTION: Define the CODEPAGE= command in the
CONFIG.SYS file using a valid code page,
and then restart the system.
HEXPLANATION: The START command has a wrong parameter or combination
of parameters.
ACTION: Check the command syntax; then retry the command.
HEXPLANATION: The spooler option was not started.
ACTION: Start the spooler by using the Spooler Object in the.
System Setup folder.
HEXPLANATION: The Presentation Manager detected an
error while trying to write to this device.
ACTION: Make sure the device is:
1. Installed and connected
2. Switched on
3. Not being used by another process
4. In the proper receive mode
Retry the command.
HEXPLANATION: 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.
HEXPLANATION:  A communications port can be
used by only one application at a time.
ACTION:  You may end a program by selecting
it from the Presentation Manager Window List
and then closing it.
HEXPLANATION:  A parallel port can be used
by only one application at a time.
ACTION:  You may end a program by selecting it
from the Presentation Manager Window List
and then closing it.
HEXPLANATION: 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;
then, try the command again.
HEXPLANATION: A Presentation Manager application cannot be
executed using the DETACH command.
ACTION: Try executing the program using the START command.
HEXPLANATION: 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.
HEXPLANATION: The file does not exist or is in a different directory.
ACTION: Check the spelling of the file name and its location.
Retry the command.
HEXPLANATION: 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. Retry the command.
HEXPLANATION: 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.
HEXPLANATION: The program generated an exception
that the system cannot resolve.  The software
diagnostic code allows determination of what type
of exception was generated.
ACTION: Correct the problem or try a different
version of the program.
HEXPLANATION: The process ended when it tried to divide
a number by zero.
ACTION: Correct the problem or try a different
version of the program.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The device name is not correct.
ACTION: Check the device name or spelling and retry the command.
HEXPLANATION: The batch file that was running cannot be found, or has
been deleted.
ACTION: Replace or reconstruct the batch file and retry the command.
HEXPLANATION: CHKDSK requires more memory to examine the extended attribute
chains for this file or directory. All the extended attribute chains
on this disk will be ignored.
ACTION: Do one of the following; then restart the system and retry the
command:
1. Reduce the number of running programs.
2. Reduce the value of BUFFERS=, TRACEBUF=, DISKCACHE=, THREADS=,
RMSIZE=, or DEVICE=VDISK.SYS statements, in the CONFIG.SYS file.
3. Remove unwanted swap files from the hard disk or diskette.
4. Install additional memory.
HEXPLANATION: One or more extended attributes already exist
on the target directory or file. The extended attribute join
operation is not allowed when extended attributes already
exist unless the override switch is selected.
ACTION: Use the /O parameter on the EAUTIL command to select
the override switch.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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; then retry the command.
1. Set the infinite timeout setting to TO=ON in the
   OS/2 session.
2. Switch to a DOS session.
HEXPLANATION: This port supports Enhanced Mode (DMA), but
the COMDMA.SYS device driver cannot use Enhanced Mode because
the Arbitration Levels are set incorrectly.  Each of the
Arbitration Levels for the COM port should be set to
DEDICATED, and there must be a difference between the
Arbitration Levels for Receive and Transmit.
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.
HEXPLANATION: The file specified does not contain a
startable program.
ACTION: Perform one of the following actions, then
restart the system:
1. Edit the CONFIG.SYS file to correct or remove the
   incorrect command.
2. Install the correct program file.
3. Install all dynamic link libraries required by the
   specified program.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The file specified does not contain a
startable program.
ACTION: Perform one of the following actions, then
restart the system:
1. Install the correct program file.
2. Install all dynamic link libraries required by the
   specified program.
HEXPLANATION: A DOS program has changed an interrupt vector
that is exclusively owned by the system.
ACTION: Correct the program and retry the command.
HEXPLANATION: A code or data segment was either
discarded or swapped out. There is not enough
available storage to reload it.
ACTION: Retry the command.
HEXPLANATION: One of the following occurred:
1. A program tried to divide a number by zero.
2. 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.
HEXPLANATION: A program enabled the single step
interrupt when it was not being run by a debugger.
ACTION: Correct the program and retry the command.
HEXPLANATION: A program started an INT 3 instruction
when it was not being run by a debugger.
ACTION: Correct the program and retry the command.
HEXPLANATION: A program started an INTO instruction
without registering an overflow exception handler.
ACTION: Correct the program and retry the command.
HEXPLANATION: A program started a BOUND instruction
without registering a bound exception handler.
ACTION: Correct the program and retry the command.
HEXPLANATION: A program started an invalid instruction
without registering an invalid opcode exception handler.
ACTION: Correct the program and retry the command.
HEXPLANATION: 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.
HEXPLANATION: The system caused a double fault exception.
ACTION: Restart the system and retry the command.
HEXPLANATION: A program ran a numeric coprocessor
instruction that tried to read or write to storage
that is past the end of a storage segment.
ACTION: Correct the program and retry the command.
HEXPLANATION: The system caused an invalid task state
segment exception.
ACTION: Restart the system and retry the command.
HEXPLANATION: A program attempted to reference a memory segment
that is not currently in storage and was not previously
discarded or swapped out.
ACTION: Correct the program and retry the command.
HEXPLANATION: One of the following occurred:
1. A program attempted to push more data
   onto the stack than the stack could hold.
2. A program called too many subroutines.
3. A program attempted to take more data off the
   stack than was pushed onto the stack.
4. A program tried to return more subroutines than were called.
ACTION: Correct the program and retry the command.
HEXPLANATION: The errors include (but are not limited to) a
memory object that is:
1. Referring to storage that is outside the limits of memory,
   restricted to privileged code, or has a selector object of
   zero.
2. Writing to a read-only segment, or a code segment.
3. Reading from an execute-only code segment.
4. Loading an invalid value into a selector register.
5. Causing a 80286 or 80386 General Protection Fault.
ACTION: Correct the program and retry the command.
HEXPLANATION: 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.
HEXPLANATION: The errors include (but are not limited to) a
memory object that is:
1. Referring to storage outside the limits of a memory, or
   restricted to privileged code.
2. Writing to a read-only memory object.
3. Writing to a code object.
ACTION: Correct the program, and retry the command.
HEXPLANATION: A program ran a numeric coprocessor
instruction that specified one or more incorrect operands.
ACTION: Correct the program and retry the command.
HEXPLANATION: A program started a numeric coprocessor
instruction that specified one or more incorrect operands.
ACTION: Correct the program and retry the command.
HEXPLANATION: A number cannot be divided by zero.
ACTION: Correct the program and retry the command.
HEXPLANATION: A program started a numeric coprocessor
instruction that generated a numeric overflow condition.
ACTION: Correct the program and retry the command.
HEXPLANATION: A program ran a numeric coprocessor
instruction that generated a numeric overflow condition.
ACTION: Correct the program and retry the command.
HEXPLANATION: A program started a numeric coprocessor
instruction that generated a precision error.
ACTION: Correct the program and retry the command.
HEXPLANATION: 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 six
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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: One of the following occurred:
1. The wrong name was entered
2. A file is missing from the application.
ACTION: Do one of the following
1. Check the instructions on how the application should be run.
2. Reinstall the application and retry the command.
Press any key to continue.
HEXPLANATION: The device that is to receive the information
is not working.
ACTION: Check the device. If it's a disk make sure there
is enough space available.
HEXPLANATION: The selected process ID(s) 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.
HEXPLANATION: Only the extension of PIP is an
acceptable file extension.
ACTION: Check the file extension to be sure
it is PIP.
HEXPLANATION: The command or program in
use requires a different version of
Operating System/2.
ACTION: Use Operating System/2
Version 2.0 and restart the system, or
install the proper version of the
command or program on the system and
retry the command.
HEXPLANATION: EDLIN was entered without
the name of the file to be edited.
ACTION: Enter EDLIN followed by the file name.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: An error occurred while
the file was being read into storage.
ACTION: Copy the file or a backup of the file
to a different disk and retry the command.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: Except for the 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.
HEXPLANATION: The replacement of a string caused the
line to expand beyond the 253-character limit.  The R
(Replace Text) command ended abnormally.
ACTION: Split the long line into shorter lines. Then,
issue the R command again.
HEXPLANATION: A destination line number is missing from
an M (Move Lines) or C (Copy Lines) command.
ACTION: Retry the command with a destination line
number.
HEXPLANATION: The T (Transfer Lines)
command could not merge the entire
contents of the file because of
insufficient storage. Only part of
the file was merged.
ACTION: Reduce the size of the specified
file or the file being edited.
HEXPLANATION: 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.
HEXPLANATION: The invalid parameter is specified in the CONFIG.SYS file.
ACTION: Correct the line in the CONFIG.SYS file that contains the error;
then, retry the operation.
HEXPLANATION: 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.
HEXPLANATION: The LOGDAEM.EXE program tried to run without the Logging
Facility device driver (LOG.SYS).
ACTION: Add the following statement to your CONFIG.SYS file:
              DEVICE=C:\OS2\LOG.SYS
Then, restart your system.
HEXPLANATION: One of the following has occurred:
1. The /E: parameter in the RUN=LOGDAEM.EXE statement contains an
   invalid file name in the CONFIG.SYS file.
2. 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.
HEXPLANATION: 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; then, use the SYSLOG command if you
want to redirect logging to another log file.
HEXPLANATION: 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; then, use the SYSLOG command to
redirect logging to another log file.
HEXPLANATION: The LOGDAEM.EXE program 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, then
redirect logging to a new log file.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: This command expected more information
than the input file contained. There is not enough
data to complete the process.
ACTION: Check the information for the command that failed.
Make sure that all the information necessary for this
command to complete normally is entered in the input file.
Retry the command.
HEXPLANATION: 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, then use the SYSLOG command to try the
log-file redirection again.
HEXPLANATION: Not enough storage is available to create the DOS
environment or the specified DOS environment size is too large.
ACTION: Perform one of the following actions, then
restart the system:
1. Edit the CONFIG.SYS file to decrease the value on the
   RMSIZE command.
2. Edit the CONFIG.SYS file to add the PROTECTONLY=YES
   command.
HEXPLANATION: There is not enough storage available to
create the DOS environment or the specified DOS environment size
is too small.
ACTION: Perform one of the following actions, then
restart the system:
1. Edit the CONFIG.SYS file to remove unnecessary DEVICE
   commands.
2. Edit the CONFIG.SYS file to increase the value on the
   RMSIZE command.
3. Edit the CONFIG.SYS file to add the PROTECTONLY=NO
   command.
HEXPLANATION: 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.
HEXPLANATION: The specified file is not a valid country
information file or the file has been damaged.
ACTION: Perform one of the following actions, then
restart the system:
1. Edit the CONFIG.SYS file to correct or remove the
   COUNTRY command.
2. Install the correct country information file.
HEXPLANATION: 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.
HEXPLANATION: Either the file does not exist or it is not in your path.
ACTION: Copy SYSLOGPM.EXE into your path; then, retry the command.
For more information about SYSLOG, refer to the OS/2 Command
Reference.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION:  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.
HEXPLANATION: One of the following errors occurred:
1. The port is not installed.
2. The port is malfunctioning.
3. A DEVICE= statement for a COMxx device driver
   is not included in the CONFIG.SYS file.
ACTION: Do the following:
1. Install the port.
2. Repair the port.
3. Put a DEVICE=COMxx statement in the CONFIG.SYS file.
Then restart the system.
HEXPLANATION: The system encountered an error while
loading the program.
ACTION: Do one of the following;
1. Retry loading the program using a backup copy
   of the program.
2. Try running the program when nothing else is
   running in the system.
3. Change the RMSIZE= statement in the CONFIG.SYS
   file to a larger size. Then restart the system
   and retry the program.
HEXPLANATION: One of the following occurred:
1. You specified a hard disk drive letter.
2. You specified an incorrect number of parameters for this command.
ACTION: Do one of the following:
1. Specify a diskette drive letter.
2. Correct the number of parameters for this command.
HEXPLANATION: The MODE command accepts the
following parameters:
To set parallel printer modes:
   MODE LPT# chars,lines,P
To set video modes:
   MODE 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=ON|OFF,XON=ON|OFF,IDSR=ON|OFF,ODSR=ON|OFF,
   OCTS=ON|OFF,DTR=ON|OFF|HS,RTS=ON|OFF|HS|TOG
To set diskette verification:
   MODE DSKT VER=OFF|ON
ACTION: Check the MODE parameters and retry the command.
HEXPLANATION: Either the network is not started, or your
CONFIG.SYS file is not correct.
ACTION: Start the network.
If the problem is not corrected, contact your network administrator.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: You specified an operation that requires the network
to be running.
ACTION: Start the network; then, retry this operation.
HEXPLANATION: 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.
HEXPLANATION: The queue that you specified is not valid.
ACTION: Verify that the spelling of the queue name is correct.
HEXPLANATION: 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 identification
number. Check the printer you sent where you sent this job.
HEXPLANATION: This printer given is not defined on the system.
ACTION: Verify the spelling of the print device given.
HEXPLANATION: You tried to create a print queue with a name that is
already in use.
ACTION: Assign the new queue with a different name.
HEXPLANATION: The system does not have enough memory available to add another
print queue.
ACTION: To free memory, delete an existing print queue.  Then, create
the new queue.
HEXPLANATION: The system does not have enough memory available to add another
print job.
ACTION: Wait a while, then send the print job again.
HEXPLANATION: The specified printer is not in use.
ACTION: Make sure that you are referring to the correct printer.
HEXPLANATION: 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.
HEXPLANATION: The spooler has not been started.
ACTION: Start the OS/2 Spooler.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: The queue driver that you specified has not been installed.
ACTION: Use the Print Destination object to install the queue driver.
HEXPLANATION: The server required to access the network may be off line.
ACTION: Retry the request.  If this problem persists, contact your system
administrator.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: You have attempted to install a block DOS device driver
or a block VDD (Virtual Device Driver). 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.
HEXPLANATION: The DOS setting specified is not valid, and a VDM
session cannot be started until this value is corrected.
ACTION: Correct the DOS setting value, and start the VDM session
again.
HEXPLANATION: The password specified is no longer valid.
ACTION: Contact your system administrator to obtain a new password.
HEXPLANATION: This network connection does not exist.
ACTION: Verify your active connections.
HEXPLANATION: The device given does not represent a known print device.
ACTION: Verify your spelling; then retry the command.
HEXPLANATION: 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.
HEXPLANATION: Check the syntax of the computer name.
ACTION: Correct the syntax of the computer name; then retry the operation.
If the problem persists, contact your system administrator.
HEXPLANATION: 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.
HEXPLANATION: You are trying to access a drive, through the prompt, that no
longer exists.
ACTION: Specify a valid drive.
HEXPLANATION: In COMMAND.COM, the correct syntax for specifying the
environment size in bytes is /E:nnn, where nnn is from 160 to 32768.
One of the following has occurred:
  1.  You specified a number that is too large (above 32768), or
      too small (below 160).
  2.  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.
HEXPLANATION: 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.
HEXPLANATION: 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 with the /E option.
HEXPLANATION: 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.
HEXPLANATION: The PATH= statement 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 try the command again.
HEXPLANATION: One of the following has occurred:
1.  There is not enough memory to load COMMAND.COM.
2.  The memory control blocks have been corrupted.
ACTION: Type EXIT to end the current copy of COMMAND.COM; then, try the
operation again.
HEXPLANATION: 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.
HEXPLANATION: Not enough storage is available to process this command.
ACTION:  Type EXIT to end the current copy of COMMAND.COM; then try the
operation again.
HEXPLANATION: The attempt to start the .EXE or .COM file failed.
The following error conditions have been checked and it is NOT:
1. File not found
2. Access denied
3. Insufficient memory
4. Bad load module format.
The program cannot be run as it now exists.
ACTION:   Contact the supplier of the application.
HEXPLANATION: The name specified should be one of the following:
1. The name of a DOS internal command.
2. The name of a DOS external command.
3. The name of an executable program whose file extension is .EXE or .COM.
4. The name of a batch file whose file extension is .BAT.
For cases 2, 3, and 4: 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.
ACTION: Try the command again using a correct name or PATH.
HEXPLANATION: 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. Be sure the COMSPEC variable is specifying a valid version of
   COMMAND.COM.
3. Be sure 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.
HEXPLANATION: 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.
HEXPLANATION: 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: You cannot change copies of COMMAND.COM by changing COMSPEC.  You
must load a secondary copy into memory.
HEXPLANATION:  The BREAK, ECHO, or VER command tried to use a parameter
other than ON or OFF.
ACTION: Retry the command with the correct parameter.
HEXPLANATION: 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.
HEXPLANATION:  The COPY command does not permit the source file
to use the binary option (/B) if it is a device.  Copying from devices can
only use ASCII files.
ACTION: Retry the COPY command without the /B after the source device name.
HEXPLANATION:  An input/output error occurred while trying to write to
a device.  The device is unable to handle the number of bytes requested.
ACTION:  Change the amount of data in the file and try the operation again.
HEXPLANATION: A FOR statement cannot be used inside another FOR statement.
ACTION: Remove the nested FOR, then try the operation again.
HEXPLANATION: An invalid number of parameters was given to the command.
ACTION: Correct the number of parameters; then try the command again.
Refer to the Command Reference for the correct number of parameters.
HEXPLANATION: 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.
HEXPLANATION: The character is not valid as a drive specification because:
  1. It is not a letter, or
  2. The drive is not available on this system.
ACTION: Retry ASSIGN and specify a valid drive letter.
HEXPLANATION: The character is not valid as a separator. The only valid
separators are: space, tab, comma, semicolon, plus sign, equal sign, or
line feed.
ACTION: Retry ASSIGN, and specify a valid separator.
HEXPLANATION: The character specified is not valid with the
command used.
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 xxxx, where xxxx
is the name of the command you tried using with the switch.
HEXPLANATION: 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; then, try LABEL again.
HEXPLANATION: An internal memory allocation strategy error occurred
when the system tried to use the LOADHIGH or LH command.
ACTION: Delete the LOADHIGH or LH command from the command line;
then, retry the command.
HEXPLANATION: 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.
HEXPLANATION: The required value following the switch character is either
incorrect or missing.
ACTION: Correct the switch-character value; then, retry the command.
HEXPLANATION: DBCS characters are not valid switch-character values.
ACTION: Correct the switch-character value; then, retry the command.
HEXPLANATION: Read-only files cannot be deleted, nor can they be 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.
HEXPLANATION: The RENAME command cannot change the path of a file.
Therefore, the second parameter cannot specify a path.
ACTION: Remove the path specified in the second parameter; then retry
the command.
HEXPLANATION: The RENAME command cannot change the drive of a file.
Therefore, the second parameter cannot specify a drive.
ACTION: Remove the drive specified in the second parameter; then retry
the command.
HEXPLANATION: You must specify a file name when using the following
commands:  RENAME, ERASE, VDISK.
ACTION: Specify a file name; then, retry the command.
HEXPLANATION: 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.
HEXPLANATION: 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: If you want to start a new buffer type:
DOSKEY/REINSTALL /BUFSIZE=size.
NOTE: This will discard all command history and
macro definitions.
HEXPLANATION: A copy of DOSKEY is already installed in this
DOS session. However, it does not match the version of DOSKEY
previously installed.
ACTION: If you want 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.
HEXPLANATION: 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: If you want to create a new DOSKEY buffer and
specify a larger size, type:
DOSKEY /REINSTALL /BUFSIZE=size.
HEXPLANATION: The DOSKEY command requires that an equal sign
be used in the following cases:
1. DOSKEY /BUFSIZE=size.
2. DOSKEY macro=text.
ACTION: Retry the command using an equal sign.
HEXPLANATION: The name specified should be one of the following:
1. The name of a DOS internal command.
2. The name of a DOS external command.
3. The name of an executable program whose file extension is .EXE or .COM.
4. The name of a batch file whose file extension is .BAT.
For cases 2, 3, and 4: If a path for the command was no specified
at the command prompt, the file must reside in the current directory
or in one of the directories specified by the PATH environment.
ACTION: Use a correct name or path; then, retry the command.
HEXPLANATION: 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 disk.
HEXPLANATION: 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 disk.
HEXPLANATION: 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.
HEXPLANATION: 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; then, retry the operation.
HEXPLANATION: The process was ended because the program generated
an unhandled fatal user (i.e. 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION:  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.
HEXPLANATION: 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 excactly
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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: This exception was raised when an exception handler
returned something except 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION: 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.
HEXPLANATION:  The DELDIR environment variable specifies a temporary
storage directory for each drive that supports the
Undelete function.  If this environment variable is not
present, or is entered incorrectly, the Undelete function
will not be active for the affected drive.
ACTION:  In order to activate the Undelete function for a drive,
add the appropriate DELDIR environment parameters to your CONFIG.SYS
file.  Refer to the Command Reference for more information.
HEXPLANATION: 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.
HEXPLANATION:  An error occured while trying to restore a deleted file to
its original path.
ACTION:  Make sure that the disk or diskette is not damaged, then retry
the command.
HEXPLANATION:  An error occured while trying to permanently discard a file
in the temporary storage directory.
ACTION:  Make sure that the disk or diskette is not damaged, then retry
the command.
HEXPLANATION:  No files matching the specified path were found.
ACTION: Enter "UNDELETE [drive:]\* /LIST /S" for a list of recoverable
files on the desired disk.
HEXPLANATION: An error occured 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:
1. Check that the disk or diskette is not damaged.
2. Make sure that the disk is not full.
3. Make sure that the you have not reached the maximum number of directories.
HEXPLANATION: The system has found that configuration memory does
not contain the correct information for your hardware configuration
(setup).
ACTION: Insert in 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.