Free crc software for linux

Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget.

SYNOPSIS

use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}

This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.

The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.

iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".

Forth Foundation Library, in short FFL is a Forth library. It gives you a collection of words written in (ANS) forth which are useful in areas such as data types, collections, interfaces, development support, and compound modules.
The modules in the library are grouped in five clusters:
- Data types - char
- Collections - single linked list
- Interfaces - crc-32
- Development - struct, unit test
- Compound - nothing yet.
Enhancements:
- This release adds four new features to the library, including an n-tree with an iterator, a SHA-256 module, and a regular expressions module.
- The library will now also run on MinForth.

PHK is a PHP-oriented package system. PHKs purpose is to package a library or an application, in order to distribute and run it as a single file. As an introduction, you may think of it as a PHP-oriented jar, with a lot of additional features.
Main features:
- No runtime software : as it was said above, there is no runtime software to install before using a PHK archive, as it contains its own runtime code. Any installed PHP (version 5.1.0 or more) is ready to include/execute a PHK archive without any modification.
- Supports libraries, applications, plugins : a PHK archive can contain a library or an application (an application is a library with an entry point). PHK archives can also be used as plugins.
- Unlimited number of subfiles : a PHK archive can contain an unlimited number of subfiles and directories. A subfile can contain up 2 Gbytes of binary data. The total size of a PHK archive is limited to 2Gbytes. Every subfile can be, on a file by file basis, compressed (gzip or bz2), and/or filtered through php_strip_whitespace() (for PHP source).
- Standard locations for package information : PHK provides standard locations for administrative informations like packages name, author, license, copyright, etc. PHK also allows to specify an icon file and an URL. All these inforamtion are displayed in webinfo mode.
- Webinfo mode : in webinfo mode, the PHK archive behaves like a small web site, allowing the user to display every information about the archive, and the content of every subfile. This mode is a standard feature of every PHK archive.
- Mount/umount user scripts : the package author can specify a mount_script. This subfile will be called every time the PHK archive is mounted. In the same manner, an umount_script can be specified.
- Built-in CLI commands : several built-in CLI commands are available. These commands are the equivalent, in CLI mode, of the webinfo mode. They allow to display every information about the PHK archives structure and content.
- Meta-packages : PHK supports meta-packages, allowing a PHK archive to be incorporated as a subfile inside another PHK archive, along with other regular files. This feature is useful for unit tests (see the Zend Framework demonstration packages for an example) or to build meta-libraries (incorporating several librairies, but without mixing them together). These sub-PHK archives can be automatically mounted when the main package is mounted.
- Web path protection : In a PHK archive, the subfiles are protected from incorrect or unauthorized access from the web. The legitimate entry points are explicitely identified, making the package easier to secure. From the web, it is impossible to display or to call a subfile if it is not explicitely enabled by an option. Among other benefits, it allows to suppress the usual empty index.htm files in every directories !
- CRC checksum : A PHK archive includes a CRC checksum mechanism. Depending on the packages options, this checksum can be verified every time the package is mounted, or on users request.
- Digital signatures : A PHK package can be digitally signed (using a digital certificate). This feature allows users to verify that their package comes from a source they trust.

