Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!mcnc!raw
From: raw@mcnc.org (Russell Williams)
Newsgroups: comp.sys.amiga
Subject: F-16 Versus DF1:  The War Continues....
Keywords: F-16 Df1: Kickstart Eliminator Addmem
Message-ID: <4168@alvin.mcnc.org>
Date: 11 Mar 89 02:08:42 GMT
Organization: Microelectronics Center of NC; RTP, NC
Lines: 30


	I'd like to being by thanking every for their help in getting my F-16
running.  However, the situation has taken a stranger twist, and I'd like to
find out why.

	The story so far...

1)  F-16 requires all 512K to run, leaving no memory for DF1:
2)  The obvious answer to this is to remove DF1:  This is obviously a clumsy
answer.
3)  Use Install2, a program which will ignore DF1: when booting up.  I haven't
tried this, but I think it will work.

However, I happen to have a kickstart eliminator.  This gives me 256k of extra
ram, and I would like to use it on F-16 because this would give me access to
the black box feature, which uses the extra ram.

To inform the system of the additional memory, I have to issue the command
ADDMEM 0f80000 0fbffff in the startup sequence.  The game loads up fine, using
the second drive, but the sound doesn't work!!!  I get the title song, and 
every time I use the engines I get a BOOM, but nothing else makes a sound.

I've tried putting the addmem statement in a seperate startup-sequence to give
it time to load so that Falcon couldn't possibly get intertwined with memory
allocation with it, but it's no good.

	I feel like I'm really close to getting this thing to work.  If anybody
has any ideas, I'd really appreciate hearing them.

					Russell Williams