  -408-


  APPENDIX A / ERROR MESSAGES


  This appendix lists error messages generated by 4DOS, 4OS2, and
  4NT, and includes a recommended course of action where
  appropriate.  If you are unable to resolve the problem, look
  through your Introduction and Installation Guide for any
  additional troubleshooting recommendations, then contact JP
  Software for technical support (see page 5).

  Error messages relating to files are generally reports of errors
  returned by the operating system.  You may find some of these
  messages (for example, "Access denied") vague enough that they are
  not always helpful.  4DOS, 4OS2, and 4NT include the file name in
  file error messages, but are often unable to determine a more
  accurate explanation of these errors.  The message shown is the
  best information available based on the error codes returned by
  the operating system.

  For some errors you are instructed to "restart the session or
  reboot the system."  This means that you should attempt to correct
  the error by closing and restarting the current session under
  OS/2, Windows 95, Windows NT, or a DOS task switcher or
  multitasker.  Under DOS without a multitasker or task switcher,
  you will probably have to reboot the system to correct the
  problem.

  The following list includes all error messages, in alphabetical
  order:

4DOS   4DOS internal stack overflow:  You attempted to nest batch
       files or commands like DO, EXCEPT, FOR, IF, IFF, GLOBAL, or
       SELECT too deep, and 4DOS ran out of stack space.
       Restructure your command, alias, or batch file, or use the
       OPTION command or the StackSize directive in 4DOS.INI to
       increase the internal stack size.

4DOS   4DOS initialization error --:  An error occurred during the
       4DOS startup process.  Look up the rest of the message in
       this list for a more specific explanation.

4DOS   4DOS server error --:  An error occurred in communication
       between 4DOS's resident and transient portions.  A more
       specific error message follows (the additional error message
       can be looked up in this list) .

4DOS   4DOS swapping failed, loading in non-swapping mode:  None of
       the swapping options worked, so 4DOS loaded in non-swapping
       mode, which requires about 200K of additional DOS memory.
       Check your Swapping specification with the OPTION command or
       in 4DOS.INI, and/or free some XMS or EMS memory or disk
       space.

4DOS   4DOS unrecoverable error XX:  An error occurred in the
       resident portion of 4DOS.  These errors will terminate
       secondary shells and, and may require you to reboot the
  -409-

       system or restart the session if they occur during a primary
       shell or if 4DOS cannot continue.  The error codes are:

            BI      Bad function code.  Contact JP Software.
            DI      Same as Disk swap file corrupted (see page 411).
            DR      Same as Swap file read error (see page 417)..
            DS      Same as Swap file seek error (see page 417)..
            EI      Same as EMS mapping error (see page 412)..
            NS      No number for new shell.  You have started too
                    many 4DOS secondary shells without properly
                    exiting some of them.  Clean up any work in
                    process and reboot the system or restart the
                    session.
            PT      Illegal process termination.  Contact JP
                    Software.
            TS      Terminated inactive shell.  Contact JP Software.
            XI      Same as XMS move failed (see page 418)..

       Access denied:  You tried to write to or erase a read-only
       file, rename a file or directory to an existing name, create
       a directory that already exists, remove a read-only directory
       or a directory with files or subdirectories still in it, or
       access a file in use by another program in a multitasking
       system.

4DOS   Address table missing:  Your 4DOS.COM file is invalid.  If
       you used an executable file compression program on 4DOS.COM,
       the compression may not be compatible with 4DOS.  Re-install
       4DOS.COM from diskette, or download a new copy.

       Alias loop:  An alias refers back to itself either directly
       or indirectly (i.e., a = b = a), or aliases are nested more
       than 16 levels deep.  Correct your alias list.

       Already excluded files:  You used more than one exclude range
       in a command.  Combine the exclusions into a single range.

4DOS   Attempt to exit from root shell:  Another program has
       probably destroyed a portion of 4DOS's memory.  Reboot the
       system or restart the session; if the error persists, contact
       JP Software.

       Batch file missing:  4DOS, 4OS2, or 4NT can't find the batch
       (.BAT or .CMD) file it was running.  It was either deleted,
       renamed, moved, or the disk was changed.  Correct the problem
       and rerun the file.

       Can't COPY or MOVE file to itself:  You cannot COPY or MOVE a
       file to itself.  4DOS, 4OS2, and 4NT attempt to perform full
       path and filename expansion before copying to help ensure
       that files aren't inadvertently destroyed.

       Can't create:  The command processor can't create the
       specified file.  The disk may be full or write protected, or
       the file already exists and is read-only, or the root
       directory is full.
  -410-

       Can't delete:  The command processor can't delete the
       specified file or directory.  The disk is probably write
       protected.

       Can't get directory:  The command processor can't read the
       directory.  The disk drive is probably not ready.

