SFV32nix 1.0a - 1998-05-08

Download sfv32nix_v1.0a.tar.gz sfv32nix 1.0a
Download sfv32nix-1.2.tar.gz sfv32nix 1.2
sfv32nix 1.2p0
Download sfv32nix-1.2p1.tar.gz sfv32nix 1.2p1
sfv32nix 1.3a0
sfv32nix 1.3a1
Download sfv32nix-1.3b0.tar.gz sfv32nix 1.3b0

Versions from https://web.archive.org/web/19990819141347/http://sfv.format.nu:80/addbug.php3

SFV32nix v1.0a

- DISCLAIMER -------------
This software is provided on "AS IS" basis, there is no warranty what so ever
of the functionality of the software. The entire risk as to quality and
performance of the software is borne by you. Should this software prove to be
defective and cause loss of any kind, you and solely you is to pay for the
expences of repair. Fantasia Software can at no level be held responsible for
any kind of liablility.

This software is Copyrighted by Alcatraz Fantasia Software. It may free of
charge be distributed in it orginal state. No part of this package may in any
way be altered without explicit authorization from Fantasia Software. No fee
may on any level be charged for this software - THIS SOFTWARE IS FREE.

However fell free to contact me and tell me what you think should be improved
and what you think is great.

- COMPILATION ------------——
SFV comes with a makefile, simply run make in the current directory and sfv
executable will be created.

The makefile works fine for me but ive heard it doesnt always to others. If it
doesnt for you - since SFV is such a huge poject, NOT - simply enter the
commmandline for the compiler manually:
gcc -o sfv sfc.c sfvMisc.c stack.c
if it still doesnt compile complaining about that the file "getopt.h" cannot
be found, open sfv.c in pico (or whatever youre favorite editor is) and
comment out that line (add // first on the line) save it and recompile it. If
someone can help me bypass theese problems, please tell me how!

SFV32nix have been successfully compiled on
IRIX Release 5.3
REDHAT 5 - Hurricane
Debian GNU/Linux 1.3
Slackware 2.0
Solaris 2.5.1 (Comment out the line #include <getopt.h> in sfv.c [add // in
front of it])
(I didnt have access to any more versions =)

Theese executables is included in the release and named accordingly.

If you can compile it on other platforms please tell me, if you cannot also
tell me and save the output of the compiler so i know what is wrong.
- USING THE SOFTWARE -----------

This version of SFV uses a new algorithm, it _CANNOT_ read checksum files
generated by previous versions of SFV. The Windows versions however are still
capable of reading those old files, if you wish to verify files against tabled
created by versions eralier, please use the windows versions of the software.

The earlier versions of SFV will therefore not be able of reading files
created with versions 1.0+. Therefore please distribute the new versions of
SFV as much as possible, so every user of the old versions will get a new copy
of the software.

The commandline can be used as any standard unix program using the getopt
functions. Short description over the commands.

-T Verify the given files against an already existsant checksum

-C Create a checksum table.

-s Does nothing in the unix version. It exists since it does in
the windows versions of SFV there it silences the output.
In UNIX redirect the output to null instead.

-f Filename Disables the autodetection of filename to use and forces
SFV to use a specified filename as the checksum file.

-1 Causes autodetection of the filename of the checksum file.
(Se below for details of the autodetection). Using the
extension .txt for the file.

-2 Same as -1 but with .sfv as extension. This is the Default.

-3 Same as -1 but with .crc as extension.

-l Enables SFV to create a logfile containing information about
the files failing the tests. This is only valid when testing

-n Filename Species the filename of the logfile, if none is specied the
default will be sfv.log. This is only valid when testing

-d Phsyicly deletes all the files that fail the tests.

-c Filename Add Filename as a comment to the checksum file. The comment is
displayed whenever testing files against the file.

-i Add´s full file information into the checksum file, causing
the filedate and filesize also to be saved, this information
is not used during testing, but can be used for visual
confirmation of filesizes etc.

-w Do not show the archive comment when testing files.

SFV has for ease of use the ability to autodetect the output/input name of the
checksum file. SFV looks for files ending with .rar, r##, s## and ### when
detecting the filename (where # is an arbitary number 0-9). The new filename
will then be the orignal filename without the previus extension and with the
extension specified by the options.

- WHAT IS SFV32? -------------
SFV stands for Simple File Validator and is just that. The reason why SFV
exists is the fact that the best archiver around - RAR - lacks a significant
ability, namely the ability to put one CRC per volume in a file which spans
over multiple volumes. This is bad news indeed when downloading a file wich
resides in 40+ volumes and it unpacks with an error there is no way of telling
in wich volume the error is.

SFV fixes the little problem quick and easy. SFV generates an external file
containing checksums of the files. If something fails when unpacking, simply
use SFV and find out wich file(s) errored out during transfer and download
only the faulty failes again rather then downloading the entire bundle.

So whats the catch?
The problem is that SFV cannot invent the checksums needed to verify the
files. They must be created first by the party keeping the files. Ie when
creating the archives you also have to create the table of checksums, once
this is done the small file containing the checksums can follow the archives
around the world.

The versions 1.0+ of SFV now also handles the reading of Validate and FileCRC
files to verify checksums of thoose. A word of warning though. Validate always
uses an uppercase version of 8.3 filename. In unix systems this is faulty
since i have to performe a case insensitive match, also there is no way to
obatin the correct 8.3 filename of a file with more chars in the name (windows
use ~1 etc.). Also FileCRC has a built in limitation of 20 chars in the
filename, simply truncating the filename after 20 chars, filenames truncated
are hard to get the correct filename out of.

All versions of SFV32 are written by Alcatraz of Fantasia Software. This
software is intended to be free to use and not associated with any kind of
lame licensing or nagging etc. Although for me as an author it is really great
to know what people think of my program, what features are missing and what
bugs there are etc.

I am also looking for some kind of ftp-site that can be used as host for the
latest SFV versions etc.

The author

On IRC - EFNet - Mr\\Alc

Via email moc.edudrebyc|cla#moc.edudrebyc|cla

Please feel free to contact me.

Also a great thanks to God-Emperor for providing me with tons of ideas etc.

OH! And im not a native enlish speaker so if the english aint good enough
tough luck! But feel free to tell me where it is wrong :)


0: All tested files ok, or program executed without errors
1: Error opening/creating/autogetting listfile
2: One or more of the tested files failed CRC
3: Error processing one or more files, ie. read error, open error etc
4: Help displayed, due to command line error or by request
5: No files processed ?!
6: Unable to create logfile, ie. disk full


v1.0a First unix version released.


See also

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License