• can deny file open, file create, file replace, file read, file write, file/directory rename, file delete, directory create, directory delete, query file/directory attributes, change attributes, query last access date, query modification date, query creation date, set last access date, set modification date, set creation date; can hide files (make them invisible, but still accessible if the user / program knows the exact location of it), and can make files fully inaccessible (invisible, and not accessible even if the user / program knows the exact location).
• can filter file patterns using wild cards, can use more than one pattern per entry (e.g. *.exe;*.dll), can filter process names, can filter exclusion filters for file names and processes, as well.
• supports tagging a password with an entry. This way an entry is protected from unauthorized users, and makes it easy to create multiple user interface in no time. Passwords help protect items from being deleted, changed and even listed, unless the user known the exact password.
• provides so many options, that help developers make programs easier, faster and in a more efficient style, like multiple patterns per entry, process filtering, the variety of file actions to choose, password protected items, patterns and passwords limited only by available memory, network file protection and a lot more.
• supports Unicode and ANSI characters, providing the ability to make applications for far east countries (Japan, China, Korea) and also Hebrew and Arabic character support. Unicode version also helps protect files without worrying about the character code page. Alfa Corporation ships ANSI and Unicode versions as separate drivers, for full compatibility.
• can protect files by user on Windows NT, using Security Descriptors.
• can protect files by time of the day.
• Supports Windows 95/98/98SE/Me/NT4 (legacy filter, on request only) 2000/XP/2003/Vista/7/2008/8.

Callback File System provides a kernel-mode driver, which calls your application when it needs to perform some file system operation, and a user-mode API for use by your application. And your application can expose generic data as a file system to third-party processes.

Such approach lets you offer the remotely stored information for system-wide access.
 
Evaluation (time-limit)
Source: On purchase/registration
Price: $2430
Source Price: $14580

Virtual disk is the one that has a file system on it, but is not physically located on a disk partition. The storage can be actually located in a file residing on a local disk, or in applicaiton resources, or in memory, or somewhere at a remote location. The important part is that this disk is visible to the user (and to other applications) as if it were a formatted hard disk partition.

Virual disk can be needed in many cases. The examples of use are:

• the application stores some data internally (in resources or in supplementary files) and it needs to use some library, which can only work with file located within a system-wide file system. The examples include DirectX libraries, Flash player, many third-party components.
• the application must hide presence of the disk from the user, while keeping it (the disk) available for some applications
• and more ...

The component may be used to format disks which are not currently in-use, and to verify the file system on any drives, but only fix it on drives that are not in-use. It may be useful for preparing removable backup drives.

These fmifs.dll APIs are undocumented by Microsoft, but were reverse engineering by System Internals. The component is is based on the command line Chkdskx and Formatx applications by Mark Russinovich available from his site.

Please note that the fmifs.dll APIs are different from most other Windows APIs and are intended to be interactive with the user, rather than passively accepting input and providing simple output. Specifically, they return progress information that is normally seen in a Windows dialog or in a command line window, showing the steps being taken and reporting any errors or corruption found. This component attempts to parse the messages and provide simple return information. A demo program illustrates the use of all the functions.
 
Fully functional
Source: Included
Exe-Demo Included

• Assign drive letter to Device/Partition
• Remove drive letter assigned to Device/Partition
• Change drive letter assigned to Device/Partition.

And if that's not easy enough, there's even a nonvisual frontend component that makes RDA appallingly easy to use - pick drive/first sector/how many sectors to read, call one procedure to perform the actual read, read data from a property.

New to RDA 1.1 - RDA has been upgraded to support partitions larger than 4GB. You can now read from or write to any sector or cluster on a FATxx or NTFS partition of any size the filesystem allows.

RDA is based on and inspired by a Delphi unit file called VWIN32, written by Geir Wikran, and incorporates portions of VWIN32 directly. As such, RDA is released under the same licensing terms as VWIN32 - free for personal or commercial use as long as the source itself is never sold or misrepresented.

RDA is designed for Delphi 7, but should be adaptible for most versions of Delphi with minimal to moderate editing.

Please note: The RDA distribution includes a demo application which requires the Hexeditor components by Markus Stephany.
 
Fully functional
Source: Included
Exe-Demo Included

SolFS is is a virtual file system, stored in single file (or database record, file resource or just memory block). SolFS has all necessary functionality, that can be found in modern file systems, such as support for streams inside of files, file and stream encryption, compression, journalling (support for data integrity), file and storage metadata, symbolic links etc.

Using SolFS you can simplify or completely solve the problem of managing large number of supplementary files, needed to your application. Now your customers won't be confused by unknown files, populating their disk drive. Also the problem of accidential file deletion is solved: all files are kept in one place out of user's touch. When you use one file (file system storage) application maintenance and user support becomes much easier.
 
Evaluation (time-limit)
Source: On purchase/registration

• Direct disk access (read/write) logical sectors
• Direct disk access (read/write) FATs, clusters - supports FAT12, FAT16 and FAT32 file systems
• Works only under Windows 9.x
• Has everything needed in order to modify any disk file or directory directly inspite of its write protection or share aware, even running executables and DLLs.

EWF is designed to protect the Windows boot volume so effectively it's write protected and boots up identically each time, with any changes made to a protected drive being lost on power down. If changes need to be saved, EWF API calls are needed followed by a reboot to actually update the protected drive.

Microsoft provides a command line utility EWFMGR.EXE that reports any protected volumes and provides various commands that will be processed on the next restart of the PC.

The EWF API allows these commands to be made from Windows applications. The Microsoft EWFAPI.H C header file is included, with the Microsoft help file that details the various APIs. The EWF API functions enable applications to query and modify EWF configuration settings for protected volumes. Typical usage scenarios for these functions include:

• Disabling/enabling EWF for a protected volume.
• Restoring or discarding an overlay level.
• Creating a checkpoint by adding an overlay level.
• Committing the current overlay.
• Persisting data through a reboot.