mirror of
https://github.com/reactos/reactos.git
synced 2025-01-08 07:11:16 +00:00
A free Windows-compatible Operating System - mirrored from GitHub
ed1b816943
It seems suspicious to directly return the value of fs_close as the NTSTATUS code of the check-disk operation (for FAT32 volumes it happens to return 1 whereas for FAT16 volumes it returns 0). The documentation of this function says that it "returns a non-zero integer if the file system has been changed since the last fs_open, zero otherwise." Maybe somebody has a more precise idea on that subject? In the meantime I also add some DPRINTs to attempt to diagnose the conditions where this problem occurs. svn path=/trunk/; revision=70434 |
||
---|---|---|
reactos | ||
rosapps | ||
rossubsys | ||
rostests | ||
wallpapers |