文件列表:

file_id.diz (1293, 2003-01-05)
files.crc (155, 2005-04-06)
crcman.c (62293, 2005-04-06)
crcman.htm (34400, 1998-09-25)
crcman.exe (47640, 2003-01-06)
update.txt (1380, 2003-01-06)
creatcrc.bat (215, 2001-07-23)

ATTENTION! ~~~~~~~~~~ If you're updating from any earlier version please read update.txt! General ~~~~~~~ For help on command line options invoke crcman without any parameters. You probably would like to pipe the output into a lister, for example, crcman|less For specific help on the -x exclude_file option please see further down. When checking files you may pipe the output through grep to see only errors: crcman crcfile | grep Error: note the capital E in Error For a changes history see crcman.c source file. If you'd like to see CRCman in action, type crcman files.crc at your prompt which will check the files of the distribution. Note that files.crc was created under DOS using the -p option to contain '/' as a separator and lowercase file names, and no carriage returns, which makes it work under DOS and UNIX. I must line out that CRCman is NOT a tool for virus protection, since it doesn't help against stealth viruses, for example. But it may be useful to find out which files are altered by any program, or if your hard disk loses a bit here and there, or to check a backup against the original files. UNIX ~~~~ Just compile, for example, gcc -O2 -o crcman crcman.c DOS ~~~ The executable was compiled using DJGPP v2.03 with gcc v2.95.2 gcc -O2 -o crcman.exe -DDOS crcman.c and packed with UPX v1.24 Some words on DOS file names and case sensitivity: The DOS path separator is '\' instead of '/'. Under DOS, all file names are compared case insensitive by the program and are written to the CRC log file as they are encountered. If option -p is specified the CRC log file is written using '/' as the separator and converting all ASCII letters [A-Z] to lowercase, and no carriage returns are written. This may come handy if you exchange files with an UNIX system. However, the program is able to read file names from the CRC log file and the command line and list files using either '/' or '\' as a separator, but only under DOS. WIN ~~~ Under win9x, long file names are used by the DJGPP executable unless there is an environment variable LFN=N set. If you dual boot a system between Windows 95 and DOS and want to use CRCman in both modes, you probably should set LFN=N for CRC file creation, since long file names would not be visible under DOS. -x exclude_file ~~~~~~~~~~~~~~~ By using the -x option you may specify a file containing a list of names of files and directories to be ignored during the scan. Each line contains exactly one name. If a path delimiter is included in the name, the name matches only if the currently scanned directory matches that path. If the name doesn't contain a path delimiter, any matching file or directory encountered during the scan will be ignored, no matter in which directory. If a directory is to be ignored, also its subdirectories will be ignored. Examples: C:\DIRNAME the directory C:\DIRNAME and all of its subdirectories will be ignored. .\SUBDIR a directory (or file) SUBDIR in the current directory will be ignored if you build a CRC file for the current directory, i.e. your command line was `crcman -b . crcfile' FOO any file or directory named FOO will be ignored anywhere. C:\DIRNAME\SUBDIR\FOO exactly this file (or directory) will be ignored.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：