11-20-2014, 08:40 AM
I just looked at the disk image (Tumblebug) that you put in the Googledrive link above. I do see a bug in SCP software when using Atari 400/800 disk images in the analyzer. If you switch the disk type to be IBM360K, TRS-80, etc. then the image shows track/side correctly. So, I have something goofed up when it comes to plugging in the values for the Atari 400/800 disks. I will have to see if this problem also exists when writing disks. It's been a long time (probably March) since I last tested Atari 400/800 disks and a lot has changed since then. Have you tried making a copy of the disk (drive 0 to drive 0 or drive 1 to drive 1) instead of imaging the disk and then trying to write the image back? You could also set the disk type to be TRS-80 as a test (Atari 400/800, IBM360K, TRS-80, CP/M, etc. are all the same disk format).
Your Tumblebug disk or (more likely) the drive head is really dirty. The flux is pretty bad, so you should clean the drive head. You can look at the flux in the analyzer by loading the image and clicking on Flux Display. A new window will open showing the flux data. Change the disk type to IBM360K so that the track/head is correct while viewing the image. Otherwise (due to the bug I see), the disk image will show up as 80 tracks, instead of 40 tracks with two heads. Both sides of the disk are imaged with Atari 400/800 disks. I will look into this more today.
Your Tumblebug disk or (more likely) the drive head is really dirty. The flux is pretty bad, so you should clean the drive head. You can look at the flux in the analyzer by loading the image and clicking on Flux Display. A new window will open showing the flux data. Change the disk type to IBM360K so that the track/head is correct while viewing the image. Otherwise (due to the bug I see), the disk image will show up as 80 tracks, instead of 40 tracks with two heads. Both sides of the disk are imaged with Atari 400/800 disks. I will look into this more today.