🚀 go-pugleaf

In article <4053@tekig5.PEN.TEK.COM> (Wayne Knapp) writes:
> Most of the fonts I use are 50 points or larger, so not many
> other programs have need of them so multitasking isn't a 
> issue since most other programs use small fonts. 

Those are pretty good sized fonts, doing a video titler?

> Can anyone give me some real help?

Sure, but you may not like it. Basically, fonts sit in chip memory because
the Text() routine uses the blitter to blit them onto the screen. Plain and
simple. OpenDiskFont() "knows" that the blitter will be used, so convientiently
puts them in chip ram where the blitter can get to them. 

You have exactly two options :
	#1) Get an "Obese" Agnus (assuming you have a 500 or a 2000) and
	    boost your Chip ram to 1Meg. Now currently the only way to do
	    this is to buy an Amiga 2500 with an orange sticker on the
	    box (very expensive) however as the 2500 requirements are met 
	    these chips will be available as a replacement part. 
	    [Est $100 - $150]

	#2) Use the SetFunction() call to change _both_ the Text() entry
	    point and the OpenDiskFont() entry point to point to your routines.
	    Using the description of the operation of Text() as a guide, 
	    rewrite it to use only the CPU to render fonts. Then rewrite
	    OpenDiskFont() to load the font into whatever memory is available
	    fast or chip.



--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.
"A most excellent barbarian ... Genghis Kahn!"