#36 Error-bytes are not made for all errors.

[Anonymous]

I have tested d64copy, StarCommand & WarpCopy.

StarCommand & WarpCopy writes ALL error-bytes to
the d64-file.

d64copy does NOT write all error-bytes... only some
of them. (Possible missing the sectors with crc-error)

Please fix this problem, as it looks like
the releases on a d64 are working - but are NOT!!!

[Spiro Trikaliotis]

Hello,

I have already seen your (?) thread on http://noname.c64.org/csdb/forums/?roomid=10&topicid=63348. I even tried to answer you, but until now, I was not able to register there.

It would be good to be able to investigate the bug by having a working example. Unfortunately, in the thread at CSDB , I can read that you do not own mnib. Thus, you cannot send me a .g64 or .nib file, right?

Either way, it would help me if you could send me a .D64 as generated by d64copy, and a D64 as generated by another tool.

Is the generated D64 from d64copy always exactly the same, or are there differences when running d64copy multiple times?

It would also help if you could me if this problem persists if the option --nowarp is selected. Could you please also test with all the transfer options (-ts1, -ts2), with --warp or --nowarp?

Regards,
Spiro

[Womo]

Since a while there is now a nibtools image added with a certain number of disk errors. Have a look at:

opencbm\internal\testsuite\errored41.txt
opencbm\internal\testsuite\errored41.nib

With this test set we are now able to find out why d64copy (presumable the 6502 code) does overlook some of the existing error type conditions.

[Spiro Trikaliotis]

Moved over to github: https://github.com/OpenCBM/OpenCBM/issues/46