MediaWiki:Sitenotice:
2025-12-29: I have restored the wiki to a backup from the end of November. Starting in September 2025, accesses went form the 800MB-1.2GB range per month to 26GB in September, 42GB in October, and 70GB in November with most accesses originating from China. As soon as I realized what was causing all the access problems in November, I shut it down (it had reached 36GB by then) behind a password/login screen. The database had gotten corrupted, and I tried a restore from just before the spike in access but that didn't work. Thus, end of November. I still have the other daily backups so if there were any important additions in December, let me know and maybe they can be recovered. - Allen H.
CPU speedup (Rainbow 1981-07)
| 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 05/2/2019. Total Pages: 747. Total Files: 997.
Home / Publications / Rainbow / Rainbow 1981 / Rainbow 1981-07 - CPU speedup (Rainbow 1981-07)
Despite the stuff you may believe or have been told about the speed of the COLOR Computer's 6809E CPU, it's really a Pretty swift little device. In fact, if you want to see a Radio Shack store Manager's eyes boggle, just put a COLOR Computer next to a Mod III in his store, write a short for-next loop to count the numbers from 1 to 1,000 on both Machines and then run them at the same time. Can you guess which Computer finishes first? Yep, old COLOR Computer!
But, there's a way to make your COLOR Computer run even faster. Just POKE 63495,0. You'll be able to see this in action right away, because the cursor will start changing colors more quickly. To get back to the "normal" speed, Just POKE 65494,0.
You have to go back to normal for cassette I/O and to transmit to the printer. If you don't, you get all sorts of messy garbage. And in ref-erence to garbage, you probably will get some on the screen (or lose control) if you let your program end while you're still in the fast for— mat. Making your last line read: "POKE 65494,0: END" will handle that problem Just fine. Its a nice feature for all sorts of uses.