From topcatdrc at yahoo.com Sat May 28 10:55:32 2011 From: topcatdrc at yahoo.com (Thomas Clayton) Date: Sat, 28 May 2011 10:55:32 -0700 (PDT) Subject: [GEM Development] mTCP: a TCP/IP stack for DOS Message-ID: <541813.42012.qm@web82302.mail.mud.yahoo.com> http://www.brutman.com/mTCP/ NO time for expalanationsSSS! From rtdos at aol.com Sat May 28 12:36:41 2011 From: rtdos at aol.com (Wood Jeff) Date: Sat, 28 May 2011 15:36:41 -0400 (EDT) Subject: [GEM Development] (no subject) Message-ID: <8CDEB85B3F7BB93-1218-7C23E@webmail-m134.sysops.aol.com> has OpenGEM or FreeGEM (which is more current?) been ported over to *nix? Woodzy http://rtdos.communitytoolbars.com http://rollyo.com/proteanthread/rtdos From jce at seasip.demon.co.uk Sat May 28 12:41:34 2011 From: jce at seasip.demon.co.uk (John Elliott) Date: Sat, 28 May 2011 20:41:34 +0100 (BST) Subject: [GEM Development] (no subject) In-Reply-To: <8CDEB85B3F7BB93-1218-7C23E@webmail-m134.sysops.aol.com> from "Wood Jeff" at May 28, 2011 3:36:41 pm GMT Message-ID: > > has OpenGEM or FreeGEM (which is more current?) been ported over to > *nix? Not to my knowledge. It's tricky because the GEM AES is written as if it's the kernel of an OS, and assumes it can see into the address space of applications that call it. That, and all the asm bits would need to be rewritten in C, and someone would need to design interfaces between the various bits. -- John Elliott