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 [2024/07/22 17:21] – [Reading 5.25″ Disks] vintagetechapp:using_fast [2024/07/22 17:28] (current) – [Concepts Common to 5.25″ and 3.5″ Disks] vintagetech
Line 65: 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 diska file name has been specified, and an export format is selected.
  
  
Line 81: Line 81:
   * 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. 
  
 {{ :gallery:fast_imager_bad_sectors.png?direct&600 }} {{ :gallery:fast_imager_bad_sectors.png?direct&600 }}