> You should not do it. Taking a memory dump of the I/O region > ($D000-$DFFF) should not be done unless really necessary. > Reason: VICE emulates the floppy drives in a "lazy" manner. They are not > emulated unless it is needed. If you read the CIA, you might have many > thousand cycles of the floppy drive executed. Good to know. I'll skip $D000-$DFFF for now. > BTW, if there is a breakpoint in the floppy drive that is executed now, > (that is, some kind of breakpoint order inversion between C64 and > floppy) in this state, VICE will crash. So far I haven't seen any crashes but I have seen sporadic response from the remote monitor when I try to use it via Telnet [with CR/LF or just CR]. Sometimes I'll start typing a command and it'll cut me off with a response to whatever I'd been able to type, even if it wasn't the command I wanted, and if it wasn't a complete command [ie. I hadn't hit ENTER]. I'm leaving this as a possible Telnet "issue" beause I don't see the same when I try to issue commands to the remote monitor from within my program. I'm having Qt signal/slot issues with the socket, but that's another matter entirely! > Indeed. When would you need a dump of the complete addressable memory? Well I have everything I need in NESICIDE to be able to show the content of RAM. If there can be RAM behind the I/O region, I'd like to dump it too. ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Wed Mar 28 22:01:45 2012
This archive was generated by hypermail 2.1.8 : 2012-03-28 22:01:49 CEST