Does anyone know whether changing the SAVMSC variable (holds the address of the first byte of screen memory) has any kind of bad effect on the printf family of calls? I am setting up a new dlist and a new screen RAM area, and after changing the system to use them a call to printf crashes the system. I am not using any kind of graphics CIO close and re-open calls, just manually changing the system pointers at 88 and 560. Dan Winslow ---------------------------------------------------------------------- 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 25 15:35:27 2009
This archive was generated by hypermail 2.1.8 : 2009-03-25 15:35:29 CET