logoAnerty's Lair - File << Software << News << Home
^ AnCrypt AnFV DriveSort jSAVF
AnCrypt v1.038
AnCrypt AnCrypt is a Notepad-like text editor which crypts the edited files (BlowFish 448bit algorithm). It can be used to carry confidential data on an USB key.

Encrypting a text file enables you to keep its content safe. Typical uses of this program would be to store passwords you can't remember, or other important information you wouldn't want other people to see.

Specially designed to be small and easy to move around, this program has nearly the same interface as the default Windows notepad. It doesn't require any installation, and allows you for example to bring it along with your sensitive data on a floppy or an USB key.

This program relies only on encryption to protect your data, and does not offer any protection against phishing attacks like memory dump, window text copy, screenshot analysis, clipboard hijacking, swap file access, keylogger, ...
If you suspect you are in an hostile environment, do not open your encrypted file.

Download: [ Win98/Me ] [ Win2k/XP/2003 ]

AnFV v1.0
AnFV AnFV enables you to perform advanced integrity check on files. Unlike many other similar softwares, AnFV pinpoints the location and extent of one or more erroneous blocks in a checked file.

The easiest way to check that a file is the same as an original is certainly to compare it byte by byte to the original. However, when the original is not available on site, for example in the case of a downloaded file, it is impossible to do so without having to download it once again. In this case, the most widespread method to check that a file is not corrupted is to compute a kind of magical number for the original file, and to compare it to the one computed for the downloaded one.

This kind of computation is called hashing, and the magical number is a hashcode. There are plenty of ways to hash data, amongst which we find the well-known CRC-32, MD5 and SHA1. If the hashcodes obtained on two blocks of data are different, we are sure that the two blocks are different. However, the reciprocal is not necessarly true, and given a hash method there is a small chance to obtain the same hashcode on two different blocks. The SFV-like file checking tools only generate one hashcode for a whole file, which is surely enough to find out that a file is corrupted, but doesn't allow for example to see that only the last 12KB of a 380MB file are corrupted. This information might allow to retrieve only the corrupted data, which in most cases is clearly faster than downloading the whole file once again.

AnFV enables you to create validation files for other files. These files contain a set of hashcodes that allow to locate corrupted blocks within a bad file with a customisable resolution. The block size can be reduced up to 256 bytes of data per block. AnFV can still use the SFV format, but in that case it won't be able to tell you where the errors are in a corrupted file.

Download: [ Windows ]

DriveSort v1.223
DriveSort DriveSort sorts the directory tables of a volume formated in FAT12/FAT16/FAT32. This sort orders the files in each folder according to their short or long names alphabetic order.

The majority of recent operating systems sort the files before showing them to the user, either by name, by size or by whatever the user choose. However, it is not always the case in embedded OSes on small portable devices like MP3 players. On these platforms, the lack of resources (CPU, memory) can lead the developper to make it display or play the files in the order in which they are on the disk.

This order depends mostly of the order in which they were added to the disk. DriveSort can change this order to help such devices to play or view their files in the order you want, by putting them on the disk in a customizable order.

Two automated sort method are available :

  • The "LFN Sort", which sorts the files and directories according to the alphabetic order of their Long File Names.
  • The "SFN Sort (I-Bead)", which sorts the files and directories according to the alphabetic order of their Short File Names.
  • ( A file or directory on a FAT volume has always a short file name, which is the old MS-DOS 8.3 name format. It means that the name part of a filename must have at most eight characters, and its extension at most three. A file or dir can also have a long file name, which can be a bit longer than 250 characters, and supports Unicode characters. If a filename contains mixed case, or has one part that doesn't fit in the 8.3 convention, the file has both short and long filenames. )

Each mode can be configured with the sort options available in the popup menu on the right of the sort icon :

  • Choice of sort order :
    • Ascending order, a file named aaaa.txt will be stored in the name table before one named aaab.txt. [Default]
    • Descending order (aaab.txt before aaaa.txt)
  • Choice of folder layout :
    • Before the files: Groups the folders together at the top of the name table, and sorts the files separately.
    • After the files: Groups the folders after the files, and sorts the files separately. [Default]
    • Mixed with the files: No difference between files and folders, they are all sorted together.

DriveSort also features a manual ordering mode for files: the "playlist" mode, in which you can drag the files in the order you want. This mode is only available on the files having a long file name, because it alters the content of the short file name of the ordered files. If it was used on a file having only a short file name, the name would be lost. The short file name is altered to become something like "XXXXXXXX.EXT", where X is a digit from the file's playlist number, and EXT is the file original extension. The long file name of the files is not modified by this method, and the files are automatically ordered on the disk using the "SFN Sort" method. This is particularly useful for multimedia players which play the songs using the short file name alphabetic order, and display them using their long file names, such as the I-Bead, the Sony K750i, some devices for GBA/NDS... The playlist mode is initially able to move .MP3, .OGG and .WMA files around, to avoid files that are not really part of a playlist, like system files. If you want to add other extensions to these, use the Extensions... menu in the playlist menu, or add them to the RecognizedExtensions option of the DriveSort.ini settings file.

This program works directly with the basic structures of the filesystem, so be careful when using it, and backup anything important before.
DriveSort can create a backup of a disk or a partition from the disk selection dialog.

Use this program at your own risks.

Screenshot: Disk selection  File properties  Playlist extensions  Update  Disk backup 

Download: [ DriveSort (EN, Windows) Signature for DriveSort (EN, Windows) ]

jSAVF v1.28
jSAVF jSAVF enables you to consult and check the integrity of an IBM iSeries (AS/400) SAVF save file on a workstation with a Java runtime environment. No connection to an iSeries is needed.

Once a SAVF is open, the objects are listed in a format similar to the one provided by the DSPSAVF command. You can export this list to a text file using the File menu in a format like the one provided by the DSPSAVF *PRINT command. Unlike DSPSAVF, you can order the displayed objects by using the list headers.

You can also export a data or source file member to a text file using the context menu. The data will be converted to be readable outside an iSeries, and put together in columns of fixed width.

These integrity checks will be performed by jSAVF :

  • The file size is validated against the SAVF header information, to be sure it has not been truncated.
  • The blocks read by jSAVF are checked against the block checksums in the SAVF. jSAVF will therefore control the integrity of part of the SAVF during its indexing, and the rest if you try to export it.

The SAVF file format analysis has been done with a good hex editor and some info found in the archive.midrange.com forum (particularly the two IBM proprietary checksum algotithms).


  • The data conversions between EBCDIC and Unicode require some Java codepages which are optional in some JRE versions. If you install a JRE, ensure you check every install option, otherwise some SAVF might not be readable.
  • jSAVF requires a JRE v1.5 or above.


  • jSAVF can only display SAVFs which are uncompressed, or compressed using the old compression method (*YES below V5R2, *LOW after). The *MEDIUM and *HIGH methods will come later.
  • jSAVF eats quite a lot of memory, especially while indexing a big compressed SAVF. By default, Java limits the amount of memory available to an application to a fixed value, often below the amount of memory really available. This limit can be increased with the -Xmx option available on the java and javaw commands (ex: java -Xmx 512m jSAVF.jar).

Download: [ Java ] [ Windows ]

Style: [ intro ] [ full ]
Questions, bugs, comments ? / Want to donate ?
-- [ Mail me Public key / Donate PayPal - The safer, easier way to pay online! ] --