Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!uw-beaver!ubc-cs!fornax!laughlin From: laughlin@fornax.UUCP (Bob Laughlin) Newsgroups: comp.sys.amiga.programmer Subject: Re: "chip" qualifier for Aztec C (V5.0d)? Summary: linker option +cd is poor substitute Message-ID: <2492@fornax.UUCP> Date: 14 Apr 91 17:55:15 GMT References: <21925@shlump.nac.dec.com> <41242@cup.portal.com> Reply-To: laughlin@lccr.UUCP (Bob Laughlin) Organization: School of Computing Science, Simon Fraser University Lines: 15 In article <41242@cup.portal.com> plav@cup.portal.com (Rick M Plavnicky) writes: > ......... >This comes up every so often. Manx currently does NOT offer the ``chip'' >keyword in their product. (Current product is referred to as 5.0e, but >signs on as 5.0d dated Sep 30 1990) > ......... One way to force screen data into CHIP ram is to use the +cd linker option with Manx 5.0d. This puts all initialized data into CHIP memory. If the initialized data in your program is largely image data then this is a reasonable alternative and is preferable to AllocMem'ing CHIP mem and copying it over. Manx 5.0d does need the chip keyword though. -- Bob Laughlin laughlin@cs.sfu.ca