Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!star.cs.vu.nl!hvaalde
From: hvaalde@cs.vu.nl (Aalderen van Harold)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: 1.44M 3.5 disks // floppies as swap space
Message-ID: <7513@star.cs.vu.nl>
Date: 11 Sep 90 08:17:14 GMT
References: <1990Jul31.165603.20869@msuinfo.cl.msu.edu> <1407@wet.UUCP> <1990Sep10.105324.26957@agate.berkeley.edu> <10562@life.ai.mit.edu>
Sender: news@cs.vu.nl
Lines: 20

entropy@rice-chex.ai.mit.edu (enthalpy) writes:

>be able to read it back??).  This entails first of all being able to
>recognize an interrupt caused by accessing memory that was paged out
>(this part might be possible) but after paging that data back in, you
>have to be able to continue from the interrupt as if nothing had ever
>happened.  The fact that this is not a supported operation on the
>68000 makes it unlikely that such a program could be written.

it is even worse, suppose the data that is paged in is executable code
it is unlikely that you can put the code segment at exectly the same place
as it was before, so in the worse possible case you have to relocate the
complete program. And what about those parts of TOS,AES,VDI, etc that expect
certain data at specific adresses.

So even if you have the hardware to support paging, you still have to hack the
complete TOS to support it too.


Harold van Aalderen, (hvaalde@cs.vu.nl)