You can use this tool for testing, debugging and learning Windows FileSystem APIs. If you use this tool with Process Monitor, you can understand how Windows FileSystems internally works.
FileTest can be built with one of these build environments:
- Visual Studio 2022+
- Visual Studio 2008
- WDK 6001
- CMake
md C:\Projects
cd C:\Projects
git clone https://github.com/ladislav-zezula/Aaa.git
git clone https://github.com/ladislav-zezula/FileTest.git
cd FileTest
call make-msvc.bat
The final EXEs will be in ./bin/Win32/Release
and ./bin/x64/Release
- Clone the repository
https://github.com/ladislav-zezula/WDK_6001
- Clone the repository
https://github.com/ladislav-zezula/FileTest
- Clone the repository
https://github.com/ladislav-zezula/Aaa
- Set the environment variable
WDKDIR
to the folder where you cloned the WDK - Run the build script
:: Assume C:\Projects as the current folder
git clone https://github.com/ladislav-zezula/WDK_6001.git
git clone https://github.com/ladislav-zezula/FileTest.git
git clone https://github.com/ladislav-zezula/Aaa.git
set WDKDIR=C:\Projects\WDK
cd FileTest
make.bat
The final EXEs will be in .\objfre_w2k_x86\i386
and .\objfre_wlh_amd64\amd64
git clone https://github.com/ladislav-zezula/FileTest.git
cd FileTest
git submodule add https://github.com/ladislav-zezula/Aaa.git ./lib/Aaa/
md build
cd build
cmake .. -G "Visual Studio 17 2022" :: For 64-bit build
cmake .. -G "Visual Studio 17 2022" -A Win32 :: For 32-bit build
cmake --build . --config Release
The final EXE fill be in .\build\Release