Date   : Fri, 11 May 2001 10:01:26 +0100
From   : "Richard Gellman" <r.gellman@...>
Subject: Re: DFS to ADFS, *MOVE/*COPY

>Can an E00 ADFS by any chance prevent programs from
>crashing due to higher PAGE in memory created by ADFS?
> Intestingly the files which have loading address of
>&E00 don't crash with DFS when PAGE=&1900 but with
>PAGE moved to &1F00 they play up.  Surely Killer
>Gorilla and Planetoid can't be that big in size?

Surely they can. BBC programs were notoriously big in comparison with the
memory space they had to use.
&1F00 was a common place to load games in - 2 pages above &1900, where page
was set to on disc-based Model Bs.
an E00 DFS will load any program into E00 because it uses higher memory for
workspace (special filing system RAM on a master 128).

Incidentally, I've found a few programs that won't work on a master UNLESS
PAGE is set to &1900. This is because they used to relocate part of there
code down to E00 via a BASIC program loaded at 1900, thereby causing a
crash.

And *MOVE tends to use user space (E00-HIMEM) and Filing System RAM as a
buffer, so any programs will be cunningly corrupted. This also happens with
the ADFS version of *COMPACT (producing the famous view-of-your-disc effect
in mode 7). The DFS version uses the standard loading buffer for *COMPACT
and therefore tends to be slower.

-- Richard Gellman