From: rogers AT westmont DOT edu (wfrogers)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: trouble accessing dos high memory
Date: 22 May 2003 21:21:46 -0700
Organization: http://groups.google.com/
Lines: 15
Message-ID: <89ce6cc3.0305222021.77a9bb0d@posting.google.com>
References: <89ce6cc3 DOT 0305220909 DOT 5c397728 AT posting DOT google DOT com> <3ecd0b5c DOT sandmann AT clio DOT rice DOT edu>
NNTP-Posting-Host: 63.147.58.59
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1053663706 25853 127.0.0.1 (23 May 2003 04:21:46 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: 23 May 2003 04:21:46 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Charles Sandmann <sandmann AT clio DOT rice DOT edu> wrote in message news:<3ecd0b5c DOT sandmann AT clio DOT rice DOT edu>...
> > the D page (in which data from the acquisition card is stored in
> > 4-byte words), which doesn't work.  The symptom is that data read from
> > memory and written to screen bears little or no resemblence to the
> > data that should be stored there from the acquisition card, and
> 
> The code looks OK at first glance.  
> 
> Does it work under DOS (not Windows)?  It could be that Windows is 
> interfering with you reading the memory.  I would make sure you don't 
> have EMM loaded (safe mode command line boot, or from a floppy).

Thanks, guys, for the help.  I have it working now.  The solution (in
addition to some of your suggestions) was to specify port 0x262
exclusively, using the outp() command.  Cheers, Warren Rogers