4 ms·
Poking random values into sections of memory. Start at n. poke in rnd(256). n++. Poke. Repeat till crash. The crash is often pretty. Some nice glitch. One wa
by swayvil 5y ago
Poking random values into sections of memory.
Start at n. poke in rnd(256). n++. Poke. Repeat till crash.
The crash is often pretty. Some nice glitch.
One was black screen with a fuzzy horizontal band of color near the top of the screen. Red, green, whatever. Sometimes 2 bands with 2 colors.
Another was a screen full of random characters. Glitched sprites. Stuff all buzzing blinking twitching.
Anybody else do this?
- fmakunbound 5y ago> Start at n. poke in rnd(256). n++. Poke. Repeat till crash. Pretty sure all my assembler attempts on the C64 back in the day were basically that
- chrismcb 5y agoYou are filling zero page with garbage. Half of zero page is used for the basic interpretor.
- deleted 5y ago[deleted]
- TedDoesntTalk 5y agoYes this also reminds me of “circuit bending”
- tacotacotaco 5y agoWarning to anyone with a physical C64, there are a couple memory addresses that if you poke them it will fry your monitor or your drive. Maybe this was a rumor as I can no longer find the source of this info but it would be a shame if someone damaged their system. Fortunately this never happened to me as a kid. I was thrilled when found one of the addresses for controlling a sprite.
- abbeyj 5y agohttps://en.m.wikipedia.org/wiki/Killer_poke https://en.m.wikipedia.org/wiki/Killer_poke
- kwijibob 5y agoIt's not on that wikipedia page but in older Linux desktops using XFree86 windows system (before X.Org) there were always warnings that certain monitor settings could break your monitor hardware permanently. I was always fearful of breaking an expensive fat monitor.
- voxadam 5y agoIt was absolutely possible to fry old fixed-frequency monitors by specifying an improper HorizSync in your XF86Config.[0] Fortunately, for most of us fixed-frequency CRTs had been largely replaced by more modern multisync monitors[1] before we were out of diapers. [0] https://retrocomputing.stackexchange.com/questions/6614/can-the-wrong-sync-frequency-really-destroy-a-crt-monitor https://retrocomputing.stackexchange.com/questions/6614/can-... [1] https://en.wikipedia.org/wiki/Multisync_monitor https://en.wikipedia.org/wiki/Multisync_monitor
- tenebrisalietum 5y agoYou might be thinking of the PET killer poke?
- eru 5y ago> I was thrilled when found one of the addresses for controlling a sprite. Wasn't that even in the printed handbook?
- chillingeffect 5y agoEnjoy random sound effects: 5 a=54272:b=26 10 poke a+int(rnd(1)*b), int(rnd(1)*256):goto10 Also change a and b to make random graphics!