🚀 go-pugleaf

[Come, come, Here boy, sit nicely...			* GROWL *]

I have some questions on the existence of virtual memory on the A3000. Even
though I haven't read anywhere that it is supported, the fact that the 68030
has an (on chip) MMU and the A3000 comes with an HD leads me to believe that
it is not impossible that it might be so, if not at date then maybe in the
future. 

* Am I right in assuming this? Please elaborate.

If the above evaluate to YES, please consider the questions below:

* What is the page size on the (assumed) virtual memory?

* How do programs/libraries/data get swapped out?

* How do * OLD * programs (that use the * OLD * rules) contend with this?

* Are there any new AllocMem(), FreeMem() etc, functions that will be used?

* If you allocate memory of less than a page, in a process, will you start out
with a page and then fill that page with data until a new page is required or
will you get a new page for every AllocMem() you do and Allocate() yourself?

* Please include any other information concerning the implementation.

Futhermore a question on another subject:

* Has the header files (Manx/Lattice C) been modified for KS/WB 2.0?

* When will we be able to recieve these new header files?

I think the turnaround of highly informative and interesting questions and
answers have been more than first rate here on c.s.a.t and I am glad to have
the privilege (no pun B^) to read it. Looking forward to an interesting
discussion.

Thank You in Advance,

		-Mike
--
INET : mikhe@ida.liu.se                                               ///
UUCP : {mcvax,munnari,ukc,unido}!enea!liuida!majestix!mikhe          ///
ARPA : mikhe%majestix.{ida.liu.se,UUCP}@seismo.CSS.GOV           \\\/// What
SNAIL: Mike Henry, Alsattersg. 3C:20, S-582 51 Linkoping SWEDEN   \XX/ Else??