meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
app:using_flux [2024/01/29 13:34] – pdevine | app:using_flux [2024/02/23 13:54] (current) – pdevine | ||
---|---|---|---|
Line 12: | Line 12: | ||
2. Insert the disk into the drive, and click Image Disk button as shown below. | 2. Insert the disk into the drive, and click Image Disk button as shown below. | ||
- | {{ : | + | {{ : |
3. The flux imager will start to record the disk. Depending on the type of drive and disk you're imaging, you might see a slightly different representation of the progress. | 3. The flux imager will start to record the disk. Depending on the type of drive and disk you're imaging, you might see a slightly different representation of the progress. | ||
Line 20: | Line 20: | ||
An aqua circle will appear to bounce between the left and right disk images; the aqua circle shows which track is currently being read. After the track completes a visual indicator of the flux transitions is shown as that mottled gray that slowly fills in the circle. This visual representation of the flux image helps represent the organization of the underlying data. MFM, GCR, and other disk types have clearly different visual images. | An aqua circle will appear to bounce between the left and right disk images; the aqua circle shows which track is currently being read. After the track completes a visual indicator of the flux transitions is shown as that mottled gray that slowly fills in the circle. This visual representation of the flux image helps represent the organization of the underlying data. MFM, GCR, and other disk types have clearly different visual images. | ||
- | Finally, as another progress indicator, colored boxes start to encircle the outside of the image. These are both progress bars and recording health indicators. When the colored bars make a complete circle the first pass of the recording has been made. | + | Finally, as another progress indicator, colored boxes may start to encircle the outside of the image. These are both progress bars and recording health indicators. When the colored bars make a complete circle the first pass of the recording has been made. 3.5" disks will show these outer progress colors while 5.25" disks will not have these indicators present. |
- | {{ : | + | {{ : |
- | * Green 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. | + | |
- | * Red means that it can't find any sector structures. | + | |
- | * Blue indicates | + | |
- | 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, and it also counts | + | 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 |
- | {{ : | + | {{ : |
Some disks have complex medleys of various formats, where publishers might have put MFM data in one set of tracks and GCR data in another. After moving across the whole surface of the disk from the outside in towards the center, the imager then reverses the process and takes a second pass through the disk gong from the inside track outward. | Some disks have complex medleys of various formats, where publishers might have put MFM data in one set of tracks and GCR data in another. After moving across the whole surface of the disk from the outside in towards the center, the imager then reverses the process and takes a second pass through the disk gong from the inside track outward. | ||
Line 36: | Line 36: | ||
As this format is designed to capture potentially intentional errors used by copy-protection mechanisms, AppleSauce will attempt to record accurate representations of blank, damaged, or corrupted data. This can be challenging as some corrupt information has occurred due to physical damage, dirt or mold on the disk, or simply the impact of time. While other data was intentionally corrupted during the disk creation process as part of a copy protection scheme. Multiple passes of each track gives the Applesauce a better sense of how to interpret this messy reality. While doing the second pass the track count decrements from the highest track to the lowest track, meaning it counts backwards. The elapsed time continues to count the total time the imaging process is taking. Below shows an image of the second pass halfway completed, note the aqua circle is traveling in the opposite direction towards the outside of the disk. | As this format is designed to capture potentially intentional errors used by copy-protection mechanisms, AppleSauce will attempt to record accurate representations of blank, damaged, or corrupted data. This can be challenging as some corrupt information has occurred due to physical damage, dirt or mold on the disk, or simply the impact of time. While other data was intentionally corrupted during the disk creation process as part of a copy protection scheme. Multiple passes of each track gives the Applesauce a better sense of how to interpret this messy reality. While doing the second pass the track count decrements from the highest track to the lowest track, meaning it counts backwards. The elapsed time continues to count the total time the imaging process is taking. Below shows an image of the second pass halfway completed, note the aqua circle is traveling in the opposite direction towards the outside of the disk. | ||
- | {{ : | + | {{ : |
4. While the disk is being imaged, you can fill out the Product Metadata on the right-hand side of the screen. Often this can be obtained from the disk label, while sometimes you need to allow the imaging process to be completed to know what's actually on the disk. For archival purposes try to be as complete as possible. Remember individuals in the future may get a copy of the .a2r and might need a serial number, unlock key, or other information that's on the disk label or jacket. More information is always better. | 4. While the disk is being imaged, you can fill out the Product Metadata on the right-hand side of the screen. Often this can be obtained from the disk label, while sometimes you need to allow the imaging process to be completed to know what's actually on the disk. For archival purposes try to be as complete as possible. Remember individuals in the future may get a copy of the .a2r and might need a serial number, unlock key, or other information that's on the disk label or jacket. More information is always better. | ||
- | {{ : | + | {{ : |
5. When the disk has completed being read, click the Save & Analyze button in the lower right-hand corner of the screen. | 5. When the disk has completed being read, click the Save & Analyze button in the lower right-hand corner of the screen. | ||
- | {{ : | + | {{ : |
6. The disk will open in the disk analyzer. | 6. The disk will open in the disk analyzer. | ||
- | {{ : | + | {{ : |
---- | ---- | ||
Line 52: | Line 52: | ||
=== Sides to Image === | === Sides to Image === | ||
- | The Sides to Image selector, just below the Image Disk button, defaults to Autodetect. In the autodetect mode the Applesauce reads the first few tracks on both Side A and Side B and attempts to determine if the disk is single or double sided. If the Side B doesn' | + | The Sides to Image selector, just below the Image Disk button, defaults to Autodetect. In the autodetect mode the Applesauce reads the first few tracks on both Side A and Side B and attempts to determine if the disk is single or double sided. If the Side B doesn' |
{{ : | {{ : | ||
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 disk shows the output of the display as the first pass is being completed. In the left-hand, Side A visualization, | + | * 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, |
{{ : | {{ : | ||
{{ : | {{ : | ||
Line 69: | Line 69: | ||
{{ : | {{ : | ||
- | * Below is an example of a 5.25" DSDD 360K MFM IBM Disk. Notice the fading that appears at the 1 o' | + | * Below is an example of a 5.25" DSDD 360K MFM IBM Disk. Notice the fading that appears at the 11 o' |
{{ : | {{ : | ||
- | * Below is an example of a 5.25" SSQD 620K Victor 9000 GCR Disk. Note the right-hand circle is black because this is a single-sided disk with no data on the 2nd side. The Flux Imager tried to read several of the outer tracks on Side B, and when it saw a pattern of no data on the 2nd side it determined it was a single sided disk. | + | * Below is an example of a 5.25" SSQD 620K Victor 9000 GCR Disk. Note the right-hand circle is black because this is a single-sided disk with no data on Side B. The Flux Imager tried to read several of the outer tracks on Side B, and when it saw a pattern of no data on the 2nd side it determined it was a single sided disk. |
{{ : | {{ : | ||
+ | |||
+ | * Below is an example of a 5.25" Flippy DSQD 1.2M Victor 9000 GCR Disk. Note the Flux Imager saw data on both sides of the disk so the autodetect treated it as a double-sided disk. But this is a flippy—meaning the disk was treated as if each side was a single-sided disk. In the vintage hardware the second side was written and read by inserting the disk upside down, hence the name flippy. Only drives that didn't utilize an index sensor could read and write flippy disks. Because of this, when read right-side up by the Applesauce the disk data will be read backwards and the track will be slightly misaligned for the Side B as the upper and lower recording heads are not in the same position relative to the disk. So after imaging the data on the second side will not be valid when read this way. | ||
+ | {{ : | ||