Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site amiga.amiga.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!caip!topaz!packard!ihnp1!ihnp4!nsc!pyramid!amiga!bobp From: bobp@amiga.UUCP (Robert S. Pariseau) Newsgroups: net.micro.amiga Subject: Re: gfxmem.c - graphical memory usage f Message-ID: <203@amiga.amiga.UUCP> Date: Thu, 7-Nov-85 14:11:12 EST Article-I.D.: amiga.203 Posted: Thu Nov 7 14:11:12 1985 Date-Received: Sun, 10-Nov-85 03:31:15 EST References: <249@caip.RUTGERS.EDU> <26600005@ccvaxa> Reply-To: bobp@snake.UUCP (Robert S. Pariseau) Organization: Commodore-Amiga Inc., 983 University Ave #D, Los Gatos CA 95030 Lines: 17 Most of the libraries and devices live in the Writeable Control Store -- the extra memory that's loaded from the kickstart disk. A few of the libraries and devices are loaded dynamically from the system boot disk (sys:), usually your workbench disk. You'll find them in the directories libs: and devs:. The DOS also has a few overlays in the l directory. The printer configuration files are kept in devs:printers All of this comes with every Amiga. The special stuff that comes with an Assembly or C development tool is the source include files that define structures and constants and the "link" librariies like amiga.lib. Amiga.lib contains, for example, the interface code that let's C programs call the entry points of the system libraries -- which basically have an assembly style entry sequence. The routines in a link library are linked in as part of your program. The WCS, libs:, and devs: thingies are shared. Any number of applications can reference them and only one copy will exist in the machine.