Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
  You are not logged in - nap
D64EIC   [2014]

D64EIC Released by :
Triad [web]

Release Date :
31 July 2014

Type :
Other Platform C64 Tool

d64 Errorinfo Combiner

User rating:awaiting 8 votes (3 left)   See votestatistics

Credits :
Code .... Sailor of Triad
Idea .... Sailor of Triad

Download :
http://csdb.dk/getinternalfile.php/131406/d64EICv1_TRIAD.zip (downloads: 693)

Look for downloads on external sites:

User Comment
Submitted by sailor on 20 August 2014
and hmm.. :) while touching the subject.. the resulting data(file) should be verified against another / different .. C64 File Integrity Tool V1.2 .. i have code to read the md5 of a file inside a .d64... but thats another story :).
User Comment
Submitted by sailor on 20 August 2014
(editing disabled...) "...on some of those disks i only read a couple of tracks just to get the best of the worst and combined them with the tool...."
User Comment
Submitted by sailor on 20 August 2014
hi, yes. Of course you need to have a "feeling" of what is best for a bad disk, there is no tool that can replace or automate experience... from my website; http://blog.worldofjani.com/?p=647 . As you can see on the picture, those disks are way past the warranty period and not helped by cleaning....on some disks read a couple of tracks just to get the best of the worst and combining them with the tool.

In the tool I also put weight on what kind of error is presented on the actual sector..
User Comment
Submitted by ΛΛdZ on 20 August 2014
Disks with many errors will usually also create (some) false positives - which makes you believe that checksum checked sectors seems ok, but are not due to the weakness in the checksum. e.g. image1.t13.s5 != image1'.t13.s5 even both has a valid error-block-info. Now this creates the need to create all possible good reads (where the data is different, but the checksums are the same) with the less error blocks... And which read is better than the other ???

In my opinion you should rather spend time on opening the sleeve and take out the floppy it self and clean it under water with soap and gently rub on it till it look clean. Then dry the floppy and put into a known-good sleeve.
Now this method gives you a good floppy to get a good read from.

Ofcos there are cases where this tool is handy and good to use, but consider my thoughts before you hammer your head into the pillow as a combined-error-free d64 is "fixed" still does not work... checksum are weak - better clean the source and get a good dump :)

Thanks to Sailor for the tool - it is easier to use than my php-code version :)
User Comment
Submitted by Groepaz on 5 August 2014
warpcopy creates error info
User Comment
Submitted by bugjam on 5 August 2014
Thanks for all the info! What about WarpCopy, do you know?
User Comment
Submitted by taper on 2 August 2014
Thanks for the info, Lemming! Good to know for sure.
User Comment
Submitted by lemming on 2 August 2014
Yess, Kryoflux has the support. You need to use the -6a parameter when converting Kryoflux dumps to .d64 with dtc.exe:

> 6a: CBM DOS sector image with error map
User Comment
Submitted by taper on 2 August 2014
Semantics... But Ian is right. :)
User Comment
Submitted by iAN CooG on 1 August 2014
I guess the confusion is due to "separate", it's not separate at all, it's appended if anything. =)
User Comment
Submitted by Groepaz on 1 August 2014
actually all tools that create (or handle) D64 files should support errorinfo - if not, they are broken :)
User Comment
Submitted by taper on 1 August 2014
Bugjam: You should be able to identify .d64 with errorinfo attached by the filesize of the image. A 35 track diskimage without errorinfo is 174848 bytes, while a 35 track disk with errorinfo is slightly larger, 175531 bytes.

Starcommander supports errorinfo. Zoomfloppy/OpenCBM and Kryoflyx did not from the beginning, but as far as I know OpenCBM now supports it, and those behind Kryoflux promised to support it "in the future", so perhaps they already implemented it by now.
User Comment
Submitted by bugjam on 1 August 2014
Sounds nice - noob question, though: what is this "separate error-information block" mentioned? Which programs/transfer methods create it, and which don't?
Search CSDb
Prev - Random - Next
Detailed Info
· Summaries (1)
· User Comments (13)
· Production Notes
Fun Stuff
· Goofs
· Hidden Parts
· Trivia
· Discuss this release
Sponsored links
Support CSDb
Help keep CSDb running:

Funding status:

About this site:
CSDb (Commodore 64 Scene Database) is a website which goal is to gather as much information and material about the scene around the commodore 64 computer - the worlds most popular home computer throughout time. Here you can find almost anything which was ever made for the commodore 64, and more is being added every day. As this website is scene related, you can mostly find demos, music and graphics made by the people who made the scene (the sceners), but you can also find a lot of the old classic games here. Try out the search box in the top right corner, or check out the CSDb main page for the latest additions.
Home - Disclaimer
Copyright © No Name 2001-2022
Page generated in: 0.082 sec.