> > Interesting, I always assumed telling the VIC to "blank" automatically > > disabled all extra accesses.... > No, it only disables the character code/colour fetches. And if I remember > correctly, the VIC-II monitors the $d011 screen blank bit twice per frame: > you get when opening the top/bottom borders). This mode saves time if you > only need to display some information (in sprites). [COPLIN, Nicholas.] Wow... all a lot more subtle than I first expected... >From testing over the weekend it seems that simply using the 80column mode on the C128 doesn't disable the VIC-II access either, you need to manually poke the blanking codes... PLEASE TAKE NOTE: The contents of this email (including any attachments) may be privileged and confidential. Any unauthorised use of the contents is expressly prohibited. If you have received this email in error, please advise us immediately (you can contact us by telephone on +61 8 9441 2311 by reverse charge) and then permanently delete this email together with any attachments. We appreciate your co-operation. Whilst Orbital endeavours to take reasonable care to ensure that this email and any attachments are free from viruses or other defects, Orbital does not represent or warrant that such are free from computer viruses or other defects. (C) 2000: Orbital Engine Company (Australia) PTY LTD and its affiliates - This message was sent through the cbm-hackers mailing list. To unsubscribe: echo unsubscribe | mail cbm-hackers-request@dot.tml.hut.fi.
Archive generated by hypermail 2.1.1.