[Coco] Emulator

Aaron Wolfe aawolfe at gmail.com
Mon Sep 7 14:15:18 EDT 2009


On Mon, Sep 7, 2009 at 1:04 PM, Wayne Campbell<asa.rand at yahoo.com> wrote:
>  just remembered. The one proof that something is different. DCom is so big that it was divided into 5 files. The main file, DCom, stayed resident, while the other parts were loaded into memory, one at a time, and executed. This was how I kept it in one 40K workspace. I wasn't ready to try using paging yet. I may be more ready now, but I wasn't then.
>
>
> Anyway, when I first ran MESS, I was able to load all of the parts into memory, without creating any new pages or windows, and it ran. It shouldn't have. It shouldn't have loaded more than DCom and one of the part files. It should have given me a memory error while loading the second part file. It didn't. A feature of NitrOS-9? A "bug" in MESS? I don't know.
>

Well, that is the question.  I suspect its just a difference in
Nitros9 and would behave the same on a real coco, but I'd hate to find
out otherwise as I am doing a project mostly under MESS and don't want
to find out down the road than it won't work on real hardware.  I do
have a coco here that I use for testing now and then, so far I haven't
seen any differences.  If you want to send me some files, I'd be happy
to try a procedure on real hardware and let you know if it behaves
differently.




> Wayne
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



More information about the Coco mailing list