Search Results for "byte on"

...Just drop in your own data files called test.jpg, test.mp3, and test.mp4 and run the scripts. Usage format is: corrupt [OPTION]... [FILE] where: OPTIONS -bit single bit error instead of byte substitution corruption -B NUM_B number of bytes per a single corruption event -kB NUM_KB number of kilobytes per a single corruption event -MB NUM_MB number of megabytes per a single corruption event -u uniform corruption instead of a random statistical event -c CHAR substitute a constant CHAR instead of a random bit/byte error

...Algorithm is simple and suitable for large file sets with few differences: basic set of duplicate candidates is determined by file size, then candidates are compared byte-wise. So for files which don't start to differ by growing at the tail it reduces read operations greatly compared to hash-based comparision (i.e. test case: 40GB of files, 16GB RAM, many differences: initial compare (uncached by OS) around 300sec, subsequent compare (relevant file parts cached by OS) ca. 2sec) Note: this program is not related to lsdup

Command-line tool to check ADFs (Amiga Disk Files) for errors and viruses. A binary is included for Windows users; Linux users are advised to compile the application themselves. Might also compile under plain DOS; but BE WARNED! When you scan files already renamed by the TOSEC standard, consider that file names may become insanely long in no time. --UPDATE OCTOBER 2014-- This project is currently suspended! I can't currently find the time to fix/update anything with this program...

FCB compares two files byte-by-byte. Files may be regular files or any kind of devices, pipes, etc. and one can be stdin. You can specify an offset if one file has a header. Usage: fcb <File1> <File2> [-h0,1] [-p0,1] [-v0,1,2,3] [-b0,1] [-q0,1]...