Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Some minuses to Txed Plus
Message-ID: <51793@sun.uucp>
Date: 3 May 88 18:24:57 GMT
References: <1744@van-bc.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 13

There is a misconception here which I would like to clear up. Basically,
when you start TxED with *no* file, it allocates a fixed amount of space
for data (35,000 bytes for TxEd 1.3). If you then try to *open* a file 
that is larger than this then it deallocates that data and trys to allocate
enough memory to hold your file plus 10,000 bytes. If it cannot do that 
then it fails. The restriction is that the actual memory holding the file
must be continuous and that is what sometimes makes it seem like TxED can't
load large files. Editing a half meg file on a half meg system is not
possible for this exact reason.


--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.