Custom Query (69 matches)

This is with a build of CS 176 without xfat. I run pmchkdsk on the drives and it opens and indicates it is checking. Leaving open for 5 plus minutes yields no change. Chkdsk from command line completes checks in 10-30 seconds.

In line 2 and 3 it is identified as UNIFAT and in line 4,5 & 10 as FAT 32

The current hard disk drive is: F: The type of file system for the disk is UNIFAT. The UNIFAT file system program has been started. FAT32: Unicode translate table for CP 850 loaded. FAT32 version 0.10.r277 compiled on Jun 13 2017 The volume label is TEST.

The Volume Serial Number is 1903-3D48.

The type of file system for the disk is FAT32.

Writing large eas to a VFAT drive causes a system trap. The eas are a thumbnail created by Lucide. It also traps in fat32 when you try to copy a file with large eas attached (again a thumbnail created by Lucide). Steps to reproduce:

Place a pdf file without a thumbnail on the VFAT drive. Open it with Lucide set to create thumbnails When you close the file or Lucide (which is when the eas get written) you trap

The same thing occurs on a FAT32 drive if you copy a pdf that already has a thumbnail as part of its eas.

Note this was not happening with r280 but was with r276 and r277.

The following is the trap screen from the VFAT trap described above. I have a system dump of both traps above. I also have a system dump from just repeatedly accessing the drive from the drives folder which was also fixed by turning off eas. All these problems go away with eas turned off.