home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Computer Panoráma
/
computer_panorama_1997-12-hibas.iso
/
SHARE
/
PACK
/
ARJ255CX.EXE
/
ERRORS.DOC
< prev
next >
Wrap
Text File
|
1997-05-08
|
19KB
|
658 lines
ERRORS.DOC April 1997
The following error messages may appear when using ARJ. A brief
explanation of each message follows:
<filename> does not exist
The file <filename> could not be found on the disk.
This error 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. To correct this problem, you need to extract the previous
portion(s) of this file.
This error will also occur during an extraction to freshen
existing files.
<filename> exists
The file <filename> already exists on the disk.
<filename> is not an ARJ archive
The file <filename> does not have a valid ARJ archive header in
the initial portion of the file. This file may not be an ARJ
archive or it may be damaged.
<filename> is not the same date/time
The file <filename> that is being appended to does not have the
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.
<filename> is same or newer
The file <filename> has the same or newer file date-time stamp
than the matching file in the archive.
<filename> is same or older
The file <filename> has the same or older file date-time stamp
than the matching file in the archive.
Already a chapter archive
The archive being converted to a chapter archive is already a
chapter 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 <filename> to archive <filename>
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 <filename>
ARJ cannot delete the file <filename>. Most likely, the file is
in use or is set as readonly.
Can't find <filename>
The file <filename> does not exist.
Can't find restart file: <filename>
The file <filename> does not exist.
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 <number>
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 <directoryname>
ARJ could not create the directory <directoryname>. The name
<directoryname> may already exist or the name may be too long.
Can't open <filename>
ARJ cannot open the file <filename>. The file may be set to
readonly or it may already be in use. The "-hq" option may be
useful in some file-in-use situations.
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 <filename> to <filename>
ARJ could not rename <filename>. The target filename may already
exist.
Can't reset <filename>
ARJ could not reset the archive bit attribute of <filename>. This
error is ignored by ARJ.
Can't seek to position <number> in file
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 -je1
The small self-extraction module does not support multiple volume
archives.
Can't write file. Disk full?
Self-explanatory.
Cannot convert an archive to a dual-name archive
A dual-name archive must be so designated at the initial archive
creation. An already existing archive cannot be converted since
the alternate filenames have not been stored in the archive.
Cannot find damage in <filename>
Using the information from the ARJ damage protection file, ARJ
could not find any damaged data areas in the ARJ archive
<filename>. There is a small probability (about 1 in 3 billion)
that ARJ cannot detect a corrupted section of data.
Chapter error
This is an internal error in chapter processing and should not
happen. This indicates a problem in the program logic. Please
notify ARJ Software of this problem.
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.
CRC INFO sections damaged
The ARJ data damage protection file is too damaged to use to
repair archive damage.
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