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_fast [2022/02/19 00:56] – vintagetechapp:using_fast [2024/07/22 17:28] (current) – [Concepts Common to 5.25″ and 3.5″ Disks] vintagetech
Line 3: Line 3:
 TODO: TODO:
   * Finish rewrite of content.   * Finish rewrite of content.
-  * Screenshots. 
  
 ===== Overview ===== ===== Overview =====
Line 9: Line 8:
 The Fast Imager is designed to quickly image unprotected floppy disks and to recover data from damaged, unprotected disks. It displays its progress and highlights bad sectors. Bad sectors can be retried multiple times in hopes of getting a clean image. The Fast Imager is designed to quickly image unprotected floppy disks and to recover data from damaged, unprotected disks. It displays its progress and highlights bad sectors. Bad sectors can be retried multiple times in hopes of getting a clean image.
  
-The Fast Imager can save the image in many formats, depending on the source disk, including platform-appropriate image files (like ''DSK'' and ''WOZ'' for Apple II disks), as well as individual files. **The Fast Imager can not write ''a2f'' files.**+The Fast Imager can save the image in many formats, depending on the source disk, including platform-appropriate image files (like ''DSK'' and ''WOZ'' for Apple II disks), as well as individual files. **The Fast Imager can not write ''a2r'' files.**
  
 ===== UI ===== ===== UI =====
  
-{{ :app:fast_imager_1.png?direct&600 |}}+{{ :gallery:fast_imager.png?direct&600 |}}
  
 **Track/Sector Grid**: The track/sector grid shows the status of each sector that the Fast Imager has read. Tracks are the columns, sectors are the rows. Each cell is colored to show its status: **Track/Sector Grid**: The track/sector grid shows the status of each sector that the Fast Imager has read. Tracks are the columns, sectors are the rows. Each cell is colored to show its status:
Line 66: Line 65:
     * The one exception is the WOZ format natively supports metadata.     * The one exception is the WOZ format natively supports metadata.
     * Only WOZ can store additional metadata, and exporting a WOZ image as any other image type will not propagate the metadata to that other format.     * Only WOZ can store additional metadata, and exporting a WOZ image as any other image type will not propagate the metadata to that other format.
-  * The Save button is disabled until both some information was successfully read off a disk and a file name has been specified.+  * The Save button is disabled until both some information was successfully read off a disk, a file name has been specified, and an export format is selected.
  
  
 ==== Reading 5.25″ Disks ==== ==== Reading 5.25″ Disks ====
  
-[image Fast Disk Imager 5.25"]+{{ :gallery:fast_imager_525.png?direct&600 }}
  
   * If the “Clean Head” and “Image Disk” buttons are not enabled as shown above, ensure that a 5.25″ disk drive is properly connected to the AppleSauce and that the AppleSauce is connected to the host computer.   * If the “Clean Head” and “Image Disk” buttons are not enabled as shown above, ensure that a 5.25″ disk drive is properly connected to the AppleSauce and that the AppleSauce is connected to the host computer.
-  * By default each track is read twice to improve confidence that the data was read correctly (double capture) +  * By default each track is read twice (double capture) to improve confidence that the data was read correctly for formats that don't have strong checksum calculations. 
-    * If you do not want this additional verification you can select “Image disks faster by not validating with double captures”. +   
- +
 ==== Reading 3.5″ Disks ==== ==== Reading 3.5″ Disks ====
  
-[image Fast Disk Imager 3.5"]+{{ :gallery:fast_disk_imager_screenshot.png?direct&600 }}
  
   * If the “Clean Head” and “Image Disk” buttons are not enabled as shown above, ensure that a 3.5″ disk drive is properly connected to the AppleSauce and that the AppleSauce is connected to the host computer.   * If the “Clean Head” and “Image Disk” buttons are not enabled as shown above, ensure that a 3.5″ disk drive is properly connected to the AppleSauce and that the AppleSauce is connected to the host computer.
   * By checking “Autofill with volume name if available”, AppleSauce will populate the “Save As” field with the disk volume name if the inserted disk is in a format it understands.   * By checking “Autofill with volume name if available”, AppleSauce will populate the “Save As” field with the disk volume name if the inserted disk is in a format it understands.
-  * There is no option to “Image disks faster by not validating with double captures” because 3.5″ disks have a strong checksum on each block and double capture is not necessary. 
  
-[image 3.5" Disk with Some Bad Blocks]+{{ :gallery:fast_imager_bad_sectors.png?direct&600 }}
  
-In the example above, most of the disk was read successfully. However the end of the disk had some read errors. If you are confident that the red blocks do not contain valid data, you can proceed to save the disk image. In the example above, 122 files were detected in the disk image, and they all verified as good. For this specific disk, it is probably unnecessary to attempt to retry the bad blocks.+In the example above, most of the disk was read successfully. However the end of the disk had some read errors. If you are confident that the red blocks do not contain valid data, you can proceed to save the disk image. In the example above, 42 files were detected in the disk image, and they all verified as good. For this specific disk, it is probably unnecessary to attempt to retry the bad blocks.
  
-[image 3.5" Attempt to Read Bad Blocks]+{{ :gallery:fast_imager_retry_bad.png?direct&600 }}
  
 Should you attempt to retry reading the bad blocks anyway, the blocks currently being re-processed appear in blue. None of the first group of bad blocks was re-read successfully so they remain red. Should you attempt to retry reading the bad blocks anyway, the blocks currently being re-processed appear in blue. None of the first group of bad blocks was re-read successfully so they remain red.