Hello André, >> >> At least Andrè mentioned that he wrote a tool that would be capable to >> read out even DOS 1 FDC ROMs (from the RRIOT chip). > > I don't remember the details, but it must be the one listed here: > http://www.6502.org/users/andre/petindex/drives/progs/index.html yes, that's correct as it looks to me. In some posting you mention a version "7" in the filename, "readfdc7". And that's exactly the filename listed in: http://www.6502.org/users/andre/petindex/drives/progs/readfdc.lst > Not sure if it actually reads the DOS1 FDC ROM though, I never had a > DOS1 drive. It uses the $E0 drive code, which is required for the > format code to be executed in a buffer (the format code does not fit > into the FDC ROM, so the execute drive code $E0 has to be there right > from the start with DOS1) See the DOS1 ROM listing around: > > FB2F A5 80 LDA DRVNUM > FB31 09 E0 ORA #$E0 ; or with EXEC > FB33 8D 03 10 STA JOBS This is interesting, so you are telling that job code 0xD0 is either missing or not working correcly with DOS1? I just checked your commented DOS1 listing a bit and the 4040 source code as well. It seems that the FDC ROM in fact does not check for Job code 0xD0, but for 0xE0 only. http://www.6502.org/users/andre/petindex/drives/roms/dos1fdc.html#FCE2 In the 4040 source I cannot clearly determine a direct match to the RRIOT ROM, so I'm not sure, if job code 0xD0 is defined there. At least code 0xD0 is defined for the bus controller ROM in an equate statement as: ;CONTROLLER JOB TYPES READ =$80 WRITE =$90 WVERFY =$A0 SEEK =$B0 BUMP =$C0 JUMPC =$D0 EXEC =$E0 So I would have to convert and test my dumper with job 0xE0. Ok, will seem if I can get this working. Womo -- ------ to obtain more infos about me, look up the page ------ ------ http://www.wmsr.de | wm (at) wmsr (dot) de ------ Message was sent through the cbm-hackers mailing listReceived on 2011-08-17 08:00:03
Archive generated by hypermail 2.2.0.