X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Jim Michaels Newsgroups: comp.os.msdos.djgpp Subject: Re: help on using dosmemput, dosmemget, anything like it Date: Fri, 20 Feb 2009 14:27:21 -0800 (PST) Organization: http://groups.google.com Lines: 26 Message-ID: <9bd2f6b6-49bb-4ab9-8349-059f41e8df68@w35g2000yqm.googlegroups.com> References: NNTP-Posting-Host: 76.115.70.155 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1235168841 22883 127.0.0.1 (20 Feb 2009 22:27:21 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Fri, 20 Feb 2009 22:27:21 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: w35g2000yqm.googlegroups.com; posting-host=76.115.70.155; posting-account=05hOMwoAAAB6R8xtiQKzEljSMzgOhVF1 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6,gzip(gfe),gzip(gfe) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com On Feb 20, 1:58=A0am, Eli Zaretskii wrote: > > From: Jim Michaels > > Date: Fri, 20 Feb 2009 00:23:53 -0800 (PST) > > > Background: > > I have no revision control (my fault), and I did something to make my > > bios disk routines not work. =A0it has gone through several fixes and > > revisions. > > problem may be that I am using a different compiler (djgpp current > > instead of 2.03 or 2.04), or it may be the code change. > > > The code seemed (?) to work on an IDE based computer, but not with my > > SATA drive. =A0SATA drives used to work with this program (I wrote to > > the SATA drive with this program once). > > Where exactly does your code fail now, and how does it fail? after the ExtendedWrite command I get the error message from the dpmi_int13 call (BIOS) returning 0x01 ERR_BAD_COMMAND in AH. it is possible the memory is not set up correctly. I think I ran into that bug once before, but I thought I fixed that with the 2 calls to dosmemput, dosmemget. Calls to ExtendedRead do not seem to fail however, when I use it to get partition information. the code almost looks exactly the same.