[GEM Development] DayDream (was NextGem..)

[Shane M. Coughlan]

>   The problem is that the internals of GEM are, to put it bluntly, ugly.
> Quite a lot of the API is designed around the assumption that the
programs,
> accessories, AES and VDI all share an address space - which makes it very
> efficient on a 512k XT, but starts biting you as soon as you get into
> protected mode. I met some of this with my DJGPP experiments, but at least
> there you could share the lower 640k of memory.
>   I think I've got the AES/VDI connection sorted now; it supports using a
> 16-bit VDI in DOSEMU and a 32-bit AES running natively. It should even be
> possible to make it work between computers over TCP/IP. But how can
> rsrc_load() be handled sanely?

Whoops.  You have a 32bit AES?  Interesting.

Regards

Shane