Message-ID: <3251E6EB.F74@cs.com> Date: Tue, 01 Oct 1996 20:52:11 -0700 From: "John M. Aldrich" Reply-To: fighteer AT cs DOT com Organization: Three pounds of chaos and a pinch of salt MIME-Version: 1.0 To: Charles Sandmann CC: DJGPP Workers Mailing List Subject: Re: Stub error messages (Was: Re: 'Cannot open') References: <9610020024 DOT AA15296 AT clio DOT rice DOT edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Charles Sandmann wrote: > > The physical memory remaining is very environment dependent ... and will > depend on if a DPMI application is running under a DPMI server or if you > are still in real mode... Yes, I have code which does this in most > (all?) environments - if I haven't sent it to you and you want it > let me know (it does call some routines from cwsdpmi since I was too > lazy to recode up VCPI and XMS API detection calls). Actually, for _remaining_ memory I had just planned to emulate go32-v2 and use the _go32_dpmi_remaining_*_memory calls. (If you don't think this is a good idea, I'd welcome alternative suggestions.) What I need to know at present is how to determine the BASE amount of RAM on the computer. For example, my PC has 24 MB of RAM installed. DJVERIFY should be able to tell me about those 24 megs no matter how much of it is in use at the time. I can't believe that this is a very complex task; I just don't know how to do it. :) Your code would be appreciated, however. Thanks! -- --------------------------------------------------------------------- | John M. Aldrich, aka Fighteer I | fighteer AT cs DOT com | | Proud owner of what might one | http://www.cs.com/fighteer | | day be a spectacular MUD... | Plan: To make Bill Gates suffer | ---------------------------------------------------------------------