Found and fixed the bug. CBM cmd builds a string consisting of path, filename and suffix characters (e.g. PRG, L,size, etc.) and uses the _same_string_ (using target path) when opening BOTH source AND target files. Guess what happens when you're trying to read from '0:filename,L129' on an SFD1001 while writing to '1:filename...' on another device? I should have been able to find this by inspection, but sometimes one misses the obvious. Finally discovered it by picking through a logic analyzer trace of IEEE bus traffic. Now that I'm knee deep in the sources, I can think of some valuable additions. Stay tuned. -- Sent from: http://cbm-hackers.2304266.n4.nabble.com/Received on 2020-10-11 20:00:03
Archive generated by hypermail 2.3.0.