Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!munnari.oz.au!murdu!ucsvc.ucs.unimelb.edu.au!u3364521
From: U3364521@ucsvc.ucs.unimelb.edu.au (Lou Cavallo)
Newsgroups: comp.sys.amiga.tech
Subject: Files larger than available memory.
Message-ID: <924@ucsvc.ucs.unimelb.edu.au>
Date: 11 Aug 90 12:38:01 GMT
Organization: I.A.E.S.R., Melbourne University
Lines: 25

G'day,

the discussion re: Virtual Memory/MMU/Protection reminds me of a tangentially
related issue.  Some criticism of Amiga software (such as word processors) is
related to the inability to deal with files/data larger than available memory.

Have developers dealt with this problem? If so how are they doing it?  If not
is it because they are waiting for VM?

I do assume this point has been discussed before. Please rather than chastise
me for bringing up the problem again perhaps someone could send me a summary.

I would have thought that this special (commercially important) case may have
led to the creation of  special purpose demand based paged memory scheme/s by
someone out there. Or would that hack (?) be too inefficient on non MMU Amiga
systems? {Kind of answering my own question there eh? :-)}

Don't Mac's run s/w that can deal with files larger than available memory?
I would presume such s/w could run on non MMU based Mac's.

{ I'm not really criticising here. I'm just wondering whether the Amiga s/w }
{ developers are (or will be) writing s/w that can deal these questions.    }

yours truly,
Lou Cavallo.