| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Poking in a command then running it properly? |
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: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3) SEEN-BY: 57/0 116/102 130/210 512 153/250 218/630 317/2 393/68 633/267 280 SEEN-BY: 640/384 712/620 848 770/0 1 3 100 340 772/0 1 210 500 @PATH: 770/3 1 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.