Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.sys.cbm    |    Discussion about Commodore micros    |    53,866 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 52,021 of 53,866    |
|    Andreas Kohlbach to Geo    |
|    Re: Poking in a command then running it     |
|    07 Jul 17 16:52:56    |
      From: ank@spamfence.net              On Fri, 7 Jul 2017 10:55:27 -0700 (PDT), Geo wrote:       >       > 60 poke631,78:poke632,197:poke633,13:pok       > e198,3       >       >       > The problem is that this doesn't execute the NEXT command. What am I doing       wrong. TIA              What is 631? Google says "Secondary addresses assigned to files", which       isn't helpful for me.              Is this time critical? Like for the interrupt vectors my POKEs often       crashed the computer. Because after poking the first value (high byte),       the C64 might already have checked the addresses of the interrupt vector       again and branched, before the slow BASIC poked the low byte to this       interrupt vector. Thus likely jumping to an area in memory filled with       garbage.       --       Andreas       You know you are a redneck if       you roll you hair with soup cans and wash it once a week.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca