Message-ID: <3251C64B.3DA6@cs.com> Date: Tue, 01 Oct 1996 18:33:00 -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: Eli Zaretskii CC: Charles Sandmann , DJGPP Workers Mailing List Subject: Re: Stub error messages (Was: Re: 'Cannot open') References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit [DJVERIFY progress report: Finished test program compilation routine. DJVERIFY is now capable of outputting a complete bug report. Changed custom stub to utilize error codes in the 100-110 range and updated the error messages in the batch file. Currently working on detection of system configuration.] Eli Zaretskii wrote: > > On Sun, 29 Sep 1996, John M. Aldrich wrote: > > > a bug report. I am working on test program compilation right now. I > > still need information on how to verify the system memory > > configuration.] > > What information do you miss? What I would particularly like is a method to determine the base amount of physical RAM on the host computer, as opposed to the physical memory remaining when the program is run. I imagine this would require some sort of BIOS call. Charles offered to send me some examples of memory detection algorithms a while back - if any of those touch on this question I'd love to see them. BTW, if anybody here would like to test out the alpha versions of DJVERIFY, I'd be happy to upload the code to DJ's server or email it to you. Any suggestions on output format would be greatly appreciated. :) -- John M. Aldrich * Anything that happens, happens. * Anything that, in happening, causes something else to happen, causes something else to happen. * Anything that, in happening, causes itself to happen again, happens again. * It doesn't necessarily do it in chronological order, though. --- Douglas Adams