meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
app:using_flux [2024/01/29 14:44] – pdevineapp:using_flux [2024/02/23 13:54] (current) – pdevine
Line 23: Line 23:
 {{ :app:flux_imager_start.png?800 |}} {{ :app:flux_imager_start.png?800 |}}
  
-  * Green indicates the track has been recorded with data that has sector structures, no bad sectors, and low noise. +  * **Green** (healthy) indicates the track has been recorded with data that has sector structures, no bad sectors, and low noise. 
-  * Yellow means that it does see sector structures, but it is also seeing a bunch of noise and/or bad sectors. +  * **Yellow** (poor) means that it does see sector structures, but it is also seeing a bunch of noise and/or bad sectors. 
-  * Red means that it can't find any sector structures.  +  * **Red** (bad) means that it can't find any sector structures.  
-  * Blue indicates it doesn't recognize the encoding format (MFM, GCR) of the track at all.+  * **Blue** (really bad) indicates it doesn't recognize the encoding format (FM, MFM, GCR) of the track at all.
  
 The flux image makes an initial first pass reading of the disk. This initial pass helps the Flux Imager get its bearing as to what's on the disk. While making the first pass the flux image counts the current track in the middle of the screen (shown as 3C in the image below, or 60 in decimal) and displays the elapsed time to read the disk on the left-hand side. The current track count is represented as a hexadecimal number. The below image shows the first pass as it's nearing completion. The flux image makes an initial first pass reading of the disk. This initial pass helps the Flux Imager get its bearing as to what's on the disk. While making the first pass the flux image counts the current track in the middle of the screen (shown as 3C in the image below, or 60 in decimal) and displays the elapsed time to read the disk on the left-hand side. The current track count is represented as a hexadecimal number. The below image shows the first pass as it's nearing completion.
Line 62: Line 62:
 Here are some example flux recordings so you can see how the visualization differs between various floppy data formats. In addition, note that the metadata fields change depending on what is selected in the Platform pulldown. This is to help you identify dependencies frequently encountered on each computing platform. Here are some example flux recordings so you can see how the visualization differs between various floppy data formats. In addition, note that the metadata fields change depending on what is selected in the Platform pulldown. This is to help you identify dependencies frequently encountered on each computing platform.
  
-  * Below is an example of a poor quality 800K Mac HFS disk. There are two points in time represented. The first image shows the output of the display as the first pass is being completed, at 1:10 elapsed. In the left-hand, Side A visualization, note the red and yellow indicators around the 8 o'clock position. Then in the second image, at 4:00 elapsed, note how many of the indicators in the 8 o'clock spot have turned yellow or green after Applesauce has made several attempts to recover the data cleanly.+  * Below is an example of a poor quality 800K Mac HFS disk. There are two points in time represented. The first image shows the output of the display as the first pass is being completed, at 1:10 elapsed. In the left-hand, Side A visualization, note the red and yellow indicators around the 8 o'clock position. Then in the second image, at 4:00 elapsed, note how many of the indicators in the 8 o'clock spot have improved to yellow or green after Applesauce has made several attempts to recover the data. Since this disk is not copy protected, attempting to recover the data using the Fast Imager would probably prove fruitful. The Fast Imager would allow for more attempts at re-reading the difficult sections of the disk. Also, the Fast Imager would allow attempts to recover the damaged sections with several different drives, where some drives might do better on certain sectors than other drives. Finally, a disk like this should be inspected under magnification to look for dirt or mold. A solid cleaning and/or a drop of cyclomethicone might render this disk fully readable.
 {{ :app:bad_disk_inital_pass.png?800 |}} {{ :app:bad_disk_inital_pass.png?800 |}}
 {{ :app:bad_disk_final.png?800 |}} {{ :app:bad_disk_final.png?800 |}}