Copy-Protected Disk (Once it dies, software gone)

[Cosmic Puppet]

Hi. I thought the same, but it was the first thing I tried. Just retested to make sure. I assume it's just poorly worded. It means that the files will only work on the disk that has copy protection.

So, again, please post the second image as I asked earlier. Take the floppy that is issuing this message. Make a new SCP image from that floppy, and post it.

Hi. Here it is:

disk2.zip

(14.46 MiB) Downloaded 5 times

[ijor]

Hi. Here it is:
disk2.zip

This is not the same "version". I mean, this disk wasn't written with an image taken from your original disk, but probably from a different image that you downloaded. So, I repeat once again. I need an image taken from the floppy disk that you wrote using an image taken from your original disk.

Anyway, I think I know what is happening. I asked and you didn't answer. Are you using a greaseweazle? If so, which software version are you using? Otherwise, which kind of flux level hardware are you using?

[kodak80]

Hi. Here it is:
disk2.zip

This is not the same "version". I mean, this disk wasn't written with an image taken from your original disk, but probably from a different image that you downloaded. So, I repeat once again. I need an image taken from the floppy disk that you wrote using an image taken from your original disk.

Anyway, I think I know what is happening. I asked and you didn't answer. Are you using a greaseweazle? If so, which software version are you using? Otherwise, which kind of flux level hardware are you using?

I wrote the provided SCP back to a floppy disk using GW and then re-dumped it. Track 11.0 is not being written back to the floppy correctly. The re-dumped SCP shows track 11.0 is not identical to the original dumped SCP and the re-dump also does not work in STeem and shows the same error as reported by Cosmic Puppet.

redump-steem.png (59.04 KiB) Viewed 80 times

Here is the re-dump from the floppy I wrote back to.

redump.zip

(21.09 MiB) Downloaded 4 times

[ijor]

I wrote the provided SCP back to a floppy disk using GW and then re-dumped it. Track 11.0 is not being written back to the floppy correctly. The re-dumped SCP shows track 11.0 is not identical to the original dumped SCP and the re-dump also does not work in STeem and shows the same error as reported by Cosmic Puppet.

Thanks Kodak. As I suspected, the problem is that track 11 has data under the index. The track must be written with the write splice shifted from the index pulse.

I am not familiar with the latest GW software versions, but if it can't do that automatically, the write splice on that track must be shifted manually.

[ijor]

Write splice on track 11 should be delayed by, approximately, 326 bytes. I don't know if the GW software accepts bytes, bits or microseconds for this parameter. Note that the trick of rotating the track data might not work because the software performs a read track. And then, data might need to have the correct alignment with the index pulse. It is the write splice that must be displaced.

[kodak80]

I wrote the provided SCP back to a floppy disk using GW and then re-dumped it. Track 11.0 is not being written back to the floppy correctly. The re-dumped SCP shows track 11.0 is not identical to the original dumped SCP and the re-dump also does not work in STeem and shows the same error as reported by Cosmic Puppet.

Thanks Kodak. As I suspected, the problem is that track 11 has data under the index. The track must be written with the write splice shifted from the index pulse.

I am not familiar with the latest GW software versions, but if it can't do that automatically, the write splice on that track must be shifted manually.

I have also just tested Supercard Pro software/flux board as well as Kryoflux software/flux board and I get the same result with all of these. Track 11.0 is not written back correctly.

[ijor]

I have also just tested Supercard Pro software/flux board as well as Kryoflux software/flux board and I get the same result with all of these. Track 11.0 is not written back correctly.

As I said, you must shift the write splice on that track. I don't think Supercard Pro or Kryoflux can do that automatically.

[Cosmic Puppet]

Hi. Here it is:
disk2.zip

This is not the same "version". I mean, this disk wasn't written with an image taken from your original disk, but probably from a different image that you downloaded. So, I repeat once again. I need an image taken from the floppy disk that you wrote using an image taken from your original disk.

Anyway, I think I know what is happening. I asked and you didn't answer. Are you using a greaseweazle? If so, which software version are you using? Otherwise, which kind of flux level hardware are you using?

Hi there. I'm using the Greaseweasle F7 Plus. Using the Greaseweasle GUI v2.114 and a new old stock Sony MPF type drive in my windows 10 PC.

AuraFluxCopy.zip

(12.73 MiB) Downloaded 5 times

[ijor]

Hi there. I'm using the Greaseweasle F7 Plus. Using the Greaseweasle GUI v2.114 and a new old stock Sony MPF type drive in my windows 10 PC.
AuraFluxCopy.zip

Thanks. Anyway, I already found, actually confirmed, the issue using Kodak's redump. The write splice on track 11 must be shifted. See my posts above.

[Cosmic Puppet]

Hi there. I'm using the Greaseweasle F7 Plus. Using the Greaseweasle GUI v2.114 and a new old stock Sony MPF type drive in my windows 10 PC.
AuraFluxCopy.zip

Thanks. Anyway, I already found, actually confirmed, the issue using Kodak's redump. The write splice on track 11 must be shifted. See my posts above.

Thanks ijor.

I'm not technically knowledgeable, but I'm wondering if the editor in HxC Floppy Emulator might help?:

Visual floppy disk.jpg (120.38 KiB) Viewed 36 times