Custom Query (69 matches)
Results (13 - 15 of 69)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #54 | fixed | DDK files in FAT32 SVN repo | ||
| Description |
I always wonder why files that are part of another set of files need to included in other projects such as these: These are from \ddk\base\h src\include\devclass.h src\include\devcmd.h src\include\devhdr.h src\include\devhelp.h src\include\dhcalls.h src\include\dskinit.h src\include\fsd.h src\include\fsh.h src\include\infoseg.h src\include\iorb.h src\include\reqpkt.h src\include\sas.h src\include\strat2.h This is not a full list. There are others pulled from other subdirectorieis of the DDK sources. Somebody send me that list. Also the inclusion of these files violates the IBM DDK license. |
|||
| #28 | fixed | Dirty flag is not respected when mounting FAT32 media | ||
| Description |
When the dirty flag is set - for whatever reason - media should not be mounted and available for writing until checked. This is expected behavior on OS/2. While autocheck may work for always-connected-at-boot-time media, it does not work for removable media. Currently, USB media inserted after boot time with the dirty flag set is simply mounted. This may lead to further data corruption unless chkdsk is performed against the volume. |
|||
| #27 | fixed | Dirty flag not cleared after manual chkdsk pass | ||
| Description |
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). |
|||
