X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f NNTP-Posting-Date: Mon, 20 May 2013 22:54:35 -0500 From: "Charles Sandmann" Newsgroups: comp.os.msdos.djgpp References: <201304061704 DOT r36H4k48018021 AT delorie DOT com> <3728e704-b839-4ad6-998e-d3aab686b649 AT googlegroups DOT com> <12d60e38-9778-4463-b914-396c2a62273f AT googlegroups DOT com> Subject: Re: ANNOUNCE: DJGPP port of GNU binutils 2.23.2 - stack size Date: Mon, 20 May 2013 22:54:22 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-RFC2646: Format=Flowed; Original Message-ID: Lines: 23 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 64.91.136.221 X-Trace: sv3-vpsj6HNZZ2mLPvcfStDj4+wO6Zu7KIYLik3xHWvXGb6Y128t0utOmF6nlrfNKjfbc2zJMy4OHXBbSp+!Q9eKnaWt9BLF97beCPQCfny5ZR2RAcR3JTcPDr/pX6B7PxQq53x0FZUw+ceK71lrkg3vLIL+dlSF!TmfPo+/aV2Ia/g+QgqUku/Hnb5SqmAUY X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 Bytes: 2333 X-Original-Bytes: 2272 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com >"RayeR" wrote in message >news:12d60e38-9778-4463-b914-396c2a62273f AT googlegroups DOT com... >Aha, so no way under DPMI 0.9 to implement classic grow-down stack? Not and have it expand and have SS=DS=CS. If SS can be independent we could move it and rebase it, but that breaks the flat 32-bit model. >But you can allocate block of memory at specific address range (or not?) - >near top of memory. No, you cannot specify an address in DPMI 0.9 (except when mapping a hardware device). You request a block of a specific size and DPMI 0.9 returns it (wherever it wants, not necessarily anyplace near where your current blocks are). >I know CWSDPMI support some functionality of DPMI 1.0 but not this? The issue is that by 1998, about 99% of DJGPP users were using some other DPMI provider (mostly in Win95 or Win98), so coding to an enhanced standard unsupported by MS was futile.