Custom Query (69 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 69)

Ticket Resolution Summary Owner Reporter
#30 fixed Timestamp off for .CHK files Lewis Rosenthal
Description

After running CHKDSK and responding "Y" to write changes, I am left with the following in the root of my FAT32 volume:

11-13-76  13:49          32,256      0  FILE0000.CHK

76 should be 16.

#29 fixed Chkdsk message is interrupted before input is requested Lewis Rosenthal
Description

When checking FAT32 media (0.10alpha7, 10/20/2016 UFAT32), and corrections must be written to disk, the message breaks before prompting for input:

[c:\]chkdsk n: /f
The current hard disk drive is: N:
The type of file system for the disk is FAT32.
The FAT32 file system program has been started.
FAT32: Unicode translate table for CP 850 loaded.
(UFAT32.DLL version 0.10a7 compiled on Oct 18 2016)
The volume label is FAT32.
The Volume Serial Number is 150A-3733.
CHKDSK is checking fats :Ok.
CHKDSK is checking files and directories...
CHKDSK is searching for lost data.
CHKDSK has searched   4% of the disk.
SYS0562: The system detected lost data on disk N:.
CHKDSK has searched 100% of the disk.

63 lost clusters found in 1 chains.
These clusters and chains will be erased unless you convert

The screen stops at this line, apparently waiting for input. Pressing Ctrl-C yields us the rest of the story:

^C
External process cancelled by a Ctrl+Break or another process
them to files.  Do you want to convert them to files(Y/N)?

Likewise, simply pressing "Y" will complete the pass (but one must know that this is the prompt).

#28 fixed Dirty flag is not respected when mounting FAT32 media Lewis Rosenthal
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.

Note: See TracQuery for help on using queries.