KryoFlux Support Forums

This coincides with my experiences! When it finaly works after 50 retries it works better and better after that! First with 10 attempts, after that with the usual 5 and at last immediately with the first atempt. I agree, it looks as if there is some layer of dirt on the surface, which is slowly worn...

Some programming languages (like java for example) use % as the indicator to place args in a string.Thats why the percent character should be avoided in filenames, even if the OS and FS allow it! BTW: The % character was also used as a wildcard in some OS in the past, making it almost impossible to ...

In observation, I have noticed that in a lot of my dumps I either get the following for Track 18 Byte 3 in the BAM: 0x00 - Single sided disk 0x80 - Double sided disk 0x2A - ????? :o In looking into this, I've not been able to find any information as to why 0x2A is often found at Track 18 Byte 3. Ho...

Simply said: You can't do a checksum in raw or stream file mode, because you don't know if checksum errors a caused by read errors or copy protection! But you can can create format guided raw or stream files, where you select multiple outputs (for example raw and AmigaDOS). In this case the AmigaDOS...

I'm sorry to repeat myself again, but don't forget, that the drive is spinning the wrong direction on the second side if you read a flippy disk in a dual head drive (without flipping it). So the data-stream has to be corrected (turned reverse) directly after you read a single track from the second s...

Yes of course, there are so many "errors" that it seems to be unformatted. Looking to the scatter plot ("View/Scatter Window" from the GUIs menu) shows that the second side in fact is very well formatted! Its just the wrong format (opposite direction) and therefore not in the pattern you choosed to ...

Could it be that you used different density line flags for g64 and d64 encoding? With the example command line in your third posting above you used -dd0 for creating g64 files. Using -dd1 may change the output...

David

It has all been discussed years ago in this forum Please use the search function with "dumping c1571 disks"...

The side two of a 1571 double mode disk would only give errors when read with flippy commands as the data have been written the oposite direction. Maybe that's the most definite way to determine if it has been written double sided or flippy mode.

David

As I said in answer #1 there is byte 3 in the BAM (side 0) with a flag indicating single-sided 1541 mode or double -sided 1571 mode!

As far as I remember the byte contains 00 for 1541 and 80 for 1571 format. But I'm not shure now, after all theese years....

David