4OS2   Can't install hook:  4OS2 cannot install the operating system
       hooks required to support the KEYSTACK command.  The
       operating system may have been damaged or improperly
       installed, or there may be too few resources to support
       KEYSTACK.

       Can't make directory entry:  The command processor can't
       create the filename in the directory.  This is usually caused
       by a full root directory.  Create a subdirectory and move
       some of the files to it.

       Can't open:  The command processor can't open the specified
       file.  Either the file doesn't exist or the disk directory or
       File Allocation Table is damaged.

       Can't remove current directory:  You attempted to remove the
       current directory, which is prohibited.  Change to the parent
       directory and try again.

4DOS   Can't set up disk swap file:  The disk swap file you
       specified cannot be opened.  The path or drive is invalid,
       the disk is full, DOS is out of file handles, or there is a
       hardware problem.  Use the OPTION command or check 4DOS.INI
       to be sure your Swapping directive is correct.

       CD-ROM door open or CD-ROM not ready:  The CD-ROM drive door
       is open, the power is off, or the drive is disconnected.
       Correct the problem and try again.

       CD-ROM not High Sierra or ISO-9660:  The CD-ROM is not
       recognized as a data CD (it may be a music CD).  Put the
       correct CD in the drive and try again.

       Clipboard is in use by another program:  4DOS, 4OS2, or 4NT
       could not access the Windows or OS/2 clipboard because
       another program was using it.  Wait until the clipboard is
       available, or close the other program, then try again.

       Clipboard is empty or not text format:  You tried to retrieve
       some text from the Windows or OS/2 clipboard, but there is no
       text available.  Correct the contents of the clipboard and
       try again.

       Command line too long:  A single command exceeded 255
       characters in 4DOS or 1023 characters in 4OS2 or 4NT, or the
       entire command line exceeded 511 characters in 4DOS, or 2047
       characters in 4OS2 or 4NT, during alias and variable
       expansion.  Reduce the complexity of the command or use a
       batch file.  Also check for an alias which refers back to
       itself either directly or indirectly.
  -411-

       Command only valid in batch file:  You have tried to use a
       batch file command, like DO or GOSUB, from the command line
       or in an alias.  A few commands can only be used in batch
       files (see the individual commands for details).

4DOS   Command tail too long, truncated:  A program attempted to
       pass a command in an improper format or a command longer than
       126 characters to a 4DOS secondary shell.  This is probably a
       bug in the program from which 4DOS was loaded.  Contact the
       author of the program or JP Software for technical
       assistance.

       Contents lost before copy:  COPY was appending files, and
       found one of the source files is the same as the destination.
       That source file is skipped, and appending continues with the
       next file.

       Data error:  The operating system can't read or write the
       device.  On a floppy drive, this error is usually caused by a
       defective disk, dirty heads, or a misalignment between the
       heads on your drive and the drive on which the disk was
       created.  On a hard drive, it may indicate temperature
       sensitivity or another hardware problem.  Retry the
       operation; if it fails again, check for a diskette or
       hardware problem.

       Directory stack empty:  POPD or DIRS can't find any entries
       in the directory stack.

       Disk is write protected:  The disk cannot be written to.
       Check the disk and remove the write-protect tab or close the
       write-protect window if necessary.

4DOS   Disk swap file corrupted:  The 4DOS disk swapping file
       (4DOSSWAP.nnn or xxxxxxxx.4SW) has been moved, deleted, or
       damaged by another program.  Reboot the system or restart the
       session.

       Drive not ready -- close door:  The removable disk drive door
       is open.  Close the door and try again.

       Duplicate redirection:  You tried to redirect standard input,
       standard output, or stand error more than once in the same
       command.

4DOS   EMS deallocation failed:  4DOS can't deallocate EMS memory
       when exiting from a secondary shell.  The EMS map has been
       corrupted or the memory area used by 4DOS or the EMS driver
       has been destroyed by a program.  Clean up any work in
       process and reboot the system or restart the session.

4DOS   EMS map save or restore failed:  4DOS cannot save or restore
       the EMS page map.  The EMS map has been corrupted, memory has
       been destroyed by a program, or you have an incompatible EMS
       driver.  If this error recurs, try another swapping method,
       update your EMS driver, or contact JP Software.
  -412-

