Custom Query (69 matches)

Inserting USB media marked dirty results in the media being mounted anyway. Running chkdsk /f against the media results in a successful chkdsk pass (according to the screen output) but the dirty flag is left unchanged (according to DFSee 13.3).

FAT32.IFS version is 0.10alpha7 (UFAT32.DLL 10-16-2016)

Marking high priority as we need to ensure that we can differentiate between clean and dirty media which is mounted after boot (autocheck is not an option for removable USB media, as the USB stack initializes too late).

as the branch/0.10 includes all changes from trunk and a lot fixes, I vote for renaming branch/0.10 to trunk. Of course the current trunk should be copied to branch first.

When playing with our Team Boot/2 bootable fat32 flash disk, I noticed the following problem: when I booted from a fat32 volume (usually, flash disk), and trying to start binaries like format.com, wget.exe, from the same FAT32 volume, I get the error like "The file format.com cannot be run in OS/2 session". If I look into the binary, I now see it being zeroed, if I view it in the hex viewer. But some binaries don't get corrupted, like shutdown.exe. I sometimes see that shutdown.exe fail to start, but after some number of attempts, it gets started, but didn't become corrupted. As it is known, the binaries are opened by the kernel Loader component, with read-write access, so it could be potentially overwritten, and it got really overwritten. What is interesting, I tried to start binaries from a non-bootable FAT32 medium, and I did not had any case when it got corrupted.