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:46] – pdevine | app:using_flux [2024/02/23 13:54] (current) – pdevine | ||
---|---|---|---|
Line 9: | Line 9: | ||
1. Click the Flux Imager button in the left-hand navigation as shown below. | 1. Click the Flux Imager button in the left-hand navigation as shown below. | ||
- | {{ : | + | {{ : |
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. | ||
Line 23: | Line 23: | ||
{{ : | {{ : | ||
- | * 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 (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. 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 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" 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. | ||
+ | {{ : | ||