4DOS   EMS mapping failed:  4DOS can't map EMS pages when swapping
       to or from EMS.  The EMS map has been corrupted or the memory
       area used by the loader or the EMS driver has been destroyed.
       Reboot the system or restart the session.

       Environment already saved:  You have already saved the
       environment with a previous SETLOCAL command.  You cannot
       nest SETLOCAL / ENDLOCAL pairs.

       Error in command-line directive:  You used the //iniline
       option to place an .INI directive on the startup command
       line, or, under 4DOS, on the SHELL= line in CONFIG.SYS, but
       the directive is in error.  Usually a more specific error
       message follows, and can be looked up in this list.

       Error on line [nnnn] of [filename]:  There is an error in
       your .INI file.  The following message explains the error in
       more detail.  Correct the line in error and restart the
       command processor for your change to take effect.

       Error reading:  The operating system experienced an I/O error
       reading from a device.  This is usually caused by a bad disk,
       a device not ready, or a hardware error.

       Error writing:  The operating system experienced an I/O error
       writing to a device.  This is usually caused by a full disk,
       bad disk, drive not ready, or hardware error.

       Exceeded batch nesting limit:  You have attempted to nest
       batch files more than 10 levels deep.

4DOS   Fatal error -- please reboot:  4DOS cannot continue due to
       the previous error.  Reboot the system or restart the
       session.

4DOS   Fatal error, some directives may not have been processed:  An
       I/O error occurred while reading your 4DOS.INI file.  There
       may be a physical problem with data on the disk or a sharing
       error on a multitasking system.

       File Allocation Table bad:  The operating system  can't
       access the FAT on the specified disk.  This can be caused by
       a bad disk, a hardware error, or an unusual software
       interaction.

4NT    File association not found:  The ASSOC command could not find
       a file association for the specified extension in the Windows
       NT registry.

       File exists:  The requested output file already exists, and
       the command processor won't overwrite it.

       File is empty:  You attempted to LIST a file with no data (a
       zero-byte file).

       File not found:  4DOS, 4OS2, or 4NT couldn't find the
       specified file.
  -413-

4NT    File type not found:  The FTYPE command could not find the
       specified file type in the Windows NT registry.

       General failure:  This is usually a hardware problem,
       particularly a disk drive failure or a device not properly
       connected to a serial or parallel port.  Try to correct the
       problem, or reboot and try again.  Also see Data error above.

       Include file not found:  You used the Include directive in
       the .INI file, but the file you specified was not found or
       could not be opened.

       Include files nested too deep:  You used the Include
       directive in the .INI file, and attempted to nest include
       files more than three levels deep.

       Infinite COPY or MOVE loop:  You tried to COPY or MOVE a
       directory to one of its own subdirectories and used the /S
       switch, so the command would run forever.  Correct the
       command and try again.

       Insufficient disk space:  COPY or MOVE ran out of room on the
       destination drive.  Remove some files and retry the
       operation.

4DOS   Insufficient load space:  There is not enough room in 4DOS's
       internal memory areas to include all of the options you
       requested in 4DOS.INI.  Contact JP Software.

4DOS   Internal DOS error:  DOS encountered an internal bug and
       failed.  Reboot the system.

4DOS   Invalid AUTOEXEC filename:  You specified an invalid path or
       filename for the AUTOEXEC file with the /P: startup switch,
       or with the DOS_AUTOEXEC setting in an OS/2 DOS session.  The
       default name will be used instead.

       Invalid character value:  You gave an invalid value for a
       character directive in the .INI file.

       Invalid choice value:  You gave an invalid value for a
       "choice" directive (one that accepts a choice from a list,
       like "Yes" or "No") in the .INI file.

       Invalid color:  You gave an invalid value for a color
       directive in the .INI file.

       Invalid count:  The character repeat count for KEYSTACK is
       incorrect.

       Invalid date:  An invalid date was entered.

       Invalid directive name:  4DOS, 4OS2, or 4NT can't recognize
       the name of a directive in your .INI file.

4DOS   Invalid DOS version:  You need a newer version of DOS to
       execute the specified command.
  -414-

       Invalid drive:  A bad or non-existent disk drive was
       specified.

