[Coco] Graphics on NitrOS9 Level 1 v3.3.0 (CoCo 1)

[Bill Pierce]

Rogelio, you could merge just runb and gfx. That would save memory. I'm not really sure how L1 allocates the memory, but I know L2 uses 8k multiples. Merging the programs (in L2) would save 8k as each program would take up an 8k block. Merged, they take 1 together (in system memory). I know L1 works differently, so it may not even matter.

 

 

Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page

E-Mail: ooogalapasooo at aol.com

 

 

-----Original Message-----
From: Rogelio Perea <os9dude at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Fri, Dec 29, 2017 8:04 pm
Subject: Re: [Coco] Graphics on NitrOS9 Level 1 v3.3.0 (CoCo 1)

On Fri, Dec 29, 2017 at 5:55 PM, Bill Pierce wrote:With Basic09, the common procedure is to merge runb, syscall, inkey, & gfx> into one file named "runb" (rename the original). Before running Basic09,> "load runb". This assures all the needed modules are in memory when needed.> Basic09 in Level 1 is going to be tricky due to memory constraints.>Understood, but the intent of my message has to do only with GFX andwhatever replaced OS9Level1v2's GRFO module.I don't need INKEY nor SYSCALL in the short circle draw procedure noted. Asyou note, memory constraints are very real in the CoCo 1 64k environment,it's tight as it is in my stock OS9L1v2 system: I can load GRFO and GFX anduse Basic09 with a 3K environment space and still run a decent 256x192graphics routine... with NitrOS9L1v3.3 that is not happening.-- RP-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco