&2
exit 1
;;
esac
# As a final step for OS-related things, validate the OS-kernel combination
# (given a valid OS), if there is a kernel.
case $kernel-$os in
linux-gnu* | linux-dietlibc* | linux-android* | linux-newlib* \
| linux-musl* | linux-relibc* | linux-uclibc* )
;;
uclinux-uclibc* )
;;
-dietlibc* | -newlib* | -musl* | -relibc* | -uclibc* )
# These are just libc implementations, not actual OSes, and thus
# require a kernel.
echo "Invalid configuration \`$1': libc \`$os' needs explicit kernel." 1>&2
exit 1
;;
kfreebsd*-gnu* | kopensolaris*-gnu*)
;;
vxworks-simlinux | vxworks-simwindows | vxworks-spe)
;;
nto-qnx*)
;;
os2-emx)
;;
*-eabi* | *-gnueabi*)
;;
-*)
# Blank kernel with real OS is always fine.
;;
*-*)
echo "Invalid configuration \`$1': Kernel \`$kernel' not known to work with OS \`$os'." 1>&2
exit 1
;;
esac
# Here we handle the case where we know the os, and the CPU type, but not the
# manufacturer. We pick the logical manufacturer.
case $vendor in
unknown)
case $cpu-$os in
*-riscix*)
vendor=acorn
;;
*-sunos*)
vendor=sun
;;
*-cnk* | *-aix*)
vendor=ibm
;;
*-beos*)
vendor=be
;;
*-hpux*)
vendor=hp
;;
*-mpeix*)
vendor=hp
;;
*-hiux*)
vendor=hitachi
;;
*-unos*)
vendor=crds
;;
*-dgux*)
vendor=dg
;;
*-luna*)
vendor=omron
;;
*-genix*)
vendor=ns
;;
*-clix*)
vendor=intergraph
;;
*-mvs* | *-opened*)
vendor=ibm
;;
*-os400*)
vendor=ibm
;;
s390-* | s390x-*)
vendor=ibm
;;
*-ptx*)
vendor=sequent
;;
*-tpf*)
vendor=ibm
;;
*-vxsim* | *-vxworks* | *-windiss*)
vendor=wrs
;;
*-aux*)
vendor=apple
;;
*-hms*)
vendor=hitachi
;;
*-mpw* | *-macos*)
vendor=apple
;;
*-*mint | *-mint[0-9]* | *-*MiNT | *-MiNT[0-9]*)
vendor=atari
;;
*-vos*)
vendor=stratus
;;
esac
;;
esac
echo "$cpu-$vendor-${kernel:+$kernel-}$os"
exit
# Local variables:
# eval: (add-hook 'before-save-hook 'time-stamp)
# time-stamp-start: "timestamp='"
# time-stamp-format: "%:y-%02m-%02d"
# time-stamp-end: "'"
# End:
cabextract-1.11/install-sh 0000755 0001750 0001750 00000035776 14376123607 012534 0000000 0000000 #!/bin/sh
# install - install a program, script, or datafile
scriptversion=2020-11-14.01; # UTC
# This originates from X11R5 (mit/util/scripts/install.sh), which was
# later released in X11R6 (xc/config/util/install.sh) with the
# following copyright and license.
#
# Copyright (C) 1994 X Consortium
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to
# deal in the Software without restriction, including without limitation the
# rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
# sell copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
# AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-
# TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
#
# Except as contained in this notice, the name of the X Consortium shall not
# be used in advertising or otherwise to promote the sale, use or other deal-
# ings in this Software without prior written authorization from the X Consor-
# tium.
#
#
# FSF changes to this file are in the public domain.
#
# Calling this script install-sh is preferred over install.sh, to prevent
# 'make' implicit rules from creating a file called install from it
# when there is no Makefile.
#
# This script is compatible with the BSD install script, but was written
# from scratch.
tab=' '
nl='
'
IFS=" $tab$nl"
# Set DOITPROG to "echo" to test this script.
doit=${DOITPROG-}
doit_exec=${doit:-exec}
# Put in absolute file names if you don't have them in your path;
# or use environment vars.
chgrpprog=${CHGRPPROG-chgrp}
chmodprog=${CHMODPROG-chmod}
chownprog=${CHOWNPROG-chown}
cmpprog=${CMPPROG-cmp}
cpprog=${CPPROG-cp}
mkdirprog=${MKDIRPROG-mkdir}
mvprog=${MVPROG-mv}
rmprog=${RMPROG-rm}
stripprog=${STRIPPROG-strip}
posix_mkdir=
# Desired mode of installed file.
mode=0755
# Create dirs (including intermediate dirs) using mode 755.
# This is like GNU 'install' as of coreutils 8.32 (2020).
mkdir_umask=22
backupsuffix=
chgrpcmd=
chmodcmd=$chmodprog
chowncmd=
mvcmd=$mvprog
rmcmd="$rmprog -f"
stripcmd=
src=
dst=
dir_arg=
dst_arg=
copy_on_change=false
is_target_a_directory=possibly
usage="\
Usage: $0 [OPTION]... [-T] SRCFILE DSTFILE
or: $0 [OPTION]... SRCFILES... DIRECTORY
or: $0 [OPTION]... -t DIRECTORY SRCFILES...
or: $0 [OPTION]... -d DIRECTORIES...
In the 1st form, copy SRCFILE to DSTFILE.
In the 2nd and 3rd, copy all SRCFILES to DIRECTORY.
In the 4th, create DIRECTORIES.
Options:
--help display this help and exit.
--version display version info and exit.
-c (ignored)
-C install only if different (preserve data modification time)
-d create directories instead of installing files.
-g GROUP $chgrpprog installed files to GROUP.
-m MODE $chmodprog installed files to MODE.
-o USER $chownprog installed files to USER.
-p pass -p to $cpprog.
-s $stripprog installed files.
-S SUFFIX attempt to back up existing files, with suffix SUFFIX.
-t DIRECTORY install into DIRECTORY.
-T report an error if DSTFILE is a directory.
Environment variables override the default commands:
CHGRPPROG CHMODPROG CHOWNPROG CMPPROG CPPROG MKDIRPROG MVPROG
RMPROG STRIPPROG
By default, rm is invoked with -f; when overridden with RMPROG,
it's up to you to specify -f if you want it.
If -S is not specified, no backups are attempted.
Email bug reports to bug-automake@gnu.org.
Automake home page: https://www.gnu.org/software/automake/
"
while test $# -ne 0; do
case $1 in
-c) ;;
-C) copy_on_change=true;;
-d) dir_arg=true;;
-g) chgrpcmd="$chgrpprog $2"
shift;;
--help) echo "$usage"; exit $?;;
-m) mode=$2
case $mode in
*' '* | *"$tab"* | *"$nl"* | *'*'* | *'?'* | *'['*)
echo "$0: invalid mode: $mode" >&2
exit 1;;
esac
shift;;
-o) chowncmd="$chownprog $2"
shift;;
-p) cpprog="$cpprog -p";;
-s) stripcmd=$stripprog;;
-S) backupsuffix="$2"
shift;;
-t)
is_target_a_directory=always
dst_arg=$2
# Protect names problematic for 'test' and other utilities.
case $dst_arg in
-* | [=\(\)!]) dst_arg=./$dst_arg;;
esac
shift;;
-T) is_target_a_directory=never;;
--version) echo "$0 $scriptversion"; exit $?;;
--) shift
break;;
-*) echo "$0: invalid option: $1" >&2
exit 1;;
*) break;;
esac
shift
done
# We allow the use of options -d and -T together, by making -d
# take the precedence; this is for compatibility with GNU install.
if test -n "$dir_arg"; then
if test -n "$dst_arg"; then
echo "$0: target directory not allowed when installing a directory." >&2
exit 1
fi
fi
if test $# -ne 0 && test -z "$dir_arg$dst_arg"; then
# When -d is used, all remaining arguments are directories to create.
# When -t is used, the destination is already specified.
# Otherwise, the last argument is the destination. Remove it from $@.
for arg
do
if test -n "$dst_arg"; then
# $@ is not empty: it contains at least $arg.
set fnord "$@" "$dst_arg"
shift # fnord
fi
shift # arg
dst_arg=$arg
# Protect names problematic for 'test' and other utilities.
case $dst_arg in
-* | [=\(\)!]) dst_arg=./$dst_arg;;
esac
done
fi
if test $# -eq 0; then
if test -z "$dir_arg"; then
echo "$0: no input file specified." >&2
exit 1
fi
# It's OK to call 'install-sh -d' without argument.
# This can happen when creating conditional directories.
exit 0
fi
if test -z "$dir_arg"; then
if test $# -gt 1 || test "$is_target_a_directory" = always; then
if test ! -d "$dst_arg"; then
echo "$0: $dst_arg: Is not a directory." >&2
exit 1
fi
fi
fi
if test -z "$dir_arg"; then
do_exit='(exit $ret); exit $ret'
trap "ret=129; $do_exit" 1
trap "ret=130; $do_exit" 2
trap "ret=141; $do_exit" 13
trap "ret=143; $do_exit" 15
# Set umask so as not to create temps with too-generous modes.
# However, 'strip' requires both read and write access to temps.
case $mode in
# Optimize common cases.
*644) cp_umask=133;;
*755) cp_umask=22;;
*[0-7])
if test -z "$stripcmd"; then
u_plus_rw=
else
u_plus_rw='% 200'
fi
cp_umask=`expr '(' 777 - $mode % 1000 ')' $u_plus_rw`;;
*)
if test -z "$stripcmd"; then
u_plus_rw=
else
u_plus_rw=,u+rw
fi
cp_umask=$mode$u_plus_rw;;
esac
fi
for src
do
# Protect names problematic for 'test' and other utilities.
case $src in
-* | [=\(\)!]) src=./$src;;
esac
if test -n "$dir_arg"; then
dst=$src
dstdir=$dst
test -d "$dstdir"
dstdir_status=$?
# Don't chown directories that already exist.
if test $dstdir_status = 0; then
chowncmd=""
fi
else
# Waiting for this to be detected by the "$cpprog $src $dsttmp" command
# might cause directories to be created, which would be especially bad
# if $src (and thus $dsttmp) contains '*'.
if test ! -f "$src" && test ! -d "$src"; then
echo "$0: $src does not exist." >&2
exit 1
fi
if test -z "$dst_arg"; then
echo "$0: no destination specified." >&2
exit 1
fi
dst=$dst_arg
# If destination is a directory, append the input filename.
if test -d "$dst"; then
if test "$is_target_a_directory" = never; then
echo "$0: $dst_arg: Is a directory" >&2
exit 1
fi
dstdir=$dst
dstbase=`basename "$src"`
case $dst in
*/) dst=$dst$dstbase;;
*) dst=$dst/$dstbase;;
esac
dstdir_status=0
else
dstdir=`dirname "$dst"`
test -d "$dstdir"
dstdir_status=$?
fi
fi
case $dstdir in
*/) dstdirslash=$dstdir;;
*) dstdirslash=$dstdir/;;
esac
obsolete_mkdir_used=false
if test $dstdir_status != 0; then
case $posix_mkdir in
'')
# With -d, create the new directory with the user-specified mode.
# Otherwise, rely on $mkdir_umask.
if test -n "$dir_arg"; then
mkdir_mode=-m$mode
else
mkdir_mode=
fi
posix_mkdir=false
# The $RANDOM variable is not portable (e.g., dash). Use it
# here however when possible just to lower collision chance.
tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
trap '
ret=$?
rmdir "$tmpdir/a/b" "$tmpdir/a" "$tmpdir" 2>/dev/null
exit $ret
' 0
# Because "mkdir -p" follows existing symlinks and we likely work
# directly in world-writeable /tmp, make sure that the '$tmpdir'
# directory is successfully created first before we actually test
# 'mkdir -p'.
if (umask $mkdir_umask &&
$mkdirprog $mkdir_mode "$tmpdir" &&
exec $mkdirprog $mkdir_mode -p -- "$tmpdir/a/b") >/dev/null 2>&1
then
if test -z "$dir_arg" || {
# Check for POSIX incompatibilities with -m.
# HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
# other-writable bit of parent directory when it shouldn't.
# FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
test_tmpdir="$tmpdir/a"
ls_ld_tmpdir=`ls -ld "$test_tmpdir"`
case $ls_ld_tmpdir in
d????-?r-*) different_mode=700;;
d????-?--*) different_mode=755;;
*) false;;
esac &&
$mkdirprog -m$different_mode -p -- "$test_tmpdir" && {
ls_ld_tmpdir_1=`ls -ld "$test_tmpdir"`
test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
}
}
then posix_mkdir=:
fi
rmdir "$tmpdir/a/b" "$tmpdir/a" "$tmpdir"
else
# Remove any dirs left behind by ancient mkdir implementations.
rmdir ./$mkdir_mode ./-p ./-- "$tmpdir" 2>/dev/null
fi
trap '' 0;;
esac
if
$posix_mkdir && (
umask $mkdir_umask &&
$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
)
then :
else
# mkdir does not conform to POSIX,
# or it failed possibly due to a race condition. Create the
# directory the slow way, step by step, checking for races as we go.
case $dstdir in
/*) prefix='/';;
[-=\(\)!]*) prefix='./';;
*) prefix='';;
esac
oIFS=$IFS
IFS=/
set -f
set fnord $dstdir
shift
set +f
IFS=$oIFS
prefixes=
for d
do
test X"$d" = X && continue
prefix=$prefix$d
if test -d "$prefix"; then
prefixes=
else
if $posix_mkdir; then
(umask $mkdir_umask &&
$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
# Don't fail if two instances are running concurrently.
test -d "$prefix" || exit 1
else
case $prefix in
*\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
*) qprefix=$prefix;;
esac
prefixes="$prefixes '$qprefix'"
fi
fi
prefix=$prefix/
done
if test -n "$prefixes"; then
# Don't fail if two instances are running concurrently.
(umask $mkdir_umask &&
eval "\$doit_exec \$mkdirprog $prefixes") ||
test -d "$dstdir" || exit 1
obsolete_mkdir_used=true
fi
fi
fi
if test -n "$dir_arg"; then
{ test -z "$chowncmd" || $doit $chowncmd "$dst"; } &&
{ test -z "$chgrpcmd" || $doit $chgrpcmd "$dst"; } &&
{ test "$obsolete_mkdir_used$chowncmd$chgrpcmd" = false ||
test -z "$chmodcmd" || $doit $chmodcmd $mode "$dst"; } || exit 1
else
# Make a couple of temp file names in the proper directory.
dsttmp=${dstdirslash}_inst.$$_
rmtmp=${dstdirslash}_rm.$$_
# Trap to clean up those temp files at exit.
trap 'ret=$?; rm -f "$dsttmp" "$rmtmp" && exit $ret' 0
# Copy the file name to the temp name.
(umask $cp_umask &&
{ test -z "$stripcmd" || {
# Create $dsttmp read-write so that cp doesn't create it read-only,
# which would cause strip to fail.
if test -z "$doit"; then
: >"$dsttmp" # No need to fork-exec 'touch'.
else
$doit touch "$dsttmp"
fi
}
} &&
$doit_exec $cpprog "$src" "$dsttmp") &&
# and set any options; do chmod last to preserve setuid bits.
#
# If any of these fail, we abort the whole thing. If we want to
# ignore errors from any of these, just make sure not to ignore
# errors from the above "$doit $cpprog $src $dsttmp" command.
#
{ test -z "$chowncmd" || $doit $chowncmd "$dsttmp"; } &&
{ test -z "$chgrpcmd" || $doit $chgrpcmd "$dsttmp"; } &&
{ test -z "$stripcmd" || $doit $stripcmd "$dsttmp"; } &&
{ test -z "$chmodcmd" || $doit $chmodcmd $mode "$dsttmp"; } &&
# If -C, don't bother to copy if it wouldn't change the file.
if $copy_on_change &&
old=`LC_ALL=C ls -dlL "$dst" 2>/dev/null` &&
new=`LC_ALL=C ls -dlL "$dsttmp" 2>/dev/null` &&
set -f &&
set X $old && old=:$2:$4:$5:$6 &&
set X $new && new=:$2:$4:$5:$6 &&
set +f &&
test "$old" = "$new" &&
$cmpprog "$dst" "$dsttmp" >/dev/null 2>&1
then
rm -f "$dsttmp"
else
# If $backupsuffix is set, and the file being installed
# already exists, attempt a backup. Don't worry if it fails,
# e.g., if mv doesn't support -f.
if test -n "$backupsuffix" && test -f "$dst"; then
$doit $mvcmd -f "$dst" "$dst$backupsuffix" 2>/dev/null
fi
# Rename the file to the real destination.
$doit $mvcmd -f "$dsttmp" "$dst" 2>/dev/null ||
# The rename failed, perhaps because mv can't rename something else
# to itself, or perhaps because mv is so ancient that it does not
# support -f.
{
# Now remove or move aside any old file at destination location.
# We try this two ways since rm can't unlink itself on some
# systems and the destination file might be busy for other
# reasons. In this case, the final cleanup might fail but the new
# file should still install successfully.
{
test ! -f "$dst" ||
$doit $rmcmd "$dst" 2>/dev/null ||
{ $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
{ $doit $rmcmd "$rmtmp" 2>/dev/null; :; }
} ||
{ echo "$0: cannot unlink or rename $dst" >&2
(exit 1); exit 1
}
} &&
# Now rename the file to the real destination.
$doit $mvcmd "$dsttmp" "$dst"
}
fi || exit 1
trap '' 0
fi
done
# Local variables:
# eval: (add-hook 'before-save-hook 'time-stamp)
# time-stamp-start: "scriptversion="
# time-stamp-format: "%:y-%02m-%02d.%02H"
# time-stamp-time-zone: "UTC0"
# time-stamp-end: "; # UTC"
# End:
cabextract-1.11/doc/ 0000775 0001750 0001750 00000000000 14376123646 011340 5 0000000 0000000 cabextract-1.11/doc/wince_cab_format.html 0000644 0001750 0001750 00000056302 13323412475 015424 0000000 0000000
Windows CE installation cabinet (.CAB) file format
Windows CE installation cabinet (.CAB) file format
Table of Contents
The Windows CE installation cabinet format was designed by Microsoft make
it easy to create packaged software for the Windows CE platform. After
generating all his executable programs, data files, help files and so on,
a developer can then write an "installation script" which lists the name
of the software package, where each file should be installed on the target
device's filesystem, registry entries to make on the target system's
Windows Registry, and so on. A tool called "CabWiz" takes the installation
script and produces a single CAB file with a special control file stored
in it. On the target Windows CE device, a program called
WCELOAD.EXE will read cabinet files, install them, register them
as installed packages, set their registry entries, and so on.
The Cabinet format was previously developed by Microsoft for creating a
simple archive format for packaged software, from entire operating systems
down to ActiveX Web plugins. They also intended to displace Sun's JAR
format for packaging Java software, but this did not succeed.
Firstly, the overall file format of a Windows CE installation cabinet is
the standard Microsoft Cabinet file format. This was originally documented
in the Microsoft document CABFMT.DOC as part of the Microsoft
Cabinet SDK (CAB-SDK.EXE), it is now documented in the Windows
Installer documentation. The format can also be gleaned from open
source tools and libraries such as cabextract and libmspack. Windows CE
installation cabinets typically use no compression (the NONE compression
method in the cabinet specification), sometimes MSZIP compression.
The filenames of the files in the cabinet use the MS-DOS "8.3" convention,
where the first eight characters in the filename come from the "true
filename", and are followed by a period and three numeric digits. The
digits form a decimal number from 000 to 999. The name part before the
period is currently always 8 characters (shorter names are padded on the
left with "0"), but this shouldn't be relied upon. Only the numeric
extension should be used to identify the file. There should not be more
than one file in the cabinet with the same numeric extension. As an
example:
| Name in cab file | Original filename |
|---|
| BLKJAC~4.000 | --- (installation data) |
| BLACKJ~1.999 | Blackjack Setup.dll |
| SELFRE~1.006 | SelfRegister.dll |
| 0Blkjack.005 | Blkjack.exe |
| 00Sample.004 | Sample.BJL |
| WINGAM~1.003 | Win Game.wav |
| LOSEGA~1.002 | Lose Game.wav |
| BLACKJ~1.001 | Blackjack Help.htp |
The order of these files within the cab file is important. The first file
in the cabinet should be the ".000" file. It should then be followed by
all other files in descending numerical order of their extensions.
These original filenames are not recoverable, they are not stored
anywhere. The only names available are the target filenames given in the FILES section of the .000
file.
All installation data is contained in the .000 file. If a .999 file
exists, it is an "application specific Setup.DLL"; a Microsoft standard
Dynamic Link Library that will be loaded and executed after installation
by the installation program. All other files are files for installation on
the Windows CE device, and the three digits should be resolved into an
integer "file number".
All multi-byte integers are little-endian. Values given in this document
are in decimal, unless otherwise specified. The overall file format of the
.000 file is as follows:
Only the fixed size header has a fixed file offset, all other strings and
sections may be at any file offset, in any order. They are typically in
the order given above. Each file offset is given in the fixed size header.
The .000 file begins at file offset 0 with a fixed size header of exactly
100 bytes. The format of this header is as follows:
| Offset | Size in bytes | Description |
|---|
| 0 | 4 | An ASCII signature, "MSCE". This is 0x4543534D
as a little-endian integer. |
| 4 | 4 | Unknown purpose, usually 0. |
| 8 | 4 | The overall length of this .000 header file,
in bytes. |
| 12 | 4 | Unknown purpose, usually 0. |
| 16 | 4 | Unknown purpose, usually 1. |
| 20 | 4 | Target architecture for this cabinet: see Appendix A. |
| 24 | 4 | Minimal version of WinCE (major version
number) required to install this cabinet, or 0 to indicate no
restriction. |
| 28 | 4 | Minimal version of WinCE (minor version
number) required to install this cabinet, or 0 to indicate no
restriction. |
| 32 | 4 | Maximal version of WinCE (major version
number) required to install this cabinet, or 0 to indicate no
restriction. |
| 36 | 4 | Maximal version of WinCE (minor version
number) required to install this cabinet, or 0 to indicate no
restriction. |
| 40 | 4 | Minmal version of WinCE (build number)
required to install this cabinet, or 0 to indicate no
restriction. |
| 44 | 4 | Maximal version of WinCE (build number)
required to install this cabinet, or 0 to indicate no
restriction. |
| 48 | 2 | The number of entries in the STRINGS section. |
| 50 | 2 | The number of entries in the
DIRS section. |
| 52 | 2 | The number of entries in the
FILES section. |
| 54 | 2 | The number of entries in the REGHIVES section. |
| 56 | 2 | The number of entries in the REGKEYS section. |
| 58 | 2 | The number of entries in the
LINKS section. |
| 60 | 4 | The file offset of the
STRINGS section in bytes. |
| 64 | 4 | The file offset of the DIRS
section in bytes. |
| 68 | 4 | The file offset of the FILES
section in bytes. |
| 72 | 4 | The file offset of the
REGHIVES section in bytes. |
| 76 | 4 | The file offset of the
REGKEYS section in bytes. |
| 80 | 4 | The file offset of the LINKS
section, in bytes. |
| 84 | 2 | The file offset of the
APPNAME string in bytes. |
| 86 | 2 | The length of the APPNAME
string in bytes, including null terminating byte. |
| 88 | 2 | The file offset of the
PROVIDER string in bytes. |
| 90 | 2 | The length of the PROVIDER
string in bytes, including null terminating byte. |
| 92 | 2 | The file offset of the
UNSUPPORTED multi string in bytes. |
| 94 | 2 | The length of the
UNSUPPORTED multi string in bytes, including null terminating
byte. |
| 96 | 2 | Unknown purpose, usually 0. |
| 98 | 2 | Unknown purpose, usually 0. |
This is a null-terminated ASCII string that gives the name of the packaged
application.
This is a null-terminated ASCII string that gives the name of the author
or publisher of the packaged application.
If this string has more than zero bytes length according to the fixed size
header, then this is a sequence of consecutive null terminated ASCII
strings. The sequence always terminates with an empty string. Each string
is the ASCII name of a Windows CE platform where this software is not
supported and will not run. Platforms seen in this sequence include "PALM
PC", "HPC", "JORDAN", "PALM PC2" and "POCKETPC".
The STRINGS section is a number of common ASCII strings that may be used
in the installation data. In other sections, strings from the STRINGS
section are referred to by their string ID. The total number of entries in
this section is given in the fixed size header. There is no padding
between string entries. The format of each STRING entry is as follows:
- 2 bytes: An integer string ID.
- 2 bytes: The length of the string, including the null terminator byte.
- X bytes: the string itself, for the length given above.
As an example, the hexadecimal byte stream 04 00 09 00 53 6F 66 74 77
61 72 65 00 decodes to "ID=4 (04 00), length=9 (09 00),
string=Software". The hexadecimal byte stream 05 00 0A 00 4D 69 63 72
6F 73 6F 66 74 00 decodes to "ID=5 (05 00), length=10 (0A 00),
string=Microsoft".
The DIRS section is a list of directory paths used in the installation. In
other sections, paths from the DIRS section are referred to by their
directory ID. The total number of entries in this section is given in the
fixed size header. There is no padding between directory entries. The
format of each directory entry is as follows:
- 2 bytes: An integer directory ID.
- 2 bytes: The length of the following directory specification, in
bytes.
- X bytes: A directory specification. This is simply an array of 16-bit
(2 byte) numbers, where each number is a string ID. The final number is
always 0, which terminates the list.
For example, the hexidecimal byte stream 01 00 0A 00 01 00 02 00 03 00
04 00 00 translates "dir ID=1 (01 00), length=10 (0A 00),
specification={1, 2, 3, 4}". Assuming string ID 1 is "foo", string ID 2 is
"bar", string ID 3 is "baz" and string ID 4 is "quux", the specification
translates from {1, 2, 3, 4} to "foo\bar\baz\quux".
The directory specification may begin with a path member of the form
"%CEn%", where n is a decimal integer from 1 to 17. This
is an abbreviation for one of the CE standard directories, as listed in Appendix B.
The FILES section is a list of files to be installed on the target
device. All files in the list should be installed. In other sections,
files from the FILES section are referred to by their file ID. The total
number of entries in this section is given in the fixed size header. There
is no padding between file entries. The format of each file entry is as
follows:
- 2 bytes: An integer file ID. The file for installation is the file in
the cabinet which has this integer as a three digit file extension.
- 2 bytes: The directory ID for where this file should be installed.
- 2 bytes: Unknown purpose, usually the same as the file ID.
- 4 bytes: File flags. A 32-bit integer. The following bits are known:
| Flag | Description |
|---|
| Bit 31 (0x80000000) | If bit is set, this file is a
reference-counting shared file. It is not deleted at uninstall time unless
its reference count is 0. |
| Bit 30 (0x40000000) | If bit is set, ignore file date
(stored in the cabinet file) and always overwrite target (on CE
device). Mutually exclusive with bit 29. |
| Bit 29 (0x20000000) | If bit is set, do not overwrite target
if target is newer. Mutually exclusive with bit 30. |
| Bit 28 (0x10000000) | If bit is set, self-register this
DLL. |
| Bit 10 (0x00000400) | If bit is set, do not copy this file
to the target unless the target already exists. Mutually exclusive with
bit 4. |
| Bit 4 (0x00000010) | If bit is set, do not overwrite target
if it already exists. Mutually exclusive with bit 10. |
| Bit 1 (0x00000002) | If bit is set, do not skip this
file. |
| Bit 0 (0x00000001) | If bit is set, warn the user if this
file is skipped. |
All other bits are unknown.
- 2 bytes: the length of the installed file's filename, including the
null terminator.
- X bytes: the installed file's filename, with the length given above.
A null terminated ASCII string.
The REGHIVES section is a list of hives in the Windows Registry. These
hives are then used in the REGKEYS section for
actual registry entries. In other sections, hives from the REGHIVES
section are referred to by their hive ID. The total number of entries in
this section is given in the fixed size header. There is no padding
between hive entries. The format of each hive entry is as follows:
- 2 bytes: An integer hive ID.
- 2 bytes: The hive root, an integer from 1 to 4:
- HKCR: HKEY_CLASSES_ROOT
- HKCU: HKEY_CURRENT_USER
- HKLM: HKEY_LOCAL_MACHINE
- HKU: HKEY_USERS
- 2 bytes: Unknown purpose, usually 0.
- 2 bytes: Length of the registry hive specification to follow, in
bytes.
- X bytes: A registry hive specification. This is simply an array of
16-bit (2 byte) numbers, where each number is a string ID. The final
number is always 0, which terminates the list.
The REGKEYS is a list of registry entries -- key / data pairs -- to be
added to the Windows Registry upon installation. All entries in the list
should be added. The total number of entries in this section is given in
the fixed size header. There is no padding between entries. The format of
each entry is as follows:
- 2 bytes: An integer key ID.
- 2 bytes: The hive ID of the hive to store this entry in.
- 2 bytes: A Boolean value, either 1 if variable substitution should be performed or 0 if not. The entry data should have substrings such as %InstallDir% or one the %CEn% values.
- 4 bytes: The type of entry data, and flags.
| Flag | Description |
|---|
| Bit 16 set, bit 0 set (0x00010001) | This key is of type
TYPE_DWORD, a 32-bit integer. |
| Bit 16 clear, bit 0 clear (0x00000000) | This key is of type
TYPE_SZ, a null terminated ASCII string. |
| Bit 16 set, bit 0 clear (0x00010000) | This key is of type
TYPE_MULTI_SZ, a list of null terminated ASCII strings. |
| Bit 16 clear, bit 0 set (0x00000001) | This key is of type
TYPE_BINARY, raw binary data in no particular format. |
| Bit 1 (0x00000002) | This is the only known flag,
NOCLOBBER. If this bit is set, the registry entry should not be
overwritten if it already exists in the registry. |
All other bits are undefined.
- 2 bytes: The length of entry data to follow, in bytes.
- X bytes: Registry entry data. This begins with a null terminated ASCII
string, giving the name of the registry key. If the empty string is used
here, this is the default key for the given hive. Immediately following
the null byte of the string is the data for the registry entry, whose
format depends on the entry type given in the flags:
- TYPE_DWORD: four bytes, giving a single 32-bit integer.
- TYPE_SZ: a single null terminated ASCII string.
- TYPE_MULTI_SZ: a sequence of consecutive null terminated
ASCII strings. The sequence always terminates with an empty string.
- TYPE_BINARY: no specific format, just raw data.
The LINKS section is a list of symbolic links to be made in the standard
installation directories, to link to installed directories or files. The
total number of links in this section is given in the fixed size header.
There is no padding between links. Each link has the following format:
- 2 bytes: An integer link ID.
- 2 bytes: Unknown purpose.
- 2 bytes: The base directory where the link will be stored, either 0 to
indicate "%InstallDir%", the default directory where the
application is installed, or a number from 1 to 17 to indicate
"%CEn%", one of the standard installation directories as defined
in Appendix B. The link specification, given below,
should be added to this base directory, to get the full name of the
link.
- 2 bytes: Integer ID of the file or directory that the link should
point to. It is either a file ID, or a directory ID, depending on the link
type. If it is a directory ID, the ID 0 can be used to refer to
%InstallDir%.
- 2 bytes: The link type. This is 0 if the link target is a directory,
or 1 if the link target is a file.
- 2 bytes: The length of the link specification in bytes.
- X bytes: The link specification. This is simply an array of 16-bit (2
byte) numbers, where each number is a string ID. The final number is
always 0, which terminates the list.
| Value | Description |
|---|
| 0 | No specific architecture |
| 103 | SHx SH3 |
| 104 | SHx SH4 |
| 386 | Intel 386 |
| 486 | Intel 486 |
| 586 | Intel Pentium |
| 601 | PowerPC 601 |
| 603 | PowerPC 603 |
| 604 | PowerPC 604 |
| 620 | PowerPC 620 |
| 821 | Motorola 821 |
| 1824 | ARM 720 |
| 2080 | ARM 820 |
| 2336 | ARM 920 |
| 2577 | StrongARM |
| 4000 | MIPS R4000 |
| 10003 | Hitachi SH3 |
| 10004 | Hitachi SH3E |
| 10005 | Hitachi SH4 |
| 21064 | Alpha 21064 |
| 70001 | ARM 7TDMI |
First, for a Handheld PC:
| Value | Standard directory |
|---|
| %CE1% | \Program Files |
| %CE2% | \Windows |
| %CE3% | \Windows\Desktop |
| %CE4% | \Windows\StartUp |
| %CE5% | \My Documents |
| %CE6% | \Program Files\Accessories |
| %CE7% | \Program Files\Communications |
| %CE8% | \Program Files\Games |
| %CE9% | \Program Files\Pocket Outlook |
| %CE10% | \Program Files\Office |
| %CE11% | \Windows\Programs |
| %CE12% | \Windows\Programs\Accessories |
| %CE13% | \Windows\Programs\Communications |
| %CE14% | \Windows\Programs\Games |
| %CE15% | \Windows\Fonts |
| %CE16% | \Windows\Recent |
| %CE17% | \Windows\Favorites |
For a Pocket PC version 1.0 or 2.0, as per Handheld PCs, except
| Value | Standard directory |
|---|
| %CE3% | undefined |
| %CE9% | undefined |
| %CE10% | undefined |
| %CE11% | \Windows\Start Menu\Programs |
| %CE12% | \Windows\Start Menu\Accessories |
| %CE13% | \Windows\Start Menu\Communications |
| %CE14% | \Windows\Start Menu\Games |
| %CE16% | undefined |
| %CE17% | \Windows\Start Menu |
For a Pocket PC version 3.0, as for 1.0 or 2.0, except
| Value | Standard directory |
|---|
| %CE6% | undefined |
| %CE7% | undefined |
| %CE8% | undefined |
| %CE12% | undefined |
| %CE13% | undefined |
| %CE16% | undefined |
cabextract-1.11/doc/cabextract.1 0000664 0001750 0001750 00000006467 14367776050 013502 0000000 0000000 .TH CABEXTRACT 1 "March 7, 2018"
.SH NAME
cabextract \- program to extract files from Microsoft cabinet (.cab) archives
.SH SYNOPSIS
.B cabextract
.RB [ -d \fIdir\fP ]
.RB [ -e \fIencoding\fP ]
.RB [ -f ]
.RB [ -F \fIpattern\fP ]
.RB [ -h ]
.RB [ -i ]
.RB [ -k ]
.RB [ -l ]
.RB [ -L ]
.RB [ -n ]
.RB [ -p ]
.RB [ -q ]
.RB [ -s ]
.RB [ -t ]
.RB [ -v ]
.I " cabinet files" ...
.SH DESCRIPTION
.B cabextract
is a program that un-archives files in the
Microsoft cabinet file format (.cab) or any binary file which contains
an embedded cabinet file (frequently found in .exe files).
.PP
.B cabextract
will extract all files from all cabinet files specified on the command line.
.PP
To extract a multi\-part cabinet consisting of several
files, only the
.I first
cabinet file needs to be given as an argument to
.B cabextract
as it will automatically look for the remaining files. To prevent
.B cabextract
from extracting cabinet files you did not specify, use the
.B -s
option.
.SH OPTIONS
A summary of options is included below.
.TP
.B \-d \fIdir\fP
Extracts all files into the directory \fIdir\fP.
.TP
.B \-e \fIencoding\fP
Specify the character encoding of filenames inside the cabinet files.
This is only needed if you find cabinet files with garbled filenames;
most software creates CAB files with either ASCII or UTF8 filenames.
The list of supported encodings is given by the command "iconv \-l".
.TP
.B \-f
Corrupted cabinet files will be 'fixed' to salvage whatever is possible from
them. File entries with bad folders or names will be skipped rather than
rejecting the entire cabinet file. Impossible file lengths will be truncated
to extract as much as possible, including when you're missing later files in
a cabinet set. Corrupted MSZIP blocks and failed block checksums will be
ignored. Warnings will be printed if any of these conditions are met.
.TP
.B \-F \fIpattern\fP
Only files with names that match the shell pattern \fIpattern\fP shall be
listed, tested or extracted. On non-GNU systems, this match may be
case-sensitive. Use the option repeatedly to supply more than one pattern.
Files will be listed, tested or extracted if they match \fIany\fP pattern.
.TP
.B \-h
Prints a page of help and exits.
.TP
.B \-i
Prompts before overwriting files.
.TP
.B \-k
Don't overwrite symlinks when extracting files.
.TP
.B \-l
Lists the contents of the given cabinet files, rather than extracting them.
.TP
.B \-L
When extracting cabinet files, makes each extracted file's name lowercase.
.TP
.B \-n
Never overwrite existing files.
.TP
.B \-p
Files shall be extracted to standard output.
.TP
.B \-q
When extracting cabinet files, suppresses all messages except errors and
warnings.
.TP
.B \-s
When testing, listing or extracting cabinets which span multiple files,
only cabinet files given on the command line shall be used.
.TP
.B \-t
Tests the integrity of the cabinet. Files are decompressed, but not
written to disk or standard output. If the file successfully decompresses,
the MD5 checksum of the file is printed.
.TP
.B \-v
If given alone on the command line, prints the version of
.B cabextract
and exits. Given with a list of cabinet files, it will list the contents
of the cabinet files.
.SH AUTHOR
This manual page was written by Stuart Caie , based on
the one written by Eric Sharkey , for the Debian
GNU/Linux system.
cabextract-1.11/doc/ja/ 0000775 0001750 0001750 00000000000 14376123646 011732 5 0000000 0000000 cabextract-1.11/doc/ja/cabextract.1 0000644 0001750 0001750 00000006635 12704420232 014044 0000000 0000000 .TH CABEXTRACT 1 "2005年10月30日"
.SH åå‰
cabextract \- Microsoft cabinet (.cab) archives ã‹ã‚‰ãƒ•ã‚¡ã‚¤ãƒ«ã‚’解å‡ã™ã‚‹ãƒ—ãƒã‚°ãƒ©ãƒ
.SH 書å¼
.B cabextract
.RB [ -d \fIdir\fP ]
.RB [ -f ]
.RB [ -F \fIpattern\fP ]
.RB [ -h ]
.RB [ -l ]
.RB [ -L ]
.RB [ -p ]
.RB [ -q ]
.RB [ -s ]
.RB [ -t ]
.RB [ -v ]
.I " ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«" ...
.SH 詳細
.B cabextract
ã¯ã€Microsoft ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«å½¢å¼ (.cab) ã¾ãŸã¯ã€
ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ãŒåŸ‹ã‚è¾¼ã¾ã‚ŒãŸ
ãƒã‚¤ãƒŠãƒªãƒ•ã‚¡ã‚¤ãƒ« (よã .exe ファイルã§è¦‹ã¤ã‹ã‚‹) ã‹ã‚‰è§£å‡ã™ã‚‹ãƒ—ãƒã‚°ãƒ©ãƒ ã§ã™ã€‚
.PP
.B cabextract
ã¯ã€ã‚³ãƒžãƒ³ãƒ‰ãƒ©ã‚¤ãƒ³ä¸Šã§æŒ‡å®šã•ã‚ŒãŸå…¨ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã‹ã‚‰
ファイルを抽出ã™ã‚‹ã§ã—ょã†ã€‚
.PP
å¹¾ã¤ã‹ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«åˆ†å‰²ã•ã‚ŒãŸãƒžãƒ«ãƒãƒ‘ートã®ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«
ã®å ´åˆã¯ã€
.I 最åˆã®
ファイルã®ã¿ã‚’
.B cabextract
ã®å¼•æ•°ã«ä¸Žãˆã‚Œã°ã€æ®‹ã‚Šã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’自動的ã«æ¤œå‡ºã—ã¾ã™ã€‚
指定ã—ãªã„ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã‚’
.B cabextract
ãŒãƒªã‚¹ãƒˆã¾ãŸã¯è§£å‡ã—ã¦ã—ã¾ã†ã®ã‚’
抑æ¢ã™ã‚‹ã«ã¯ã€-s オプションを使用ã—ã¦ãã ã•ã„。
.SH オプション
オプションã®è¦ç´„ã¯ã€ä»¥ä¸‹ã‚’å‚照下ã•ã„。
.TP
.B \-d \fIdir\fP
ディレクトリ \fIdir\fP ã«å…¨ã¦ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚’解å‡ã—ã¾ã™ã€‚
.TP
.B \-f
ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã‚’抽出ã™ã‚‹å ´åˆã€
å•é¡ŒãŒã‚ã£ãŸ MSZIP ブãƒãƒƒã‚¯ã‚’無視ã—ã¾ã™ã€‚
å•é¡ŒãŒã‚ã£ãŸ MSZIP ブãƒãƒƒã‚¯ãŒã‚ã£ãŸå ´åˆã«ã¯ã€
è¦å‘Šãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’表示ã—ã¾ã™ã€‚
.TP
.B \-F \fIpattern\fP
シェル・パターン \fIpattern\fP ã¨ä¸€è‡´ã™ã‚‹åå‰ã®ãƒ•ã‚¡ã‚¤ãƒ«ã®ã¿ãŒè§£å‡ã•ã‚Œã¾ã™ã€‚
éžGNU システムã«ãŠã„ã¦ã¯ã€ã“ã®ä¸€è‡´ã¯ã€ã‚±ãƒ¼ã‚¹ã‚»ãƒ³ã‚·ãƒ†ã‚£ãƒ–ã§ã™ã€‚
.TP
.B \-h
ヘルプã®ãƒšãƒ¼ã‚¸ã‚’表示ã—終了ã—ã¾ã™ã€‚
.TP
.B \-l
ãれらを抽出ã™ã‚‹ã®ã§ã¯ãªãã€
指定ã•ã‚ŒãŸã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã®å†…容を一覧表示ã—ã¾ã™ã€‚
.TP
.B \-L
ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã‚’抽出ã™ã‚‹å ´åˆã€
å„解å‡ã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«åã‚’å°æ–‡å—ã¨ã—ã¦ä½œæˆã™ã‚‹ã€‚
.TP
.B \-p
ファイルã¯ã€æ¨™æº–出力ã«è§£å‡ã•ã‚Œã¾ã™ã€‚
.TP
.B \-q
ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã‚’抽出ã™ã‚‹å ´åˆã€
エラーã¨è¦å‘Šãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’除ãã€å…¨ã¦ã®ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’表示ã—ã¾ã›ã‚“。
.TP
.B \-s
複数ã®ãƒ•ã‚¡ã‚¤ãƒ«ã«ã¾ãŸãŒã‚‹ã‚ャビãƒãƒƒãƒˆã‚’リストã™ã‚‹ã‹è§£å‡ã™ã‚‹å ´åˆã€
コマンドライン上ã§æŒ‡å®šã—ãŸã‚ャビãƒãƒƒãƒˆãƒ»ãƒ•ã‚¡ã‚¤ãƒ«ã®ã¿ã‚’使用ã—ã¾ã™ã€‚
.TP
.B \-t
ã‚ャビãƒãƒƒãƒˆã®æ•´åˆæ€§ã‚’テストã—ã¾ã™ã€‚ファイルã¯ã€è§£å‡ã•ã‚Œã¾ã™ãŒã€
ディスクã¾ãŸã¯æ¨™æº–出力ã«ã¯æ›¸ã‹ã‚Œã¾ã›ã‚“。ファイルã®è§£å‡ã«æˆåŠŸã—ãŸå ´åˆã«ã¯ã€
ファイルã®MD5ãƒã‚§ãƒƒã‚¯ã‚µãƒ ãŒè¡¨ç¤ºã•ã‚Œã¾ã™ã€‚
.TP
.B \-v
コマンドラインã‹ã‚‰ã€å˜ç‹¬ã§æŒ‡å®šã•ã‚ŒãŸå ´åˆã¯ã€
.B cabextract
ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ç•ªå·ã‚’表示ã—ã¦çµ‚了ã—ã¾ã™ã€‚
ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒªã‚¹ãƒˆã‚’与ãˆãŸå ´åˆã¯ã€
ã‚ャビãƒãƒƒãƒˆãƒ•ã‚¡ã‚¤ãƒ«ã®å†…容を一覧表示ã—ã¾ã™ã€‚
.SH 著者
ã“ã®ãƒžãƒ‹ãƒ¥ã‚¢ãƒ«ãƒšãƒ¼ã‚¸ã¯ã€
Stuart Caie ã«ã‚ˆã£ã¦æ›¸ã‹ã‚Œã€
Debian GNU/Linux システムã®ãŸã‚ã«ã€
Eric Sharkey ã®ã¿ã«ã‚ˆã£ã¦ãƒ™ãƒ¼ã‚¹ãŒæ›¸ã‹ã‚Œã¾ã—ãŸã€‚
.SH 訳者
日本語訳ã¯ã€Katsumi Saito ãŒè¡Œã„ã¾ã—ãŸã€‚
cabextract-1.11/doc/magic 0000664 0001750 0001750 00000003352 13370030321 012242 0000000 0000000 #------------------------------------------------------------------------------
# Microsoft Cabinet files
#
# From (part of cabextract package)
0 string MSCF\0\0\0\0 Microsoft Cabinet file
>8 lelong x \b, %u bytes
>28 leshort 1 \b, 1 file
>28 leshort >1 \b, %u files
#------------------------------------------------------------------------------
# InstallShield Cabinet files
#
# From (part of cabextract package)
0 string ISc( InstallShield Cabinet file
>5 byte&0xf0 =0x60 version 6,
>5 byte&0xf0 !0x60 version 4/5,
>(12.l+40) lelong x %u files
#------------------------------------------------------------------------------
# Windows CE package files
#
# From (part of cabextract package)
0 string MSCE\0\0\0\0 Microsoft WinCE install header
>20 lelong 0 \b, architecture-independent
>20 lelong 103 \b, Hitachi SH3
>20 lelong 104 \b, Hitachi SH4
>20 lelong 0xA11 \b, StrongARM
>20 lelong 4000 \b, MIPS R4000
>20 lelong 10003 \b, Hitachi SH3
>20 lelong 10004 \b, Hitachi SH3E
>20 lelong 10005 \b, Hitachi SH4
>20 lelong 70001 \b, ARM 7TDMI
>52 leshort 1 \b, 1 file
>52 leshort >1 \b, %u files
>56 leshort 1 \b, 1 registry entry
>56 leshort >1 \b, %u registry entries
cabextract-1.11/TODO 0000644 0001750 0001750 00000001535 12534254616 011201 0000000 0000000 Automatic renaming of files in their long form, for Windows CE install
cabs. This would probably be another program using libmspack, rather than
auto-detected by cabextract.
Provide tool for finding OLE2 streams and dumping them. Some InstallShield
Wizard use MS CAB files inside MS OLE2 streams. They look normal, but
every so often, there's a 512 bytes extra here and a 512 bytes missing
there, so the cabinets aren't contiguous.
More advanced repair of corrupted CABs? Possible?
cabjoin - a new program that will read multipart cabinets and output a
single cabinet file containing all parts.
Allow reading a cabinet from stdin.
Allow an exacting list of files to be matched rather than a single pattern
match. Allow more than one pattern match?
cabextract should be localised.
cabextract should not overwrite the source cabinet files when unpacking.
cabextract-1.11/INSTALL 0000644 0001750 0001750 00000036626 14376123607 011554 0000000 0000000 Installation Instructions
*************************
Copyright (C) 1994-1996, 1999-2002, 2004-2017, 2020-2021 Free
Software Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without warranty of any kind.
Basic Installation
==================
Briefly, the shell command './configure && make && make install'
should configure, build, and install this package. The following
more-detailed instructions are generic; see the 'README' file for
instructions specific to this package. Some packages provide this
'INSTALL' file but do not implement all of the features documented
below. The lack of an optional feature in a given package is not
necessarily a bug. More recommendations for GNU packages can be found
in *note Makefile Conventions: (standards)Makefile Conventions.
The 'configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a 'Makefile' in each directory of the package.
It may also create one or more '.h' files containing system-dependent
definitions. Finally, it creates a shell script 'config.status' that
you can run in the future to recreate the current configuration, and a
file 'config.log' containing compiler output (useful mainly for
debugging 'configure').
It can also use an optional file (typically called 'config.cache' and
enabled with '--cache-file=config.cache' or simply '-C') that saves the
results of its tests to speed up reconfiguring. Caching is disabled by
default to prevent problems with accidental use of stale cache files.
If you need to do unusual things to compile the package, please try
to figure out how 'configure' could check whether to do them, and mail
diffs or instructions to the address given in the 'README' so they can
be considered for the next release. If you are using the cache, and at
some point 'config.cache' contains results you don't want to keep, you
may remove or edit it.
The file 'configure.ac' (or 'configure.in') is used to create
'configure' by a program called 'autoconf'. You need 'configure.ac' if
you want to change it or regenerate 'configure' using a newer version of
'autoconf'.
The simplest way to compile this package is:
1. 'cd' to the directory containing the package's source code and type
'./configure' to configure the package for your system.
Running 'configure' might take a while. While running, it prints
some messages telling which features it is checking for.
2. Type 'make' to compile the package.
3. Optionally, type 'make check' to run any self-tests that come with
the package, generally using the just-built uninstalled binaries.
4. Type 'make install' to install the programs and any data files and
documentation. When installing into a prefix owned by root, it is
recommended that the package be configured and built as a regular
user, and only the 'make install' phase executed with root
privileges.
5. Optionally, type 'make installcheck' to repeat any self-tests, but
this time using the binaries in their final installed location.
This target does not install anything. Running this target as a
regular user, particularly if the prior 'make install' required
root privileges, verifies that the installation completed
correctly.
6. You can remove the program binaries and object files from the
source code directory by typing 'make clean'. To also remove the
files that 'configure' created (so you can compile the package for
a different kind of computer), type 'make distclean'. There is
also a 'make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
7. Often, you can also type 'make uninstall' to remove the installed
files again. In practice, not all packages have tested that
uninstallation works correctly, even though it is required by the
GNU Coding Standards.
8. Some packages, particularly those that use Automake, provide 'make
distcheck', which can by used by developers to test that all other
targets like 'make install' and 'make uninstall' work correctly.
This target is generally not run by end users.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the 'configure' script does not know about. Run './configure --help'
for details on some of the pertinent environment variables.
You can give 'configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here is
an example:
./configure CC=c99 CFLAGS=-g LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you can use GNU 'make'. 'cd' to the
directory where you want the object files and executables to go and run
the 'configure' script. 'configure' automatically checks for the source
code in the directory that 'configure' is in and in '..'. This is known
as a "VPATH" build.
With a non-GNU 'make', it is safer to compile the package for one
architecture at a time in the source code directory. After you have
installed the package for one architecture, use 'make distclean' before
reconfiguring for another architecture.
On MacOS X 10.5 and later systems, you can create libraries and
executables that work on multiple system types--known as "fat" or
"universal" binaries--by specifying multiple '-arch' options to the
compiler but only a single '-arch' option to the preprocessor. Like
this:
./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
CPP="gcc -E" CXXCPP="g++ -E"
This is not guaranteed to produce working output in all cases, you
may have to build one architecture at a time and combine the results
using the 'lipo' tool if you have problems.
Installation Names
==================
By default, 'make install' installs the package's commands under
'/usr/local/bin', include files under '/usr/local/include', etc. You
can specify an installation prefix other than '/usr/local' by giving
'configure' the option '--prefix=PREFIX', where PREFIX must be an
absolute file name.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
pass the option '--exec-prefix=PREFIX' to 'configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like '--bindir=DIR' to specify different values for particular
kinds of files. Run 'configure --help' for a list of the directories
you can set and what kinds of files go in them. In general, the default
for these options is expressed in terms of '${prefix}', so that
specifying just '--prefix' will affect all of the other directory
specifications that were not explicitly provided.
The most portable way to affect installation locations is to pass the
correct locations to 'configure'; however, many packages provide one or
both of the following shortcuts of passing variable assignments to the
'make install' command line to change installation locations without
having to reconfigure or recompile.
The first method involves providing an override variable for each
affected directory. For example, 'make install
prefix=/alternate/directory' will choose an alternate location for all
directory configuration variables that were expressed in terms of
'${prefix}'. Any directories that were specified during 'configure',
but not in terms of '${prefix}', must each be overridden at install time
for the entire installation to be relocated. The approach of makefile
variable overrides for each directory variable is required by the GNU
Coding Standards, and ideally causes no recompilation. However, some
platforms have known limitations with the semantics of shared libraries
that end up requiring recompilation when using this method, particularly
noticeable in packages that use GNU Libtool.
The second method involves providing the 'DESTDIR' variable. For
example, 'make install DESTDIR=/alternate/directory' will prepend
'/alternate/directory' before all installation names. The approach of
'DESTDIR' overrides is not required by the GNU Coding Standards, and
does not work on platforms that have drive letters. On the other hand,
it does better at avoiding recompilation issues, and works well even
when some directory options were not specified in terms of '${prefix}'
at 'configure' time.
Optional Features
=================
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving 'configure' the
option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'.
Some packages pay attention to '--enable-FEATURE' options to
'configure', where FEATURE indicates an optional part of the package.
They may also pay attention to '--with-PACKAGE' options, where PACKAGE
is something like 'gnu-as' or 'x' (for the X Window System). The
'README' should mention any '--enable-' and '--with-' options that the
package recognizes.
For packages that use the X Window System, 'configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the 'configure' options '--x-includes=DIR' and
'--x-libraries=DIR' to specify their locations.
Some packages offer the ability to configure how verbose the
execution of 'make' will be. For these packages, running './configure
--enable-silent-rules' sets the default to minimal output, which can be
overridden with 'make V=1'; while running './configure
--disable-silent-rules' sets the default to verbose, which can be
overridden with 'make V=0'.
Particular systems
==================
On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC
is not installed, it is recommended to use the following options in
order to use an ANSI C compiler:
./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
HP-UX 'make' updates targets which have the same timestamps as their
prerequisites, which makes it generally unusable when shipped generated
files such as 'configure' are involved. Use GNU 'make' instead.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
parse its '' header file. The option '-nodtk' can be used as a
workaround. If GNU CC is not installed, it is therefore recommended to
try
./configure CC="cc"
and if that doesn't work, try
./configure CC="cc -nodtk"
On Solaris, don't put '/usr/ucb' early in your 'PATH'. This
directory contains several dysfunctional programs; working variants of
these programs are available in '/usr/bin'. So, if you need '/usr/ucb'
in your 'PATH', put it _after_ '/usr/bin'.
On Haiku, software installed for all users goes in '/boot/common',
not '/usr/local'. It is recommended to use the following options:
./configure --prefix=/boot/common
Specifying the System Type
==========================
There may be some features 'configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, 'configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
'--build=TYPE' option. TYPE can either be a short name for the system
type, such as 'sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS
KERNEL-OS
See the file 'config.sub' for the possible values of each field. If
'config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the option '--target=TYPE' to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with '--host=TYPE'.
Sharing Defaults
================
If you want to set default values for 'configure' scripts to share,
you can create a site shell script called 'config.site' that gives
default values for variables like 'CC', 'cache_file', and 'prefix'.
'configure' looks for 'PREFIX/share/config.site' if it exists, then
'PREFIX/etc/config.site' if it exists. Or, you can set the
'CONFIG_SITE' environment variable to the location of the site script.
A warning: not all 'configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to 'configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the 'configure' command line, using 'VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified 'gcc' to be used as the C compiler (unless it is
overridden in the site shell script).
Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
Autoconf limitation. Until the limitation is lifted, you can use this
workaround:
CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
'configure' Invocation
======================
'configure' recognizes the following options to control how it
operates.
'--help'
'-h'
Print a summary of all of the options to 'configure', and exit.
'--help=short'
'--help=recursive'
Print a summary of the options unique to this package's
'configure', and exit. The 'short' variant lists options used only
in the top level, while the 'recursive' variant lists options also
present in any nested packages.
'--version'
'-V'
Print the version of Autoconf used to generate the 'configure'
script, and exit.
'--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally 'config.cache'. FILE defaults to '/dev/null' to
disable caching.
'--config-cache'
'-C'
Alias for '--cache-file=config.cache'.
'--quiet'
'--silent'
'-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to '/dev/null' (any error
messages will still be shown).
'--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
'configure' can determine that directory automatically.
'--prefix=DIR'
Use DIR as the installation prefix. *note Installation Names:: for
more details, including other options available for fine-tuning the
installation locations.
'--no-create'
'-n'
Run the configure checks, but stop before creating any output
files.
'configure' also accepts some other, not widely useful, options. Run
'configure --help' for more details.
cabextract-1.11/md5.h 0000664 0001750 0001750 00000013053 13464343137 011347 0000000 0000000 /* md5.h - Declaration of functions and data types used for MD5 sum
computing library functions.
Copyright (C) 1995, 1996, 1999 Free Software Foundation, Inc.
NOTE: The canonical source of this file is maintained with the GNU C
Library. Bugs can be reported to bug-glibc@prep.ai.mit.edu.
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2, or (at your option) any
later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software Foundation,
Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
#ifndef _MD5_H
#define _MD5_H 1
#include
#include
/* The following contortions are an attempt to use the C preprocessor
to determine an unsigned integral type that is 32 bits wide. An
alternative approach is to use autoconf's AC_CHECK_SIZEOF macro, but
doing that would require that the configure script compile and *run*
the resulting executable. Locally running cross-compiled executables
is usually not possible. */
#if HAVE_INTTYPES_H || HAVE_STDINT_H
# if HAVE_INTTYPES_H
# include
# else
# include
# endif
typedef uint32_t md5_uint32;
typedef uintptr_t md5_uintptr;
#else
# if defined __STDC__ && __STDC__
# define UINT_MAX_32_BITS 4294967295U
# else
# define UINT_MAX_32_BITS 0xFFFFFFFF
# endif
/* If UINT_MAX isn't defined, assume it's a 32-bit type.
This should be valid for all systems GNU cares about because
that doesn't include 16-bit systems, and only modern systems
(that certainly have ) have 64+-bit integral types. */
# ifndef UINT_MAX
# define UINT_MAX UINT_MAX_32_BITS
# endif
# if UINT_MAX == UINT_MAX_32_BITS
typedef unsigned int md5_uint32;
# else
# if USHRT_MAX == UINT_MAX_32_BITS
typedef unsigned short md5_uint32;
# else
# if ULONG_MAX == UINT_MAX_32_BITS
typedef unsigned long md5_uint32;
# else
/* The following line is intended to evoke an error.
Using #error is not portable enough. */
"Cannot determine unsigned 32-bit data type."
# endif
# endif
# endif
/* We have to make a guess about the integer type equivalent in size
to pointers which should always be correct. */
typedef unsigned long int md5_uintptr;
#endif
#undef __P
#if defined (__STDC__) && __STDC__
#define __P(x) x
#else
#define __P(x) ()
#endif
/* Structure to save state of computation between the single steps. */
struct md5_ctx
{
md5_uint32 A;
md5_uint32 B;
md5_uint32 C;
md5_uint32 D;
md5_uint32 total[2];
md5_uint32 buflen;
char buffer[128];
};
/*
* The following three functions are build up the low level used in
* the functions `md5_stream' and `md5_buffer'.
*/
/* Initialize structure containing state of computation.
(RFC 1321, 3.3: Step 3) */
extern void md5_init_ctx __P ((struct md5_ctx *ctx));
/* Starting with the result of former calls of this function (or the
initialization function update the context for the next LEN bytes
starting at BUFFER.
It is necessary that LEN is a multiple of 64!!! */
extern void md5_process_block __P ((const void *buffer, size_t len,
struct md5_ctx *ctx));
/* Starting with the result of former calls of this function (or the
initialization function update the context for the next LEN bytes
starting at BUFFER.
It is NOT required that LEN is a multiple of 64. */
extern void md5_process_bytes __P ((const void *buffer, size_t len,
struct md5_ctx *ctx));
/* Process the remaining bytes in the buffer and put result from CTX
in first 16 bytes following RESBUF. The result is always in little
endian byte order, so that a byte-wise output yields to the wanted
ASCII representation of the message digest.
IMPORTANT: On some systems it is required that RESBUF be correctly
aligned for a 32 bits value. */
extern void *md5_finish_ctx __P ((struct md5_ctx *ctx, void *resbuf));
/* Put result from CTX in first 16 bytes following RESBUF. The result is
always in little endian byte order, so that a byte-wise output yields
to the wanted ASCII representation of the message digest.
IMPORTANT: On some systems it is required that RESBUF is correctly
aligned for a 32 bits value. */
extern void *md5_read_ctx __P ((const struct md5_ctx *ctx, void *resbuf));
/* Compute MD5 message digest for bytes read from STREAM. The
resulting message digest number will be written into the 16 bytes
beginning at RESBLOCK. */
extern int md5_stream __P ((FILE *stream, void *resblock));
/* Compute MD5 message digest for LEN bytes beginning at BUFFER. The
result is always in little endian byte order, so that a byte-wise
output yields to the wanted ASCII representation of the message
digest. */
extern void *md5_buffer __P ((const char *buffer, size_t len, void *resblock));
/* The following is from gnupg-1.0.2's cipher/bithelp.h. */
/* Rotate a 32 bit integer by n bytes */
#if defined __GNUC__ && defined __i386__
static inline md5_uint32
rol(md5_uint32 x, int n)
{
__asm__("roll %%cl,%0"
:"=r" (x)
:"0" (x),"c" (n));
return x;
}
#else
# define rol(x,n) ( ((x) << (n)) | ((x) >> (32-(n))) )
#endif
#endif
cabextract-1.11/ChangeLog 0000664 0001750 0001750 00000074460 14374414524 012274 0000000 0000000 2023-02-19 Stuart Caie
* ensure_filepath(): had wrong logic, for the archive-controlled
part of a pathname, it was using the result of lstat() whether
it succeeded or not, and thus not creating directories when it
ought to. Fixed and added a testcase for cabextract's --directory
option. Thanks to iq2luc for raising the issue and offering a fix.
2023-02-04 Stuart Caie
* src/cabextract.c: By default, cabextract will now overwrite
symlinks if they're in the path of files it wants to extract,
rather than follow them. This is also what unzip and tar do
by default. If you want to keep symlinks, use the new -k option.
This also adds new options regarding overwriting files. You can
now add the -n option to never overwrite, or the -i option
for an interactive prompt asking you if you want to overwrite.
Thanks to wereii for raising this issue and working on the
solution.
2023-02-03 Stuart Caie
* configure.ac: do AC_CHECK_SIZEOF([off_t]) test only after
AC_SYS_LARGEFILE, because the latter can alter the size of off_t.
2019-04-10 Stuart Caie
* src/cabextract.c: support more than one filter (-F) option in
cabextract, e.g. cabextract -F *.mov -F *.avi file.cab. Thanks
to caesarshift for the idea.
2018-12-03 Stuart Caie
* test: support builddir being on a path that includes spaces
2018-11-09 Stuart Caie
* test/case-utf8.test: Some environments (e.g. DJGPP) don't have a
UTF-8 locale, so won't pass the case.test testcase. Break it into
case-ascii.test and case-utf8.test, and skip the latter if
"cabextract -L" has no effect on non-ASCII filenames. Thanks to
Robert Riebisch for highlighting this.
2018-11-08 Stuart Caie
* src/cabextract.c: make multiple attempts at iconv_open() with
different names for the UTF-8 encoding: "UTF-8", "UTF8" and "UTF_8".
"UTF8" works with glibc, libiconv, newlib, Solaris libc and FreeBSD
libc, while "UTF-8" doesn't work with newlib. But if you have
libiconv >= 1.13, it removes "UTF8" support unless you define
USE_HPUX_ALIASES, or patch it back in (as Cygwin does).
Thanks to Ryan Schmidt for letting me know about this.
2018-11-03 Stuart Caie
* test: use the autotools test system instead of a custom makefile.
You can now use 'make check' to test cabextract, and the test files
are now distributed with cabextract.
2018-10-30 Stuart Caie
* configure.ac: remove obsolescent C library tests. AC_HEADER_STDC is
removed, and so are most checks for standard C headers. cabextract now
makes these assumptions:
-
exist
- is protected from double-inclusion (AC_HEADER_TIME obsolete)
- if you have iconv(), towlower(), utime(), utimes(), you also
have their header files
- BSD has memcpy(), memmove(), strrchr() in and has
strcasecmp() in
2018-10-26 Stuart Caie
* configure.ac, Makefile.am: use pkg-config's PKG_CHECK_MODULES
when looking for an external libmspack. You still need to supply
--with-external-libmspack to use an external libmspack. If you
don't like or use pkg-config, you can set the environment variables
libmspack_CFLAGS and libmspack_LIBS before running configure.
2018-10-26 Stuart Caie
* autogen.sh, distcheck.sh: I've introduced new build scripts.
Use cleanup.sh to remove all generated files, autogen.sh to
generate the configure script, rebuild.sh to (re)build and test
cabextract, and finally use distcheck.sh to both build and
distcheck cabextract, both with the --with-external-libmspack
configure option and without.
2018-10-22 Stuart Caie
* amibuild.sh: include cabinfo in the Amiga distribution. Thanks to
Stefan Haubenthal for the suggestion.
2018-10-16 Stuart Caie
* src/cabinfo.c: thanks to Micah Snyder for sending some very corrupt
files, where cabinet blocks can be found absolutely anywhere, not in
a continguous sequence after the file entries, I found cabinfo unfit
for purpose. I've updated it with a new output format, where the
blocks for a folder appear immediately after each folder, rather than
all at the end.
2018-10-16 Stuart Caie
* src/cabextract.c: use libmspack's new MSCABD_PARAM_SALVAGE mode
for cabextract -f, to allow extracting even more data from broken
cabinet files.
2018-07-31 Stuart Caie
* configure.ac: drop AC_FUNC_MKTIME. Looking into it, even C89 has
a mktime() function, the configure test is mostly checking if it
is POSIX-conformant or not, and substitutes mktime.c if not. But
even the replacement has no TZ handling, so it seems OK to me to
accept the system mktime() in any case. The fnmatch() and getopt()
substitutions remain because they enable GNU extensions that
cabextract uses (FNM_CASEFOLD and getopt_long() respectively).
Thanks to Stefan Haubenthal for bringing up the issue.
2018-07-28 Stuart Caie
* src/cabinfo.c: cabinfo now supports examining more than one file
2018-07-17 Stuart Caie
* amibuild.sh: support using setlocale()/iconv() in the OS4 version.
* amibuild.sh: build the 68K version with -noixemul so the resulting
executable doesn't need ixemul.library, libnix is used instead.
Because libnix has no umask(), add a HAVE_UMASK feature test.
* src/cabextract.c: add a new feature flag, LATIN1_FILENAMES,
which should be defined if the host environment expects ISO-8859-1
filenames rather than UTF-8. This adds in a step to translate
even UTF-8 filenames to ISO-8859-1. It's only enabled for the
Amiga build so far.
2018-03-07 Stuart Caie
* configure.ac, src/cabextract.c: add support for choosing the
character encoding of non-UTF8 filenames, using the iconv library.
This is based on a patch originally developed by Kevin Tardif.
* src/cabextract.c: try setting various UTF8 locales for LC_CTYPE,
in order to get tolower() / towlower() to lowercase non-ASCII
characters. Again, thanks to Kevin Tardif for discussing this
and supplying a proposed patch.
2016-04-16 Stuart Caie
* configure.ac: change my email address to kyzer@cabextract.org.uk
2015-05-10 Stuart Caie
* wince_rename, wince_info: allow the possibility that strings have
more than one null byte. Thanks to Stefan Riegler for the suggestion.
2015-05-10 Stuart Caie
* Makefile.am: Add subdir-objects option as suggested by autoreconf.
* configure.ac: Add AM_PROG_AR as suggested by autoreconf.
2015-02-25 Stuart Caie
* create_output_name(): Simplify code; do path checking only after
output name has been constructed. Use towlower to lowercase UTF-8
characters. Remove both leading '/' and '\' from cab filenames and
change both "../" and "..\" to "xx", for Cygwin and other Cygwin-like
environments that use both '/' and '\' as path separators. Thanks to
Alexander Cherepanov and the MITRE team.
2015-02-18 Stuart Caie
* create_output_name(): the check against leading slashes could be
evaded with malformed UTF-8. Thanks to Alexander Cherepanov for
reporting the issue.
2015-01-18 Stuart Caie
* wince_rename: installed files now include their install directories.
Thanks to Alfonso Acosta for sending a patch.
2015-01-08 Stuart Caie
* create_output_name: avoid invalid memory reads because of invalid
UTF-8 encodings. Use the Unicode substitution character for most
bad UTF-8 or Unicode encodings. Thanks to Hanno Böck.
* src/cabinfo.c: stop trying to convert UTF-8 to ASCII in filename.
Instead, prepend "UTF: " and print it to the terminal verbatim.
2011-07-19 Stuart Caie
* doc/ja/cabextract.1: Katsumi Saito updated the Japanese translation
of cabextract's manpage to include the -t option. Thanks again!
2011-05-11 Stuart Caie
* src/cabinfo.c: changed the largefile detection header to the same
as mspack/system.h
2011-04-27 Stuart Caie
* src/cabextract.c: changed char* to const char* in line with changes
in libmspack. See mspack/ChangeLog for more details.
2011-04-25 Stuart Caie
* load_spanning_cabinets(): Print the error code caused by a failed
cabinet merge, before ruining the error code by calling cabd->close().
Thanks to Drew D'Addesio for reporting the problem.
2011-01-19 Stuart Caie
* doc/wince_cab_format.html: Identified a new file flag in the WinCE
header file. Thanks to Paul Sokolovsky for asking me to look into it.
2010-07-19 Stuart Caie
* mspack: MS-ZIP recovery now recovers more bytes. Also, when a file
fails to unpack because of a read error during decompression, all
subsequent files in the same folder will give the same error, instead
of claiming to be OK. See mspack/ChangeLog for full details.
2010-07-17 Stuart Caie
* src/cabsplit: added new program, cabsplit, which splits cabinet
files into one cabinet file per folder. Useful for debugging.
2010-06-17 Stuart Caie
* configure.ac: Added --external-libmspack option, which allows
you to use the libmspack library installed on your system rather
than the copy bundled with cabextract. Thanks to Patrice Dumas
for the patch.
2010-06-10 Stuart Caie
* mspack: bugs in MS-ZIP and Quantum decoders have been fixed. See
mspack/ChangeLog for full details.
2010-05-06 Stuart Caie
* configure.ac, cabextract.c: added support for the one-arg mkdir()
found in the MinGW32 environment. Thanks to Kevin O'Rourke for
reporting this.
2009-09-24 Stuart Caie
* doc/wince_cab_format.html, src/wince_info, src/wince_rename:
The files in Windows CE cabinets are numbered after the first
ID in the FILES section, rather than what I termed the "real ID".
Fixed the documentation and the wince tools to match. The purpose
of the field previously called "real ID" is now unknown. Thanks
to Marco Schindler for discovering this.
2007-08-07 Stuart Caie
* all: cabextract and libmspack have moved to the domain
www.cabextract.org.uk. Updated the documentation to reflect this.
2007-01-20 Stuart Caie
* create_output_name(): add UTF-8 support for 6-byte characters.
Apparently they go that far these days.
2007-01-20 Stuart Caie
* doc/wince_cab_format.html, src/wince_info: The REGKEYS "unknown"
flag appears to be a boolean indicating whether variable
substitution should take place. Thanks to Dominique Gallot for
discovering it.
2006-06-21 Stuart Caie
* create_output_name(): add UTF-8 support for 4-byte characters.
2006-03-01 Stuart Caie
* process_cabinets(): on the advice of Mike Mohr, cabextract no
longer skips entire cabinets, when create_output_filename()
returns NULL, it only skips the affected files now.
2005-10-30 Stuart Caie
* src/cabextract.c: added test mode to cabextract, wherein files
aren't extracted, only passed through an MD5 checksum generator.
cabextract then lists which files passed and which files failed.
* process_cabinets(): fixed the problem where filters don't match
when -d option is also used. The filters match on the full
output-file path, including the -d directory specified. We now
trim this off before matching.
2005-10-29 Stuart Caie
* fnmatch.c, getopt.c: finally resolved problems with all the GNU
replacement functions. Obtained new versions of fnmatch and
getopt, removing the need for alloca.c, coded out the requirement
for mempcpy in getopt.c (I don't think it was needed anyway, but
just to be sure I changed it to use just memcpy). Tested on Mac OS X
(both native and using fink), Solaris 8 and Cygwin as well as Debian.
* configure.ac: Removed the AC_FUNC_ALLOCA and
AC_REPLACE_FUNCS([mempcpy])
2005-07-05 Stuart Caie
* src/cabinfo.c: This can now search and print accurate output for
cabinets (and files containing cabinets) over 2GB.
2005-04-21 Stuart Caie
* src/cabinfo.c: This now prints if the NAME_IS_UTF flag is set for
each file.
2004-10-19 Stuart Caie
* create_output_name(): fixed out-by-one error in UTF-8 decoder. All
UTF-8 filenames would reach the "error in UTF-8 decode" section,
because the test for that section was "pointer >= last_character",
not "pointer > last_character".
2004-10-18 Stuart Caie
* process_cabinet(): now accepts that failure of create_output_name()
is an error, and also lets that function print an error message
rather than printing one itself.
* create_output_name(): improved the two error messages that could
be printed.
2004-10-15 Stuart Caie
* create_output_name(): removes leading "./" and "../" as well as
leading slashes from the input filename. Thanks to David Banz for
pointing this out, as well as http://www.securityfocus.com/bid/11376/
2004-07-16 Stuart Caie
* Makefile.am: added -DMSPACK_NO_DEFAULT_SYSTEM. Why wasn't this in
earlier?
* src/cabextract.c: added prototypes of the cabx_ functions,
removed the prototype of cabextract_system and moved the real
cabextract_system to before main(). This is so AIX doesn't fail on
seeing an extern and a static definition of the same
global. That's messed up!
* alloca.c, fnmatch*, getopt*, mempcpy.c: imported these from
gcc's latest libiberty. This should fix problems with Cygwin.
2004-03-18 Stuart Caie
* process_cabinet(): added missing printf argument when errors on
extracting to stdout occur. Thanks to Moritz Barsnick for finding
it.
2004-03-08 Stuart Caie
* all: tidy-ups for 1.0 release
2003-09-04 Stuart Caie
* set_date_and_perm(): implemented the utimes() alternative to
utime().
* set_date_and_perm(): sets the date before the permissions are set,
in case read-only files really do get -r--r--r-- permissions and
your dumb OS won't let the date can't be changed.
2003-08-14 Stuart Caie
* wince_cab_format.html: Shaun Jackman worked out six more fields
in the header.
2003-08-12 Stuart Caie
* cabextract.c: rewrote all function documentation in javadoc /
doxygen format.
* configure.ac: added AC_FUNC_ALLOCA / @ALLOCA@ / alloca.c because
I noticed that fnmatch.c uses alloca().
2003-08-11 Stuart Caie
* main(): Removed the redundant args.list with args.view. I was
wondering why cabextract -l file.cab was trying to extract instead
of list...
2003-08-06 Stuart Caie
* configure.in, Makefile.am: rewrote the configure and build
scripts, in the new style. fnmatch sources are now bundled, and
now all the support code and tools are in the top directory,
leaving src/ with nothing but cabextract code in it.
2003-08-05 Stuart Caie
* wince_cab_format.html: converted the WinCE CAB format document
from text to HTML.
2003-07-29 Stuart Caie
* cabextract.c: now rewritten to use libmspack.
* process_cabinet(): the cabinet listing now has space for 10
digits in the size field, for those really big compressed files.
The maximum size of a file is 4294967295 bytes.
2003-07-18 Stuart Caie
* cabextract.c: started refactoring cabextract to use the
libmspack library. Moved everything out of cabextract.c and will
start moving things back in as necessary.
* doc, mspack: added a doc directory, where fun things like manual
pages, magic files and file format documents go. Made a directory for
libmspack files.
2003-06-07 Stuart Caie
* mspack: started creation of the libmspack library, based on the
cabextract code. See http://www.kyz.uklinux.net/libmspack/ for more
details about the library.
2003-05-14 Stuart Caie
* magic.cabinet: fixed errors in CAB magic definition
* magic.wince: added magic file entry for WinCE install format
* configure.in: added large file support
2003-04-21 Stuart Caie
* ja/cabextract.1: Katsumi Saito kindly translated the updated
manual page into Japanese for me.
2003-04-20 Stuart Caie
* cabextract.1: finally decided on feature set for cabextract 0.7,
so I updated the manual to reflect that.
2003-03-12 Stuart Caie
* wince_cab_format.txt: reverse engineered most of the file format
for Windows CE installation CAB header files. Windows CE uses
normal cabinet files, but the files inside the cabinets use short
filenames and a special binary header to specify full filenames,
install directories, registry entries and symbolic links. If
anyone wants to help fill in the remaining fields, I'm all ears.
2002-11-19 Stuart Caie
* cabextract.c: moved the generation of the correct unix filename
for an extracted file out of file_open() and into the main
process_cabinet() function (it now has a helper function called
create_output_name()). This is to make the real filename available
outside of file_open(). (See below)
* file_close(): chmod() and utime() are now called on the correct
filename :)
2002-11-13 Stuart Caie
* unix_directory_seperators(): this is a new function added to
determine whether the CAB file is using "wrong" UNIX-style forward
slashes as directory seperators. Microsoft CAB files use
MS-DOS backslashes, however the tools Cablinux and PowerArchiver
create CABs with forward-slashes.
2002-09-12 Stuart Caie
* file_cabs_in_file(): if the file itself doesn't exist, we no
longer print "Not a Microsoft cabinet file" for not finding any
cabinets in that file.
2002-09-08 Stuart Caie
* cabextract.c: cabextract used to segv if an LZX or Quantum
folder came after an MSZIP folder, because the window pointer
would be filled in by MSZIP's state. To solve this, I took the
window pointers and associated variables out of the state union,
and I also started clearing the state structure on startup. I also
removed the 'what was the old compression type / free window' code
and replaced it with a simple 'free LZX/QTM window if it exists'
before ZIP initialisation.
2002-09-08 Stuart Caie
* find_cabs_in_file(): if a file begins with "ISc(", cabextract
now prints a message about how to unpack InstallShield '.cab'
files, which begin with this signature.
2002-09-08 Stuart Caie
* cabextract.c: After seeing what some people think the command
line syntax is for cabextract is
(e.g. http://slashdot.org/comments.pl?sid=39401&cid=4210033) I
have decided to be nice to people who don't read manuals, and
refuse to extract files given on the command line if they've
already been extracted as part of another cabinet. This does
preclude the scenario where a file is not only part of a
multi-part set, but has a cabinet at offset 0 and _also_ has
embedded cabs later on. The new functionality is implemented by
the new functions remember_cabinet() and known_cabinet(), which
use a simple linked list. If you want the old behaviour of
cabextract back, do "find -exec cabextract {} \;".
2002-09-08 Stuart Caie
* configure.in: Upgraded my autoconf to one that has the AC_EXEEXT
bug fixed (look up AC_EXEEXT xSYM on the Internet :). Now it
complains about me writing to LIBOBJS directly, so I use the macro
AC_LIBOBJ twice to add getopt and getopt1 to LIBOBJS.
2002-08-20 Stuart Caie