"detect" doesn't recognize 1541 with custom ROM
Brought to you by:
strik
Menu
▾
▴
#16 "detect" doesn't recognize 1541 with custom ROM
Maybe this issue is known for long. cbmctrl "detect"
doesn't detect one of my 1541 disk drives that is
equipped with the Speeder system Professional DOS. It
seems that important locations within the ROM are
different from other 1541 DOS ROMs and therefore the
detection routine says "unknown".
Maybe we should collect a huge heap of different
IEC/IEEE disk drives and perhaps other devices. Then a
clustering technique/algorithm should/could be used to
find similarities and differences for each such group
and between each of these groups. I got an idea like
data mining based on byte-by-byte comparisons of all
the different ROMs presorted into groups of drive types.
Discussion
Logged In: YES
user_id=1059994
Please send me the ROM image of your speeder, or tell me
where I can download it.
Currently, the detection is very simple, it only reads 2
bytes from $FF40. Thus, a speeder can become "unknown" very
easily.
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Logged In: YES
user_id=1059994
reopened, as it is really a problem. It will be fixed AFTER
the next release.
Meanwhile Tommy contributed a somwhat improved version of cbmctrl detect to integrate support for the Commodore CBM series of floppy disk drives, namely the 3040, 4040, 8050 dos2.5 and 8250 dos2.7 (also SFD-1001). Furthermore in the integrattion process support for the detection of Professional-DOS was added also.
Because of this the priority is lowered to 2, but an improved detection with supporting a lot more well known drive DOS ROMs is still required.
Moved over to github (#42)