| |
ΛΛ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 ?
|
|
| |
sailor
Registered: Jan 2002
Posts: 90 |
Hello,
I might be slight off-topic, but another tool is mnib (yes, i know its mainly for protected software) but you can use -i switch and then later on covert them from nib>.d64 with the errorbytes/info.. I don't know how this errorinfo compares to other software.
From the c64preservation.com page:
"Interactive mode should be working 100% now. Command line interface to this is clunky, but functional. Allows 9 second backups. :)"
/Jani
|
| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
I did not try mnib yet as it requires soldering in my 1541-II,
but Im sure mnib works better than openCBM.
StarCommander: I just verified with starcommander, and it
makes same error-bytes as WarpCopy so far.. so it seems that
OpenCBM is broken!
Please verify anyone!
|
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
ehm i dunno, but i xferred some disks with opencbm with error info, and was able to use the disk, just not the broken file(s) - isnt that the whole idea ? to copy what you can ?
to repair a broken pacman game, isnt possible anyway ?
i admit i dont really know what to use the error info for..
if i can copy all working files on a disk, then i am happy. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11360 |
Quote:i admit i dont really know what to use the error info for
you use it to see which files have errors =P if you copy d64s without errorinfo you have no way to check wether files have errors other than loading and running them. |
| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
It IS possible to repair broken files if you have more version
of the same file with different errors...
Files can be split up in block of 254bytes(sectors), on
d64 files each sector has an error block attached - atleast
using warpcopy/starcommander.
Here is an example of pacman (rambones) where you can
imagine 3 different "versions" that have different errors:
p1: [1][5][5][1]...[1]
p2: [1][5][1][1]...[1]
p3: [1][1][2]
[1] = ok
[2] = illigal next t/s
[5] = crc error
to get a working version in this example just combine
the "working" blocks and get a working pacman:
p4: [1][1][1][1]...[1]
I have done it with serveral missing releases for TDD, CSDB
& Mason - where none of the versions worked individual!
Having error information is pretty useful to repair
releases- so using openCBM is damn shitty as it doesnt
write all error-bytes.
Also .. with no error-bytes it will look as if the disk
works, which is even more fucked... as u might have
to load and run ALL files to determine if the release is
ok... with games u possible will have to complete the
entire game... which can take quite some time...
|
| |
strik
Registered: Feb 2009
Posts: 4 |
Quote: 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 ?
Hello,
this is Spiro from OpenCBM. I was not able to answer earlier as I only got my CSDB account today. ;)
Quote:
OpenCBM doesnt mark ANY of them, but I can verify
some of them using d64scan(groepaz) - atleast those
with t>40 etc.
thank you for your report, which I also found on http://sourceforge.net/tracker2/?func=detail&aid=2544083&group_... I also answered there that I need more information. Ideally, you would send me a .G64 or .nib file of the disk in question. If it is not available - from reading your other answers, I conclude that you do not have an XP1541 cable - at least send me the .d64 from OpenCBM and a correct one.
Furthermore, you might want to test some variants for d64copy, and try it multiple times:
- the option --nowarp
- the other transfer options -ts1, -ts2
That would result in 8 files from OpenCBM:
- --nowarp -ts1 (2 times)
- --nowarp -ts2 (2 times)
- --warp -ts1 (2 times)
- --warp -ts2 (2 times)
and the "working" .d64 of another tool, of course.
Hopefully, this information will help me to find the cause of this problem.
Regards,
Spiro |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
thats really cool Mdz!
its like a RAID 5 :)
what prg can do this ? combine several copies to working one ? |
| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
Rambones: I have made such tool... will be released at
MaZZa :)
Spirio : I have an XA1541, and WarpCopy+NET. Recently I got
a XAP1541 cable to make .g64 with mnib, but I still
need to do the last soldering to actually use it.
- please PM me your email so I can send you the
files. Thanks for joining in to solve the problem!
|
| |
ΛΛ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
|
