| MediaWiki:Sitenotice |
|---|
| 2026-03-12: Cocopedia.com is now using a new caching system that should make things faster. Please let me know if you encounter any new issues.
2026-03-15: MediaWiki has been reinstalled and the old database and files restored. It was pretty clogged up from being upgraded so many times since 2004. I am also testing out Cloudflare to see if it can prevent the 'bot assaults that took the site down last year. OS-9 Al (talk) 21:20, 15 March 2026 (EDT)) |
Thanks for the memories (Rainbow 1981-08): Difference between revisions
Luis46coco (talk | contribs) mNo edit summary |
Luis46coco (talk | contribs) mNo edit summary |
||
| Line 3: | Line 3: | ||
There is a way. . . | There is a way. . . | ||
Just '''POKE 25,6:NEW''' when you power up, and you will have an additional 1.5K of | Just '''POKE 25,6:NEW''' when you power up, and you will have an additional 1.5K of bona fide memory to use. We aren't exactly sure what this does, but it seems to remove the high-res graphic screen from memory. It stays gone so long as you don't PCLEAR the Color Computer. | ||
You have to plan advance. The Poke doesn't work if you leave off the :NEW, and, if you have a program residig in memory, the :NEW will wipe. | You have to plan advance. The Poke doesn't work if you leave off the :NEW, and, if you have a program residig in memory, the :NEW will wipe. | ||
Revision as of 21:32, 28 March 2019
Yes, we do love the Color Computer, but we get somewhat unhappy when we get right on the edge of usable memory and realize there is some 1.5K being "eaten" up by high-res graphic screens we're not ptanning to use.
There is a way. . .
Just POKE 25,6:NEW when you power up, and you will have an additional 1.5K of bona fide memory to use. We aren't exactly sure what this does, but it seems to remove the high-res graphic screen from memory. It stays gone so long as you don't PCLEAR the Color Computer.
You have to plan advance. The Poke doesn't work if you leave off the :NEW, and, if you have a program residig in memory, the :NEW will wipe.
One way to avoid this problem If you did not plan ahead would be to CSAVE the program, reset the memory and then CLOAD the program back in.
As Bob Hope said...
