X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "Rod Pemberton" <do_not_have AT nohavenot DOT cmm>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: failure of __dpmi_set_segment_limit() problem
Date: Thu, 9 Oct 2008 18:06:21 -0400
Organization: Aioe.org NNTP Server
Lines: 30
Message-ID: <gclvag$mho$1@aioe.org>
References: <gcbnih$6pq$1 AT aioe DOT org> <MOadnT7eV5OCQHfVnZ2dnUVZ_g6dnZ2d AT earthlink DOT com> <gcf1pk$6q8$1 AT aioe DOT org> <EfSdnbKNq9VBs3HVnZ2dnUVZ_jidnZ2d AT earthlink DOT com>
NNTP-Posting-Host: mQokHQeKeRC37oD/Mq9UYg.user.aioe.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse AT aioe DOT org
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1933
X-Newsreader: Microsoft Outlook Express 6.00.2800.1933
X-Priority: 3
X-MSMail-Priority: Normal
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


"Charles Sandmann" <cwsdpmi AT earthlink DOT net> wrote in message
news:EfSdnbKNq9VBs3HVnZ2dnUVZ_jidnZ2d AT earthlink DOT com...
> >> Under my old toolkit (v2.03) I can't reproduce the problem, compiling
> >> the .s  file.
> >
> > Could I ask you to try it under v2.04 too?
>
> How about a private email containing a broken .EXE?  It could be binutils
> versions alignment of data, or other things.
>
> I don't have an install with anything newer than the 2.03 refresh date.
>

Sorry, I don't use email.  Would you like a large .uue posted here? (No.)
I've posted the .zip'd .exe to Rapidshare (click "Free User"):
  http://rapidshare.com/files/152493125/PROB.ZIP.html

Although the original source is consistent for v2.03, the modified assembly
version seems to be intermittent.  So, I only posted v2.04 of the modified
assembly which seem more consistent.  The .exe's fail for me under MS-DOS
v7.10 (both safe mode and normal command prompt) and Win98SE dosbox.

It doesn't seem to be the DPMI host since it fails under Windows and all
other hosts.  When v2.03 fails, setting some DOS vars for the v2.03 version
corrects the problem...


RP