home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
CRCOK157.ZIP
/
CRC_OK.DOC
< prev
next >
Wrap
Text File
|
1995-06-27
|
11KB
|
246 lines
┌─────╖ ┌──────╖ ┌─────╖ ┌─────╖ ┌─╖┌───╖
│ ╔═╕ ║ │ ╔══╕ ║ │ ╔═╕ ║ │ ╔═╕ ║ │ ║│ ╔═╝
│ ║ ╘═╝ │ ╙──┘ ║ │ ║ ╘═╝ ┌─────╖ │ ║ │ ║ │ ╙┘ ╙─╖ Version 1.57
│ ║ ┌─╖ │ ╔═╕ ╔╝ │ ║ ┌─╖ ╘═════╝ │ ║ │ ║ │ ╔══╕ ║
│ ╙─┘ ║ │ ║ │ ╙╖ │ ╙─┘ ║ │ ╙─┘ ║ │ ║ │ ║ ▓▓▓ beerware ▓▓▓
╘═════╝ ╘═╝ ╘══╝ ╘═════╝ ╘═════╝ ╘═╝ ╘═╝
───────────────────────────────────────────────────────────────────────────────
This program is (c) Peter Hampf --- pbs data vec
Graf von Galen Str. 27
49377 Vechta
Germany
2:241/1090@fidonet
246:6101/0@PB-Net
9:491/6010@virnet
21:490/2105@gernet
Tue., Jun. 27. 1995
All rights reserved
───────────────────────────────────────────────────────────────────────────────
Only a few questions and the answers to complete this doc :-)
Q.: What does this program do?
A.: It compares the CRC - checksum in a TIC (or BAD) file against the real
CRC - checksum of the file which belongs to the TIC - file.
If the checksum is wrong, a new TIC - file with the correct checksum
will be generated.
Furthermore the SIZE line will be corrected, and -optional- the REPLACES
line. (Call "CRC_OK /?" for a little more information!)
Q.: Why this program?
A.: Because I use MTA (a really great program from Rob van Hoeven) :-)
If my system receives a TIC - file, the corresponding file will be
converted into an ARJ. Under some circumstances the CRC - checksum for
the new generated archive is calculated incorrect.
Q.: Can I use it for other things?
A.: Of course ... e.g. if you are going to hatch an own program and two
minutes later you have to change something [:-)] --- you have not to
hatch the altered version again. Just call CRC_OK to make the new
checksum in the old TIC-files... .
Or if your tick-manager always uses REPLACE (like Filescan does!) and
you don't want your files to replaces automatically: just call
CRC_OK /R=DUMMY.DAT (or something else as filename) and your REPLACES-
line will be invalidated!
Q.: Are there any limitations?
A.: Yes! :-)
The TIC - file may not exceed 52 KB :-)))))
Q.: How have I to call the program?
A.: CRC_OK [path_to_ticfiles] [path_to_file_in_ticfile] [/R<=some.nam>]
Just place this call *after* the MTA - call and *BEFORE* your TICK-call!
Q.: Is this program free?
A.: NOOOO!! Under NO circumstances! It is beerware :-) That means, if you
ever meet me anywhere, you have to pay a beer for me!
If you don't want to pay this beer, you can send me a nice postcard
alternatively ! (I would very pleased if you do so! Really!!)
NOTE: this program is NOT public domain! It is (c) by pbs!
You may NOT alter it (or it's doc:-) in any way!!!
Q.: What the hell are these [C] letters on the screen?
A.: Simple: [C] -> CRC corrected
[R] -> REPLACES - extension corrected
[XR] -> REPLACES - line invalidated
[NOF] -> No file. File mentioned in the TIC-file is missing.
[R] -> file has been renamed, extension corrected!
[D] -> corrected UNIX-style DATE - line
Q.: Guaranties?
A.: grmpf...hahahahaha ... MAAAAAMA
------------------------------------------------------------------------------
Changes:
========
v1.10 31.07.1992: - removed the limitation that the FILE-line had to
----------------- appear in front of the CRC-line.
Works very smart now ;-)
+ added a second parameter. If specified, this is the
path to the files (FILE <name> - line in tic-file)
You can give this parameter in ADDITION to the first
one (path to tic-files) if the tics are in another
directory than the files... .
e.g.: CRC_OK .\ H:\FILES\SDSRA
^ ^
| |
| +-- here are the files
|
+----- tics are in the current path
v1.20 13.08.1992: + CRC_OK will now always correct the SIZE line in
----------------- the tic-file, too!
(Necessary for example for 're-hatching' a changed
version of one of your programs ;-) )
v1.30 24.08.1992: + added logging in CRC_OK.LOG in CRC_OK's homedir!
v1.40 06.10.1992: only internal....
v1.41 07.10.1992: + added REPLACE-line handling and invalidating.
----------------- + changed the TIC-handling at all! (a total rewrite)
+ added correction of the SIZE-line, even if the CRC
is correct.
+ added /L-parameter to specify another LOG-file!
v1.50 30.11.1992: - Fixed bug with non-existing CRC lines in TICs.
-----------------
+ added file CRC_OK.CTL (in the same directory as the
EXE-file). This file contains your fileareas and the
paths to them. One per line. Example:
DISPAREA E:\FD\FILES\DISP
If CRC_OK.CTL is present, the file mentioned in the
TIC-file will be searched in it's area-path instead
of the current directory or command-line-parameter
--->>> /FI. If you give the default search-path as /FI-
commandline parameter, the contents of CRC_OK.CTL
will be ignored!!!!!!!!!
+ added support for FILESCANs renamed TIC-files.
The known extensions are:
.BAD, .UNK, .MIS, .CON,
.BYU, .NOU, .UNL, .SEC,
.PW, .CRC, .DUP
All files with this extensions are treated as valid
TIC-files.
v1.51 10.12.1992: + if CRC_OK.CTL is present *AND* the file mentioned in
----------------- the TIC-file resides in the same directory than the
TIC itself (*AND* no second parameter is given on
the commandline!), THIS file is used instead of the
file in the areapath from CRC_OK.CTL!
v1.52 17.12.1992: + you may specify a single tic-file as first parameter
----------------- instead of only a whole directory.
>> CRC_OK C:\FD\OUT\TK123831.TIC
- fixed a bug in searching for the keywords in tic-
files. (The search is binary.) If the word "File"
did appear within (e.g.) the description-line, it
could have been identified as file-keyword :-(
To be valid the keywords MUST start at character 1
of the corresponding line now and may not be
preceded by spaces or tabs. This is normally the
case in every known tic-file.
v1.53 27.12.1992: - fixed a silly bug: if both lines, size- and crc-,
----------------- had to be corrected and the length of the size-line
had to be changed, the crc-line would have been
written incorrectly. (Not very likely to happen, but
even possible!)
v1.54 02.04.1993: + CRC_OK now handles renamed files! e.g. if MTA renamed
----------------- a file FILEA.ARJ to FILEA.ZIP and did not correct your
TIC-file (can happen if you haven't installed properly)
CRC_OK will do it for you.
But be aware: the first matching file (FILEA.*) will
be inserted into your TIC-file, either from the actual
path or the path from CRC_OK.CTL (or from commandline-
parameter #2).
If the file FILEA.ARJ does not exist anymore, CRC_OK
will search for:
1.) FILEA.ARJ in your Areapath (from CRC_OK.CTL)
2.) FILEA.* in the TIC-files' directory
3.) FILEA.* in your Areapath (from CRC_OK.CTL)
v1.55 21.04.1994: + added check for DATE line. If the unix-style file-
----------------- date is not correct, CRC_OK will correct it ...
This will only be done if /UNIX (/UN) has been speci-
fied on the commandline.
- changed commandline-parsing!!!!!
Path to ticfile is now: /TICPATH=<path>
Path to filearea is now: /FILEPATH=<path>
(maybe abbreviated to /TI=<path> and /FI=<path>)
v1.56 03.10.1994: - small bugfix: September and October were reversed
----------------- in the logfile.
+ CRC_OK supports ENVIRONMENT-variables in pathnames
now. You may use $[VARIABLE] (the name of the variable
must be enclosed in brackets and preceded by an
$-sign!) in the command- line parameters /TI and /FI
*and* inside the ctl- file! Example:
CRC_OK /TI=$[FD]\OUTTIC /FI=$[FILES]\SDN
You must have defined FD and FILES in your environment,
for example:
SET FD=D:\FD\
SET FILES=P:\BASE\FILES
The backslash is optional and will be added/handled by
CRC_OK itself!
A line inside CRC_OK.CTL may look like this:
disparea $[files]disp
NOTE: unresolved environmentvariables will NOT be
replaced! So ensure that they are defined!
v1.57 27.07.1995: + added the /CRC parameter. If you are using this pa-
----------------- rameter, CRC_OK will create and insert a NEW CRC
line, if there is NO ONE in the TIC file.
- CRC_OK should not change to a default screen mode
anymore if you have any unusual mode on you machine.
CRC_OK is extremely fast, all TIC-file-access is done binary. If you have any
problems, please let me know, I will fix'em asap!
Ok, now have fun and always good 'ticking' :-)))
Peter