Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!usc!rpi!zaphod.mps.ohio-state.edu!menudo.uh.edu!gbdata!root From: root@gbdata.hou.tx.us ((Gary Clark II)) Newsgroups: comp.os.coherent Subject: Re: Coherent Small Model Limitation Summary: Coherent small memory model Keywords: coherent Message-ID: <9104271702.46@gbdata.hou.tx.us> Date: 27 Apr 91 23:02:43 GMT References: <184@lip.hanse.de> Reply-To: root@gbdata.hou.tx.us ((Gary Clark II)) Followup-To: comp.os.coherent Organization: GB Data Systems Lines: 20 Michael, The problems not with the C complier! It's in the kernel it self. When you the system, the protected mode of the 286 keeps you confined to 64k pretty much. You CAN use more, but only if you are running in supervisor mode and can play with a couple of the pointers(note this is under Coherent, when running things like xenix and SysV/AT the kernel plays with the pointers for you) This means that when writeing a device driver you can use more than 64k but really no place else, util they mod the kernel. Now I just wish they would give us atlest the option to generate 386 code for our programs.(you can use 32bit code in a 64k segment...) Does anyone disagree? Let me know. Gary -- Gary Clark II | Public Access Coherent System 713-364-9041 GB Data Systems | UUCP: !uhnix1!gbdata!root | root@gbdata.uucp Houston, Texas | INTERNET: postmaster@gbdata.hou.tx.us USA | Disclaimer: Why have one if they don't work?