Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!uwvax!oddjob!hao!noao!mcdsun!rover!mph
From: mph@rover.UUCP (Mark Huth)
Newsgroups: comp.sys.amiga
Subject: Re: Pointer disappearing
Message-ID: <417@rover.UUCP>
Date: Mon, 13-Jul-87 20:09:06 EDT
Article-I.D.: rover.417
Posted: Mon Jul 13 20:09:06 1987
Date-Received: Thu, 16-Jul-87 07:37:38 EDT
References: <3955@burdvax.PRC.Unisys.COM>
Reply-To: mph@rover.UUCP (Mark Huth)
Organization: Motorola Microcomputer Division, Tempe, Az.
Lines: 14
Keywords: Extra Memery Pointers

The problem with pointers disappearing after addition of memory is caused
by programs which were developed and tested on 512k machines.  The addition
of memory causes these programs to fail if they have buffers which must be in
chip memory (floppy buffers, video images).  Textcraft comes to mind, and I'm
sure that there are others.  There is a program (FixHunk, maybe) that forces
the whole thing to be loaded into low memory.  ATOM will modify object modules
before linking, and the Lattice 3.10 C compiler has command line directives to
make specific hunks load into memory of one type or the other.

Before I did this, I deciphered the load module format and modified the
hunk type of the BSS or data segments.  The load module format is in the
Meager Dog technical manual.  If the program Allocates the memory, you are
forced into patching the load module constants which specify the memory
type to be allocated - good luck.