Category : Utilities for DOS and Windows Machines
Archive : ARJ241A.ZIP
Filename : ERRORS.DOC
Output of file : ERRORS.DOC contained in archive : ARJ241A.ZIP
ERRORS.DOC April 1993
The following error messages may appear when using ARJ. A brief
explanation of each message follows:
The file
may occur in a multiple volume extraction if ARJ is trying to
extract a split file. If this split file is not the beginning of
the file, ARJ will look for the beginning of the file on the disk.
If this file is missing, ARJ will report this error.
The file
The file
the initial portion of the file. This file may not be an ARJ
archive or it may be damaged.
The file
correct file date-time stamp. This message occurs during multiple
volume extraction when the portion of the file on disk does not
match the portion in the archive. This can happen if a multiple
volume extraction was interrupted by a "quit" response.
The file
than the matching file in the archive.
Archive name argument missing
The ARJ command is missing the name of the ARJ archive filename.
Arg table overflow
There are more than 64 arguments on the ARJ command line.
*** Valid ARJ-SECURITY envelope signature:
This message is displayed when ARJ has verified that the archive
has a valid ARJ-SECURITY envelope. This indicates that the archive
contents are intact and unmodified as originally distributed by the
individual identified in the text that follows this message.
Bad command syntax
The ARJ command line is not correct syntactically.
Bad file data
The file in the ARJ archive is damaged and has invalid data in it.
It is not possible to recover this file in an undamaged format.
Bad file data or bad password
The file in the ARJ archive is damaged or you may have supplied
the wrong password to the "-g" option. Check the password that
you specified.
Bad header
The ARJ archive file description information record is damaged.
Bad or missing SECURITY key
An invalid or missing security key was provided to ARJ. Check
to see if the security key is correct.
Break signaled
The user pressed Control C or Control BREAK.
Can't copy temp
This error usually means that there is not enough disk space to
copy the intermediate archive file to its destination drive. ARJ
does not purge the intermediate archive file in this situation so
that the file can be copied manually to a drive with enough disk
space.
Can't delete
ARJ cannot delete the file
in use or is set as readonly.
Can't find
The file
Can't find restart file:
The file
Can't find restart information
During the scan of the specified index file, ARJ could not find
a line of text similar to the following:
Next volume - 001 1 19931 C:\ARC\VGA640.DRV
This can happened if the index file is damaged or was created by
a version of ARJ prior to 2.39.
Can't get volume label
ARJ could not read the volume label of the drive specified.
Can't handle ARJ-SECURITY version
This version of ARJ encountered an ARJ-SECURITY envelope version
of which it does not know how to verify the integrity.
Can't make directory
ARJ could not create the directory
Can't open
ARJ cannot open the file
readonly or it may already be in use.
Can't order a multiple volume archive
Re-ordering a multiple volume archive is NOT allowed.
Can't read file or unexpected end of file
This error message usually occurs if the end of the file has been
reached when ARJ is expecting more data.
Can't rename
ARJ could not rename
exist.
Can't reset
ARJ could not reset the archive bit attribute of
Can't seek to position
ARJ could not seek to the position in the file. This file may not
be as large as the position specified.
Can't update an ARJ-SECURED archive!
Modification of an ARJ-SECURED archive is NOT allowed.
Can't use -jt1 or -jt2 with -e or -e1
ARJ always uses the filename stored in the archive to access the
file during the compare operation. The -e and -e1 options strip
significant information from the filename.
Can't use -v with self-extraction
The ARJ self-extraction modules do not support multiple volume
archives.
Can't write file. Disk full?
Self-explanatory.
CRC error
The file in the ARJ archive is damaged and has invalid data in it.
It is not possible to recover this file in an undamaged format.
If this error is encountered when ARJ initially starts up, this
indicates that the ARJ runfile is probably damaged.
Critical device error
A DOS critical error has occurred. ARJ has trapped this error
condition and returned a error.
*** Damaged ARJ-SECURED archive!
This ARJ archive has been damaged or corrupted. The contents of
the archive are not in the same condition as when it was created.
Delete argument missing
The ARJ delete command requires that a filename or wildspec be
specified on the command line. It does not assume "*.*".
*** Detected an OBSOLETE ARJ-SECURITY envelope. NOT verified!
ARJ has detected a version 1 ARJ-SECURITY envelope. ARJ has not
verified the validity of the ARJ-SECURITY envelope because of
the obsolescence of version 1 envelopes.
Exceeded maximum path size of
The maximum pathname length is limited in size to
characters.
Exceeded name limit of
The number of filenames encountered by ARJ has exceeded the
documented limited of
File is password encrypted
ARJ is skipping the current file because it is password encrypted
(garbled) and no password has been specified on the command line
with the "-g" option.
Found
ARJ has encountered
Garbled files are not allowed for SFXJR
The small self-extractor module does not support the extraction of
garbled files.
Header CRC error
The file description header record in the archive is damaged.
This cannot be fixed. The use of the "-jr" option will allow the
recovery of files after the damaged section.
Invalid command:
The specified
Invalid comment header
This error should never happen.
Invalid date string:
The date
in YYMMDDHHMMSS format where YY represents the two digit year, MM
represents the month, DD represents the day, HH represents the
hour, MM represents the minutes, and SS represents the seconds.
Invalid multiple volume file sequence
ARJ has detected a sequence error in a series of multiple volume
archives. This error should never occur.
Invalid parameter string:
The parameter string
Invalid switch:
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/