Custom Query (69 matches)
Results (43 - 45 of 69)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #61 | fixed | SVN rev 299: newview.exe crashes on searching in IFS.INF | ||
| Description |
I realized that IFS.INF has been enhanced with previously missing information about 32-bit entry points and enhanced system structures to support 64-bit file sizes and file offsets (which of course is a good thing). Unfortunately, the created IFS.INF is no longer searchable via newview.exe. I searched for term "FS_NAME" and newview.exe crashed. I would be good if IFS.INF would be rebuilt. Maybe Watcom's wipfc.exe has a bug. Maybe it needs to be rebuilt with ipfc.exe from the IBM OS/2 toolkit (just a guess). |
|||
| #62 | fixed | CACHEF32.EXE no longer respects the /S parameter | ||
| Description |
Using build 0.10.r288. CACHEF32.EXE displays the message: FAT32: Unicode translate table for codepage xxx loaded. even when the /S (silent) switch is specified. This is a regression to a long-running bug which was present in FAT32 builds 0.9.12 and earlier. This was fixed in 0.9.13 and the /S switch functioned as expected in that and later versions until the appearance of this regression. |
|||
| #63 | fixed | SVN rev 315: Specified /FAT switch: access to USB floppy (FAT12) becomes unbearingly slow | ||
| Description |
Using SVN rev 315:
1) added the /FAT switch to FAT32.IFS. The original intention was to be able to use a FAT16 partition > 2 GB as a dump partition (and therefore to get rid of UDUMPFS.IFS which by the way works fine just as you described in FAT32.IFS) The result was that it took for ages for the contents to show up. Accessing a file of only 20 bytes took for ages even though the actual floppy read was very short (the drive just kept spinning for a very long time without any apparent activity). Removing the /FAT switch and therefore using the kernel builtin FAT12/FAT16 support fixed the problem, that is, it worked and works with a speed that can be expected from a floppy drive. Would there be a chance to exclude FAT12 media from support by FAT32.IFS or at least make this configurable via a switch ? |
|||
