Custom Query (69 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (49 - 51 of 69)

Ticket Resolution Summary Owner Reporter
#69 fixed SVN rev 333: CHKDSK shows wrong version info erdmann
Description

When chkdsk is run you get this: ... FAT32: Unicode translate table for CP 437 loaded. FAT32 version 0.10.r331 compiled on Feb 11 2018 ...

However the version should be: 0.10.r333

#70 fixed IBMWorks database fails to open Barry Landy
Description

Using FAT32.IFS release 336 and opening the addressbook (aka phone) feature of IBMWorks the application opens with an apparently empty database.

It works fine in R290 and shows a populated database

the database is not damaged by the failure

#72 fixed SVN rev 352: chkdsk fails on second run erdmann
Description

If I test an intact FAT16 volume "X:" with chkdsk, I get reported a "no error". If I rerun chkdsk I always get this:

[d:\]chkdsk x: /F |more

The current hard disk drive is: X:
The type of file system for the disk is FAT32.
The FAT32 file system program has been started.
FAT32: Unicode translate table for CP 437 loaded.
FAT32 version 0.10.r352 compiled on May  8 2018
The volume label is VFDISK.
The Volume Serial Number is 255D-E414.
The type of file system for the disk is FAT12.

CHKDSK is checking fats :Ok.
CHKDSK is checking files and directories...
CHKDSK is searching for lost data.
CHKDSK has searched   0% of the disk.
SYS0562: The system detected lost data on disk X:.
CHKDSK has searched 100% of the disk.

1 lost clusters found in 1 chains.
These clusters and chains will be erased unless you convert
them to files.  Do you want to convert them to files(Y/N)? 1 lost clusters found
 in 1 chains
These clusters and chains will be erased unless you convert
them to files.  Do you want to convert them to files(Y/N)?

I have also experienced this very same error with FAT32 formatted partitions. This error is new, I don't know when it started to show.

1) No matter if I select "Y" or "N", there are no lost clusters and therefore there is nothing to convert to a file.

2) Look at the screwed up screen text output. Something is going badly wrong in properly flushing the text to the text screen.

The only way to make this error go away is to reboot the system.

Note: See TracQuery for help on using queries.