MP3val is a tool for MPEG audio files validation and (optionally) fixing problems.
It was primarily designed for MPEG 1 Layer III (MP3) files, but supports also other MPEG versions and layers.
MP3val can be useful for finding corrupted files (e.g. incompletely downloaded).
MP3val supports:
- MPEG-1, 2, 2.5; Layers I, II, III
- ID3v1 tags (must be at the very end of the file)
- ID3v2 tags (must be at the very beginning of the file)
- APEv2 tags
Enhancements:
- More precise report about CRC.
- A new option added to keep file timestamps.
- Added more accurate handling of write errors (Debian #413946).
- Attributes are now correctly preserved.

FLAC is Free Lossless Audio Codec. Grossly oversimplified, FLAC is similar to MP3, but lossless, meaning that audio is compressed in FLAC without any loss in quality.
This is similar to how Zip works, except with FLAC you will get much better compression because it is designed specifically for audio, and you can play back compressed FLAC files in your favorite player (or your car or home stereo, see supported devices) just like you would an MP3 file.
FLAC is freely available and supported on most operating systems, including Windows, "unix" (Linux, *BSD, Solaris, OS X, IRIX), BeOS, OS/2, and Amiga. There are build systems for autotools, MSVC, Watcom C, and Project Builder.
The FLAC project consists of:
the stream format
reference encoders and decoders in library form
flac, a command-line program to encode and decode FLAC files
metaflac, a command-line metadata editor for FLAC files
input plugins for various music players
When we say that FLAC is "Free" it means more than just that it is available at no cost. It means that the specification of the format is fully open to the public to be used for any purpose (the FLAC project reserves the right to set the FLAC specification and certify compliance), and that neither the FLAC format nor any of the implemented encoding/decoding methods are covered by any known patent. It also means that all the source code is available under open-source licenses. It is the first truly open and free lossless audio format.
Main features:
- Lossless: The encoding of audio (PCM) data incurs no loss of information, and the decoded audio is bit-for-bit identical to what went into the encoder. Each frame contains a 16-bit CRC of the frame data for detecting transmission errors. The integrity of the audio data is further insured by storing an MD5 signature of the original unencoded audio data in the file header, which can be compared against later during decoding or testing.
- Fast: FLAC is asymmetric in favor of decode speed. Decoding requires only integer arithmetic, and is much less compute-intensive than for most perceptual codecs. Real-time decode performance is easily achievable on even modest hardware.
- Hardware support: Because of FLACs free reference implementation and low decoding complexity, FLAC is currently the only lossless codec that has any kind of hardware support.
- Streamable: Each FLAC frame contains enough data to decode that frame. FLAC does not even rely on previous or following frames. FLAC uses sync codes and CRCs (similar to MPEG and other formats), which, along with framing, allow decoders to pick up in the middle of a stream with a minimum of delay.
- Seekable: FLAC supports fast sample-accurate seeking. Not only is this useful for playback, it makes FLAC files suitable for use in editing applications.
- Flexible metadata: New metadata blocks can be defined and implemented in future versions of FLAC without breaking older streams or decoders. Currently there are metadata types for tags, cue sheets, and seek tables. Applications can write their own APPLICATION metadata once they register an ID
- Suitable for archiving: FLAC is an open format, and there is no generation loss if you need to convert your data to another format in the future. In addition to the frame CRCs and MD5 signature, flac has a verify option that decodes the encoded stream in parallel with the encoding process and compares the result to the original, aborting with an error if there is a mismatch.
- Convenient CD archiving: FLAC has a "cue sheet" metadata block for storing a CD table of contents and all track and index points. For instance, you can rip a CD to a single file, then import the CDs extracted cue sheet while encoding to yield a single file representation of the entire CD. If your original CD is damaged, the cue sheet can be exported later in order to burn an exact copy.
- Error resistant: Because of FLACs framing, stream errors limit the damage to the frame in which the error occurred, typically a small fraction of a second worth of data. Contrast this with some other lossless codecs, in which a single error destroys the remainder of the stream.
What FLAC is not:
- Lossy. FLAC is intended for lossless compression only, as there are many good lossy formats already, such as Vorbis, MPC, and MP3 (see LAME for an excellent open-source implementation).
- SDMI compliant, et cetera. There is no intention to support any methods of copy protection, which are, for all practical purposes, a complete waste of bits. (Another way to look at it is that since copy protection is futile, it really carries no information, so you might say FLAC already losslessly compresses all possible copy protection information down to zero bits!) Of course, we cant stop what some misguided person does with proprietary metadata blocks, but then again, non-proprietary decoders will skip them anyway.

AdvanceSCAN project is a commandline ROM manager for emulators.
AdvanceSCAN is a command line ROM manager for MAME, MESS, AdvanceMAME, AdvanceMESS, and Raine for Unix, DOS, and Windows.
Main features:
- Directly read, write zip archives without decompressing and recompressing them for the best performance.
- Add, copy, move and rename files in the zip archives. Any rom that you have is placed automatically in the correct zip.
- Recognize the text files added by rom sites and delete them.
- Recognize the text files added by the rom dumpers and keep or delete them.
- Its safe. On all the zip operations any file removed or overwritten is saved in the `rom_unknown `sample_unknown directories and kept for future uses. This will prevent any unwanted remove operation.
- Generate differential rom sets.
Enhancements:
- New rom zips are now created only if at least one unique rom is found. Roms shared with other games dont trigger the zip creation. For example, galaga88
- and pacmania share the rom ns1-mcu.bin. This functionality prevents the creation of the galaga88 zip from a correct copy of pacmania using only the
- ns1-mcu.bin file.
- Relaxed a consistency check for the local header in zip files. The crc and size entries are allowed to contain the real value also if a data descriptor is present.