From: Nate Eldredge Newsgroups: comp.os.msdos.djgpp Subject: Re: farptr problem Date: Wed, 22 Sep 1999 12:59:34 -0700 Organization: Harvey Mudd College Message-ID: <37E93526.56813599@hmc.edu> References: NNTP-Posting-Host: mercury.st.hmc.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: nntp1.interworld.net 938030402 64284 134.173.45.219 (22 Sep 1999 20:00:02 GMT) X-Complaints-To: usenet AT nntp1 DOT interworld DOT net NNTP-Posting-Date: 22 Sep 1999 20:00:02 GMT X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.13pre10 i586) X-Accept-Language: en Lines: 19 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Anuj Bhatia wrote: > > Hi > > I'm trying to read the VESA OEM String from my program. I have read the > faq and an article on www.delorie.com. I have followed all the > instructions. My problem is that whenever I use the _farpeekb function in > a loop I always get a string of ASCII 1's. However when I use the > dosmemget function the results are correct. I am using _dos_ds as the > selector for the farpeekb function. (I have read that the dosmemget > function also uses _dos_ds internally). I do convert the far ptr returned > by the VESA driver to a linear offset. (I use the same offset for farpeekb > and dosmemget). Why doesn't farpeekb work? There's no inherent reason why it shouldn't. Please post your code. -- Nate Eldredge neldredge AT hmc DOT edu