home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 6 File
/
06-File.zip
/
fbd099.zip
/
fbdiff.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1995-11-15
|
14KB
|
367 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
FBDIFF (File Base DIFFerencer) is a monitoring program that tracks changes made
to a given set of files between its executions. This program can be used for
virus detection (although I recommend that this program not be used as your
only means of detecting viruses) and poor-man's audit trails for networks
(trace changes in private directories between each user's logon). There are
surely many more uses for FBDIFF than I have thought of.
ΓòÉΓòÉΓòÉ 2. Contact Information ΓòÉΓòÉΓòÉ
Contact information:
Internet email: csbh@tcsconcordia.tor250.org
Fidonet: C. Henshaw 1:250/820
Snailmail:
Mr C. Henshaw,
48 Millwood Road,
Toronto, Ontario
Canada. M4S-1J7.
Don't bother looking in the phonebook for my number. I'm not listed.
ΓòÉΓòÉΓòÉ 3. Requirements ΓòÉΓòÉΓòÉ
FBDIFF requires the following minimum configuration:
o A computer running OS/2 2.0 or greater.
o 4MB RAM. 8MB is recomended for the extended version.
o At least 500KB of free disk space.
o HPFS long file names are supported but not required.
ΓòÉΓòÉΓòÉ 4. Legal Issues ΓòÉΓòÉΓòÉ
The FBDIFF package is Copyright 1995 C. Henshaw. All rights reserved.
OS/2 is a trademark of the IBM Corporation.
UNIX is a trademark of AT&T.
Macintosh is a trademark of Apple Computers.
Netscape, The Stentor Group, Bell Canada, Roger's Communications and their
agents and employees may not use this program without a special agreement.
FBDIFF is supplied as is. The author disclaims all warranties, either
expressed or implied, including, without limitation, the warranties of
merchantability and of fitness for any purpose. The author assumes no
liability for damages, even if the author is aware of a problem, direct or
consequential, which may result from the use of FBDIFF. This includes loss of
data, profit or other damages resulting from the use of FBDIFF.
FBDIFF is not even guaranteed to take up space on your disk. You may use this
program at your own risk.
ΓòÉΓòÉΓòÉ 5. Getting Started ΓòÉΓòÉΓòÉ
Getting started is easy. All you need to do is load FBDIFF.CFG into your
favorite text editor and edit it to suit your needs. The provided FBDIFF.CFG
is an example only. Refer to the next section for information on all supported
configuration keywords.
ΓòÉΓòÉΓòÉ 6. FBDIFF.CFG ΓòÉΓòÉΓòÉ
FBDIFF.CFG is a human-readable text file that controls FBDIFF's operation. You
can edit this file with any standard text editor, such as OS/2's Editor or EPM.
The Type: footer on every keyword in this reference tells you if the keyword is
optional or required for the operation of FBDIFF and how many times it may be
used. Depending on the keyword, uses over the maximum number will result in
prior keywords of the same type being ignored or an error message being
generated.
ΓòÉΓòÉΓòÉ 6.1. CRCSCAN ΓòÉΓòÉΓòÉ
Syntax: CRCSCAN <mask>
Directs FBDIFF to calculate CRCs for all files matching the specifed include
mask.
The mask structure is slightly different from the standard OS/2 wildcard
system. FBDIFF's masks are compared as text masks, so CRCSCAN does not have
any knowledge of the path system. This is not a bug, but a feature. The mask
structure is much more flexible, so, for example, large groups of files may be
included for CRC calculation in all directories in only one CRCSCAN.
Note: This keyword will slow FBDIFF's operation considerably.
Example:
CRCSCAN *.exe
Directs FBDIFF to calculate CRCs for all .EXE files in it's scanlist.
Type: Optional. Maximum 1
ΓòÉΓòÉΓòÉ 6.2. DBNAME ΓòÉΓòÉΓòÉ
Syntax: DBNAME <filename>
Directs FBDIFF to store its file index in a file other than FBDIFF.IDX. This
keyword is most useful in multi-user environments where each user may wish to
maintain different scanlists and index.
Example:
DBNAME H:\FBDIFF\user01.idx
Directs FBDIFF to store its file list in H:\FBDIFF\user01.idx instead of
FBDIFF.IDX.
Type: Optional. Maximum 1
ΓòÉΓòÉΓòÉ 6.3. DUPEDETECT ΓòÉΓòÉΓòÉ
Syntax: DUPEDETECT <criteria>
Sets the criteria which FBDIFF will use to determine if two given files are
duplicates of each other. Any combination of the following keywords may be used
to define a criteria: name, size, date, time, attr and crc. The keywords are
not case sensitive.
Example:
DUPEDETECT name size date time
Directs FBDIFF to consider files with the same name, size, date and time to be
duplicates.
Type: Optional. Maximum 1
ΓòÉΓòÉΓòÉ 6.4. DUPESCAN ΓòÉΓòÉΓòÉ
Syntax: DUPESCAN
Enables duplicate scanning. If this option is present in FBDIFF.CFG, FBDIFF
will find all duplicates in the scanlist. DUPESCAN also switches EXCLUDE from
change exclusions to duplicate exclusions. All occurrences of EXCLUDE *above*
DUPESCAN prevent files from being monitored for removal, addition or changes.
All EXCLUDE's below DUPESCAN prevent files from being reported as duplicates.
The same wildcard rules apply to duplicate EXCLUDE as to monitor EXCLUDE.
Duplicate EXCLUDEs are stored in a different internal table, so you will always
have 64 duplicate EXCLUDEs available even if you have used all 64 monitor
excludes.
Example:
DUPESCAN
Directs FBDIFF to scan for duplicates in the scanlist and to consider all
EXCLUDE entries after the current line to be duplicate-report excludes.
Type: Optional. Maximum 1
ΓòÉΓòÉΓòÉ 6.5. EXCLUDE ΓòÉΓòÉΓòÉ
Syntax: EXCLUDE <mask>
If occurring before before the DUPESCAN keyword, this keyword directs FBDIFF to
exclude a given file or group of files from monitoring for changes, addition or
deletion. If occurring after the DUPESCAN keyword, this keyword directs FBDIFF
to ignore a file or group of files in duplicate file searches.
The mask structure is slightly different from the standard OS/2 wildcard
system. FBDIFF's masks are compared as text masks, so EXCLUDE does not have
any knowledge of the path system. This is not a bug, but a feature. The mask
structure is much more flexible, so, for example, large groups of files may be
excluded from monitoring across all directories in only one EXCLUDE.
Examples:
EXCLUDE C:\*\FILES.BBS
Excludes all FILES.BBS files on drive C: from monitoring.
DUPESCAN
EXCLUDE C:\*\FILES.BBS
Excludes all FILES.BBS files from duplicate scanning.
Type: Optional. Maximum 64 for changes, with an aditional 64 for duplicates.
ΓòÉΓòÉΓòÉ 6.6. REPORT ΓòÉΓòÉΓòÉ
Syntax: REPORT <filename>
Directs FBDIFF to write a text file containing a report of changes and
duplicates (if enabled, see DUPESCAN) to the specified file. The file will be
overwriten every time FBDIFF is run.
Example:
REPORT G:\NETWORK\LOGS\DIFFLIST
Directs FBDIFF to write a human-readable list of all files that have been
added, deleted or modified since FBDIFF was last run. If duplicate scanning is
enabled (See EXCLUDE), all found duplicates will also be listed.
Type: Optional. Maximum 1
ΓòÉΓòÉΓòÉ 6.7. REPORTWIDTH ΓòÉΓòÉΓòÉ
Syntax: REPORTWIDTH <width>
Sets the column width for FBDIFF's text report. The default screen width is 80
columns. All data is still displayed in narrow report widths, but it may take
more than one line to display it. The default value is 132.
Example:
REPORTWIDTH 120
Directs FBDIFF to write its human-readable report for 120 column display.
Type: Optional. Maximum 1
ΓòÉΓòÉΓòÉ 6.8. SCAN ΓòÉΓòÉΓòÉ
Syntax: SCAN <path\fmask>
Directs FBDIFF to scan the specified drive and path for modified files. If
duplicate scanning is enabled (see DUPESCAN), FBDIFF will also scan for
duplicates in the specified drive and path.
Example:
SCAN C:\*.*
Directs FBDIFF to scan all files (unless EXCLUDEd) for changes or duplicates
(if enabled).
Note: FBDIFF will read only 4096 files in the unregistered version. Be sure
to SCAN 4096 or fewer files. EXCLUDEs do not remove files from the scan
list.
Type: Required. Maximum 26
ΓòÉΓòÉΓòÉ 7. Command Line Options ΓòÉΓòÉΓòÉ
FBDIFF supports only one command line option - '@.' The @ directive is used to
specify a different configuration file than the default FBDIFF.CFG. This
directive is most useful in a network environment. Any other options are
ignored.
Example:
FBDIFF @someotherconfig.cfg
Directs FBDIFF to use the configuration information contained in
someotherconfig.cfg instead of FBDIFF.CFG for its current execution. Combined
with the DBNAME keyword, this feature can be used to keep multiple databases
and multiple scan/excude lists.
ΓòÉΓòÉΓòÉ 8. Known Bugs ΓòÉΓòÉΓòÉ
Please read the Legal Issues section before continuing.
I currently know of no major bugs that could cause FBDIFF to report the wrong
information or destroy data during normal operation. FBDIFF should perform
correctly assuming that it is provided with correct information.
It is highly recomended that you delete FBDIFF's index (FBDIFF.IDX unless
DBNAME has been used) if you change either the SCAN or EXCLUDE lists. If you
do not delete the index, FBDIFF may report bad data the first time it is run.
Note: If you disable OS/2's hard error popup box, FBDIFF will NOT handle hard
errors gracefully. Cavat Emptor!
ΓòÉΓòÉΓòÉ 9. Registration ΓòÉΓòÉΓòÉ
Note: People who register this beta will receive a free upgrade to the first
release version.
This means that you may copy and distribute FBDIFF freely, but if you intend to
continue using it after 20 days, you are expected to register your copy or stop
using it. By registering, you are helping to pay my expenses and are giving me
a good reason to continue to work on this software.
FBDIFF's standard edition is not suitable for use on systems that contain more
than 32,767 files. The extended edition will process up to 128,000 files. The
extended edition also supports exclusions from CRC scanning. These are the
only differences between the extended and standard editions.
Registered users will be receive notices and special upgrade prices for new
releases. While a registration is vaild for all minor releases with the same
major version number, minor release updates will not be mailed out. Minor
updates for the registered versions will be made available as publicly
distributed patches.
FBDIFF's registration cost is on a sliding scale. Private users pay less than
comercial users. Users are considered private if this program will be used on
equipment that they personally own or rent. If you make more than $100,000 a
year, consider yourself a comerical user.
Users are considered comercial if this program will be used on equipment owned
or rented by a comercial, industrial or military establishment. If FBDIFF is
used to monitor files generated by multiple workstations, multiple licenses
must be purchased, even if each workstation does not actually use the program.
I.E. If FBDIFF is used to monitor work from 15 computers, you must buy at
least 15 licenses.
If you are a shareware author, a registered copy of one of your programs may be
accepted at my descretion as payment for a registered copy of FBDIFF.
Order form for private users
Order form for comercial users
ΓòÉΓòÉΓòÉ 10. Future Changes and History ΓòÉΓòÉΓòÉ
Future Changes: A full file manager and report front end is in the works.
History:
0.9.9 First public release version.
0.0.6 Used internally for testing (1 month).
0.0.0 Used internally for testing (2 months).
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Fatal errors caused by hardware faults, such as a disk that has not been
formatted or a disk that has been formatted by Some Other Operating System.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Latin; meaning 'let the buyer beware.' If you are running with AUTOFAIL=YES,
be careful.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
AUTOFAIL=YES in CONFIG.SYS
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Another operating system, such as UNIX or the Macintosh System.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Report widths narrower than 80 columns.