4DOS   Invalid INI file path or name, file not processed:  The path
       or name for the initialization file on the SHELL= line in
       CONFIG.SYS, or on the startup command line, is invalid.
       Correct the @d:\path\inifile option to name the correct file.

       Invalid key name:  You tried to make an invalid key
       substitution in the .INI file, or you used an invalid key
       name in a keystroke alias or command.

       Invalid numeric value:  You gave an invalid value for a
       numeric directive in the .INI file.

       Invalid parameter:  The command processor didn't recognize a
       parameter.  Check the syntax and spelling of the command you
       entered.

       Invalid path:  The specified path does not exist.

       Invalid path or file name:  You used an invalid path or
       filename in a directive in the .INI file.

4DOS   Invalid startup switch, ignored:  You passed 4DOS an invalid
       option on the SHELL= line in CONFIG.SYS or on the startup
       command line for a secondary shell.

4DOS   Invalid Swapping option or path:  The swap type or disk swap
       path in the 4DOS.INI Swapping directive is invalid.  4DOS
       ignores the bad swap type or path and attempts to scan the
       rest of the Swapping specification for a valid option.
       Multiple errors in the Swapping directive will cause this
       message to repeat.

       Invalid time:  An invalid time was entered.  Check the syntax
       and reenter.

       Keystroke substitution table full:  4DOS, 4OS2, or 4NT ran
       out of room to store keystroke substitutions entered in the
       .INI file.  Reduce the number of key substitutions or contact
       JP Software.

4DOS   KSTACK.COM not loaded:  You attempted to execute a KEYSTACK
       command without loading KSTACK.COM.  See KEYSTACK for more
       information.

       Label not found:  A GOTO or GOSUB command referred to a non-
       existent label.

4DOS   Memory [allocation | deallocation] error:  4DOS can't
       allocate or deallocate memory while loading, or while
       reserving or releasing memory for internal use.  DOS memory
       allocation has been corrupted, or another application has
       reserved memory incorrectly.  Reboot the system or restart
       the session.
  -415-

