Custom Query (69 matches)

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:

1. Place a pdf file without a thumbnail on the VFAT drive.
2. Open it with Lucide set to create thumbnails
3. 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.

TRAP SCREEN INFORMATION

Trap screen 1 found at address #70:989c This screen is most likely related to a previous trap.

P1=XXXXXXXX P2=XXXXXXXX P3=XXXXXXXX P4=XXXXXXXX CS:EIP=e800:00000352 CSACC= CSLIM= SS:ESP=960c:0000e868 SSACC=5089 SSLIM=000f2847 EBP=00001293 FLG=000a6282 EAX=00004800 EBX=00000e74 ECX=0000e6c7 EDX=00000000 ESI=00000222 EDI=000039df DS=04d5 DSACC= DSLIM= ES=0e74 ESACC=70b8 ESLIM=000474b8 FS=0000 FSACC= FSLIM= GS=0000 GSACC= GSLIM=* No Symbols Found #

Trap screen 2 found at address #70:9c84

EAX=00004800 EBX=00000e74 ECX=0000e6c7 EDX=00000000 ESI=00000222 EDI=000039df DS=04d5 DSACC= DSLIM= ES=0e74 ESACC=70b8 ESLIM=000474b8 FS=0000 FSACC= FSLIM= GS=0000 GSACC= GSLIM= CS:EIP=e800:00000352 CSACC= CSLIM= SS:ESP=960c:0000e868 SSACC=5089 SSLIM=000f2847 EBP=00001293 FLG=000a628

ASCII found at #70:9c84-12 is b3c17aa8 (Exception Code?) b3c17aa8: Unknown error code in 3175 trap info:

ASCII found at #70:9c84-9 is a0c3d12e. (Linear Address?) No Symbols Found # #

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.

We now run into a problem that due other developments to be able to boot from a FAT32 drive. All is working ok till the volume is in dirty state, unlike hpfs, jfs, and others the fat32.ifs driver wont run chkdsk to have a clean state after it. The job to run chkdsk is made by the cachef32 later in the boot process, however in this stage it will run into a "SYS0108 drive is locked by another process" ... so there is no way to have a clean drive in this situation. chkdsk handling needs to be moved to the ifs driver.