Sender: nate AT cartsys DOT com
Message-ID: <378EC30D.A2FCE19E@cartsys.com>
Date: Thu, 15 Jul 1999 22:28:45 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.10 i586)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: malloc() and CWSDPMI 4.0
References: <378bbab9 DOT 22414525 AT news DOT uni-wuppertal DOT de> <378CB591 DOT 82CC6753 AT americasm01 DOT nt DOT com> <378e1f70 DOT 6963482 AT news DOT uni-wuppertal DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Winfried Salomon wrote:

> This seems to be an disadvantage, but I only need to allocate the
> block at the beginning and i don't free it, so it should work. The
> program shall test the Ram, because I have problems with SIMMs. Years
> ago I have written such a program in Fortran77, it *must* work in C! I
> want to write test patterns in this block and think about an array to
> fill and verify it. The address of the memory cell should be offset +
> index.

If you'd rather not reinvent the wheel, there is a nice memory tester
called memtest86.  You put it on a floppy and boot, so it sees raw
memory and is OS-independent.

ftp://sunsite.unc.edu/pub/Linux/system/hardware/memtest86-1.4a.tar.gz

Extract the file image.bin, put it on a floppy using rawrite
(ftp://ftp.cdrom.com/pub/linux/slackware/install/rawrite3.{com,doc}),
and boot from it.  Then leave it there for a while.
-- 

Nate Eldredge
nate AT cartsys DOT com