  -426-




  APPENDIX A / ERROR MESSAGES


  This appendix lists error messages generated by Take Command, 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 your Introduction and Installation Guide).

  Error messages relating to files are generally reports of errors
  returned by Windows or OS/2.  You may find some of these messages
  (for example, "Access denied") vague enough that they are not
  always helpful.  Take Command includes the file name in file error
  messages, but is 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.

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

       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.

       Alias loop:  An alias refers back to itself either directly
       or indirectly (i.e., a = b = a), or aliases are nested more
       than 16 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.

TC16   Application requires Windows NT:  This program requires
       Windows NT features not available in Windows 3.x.  Obtain a
       16-bit version of the program, or run it under Windows NT.

TC16   Application requires 32-bit Windows:  This program requires
       32-bit features not available in Windows 3.x.  Obtain a 16-
       bit version of the program, or run it under Windows NT or
       Windows 95.

       Bad disk unit:  Generally caused by a disk drive hardware
       failure.

       Batch file missing:  Take Command 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.
  -427-



       Can't COPY or MOVE file to itself:  You cannot COPY or MOVE a
       file to itself.  Take Command attempts to perform full path
       and filename expansion before copying to help ensure that
       files aren't inadvertently destroyed.

       Can't create:  Take Command 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.

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

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

TCOS2  Can't install hook:  Take Command 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.

TC16   Can't load compressed EXE file:  Windows cannot read the EXE
       file you tried to run.  The file may be corrupted.  Reinstall
       the file or restore it from a backup.

TC16   Can't load real-mode application:  Windows cannot load the
       application.  The file may be corrupted.  Reinstall the file
       or restore it from a backup.

TC16   Can't load second instance:  Windows cannot load a second
       copy of the application.  Use the first copy, or close it
       before opening the second.

       Can't make directory entry:  Take Command 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:  Take Command 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 the operating system does not allow.
       Change to the parent directory and try again.

TC16   CAVEMAN.386 a.b.c installed -- Take Command requires x.y.z:
       You are running an older version of CAVEMAN.386 with a newer
       version of Take Command.  If you just upgraded Take Command,
       check the DEVICE statement in your SYSTEM.INI file to make
       sure it points to the correct directory for the new version.
       If you cannot resolve the problem contact JP Software or your
       dealer for assistance.  See the Take Command/16 Introduction
       and Installation Guide for details on installing Caveman.
  -428-



       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:  Take Command could
       not access the Windows or OS/2 clipboard because another
       program was using it.  Wait until the clipboard is available,
       or complete any pending action in 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 Take Command/16 or 1023 characters in Take
       Command/32 or Take Command for OS/2, or the entire command
       line exceeded 511 characters in Take Command/16, or 2047
       characters in Take Command/32 or Take Command for OS/2,
       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.

       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).

       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:  Windows or OS/2 can't read or write properly to
       the device.  On a floppy drive, this error is usually caused
       by a defective floppy disk, dirty disk drive heads, or a
       misalignment between the heads on your drive and the drive on
       which the disk was created.  On a hard drive, this error may
       indicate a drive that is too hot or too cold, or a hardware
       problem.  Retry the operation; if it fails again, correct the
       hardware or diskette problem.

       DDE [error message]:  A DDE transaction could not be
       completed by the DDEEXEC command.  The error message explains
       the reason.  Consult the documentation for the DDE server you
       are using for additional details if necessary.
  -429-



TC16   DLL is corrupt:  A Dynamic Link Library associated with the
       program you tried to run is corrupt.  Reinstall the .DLL
       file, or restore it from a backup.

       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.

       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.  Correct the command and try again.

       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, 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 Take
       Command for your change to take effect.

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

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

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

       File Allocation Table bad:  Windows 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.

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

       File exists:  The requested output file already exists, and
       Take Command won't overwrite it.
  -430-



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

       File not found:  Take Command couldn't find the specified
       file.  Check the spelling and path name.

