On 2013-11-09, at 01:45, Groepaz <groepaz@gmx.net> wrote: >>> I have only ever needed something like that to find out how much RAM >>> is installed in the drive and where it is located - all other info is >>> known anyway (like location of i/o chips). >> >> Not really. DD3 equipped 1541 is a good example of a situation when this >> does not hold true. It has different I/O location (the parallel port PIA), >> different RAM size/location and different ROM size/location. > > but that is fairly easy to detect by simply querying the dos error channel, > isnt it? I could think of a database of known expansions for example - that’s correct but it still depends on the actual updates of the database content. And the use-case I am aiming at is: - someone on the other side of the globe tells me that he’s got a strange, non-standard drive - I ask him to read the error channel. He reads the 73 message and it says “TURBO CORBA V4” - he’s got neither will to rip the drive apart, nor technical knowledge enough to analyse the circuit and find out where the ROMs are addressed nor any tool to read the removed ROM chips out I’d like to send him the program (not knowing what the “turbo cobra v4” is) and get exact rom dumps back > so well, what i'd do in the drive would be (in this order) > - check the error channel/poweron message. fortunately those drive extensions > that added more than just a different ROM were not cloned a lot, so this > should give a good hint on wether there is someting like dolphin dos 3 73 says strange things sometimes. The lame rippers/cloners routinely put whatever they thought would look c00l.. > - do a ram/rom check. after that you know for certain what cant be ROM because > it is either RAM or i/o (ie, a value written can be read back) > - do empty i/o check, ie read blocks and check for $ff > - probe for i/o chips at known locations > > additionally, maybe try to find some specific ROMs at known locations and > check by checksum - things like dd3 should be detectable that way I think I’ll try something along those lines. I am afraid however that I may for example hit some unknown chips and lock the machine up (not permanently I mean but enough to render the program useless) by writing to them. -- SD! Message was sent through the cbm-hackers mailing listReceived on 2013-11-09 02:00:03
Archive generated by hypermail 2.2.0.