4DOS   Memory destroyed:  The DOS memory control blocks have been
       corrupted.  Reboot the system or restart the session.

       Missing ENDTEXT:  A TEXT command is missing a matching
       ENDTEXT.

       Missing GOSUB:  Your batch file attempted to RETURN from a
       subroutine, but no subroutine had been called with GOSUB.

       Missing SETLOCAL:  An ENDLOCAL was used without a matching
       SETLOCAL.

       No aliases defined:  You tried to display aliases but no
       aliases have been defined.

       No closing quote:  4DOS, 4OS2, or 4NT couldn't find a second
       matching back-quote [`] or double-quote ["] on the command
       line.

       No expression:  The expression passed to the @EVAL variable
       function is empty.  Correct the expression and retry the
       operation.

4DOS   No file handle available:  This is an internal 4DOS disk
       swapping error.  Change to another swapping method if
       possible, or contact JP Software.

4DOS   No room for INI file name:  4DOS does not have enough space
       to pass the name of your .INI file to secondary shells; see
       String area overflow for more details.  Any [Secondary]
       section in 4DOS.INI will be ignored in secondary shells.

4DOS   No UMBs; loading low:  The LOADHIGH (or LH) command can't
       find any UMBs for your program.  The program is loaded into
       base memory.  LH and LOADHIGH only work with MS-DOS 5.0 and
       above, when the DOS=UMB directive is included in CONFIG.SYS
       and sufficient upper memory space is available for the
       program.

4DOS   No upper memory available, low memory will be used for ...:
       You asked 4DOS to load the block of memory named in the
       message into a UMB via the corresponding directive in
       4DOS.INI (UMBLoad, UMBEnvironment, etc.), but no UMB was
       available.  Check that your XMS driver is properly installed
       and/or free up some UMB space in use by another program.

4DOS   Non-DOS disk:  DOS can't read the disk.  Either the disk is
       bad, or it has been formatted by a different operating
       system.  Reformat it as a DOS disk.  Also see Data error
       above; the problems described there can sometimes cause this
       error.

       Not an alias:  The specified alias is not in the alias list.

       Not in environment:  The specified variable is not in the
       environment.
  -416-

4DOS   Not in swapping mode:  You attempted to turn swapping on or
       off with the SWAPPING command, but 4DOS is loaded in non-
       swapping mode.

       Not ready:  The specified device can't be accessed.

       Not same device:  This error usually appears in RENAME.  You
       cannot rename a file to a different disk drive.

4DOS   Out of environment/alias space:  4DOS has run out of space
       for environment variables or aliases.  Edit the SHELL line in
       CONFIG.SYS or the Environment directive in 4DOS.INI to
       increase the environment size, or the Alias directive in
       4DOS.INI to increase the alias list size.

       Out of memory:  The command processor or the operating system
       had insufficient memory to execute the last command, or under
       DOS, the memory control blocks have been destroyed.  If this
       error occurs in a 4DOS secondary shell, return to the primary
       shell before running the command.  Otherwise, try to free
       some memory by removing memory-resident programs (under DOS),
       or closing other sessions (under OS/2 and Windows NT).  If
       the error persists, contact JP Software for assistance.

4DOS   Under 4DOS, if the base memory (DOS RAM) figures reported by
       MEMORY are unreasonable, the memory control blocks have
       probably been destroyed and you must reboot the system or
       restart the session.

       Out of paper:  The operating system detected an out-of-paper
       condition on one of the printers.

       Overflow:  An arithmetic overflow occurred in the @EVAL
       variable function.  Check the values being passed to @EVAL.
       @EVAL can handle 16 digits to the left of the decimal point
       and 8 to the right.

       Read error:  The operating system encountered a disk read
       error; usually caused by a bad or unformatted disk.  Also see
       Data error above.

4DOS   Region unavailable, using first available region for ...:
       You used a 4DOS.INI directive to load the block of memory
       named in the message into a specific UMB region, but that
       region was unavailable.  Check the use of upper memory for
       device drivers and other programs loaded before 4DOS, or
       change the requested region.

       Sector not found:  BIOS disk error, usually caused by a bad
       or unformatted disk.  Also see Data error above.

       Seek error:  The operating system can't seek to the proper
       location on the disk.  This is generally caused by a bad disk
       or drive.  Also see Data error above.

       Sharing violation:  You tried to access a file in use by
       another program in a multitasking system or on a network.
  -417-

       Wait for the file to become available, or change your method
       of operation so that another program does not have the file
       open while you are trying to use it.

4DOS   Specified INI file not found:  The file specified with the
       @inifile option on the 4DOS command line does not exist.

       String area overflow:  The command processor ran out of room
       to store the text from string directives in the .INI file.
       Reduce the complexity of the .INI file or contact JP Software
       for assistance.

4DOS   Swap file [seek | read | write] failed:  4DOS encountered an
       I/O error while accessing the disk swap file (4DOSSWAP.nnn or
       xxxxxxx.4SW).  The disk was changed, the file has been
       destroyed by a program, or 4DOS's memory area has been
       overwritten by another program.  Reboot the system or restart
       the session.

       Syntax error:  A command or variable function was entered in
       an improper format.

4DOS   Syntax error in region number or size:  You specified an
       invalid region number or size in the LH or LOADHIGH command.

4DOS   Too many SETs in CONFIG.SYS:  The SET commands in your Novell
       DOS / OpenDOS CONFIG.SYS file exceeded the size of 4DOS's
       buffer area.  Reduce the length of the commands or contact JP
       Software for assistance.

4DOS,  Too many open files:  DOS or OS/2 has run out of file
4OS2   handles.  Try increasing the FILES setting in CONFIG.SYS.

4DOS   Transient memory [allocation | deallocation] error:  4DOS
       could not reserve or release memory for its transient portion
       (probably in a SWAPPING OFF or SWAPPING ON command).  The
       memory control blocks have been destroyed, or a program has
       fragmented memory.  Reboot the system or restart the session.

       Unbalanced parentheses:  The number of left and right
       parentheses did not match in an expression passed to the
       @EVAL variable function.

       Unknown command:  A command was entered that 4DOS, 4OS2, or
       4NT didn't recognize and couldn't find in the current search
       path.  Check the spelling or PATH specification.  You can
       handle unknown commands with the UNKNOWN_CMD alias (see page
       186).

       UNKNOWN_CMD loop:  The UNKNOWN_CMD alias (see page 186)
       called itself more than ten times.  The alias probably
       contains an unknown command itself, and is stuck in an
       infinite loop.

       Variable loop:  A nested environment variable refers to
       itself, or variables are nested more than 16 deep.
  -418-

4OS2,  Window title not found:  The ACTIVATE or WINDOW command
4NT    cannot find a window with the title you specified.

       Write error:  The operating system encountered a disk write
       error; usually caused by a bad or unformatted disk.  Also see
       Data error above.

4DOS   XMS deallocation failed:  4DOS could not deallocate XMS
       memory when exiting a secondary shell.  XMS memory has been
       destroyed; reboot the system or restart the session.

4DOS   XMS move failed:  4DOS could not move data between base
       memory and XMS memory while swapping itself.  XMS memory has
       been destroyed; reboot the system or restart the session.
