MediaWiki:Sitenotice:
2024-03-02: The wiki ran out of disk space, so things were not working. This has been resolved by adding another 5GB of quota ;-) Thanks to Tim Lindner for reporting the issues.
2020-05-17: If a page gives you an error about some revision not being found, just EDIT the page and the old page should appear in the editor. If it does, just SAVE that and the page should be restored. OS-9 Al (talk) 12:22, 17 May 2020 (CDT)
Thanks for the memories (Rainbow 1981-08)
| WELCOME |
|---|
| Looking for CoCo help? If you are trying to do something with your old Color Computer, read this quick reference. Want to contribute to this wiki? Be sure to read this first. This CoCo wiki project was started on October 29, 2004. --OS-9 Al |
See Recent Changes. | About this site. | Join the E-Mail List or Facebook Group. | Contact me with updates/questions.
This page was last updated on 08/4/2019. Total Pages: 744. Total Files: 994.
Home / Publications / Rainbow / Rainbow 1981 / Rainbow 1981-08 - Thanks for the memories (Rainbow 1981-08)
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...
Transcriber's notes: To work properly it must be: POKE 25,6: POKE &h600,0: NEW
This is because the area for the basic must start with zero, and depending on the boot, the memory is initialized with 0 for the even bytes and $FF for the odd bytes, or vice versa, because it is sometimes there is a 0 in &h600 and sometimes not, only working sometimes, for more security erase &h600 to 0, (does not work for Disk)