TC32   File type not found:  The FTYPE command could not find the
       specified file type in the Windows 95 or 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.

TC16   Incorrect operating system:  The application you tried to run
       requires a different operating system.  Contact the
       manufacturer of the application for support.

TC16   Incorrect Windows version:  The application you tried to run
       requires a different version of Windows than the one you are
       using.  Contact the manufacturer of the application for
       support.

       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.

       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.
  -431-



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

       Invalid directive name:  Take Command can't recognize the
       name of a directive in your .INI file.

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

TC16   Invalid EXE file:  Windows cannot execute the program.  The
       EXE file may be corrupted.  Reinstall the file or restore it
       from a backup.

       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:  Take Command didn't recognize a
       parameter.  Check the syntax and spelling of the command you
       entered.

       Invalid path:  The specified path does not exist.  Check the
       disk specification and / or spelling.

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

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

       Keystroke substitution table full:  Take Command ran out of
       room to store keystroke substitutions entered in the .INI
       file.  Reduce the number of key substitutions or contact JP
       Software or your dealer for assistance.

       Label not found:  A GOTO or GOSUB referred to a non-existent
       label.  Check your batch file.

       Listbox is full:  There is no more room in the Find Files /
       Text dialog's results box.  Use a more selective search, or
       use the FFIND command rather than the dialog.

       Missing ENDTEXT:  A TEXT command is missing a matching
       ENDTEXT.  Check the batch file.

       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.
  -432-



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

       No closing quote:  Take Command 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.

TC32   No shared memory found:  The SHRALIAS command could not find
       any global alias list, history list, or directory history
       list to retain, because you executed the command from a
       session with local lists.  Start Take Command with at least
       one global list, then invoke SHRALIAS.

       Not a directory:  The command requires a directory name, but
       you gave a file name, or a name which does not exist at all.

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

TC16   Not an exexcutable file:  Windows cannot run the file.
       Either you specified a file which is not executable, or the
       file has been corrupted.  Correct the command, reinstall the
       file, or restore it from a backup.

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

       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.

       Out of memory:  Take Command or the operating system had
       insufficient memory to execute the last command.  Try to free
       some memory by closing other sessions.  If the error
       persists, contact JP Software for assistance.

       Out of paper:  The operating system detected an out-of-paper
       condition on one of the printers.  Check your printer and add
       paper if necessary.

       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.

TC16   Path not found:  Windows cannot find the file you tried to
       run.  Re-enter the command with the correct path.

TC16   Quit the active applications before exiting Windows:  The
       EXIT command failed when exiting with Take Command running as
  -433-



       the Windows shell, because one or more other applications
       would not close.  Close the other application(s) manually and
       try again.

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

       Sector not found:  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 error or Sharing violation:  You tried to access a
       file in use by another program, or modify or delete an
       executable file while it was running.  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.

TC32   SHRALIAS already loaded:  You used the SHRALIAS command to
       load SHRALIAS.EXE, but it was already loaded.  This message
       is informational and generally does not indicate an error
       condition.

TC32   SHRALIAS not loaded:  You used the SHRALIAS /U command to
       unload SHRALIAS.EXE, but it was never loaded.  This message
       is informational and may not indicate an error condition.

       Startup failed, contact JP Software:  Take Command could not
       initialize and start operation.  Contact JP Software or your
       dealer for assistance.

       String area overflow:  Take Command 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.

       Syntax error:  A command or variable function was entered in
       an improper format.  Check the syntax and correct the error.

       Too many open files:  Windows has run out of file handles.

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

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



       Unknown command:  A command was entered that Take Command
       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
       216).

TC16   Unknown EXE type:  Windows cannot execute the program.  The
       EXE file may be corrupted.  Reinstall the file or restore it
       from a backup.

       Variable loop:  A nested environment variable refers to
       itself, or variables are nested more than 16 deep.  Correct
       the error and retry the command.

       Window title not found:  The ACTIVATE command could not find
       a window with the specified title.  Correct the command or
       open the appropriate window and try again.

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