From:	Charles Sandmann <sandmann AT new-orleans DOT NeoSoft DOT com>
Subject:	Re: Should "topline" report MORE memory than GO32 does? [was: Ramdrive]
To:	turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp (Stephen Turnbull)
Date:	Wed, 11 Jan 1995 07:55:23 -0600 (CST)
Cc:	bdavidson AT ra DOT isisnet DOT com, djgpp AT sun DOT soe DOT clarkson DOT edu

>    to you (although  was _pretty_ sure).  Now go32 reports 1400Kb, and 
>    topline under info reports 1768Kb!! (aside: surely KB not Kb; I always 
> 
> Any gurus out there know what's going on here?  Looks like something
> is confused about how much memory there is!  Is it GO32 or Info or what?

GO32 reports the amount of extended memory, topline reports the amount of
working memory (which also includes the free DOS 1Mb area memory).  The
368K difference is the amount of free DOS memory when the program is loaded.
GO32 uses this memory too before starting to page.

>    and protection faults.  That is what I find weird.  The same sequence of 
>    commands under the same environment produces different (or differently 
>    reported) exceptions at different points in the program.  I would have 
>    thought that I would see the problem at *exactly* the same place after 
>    *exactly* the same commands (and it would raise the same error message).
> 
> It is probably not worth your time to try to gt symify to work on info
> stack traces then.  Sounds like an OS problem.

Sounds like a hardware problem; maybe a bad memory spot?  Clocks running 
faster than some component rated for?  Or a buggy ISR?

Try booting with missing config.sys/autoexec.bat and see if it works.

- Raw text -