Custom Query (69 matches)

The driver seems to corrupt partitions that where formatted with other filesystems: on boot, I have a couple of USB sticks attached, 2 of these are formatted with FAT32, another one is partitioned with 2 partitions and formatted with JFS and HPFS respectively (yet another is partitioned with 1 partition and formatted with JFS but this is irrelevant for this problem). On this two partition stick, the HPFS partition is getting corrupted without having been accessed at all. Running chkdsk on this HPFS partition also kills the JFS partition. Normally, running chkdsk on that HPFS partition has never caused a problem. The only idea I have is that the changes done to FS_MOUNT entry point might be causing these problems. It's invoked for every partition for EVERY filesystem driver, so that might be the relation to other filesystem drivers and filesystems.

I can also remember a problem in FS_MOUNT where the pDevCaps pointer was NULL where it should not have been in which case it was requeried in an alternative way (by the "ReturnDriverCaps?" function which I had implemented for exactly this purpose). This code was now removed from FS_MOUNT (for whatever reason).

Running Ko Myung Hun's 9.13 version is not causing these problems.

Latest FAT32 alpha binaries report themselves as 0.9.13, conflicting with the latest tagged release, which is confusing.

Version strings should be updated to the expected GA version level, even if "a" or "b" are appended to denote alpha or beta status.

Examples:

FAT32.IFS:

FAT32.IFS version 0.9.13 Mar 22 2015

UPFAT32.DLL:

FAT32 0.9.13 (UFAT32.DLL version %s compiled on Mar 22 2015)

I decided I wanted an easier clean so have added clean to the make files and created a base directory makefile.