Jump to content

westman

New Members
  • Content Count

    2
  • Joined

  • Last visited

Posts posted by westman


  1. The problem seems to be that the variable "dn" that holds the drive number gets cleared (along with all other variables) by the CLR command in line 170.  This sets "dn" to zero, and all drive accesses after that goes to device #0 (the keyboard) instead of the disk drive.  Moving the drive number configuration after line 170 would be an easy fix, or you could figure out what the CLR is supposed to accomplish and just clear the variable(s) that needed clearing at that point.  (I tested just removing the CLR, as I couldn't see any obvious reasons why it was there, and didn't notice anything going wrong.  I may have missed something, or the CLR is simply unnecessary.)


  2. On 2/24/2021 at 5:24 PM, brain said:

    Thus, the first allows the VIC-II to make a rule: sprite data must be aligned on a 64 byte boundary

    Then, the pointer for the sprite data doesn't need to store the lower 6 bits of the address, since it will always be 0.

    Also, sprite addresses are relative to the current VIC-II bank (16 KB in size), meaning that the top 2 bits of a full 16-bit address aren't needed either.  The total savings of 6+2 bits means that each sprite pointer fits in exactly one byte, which is neat and efficient.  

×
×
  • Create New...