[Coco] Dumb OS9 graphics question

[Bill Pierce]

Allen
vdgint went the same route as all the others. covdg=vdgint, cowin=windint, cograf=stripped down cowin(?)
Most of the OS-9 system modules (if not all) have been renamed to reflect their changes and prevent clashes with the originals which can no longer be used. Also, each system module has build conditionals for 6809, 6309, Level 1, Level 2, Tano Dragon, Dragon, Dragon Alpha, and Liber8 (where applicable)

Have fun figuring that out.... :-)

Bill Pierce
My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com




-----Original Message-----
From: Allen Huffman <alsplace at pobox.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Thu, Apr 4, 2013 10:47 am
Subject: Re: [Coco] Dumb OS9 graphics question


On Apr 4, 2013, at 7:00 AM, Robert Gault <robert.gault at att.net> wrote:

> Unless you want to hijack the entire OS-9 system and possibly require a reboot 
after ending your program, hardware manipulation is best left to OS-9 itself. 
That means you should use CoVDG for working with Pmode type screens.

Years ago, I believe it was Robert who provided me sample code to get access to 
the CoCo 3 hi-res screens under stock OS-9 so I could write my Space Invaders 
style game, Invaders09.

Where did "CoVDG" come from? What happened to VDGINT?

		-- Allen


--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco