ERRORS.DOC November 1996 JAR ERROR MESSAGES WITH BRIEF EXPLANATION: #100 Can't open file for reading This error message usually occurs if JAR is trying to compress a file which is locked by another application. #101 Can't create file JAR can't create a file with the specified name. Filename may contain unsupported characters. #102 Unknown, no description available JAR detected an error situation but a description is not available. This is an internal JAR error. #104 Wrong program flow detected at (,) Possibly conflict with used software or hardware One of the internal JAR checks failed. This may be an internal JAR error or a conflict with installed software or hardware. #105 Internal at (,) Possibly conflict with hardware Another type of internal JAR check failed. #107 EMS call failed Extended error code EMS memory manager returned error code. Check that your memory manager is installed properly and does not conflict with other software or hardware. #108 XMS call failed Extended error code XMS memory manager returned error code. Check that your memory manager is installed properly and does not conflict with other software or hardware. #109 Internal table overflow Near memory heap exhausted. You need to specify a simpler command or fewer arguments. #110 Not enough memory Not enough conventional memory to run program. The JAR DOS version usually uses less memory if EMS memory is available. Detailed information about memory usage available in JAR.DOC. #111 DOS version 3.30 required JAR requires DOS version 3.30 or higher. #112 Can't read file File read operation failed. #113 Can't write file File write operation failed. Usually this means that disk space is exhausted. #114 Can't seek file Seek operation on file failed. #115 Unexpected end of file while reading JAR expected that more data would be available. Possibly the archive is damaged. #116 Requested command exhausted all virtual memory. Please specify simpler operation JAR uses built-in virtual memory (VM) to process many files using a limited amount of physical memory. On update operations JAR can use up to 25Mbytes of virtual memory. Reported error means that all VM is exhausted. You need to decrease the number of files to be processed. #117 Bad data to decompress JAR engine detected data which cannot be decompressed. This means that your archive is damaged. You can try the "-jr" and "-hx" options to extract files. #118 Can't read directory Directory scan operation failed. #119 Error while reading directory Directory scanning can't be completed. #120 Scanned filename can't be stored into archive JAR scanned filename which contains unsupported binary characters. Probably your directory or disk FAT is damaged. #121 File size changed since scanning JAR uses the scanned file size to choose the proper compression method. So the file size should not change until after the file is compressed. #122 Test with compressed file contents failed. Probably file was modified The file comparison test with option "-ht1" failed. One possibility is that the file has been modified since the time of compression. Another possibility is faulty hardware or software. #123 CRC check failed File failed CRC check. The archive is damaged. You can try the "-jr" and "-hx" options to extract files. #124 Path is too long to be processed JAR supports paths up to about 380 characters length. #125 Path within archive is not valid You specified an incorrect path to be stored within an archive. Note that JAR does not support the storing of drive letters within an archive. Use the "-ho" option instead. #126 Can't store two files into same location JAR does not support the storing of two filenames with the same path in an archive. Use the "-ho" or "-jf" options as a possible workaround. #127 File is greater than 1G so can't be handled The current JAR engine does not support compression of files larger than 1Gbyte. #128 Unsupported header format. Probably it is damaged JAR detected unsupported header format. Archive is damaged. #129 Necessary program version or higher Newer compressor version required. Note that the JAR archive records the necessary compressor version for three types of operations: update, extract and list. #134 Error reading standard input Read from standard input failed. #135 Argument is too long Command line or response file argument is too long. #136 Binary character parsed Command line or response file contains binary characters. #137 No trailing quote Incorrectly specified quoted argument. #138 Response file is nested too deep Self-explanatory. #139 No command No command specified. #140 Unknown switch Command line or response file contains incorrect switch. #141 Wrong parameter Self-explanatory. #142 Unknown command Self-explanatory. #143 Option