Custom Query (69 matches)
Results (46 - 48 of 69)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18 | invalid | Ability to at least read Windows long filenames on FAT32 | ||
| Description |
MS holds several FAT-related patents specific to the storage of long filenames (see http://en.swpat.org/wiki/Microsoft_FAT_patents for links). However, none of those should preclude us from reading the Windows LFNs so that they don't show up as blah~1.ext. As we store LFNs differently, we could at least read the Windows LFNs and when saving to a new LFN, then store using our method. |
|||
| #21 | invalid | Implement formatting in an expected manner (format x: /fs:FAT32) | ||
| Description |
Currently, formatting a FAT32 volume involves running a standalone executable (fat32fmt.exe) with its own syntax. Formatting FAT32 should be accomplished as with any other filesystem under OS/2, via the format command: FORMAT X: /FS:FAT32 It should also be possible, then, to enhance PMFORMAT.EXE to support formatting FAT32 (not that such an enhancement belongs to this ticket or this project). |
|||
| #22 | fixed | Update version strings in all binaries to reflect current level | ||
| Description |
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) |
|||
