| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
OpenCBM, WarpCopy, StarCommander...
Im conserned about the different transfer tools
as I can verify that they transfer same floppy disk
on same 1541-II drive with different output on the error-bytes(d64).
I just tested serverel disks with many errors.
Warp copy marks them in the error bytes correctly.
OpenCBM doesnt mark ANY of them, but I can verify
some of them using d64scan(groepaz) - atleast those
with t>40 etc.
Why does openCBM *not* write all error codes to
the error-bytes ???
Indeed Im not sure anyone should NOT use OpenCBM before
we have a good answer (or fix!)
Can anyone confirm or argue on this problem with OpenCBM ?
|
|
... 8 posts hidden. Click here to view all posts....
|
| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
Spirio: I need you email to send you the files!
|
| |
strik
Registered: Feb 2009
Posts: 4 |
Hello,
I am sorry, I was busy and not online the last days.
I just sent you my mail address. Hopefully, I did it right. If not, just re-contact me.
Regards,
Spiro |
| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
Spirio: mail sent.
Update: I have soldered the XAP1541 to my 1541-II and
tested the nibtools. NibTools also work with the same
error-bytes as StarCommander and WarpCopy.
So there is defenitly a problem with OpenCBM and writing
correct error-bytes!
Hope to see a fix to the bug in OpenCBM soon!
|
| |
E$G
Registered: Dec 2007
Posts: 840 |
@MdZ -> Hope to see a fix to the bug in OpenCBM soon!
I hope too so i can restart my transfers for U all! E$G
|
| |
sailor
Registered: Jan 2002
Posts: 90 |
nice work with all the testing MdZ, good effort!
Regards
Jani |
| |
strik
Registered: Feb 2009
Posts: 4 |
Hello,
sorry for the late answer, I am busy with other things at the moment.
Having had a look at the files send to me, I can clearly confirm these problems with error bytes. Using --nowarp on d64copy (OpenCBM), the files seem to be completely deterministic, always the same - and OpenCBM does not see any errors in transferring them.
With --warp option (which is default), things change, and the files are always different. It's the same with WarpCopy and SC, though: Almost every file is different.
I will have a more detailed look at the .NIB and .G64 files sent to me, as I want to find out who is right and who is wrong. My current working assumption is that d64copy with --nowarp behaves correctly and can correct the read errors (by reading the blocks multiple times), while SC, WarpCopy and d64copy with --warp erroneously do not fix the problems. Note, however, that this working assumption might proove wrong.
There is one problem with d64copy anyway: Other than specified in the D64 "specification", the error byte for an error-free block is written as 0x00, not as 0x01 as it should be.
So much for the time being. I will answer again when I found out more.
Regards,
Spiro |
| |
Tadpole
Registered: Jun 2002
Posts: 24 |
Sorry to push this old thread again, but I've got a little question:
If I transfer single (!) files from 5,25" disk to the PC via the Star Commander and a XE-1541-cable (yes, both work of course), does the SC give me a note, if a file is broken, or does he copy it... and yes, I really copy single files and not the complete disk... :-)
Thanxxx. |
| |
sailor
Registered: Jan 2002
Posts: 90 |
@Tadpole:
If starcommander is unable to read a file properly, i.e. due to an diskerror, it will inform you. IIRC, a "beep"-sound and a textbox with options to retry/skip or something like it.
Remember that even if SC manages to copy a file, it does not mean its OK, it just has transferred OK.
The file has to be functional on the physical disk to begin with.
Regards
Jani
|
| |
Tadpole
Registered: Jun 2002
Posts: 24 |
...thanks a lot - that's what I wanted to read... :-) |
| |
sailor
Registered: Jan 2002
Posts: 90 |
np :)
hmm.. could be that when retrying a read on a file with disk-error it might result in faulty byte(s).. or on several transfers on same file it might result in different byte(s) in that position.
..not sure though, someone who knows might fill in here... ?
..this could pass undetected if the file is not heavily crunched when trying to execute it.
/Jani
|
| Previous - 1 | 2 - Next |
