Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.


#14 Transfer autodetection should _not_only_ detect presence


All the autodetection rules should be enhanced in a way
so that they don't only check, if a decent feature is
present, but if it is valid and/or working, too.

Concretely I want d64copy to check, if an autodetected
parallel cable is working 100%, before it is used. I
the autodetection finds that the cable has got some
failure, it should print otu a warnign and fall back to
the next capable transer mechanism.

At my test environment it happened that there was a
1541 disk drive with a somewhat blown VIA chip the
parallel cable was connected to. I didn't recognize
this and thought d64copy got a software problem (bug).
Then I checked with MNib and this one told me a "Code
verify: FAILED" which brought me to the idea that the
parallel cable is not working.

In case of the parallel cable it should be enough for
the validness detection, if the four values:
55/AA/00/FF are transmitted, or 5A/0F/A5/F0, or ...


  • Womo

    A somewhat slow method is attached as a patch to detectxp1541.c.

    This is to document the core idea only, this implementation is a bit too slow, because it does each and every device port access with single M-W commands. It would be better to write some custom drive code to do:

    a) hardware detection (memory mapping, 1541 vs. 1541C vs. 1571)
    b) port chip detection (VIA, CIA, PIA 6821)
    c) parallel cable test with custom IEC bus signalling

    File Added: detectxp1541_in+out.patch



Cancel   Add attachments