Path: utzoo!utgpu!attcan!uunet!yale!eagle!jtreworgy
From: jtreworgy@eagle.wesleyan.edu
Newsgroups: comp.sys.amiga.tech
Subject: One more wish for 1.4
Message-ID: <478@eagle.wesleyan.edu>
Date: 11 Aug 89 15:17:28 GMT
References: <13080@well.UUCP>
Lines: 26

In article <13080@well.UUCP>, xanthian@well.UUCP (Kent Paul Dolan) writes:
> Hack, however (at least my version), is one of those antiques ported before
> anybody had more than 512K memory on their Amigas, and it needs to be
> restricted to chip ram, or all the pictures get lost.  Hack played on a
> continually blank screen is _boring_!
> 

> Flipping the NoFastRam toggle while I'm loading stuff into RAM: isn't such
> a hot idea, though; some of my RAM: segment allocations end up in chip ram,
> and there they stay until I reboot, since the stuff I'm loading while I play
> is pretty much "read-only".
> 
[...]

Here's a better idea... use FixHunk or PowerPacker (which I recently posted in
comp.sys.amiga) to force your program to load into chip ram. I have done this
to every such program, and never had a problem (except of course that I've got
all this fast RAM & the stupid things are residing in CHIP ram!).

I'm not sure about fixhunk, but with powerpacker you can choose which hunks you
want forced into CHIP ram; usually just putting the data hunks there does the
trick.
-- 
James A. Treworgy
jtreworgy@eagle.wesleyan.edu
jtreworgy%eagle@WESLEYAN.BITNET