File System Check (fsCheck)

The fsCheck tap validates the file system of a toppy disk. This eliminates the need to attach the disk to a pc so that it can be analyzed using TopfHDRW (although TopfHDRW may still need to be used if the file system needs to be repaired).

The tap can be installed in \ProgramFiles or one of its subfolders (“\ProgramFiles\Auto Start” is not recommended!).

The tap can normally be run while other taps are running irrespective of whether or not the toppy is Time Shifting or Recording (but you may have to run without other taps if memory is “low”).

As this tap is primarily for use when the disk structure is suspect, it needs to be loaded onto the toppy in anticipation of a future problem (this avoids modifying the file system when it may be corrupted).


When run, fsCheck scans the disk and produces a report that contains the following sections :- 

· VERDICT (“appears  GOOD” or “appears  CORRUPTED”)
· File summary (the number of files, folders and capacity of the disk)
· A summary of issues (numbers of each type of issue and type of fix) 
· The issues (later ones may be suppressed if a “large” number exist)
· Disk Geometry (sectors, clusters, FAT size)
· Disk Usage (similar to the File summary) 
· SMART data (output similar to that produced by the HDDInfo tap)
· SMART Interpretation (an interpretation of the SMART data – see pdf file)
· Performance Statistics (memory usage/analysis time)

The “report” is built up in memory and is displayed on the TV screen and also output to the RS232 serial interface (for those who can process this data).

For a “normal” toppy, this report will look very boring as there should be no issues (assuming one treats any flagged Time Shifting or “Recording in progress” as comments).

When the number of issues is “large”, some may be suppressed from the onscreen display (it is unlikely that anyone wants to scroll through hundreds of lines using button presses) and from the serial interface (to improve performance because this is a slow device). Note: Both outputs have their own suppression point (and they may not be the same!).

The full report can be stored to disk by pressing the Record or Archive buttons on the remote control (you should really only do this if the disk doesn’t appear corrupt!).

The file will be normally be written to \ProgramFiles\Logs\fsCheck_yyyy-mm-dd_hh-nn.log where the yyyy, nn, dd, hh, and nn represent the current date, month, day, hours and minutes respectively.
Note: This file may be written to \ProgramFiles if the Logs folder does not exist and the file system appears to be corrupted.