Kernel: Multiplatform (DOS, Maybe Windows, Linux, TOS (EMUTOS), embedded systems, and for me OS/2 :D). Basically whatever GCC runs on.<br><br>Drivers: How about a HAL like in NT,2K etc. The HAL could take care of system calls of whatever platform it was on.<br>
<br>Atari: Atari users have done a lot to modernize GEM and VDS, et all. See what we can use to bring/merge GEM into one multiplatform GUI. To be honest, I don't think there was a true multiplatform (GUI GEM 1.x and maybe GEOS but not really that multiplatform).<br>
<br>AES: Look at how XaAES is done. See how they overcome the kernel part and run AtariGEM apps.<br><br>Just me two cents, Feel free to ignore or ridicule :D<br><br> <br><br><br><br><div class="gmail_quote">On Mon, Nov 9, 2009 at 3:02 PM, John Elliott <span dir="ltr"><<a href="mailto:jce@seasip.demon.co.uk">jce@seasip.demon.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">> I think a starting point for you is probably to have a chat with John.<br>
> He has done a lot of the work to modernize GEM. His site is here:<br>
> <a href="http://www.seasip.info/Gem/index.html" target="_blank">http://www.seasip.info/Gem/index.html</a><br>
<br>
</div> You rrrrang, milord?<br>
<br>
For what it's worth, I did get the AES building in DJGPP some years ago. I<br>
emphasise 'building' rather than 'running' -- it turned out the 16->32 bit<br>
transitions somewhere in the DPMI host or the libraries weren't re-entrant,<br>
which put something of a spanner in the works.<br>
<br>
If anyone wants to write a proper 32-bit PC-GEM, they'll have to consider:<br>
<br>
* What kernel it's hosted on -- DOS, Linux, something else?<br>
<br>
* Memory protection. The AES thinks it _is_ the kernel and can see into the<br>
memory of all the applications running under it. If you want to get this<br>
working on a proper multitasking OS, you'll have to come up with some way<br>
round this -- either using shared memory, or marshalling object trees to<br>
and fro. (If the latter, the 16<-->32 marshalling code in my DJGPP bindings<br>
may help you).<br>
<br>
* How are drivers implemented? The current ones are all 16-bit asm jobs.<br>
<br>
--<br>
<font color="#888888">John Elliott<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
gem-dev mailing list<br>
<a href="mailto:gem-dev@simpits.org">gem-dev@simpits.org</a><br>
<a href="http://www.simpits.org/mailman/listinfo/gem-dev" target="_blank">http://www.simpits.org/mailman/listinfo/gem-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Bro. Michael Henry<br>Associate Pastor<br>Monticello Christian Church<br><br>1 Timothy 1:15 "This is a faithful saying, and worthy of all acceptation, that Christ Jesus came into the world to save sinners; of whom I am chief."<br>