Path: utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!deimos.cis.ksu.edu!rutgers!sunybcs!ugkamins
From: ugkamins@sunybcs.uucp (John Kaminski)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Fonts in MEMF_PUBLIC
Keywords: not MEMF_CHIP
Message-ID: <5336@cs.Buffalo.EDU>
Date: 19 Apr 89 03:12:30 GMT
References: <4039@tekig5.PEN.TEK.COM>
Sender: nobody@cs.Buffalo.EDU
Reply-To: ugkamins@sunybcs.UUCP (John Kaminski)
Organization: SUNY/Buffalo Computer Science
Lines: 23

In article <4039@tekig5.PEN.TEK.COM> wayneck@tekig5.PEN.TEK.COM (Wayne Knapp) writes:
>I'm looking for two pieces of code that may all ready exist.
>  1.  Routines that run fonts out of MEMF_PUBLIC instead of
>      MEMF_CHIP.  I would be delighted with just the code
>      to load a font.
I thought the idea of public memory was the idea that the memory was accessible
by everything in the system.  Therefore, wouldn't public memory be chip memory?
>  2.  A working example of a user copper list.
Sorry, I'm not that much of a techie.
>These may be of interest to other people also, so are there
>any hero's out there?
>                              Wayne Knapp
hero's what?

         _ _
        ////    The Amiga 1000 refuses to die.
       ////     Old McDonald had the right idea in his song: EIEIO
_ _   ////         E-xcellence I-n E-ducation I-s O-bsolete
\\\\ ////       Being correct is being replaced by "close enough."  Soon
 \\\X///        "close enough," due to erosion of standards, will not
  \XXX/         be intelligible to me.  The next generation will be more
                leniant in acceptable standards, and the next generation
                will add its leniancy, and so on.