X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Received:	by 2002:adf:dcd2:: with SMTP id x18mr20074747wrm.340.1566115801673;
	Sun, 18 Aug 2019 01:10:01 -0700 (PDT)
From:	Rod Pemberton <invalid AT lkntrgzxc DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: [PATCH] exec: fix inversions in leak detection logic
Date:	Sun, 18 Aug 2019 04:12:36 -0400
Organization:	Aioe.org NNTP Server
Lines:	39
Message-ID:	<qjb14m$1kqj$1@gioia.aioe.org>
References:	<964e3268-2f75-ee73-ab5a-b01bf1aadb98 AT yandex DOT ru>
NNTP-Posting-Host:	+15yR2JuBIwiofOqK4kSZw.user.gioia.aioe.org
Mime-Version:	1.0
X-Complaints-To:	abuse AT aioe DOT org
X-Notice:	Filtered by postfilter v. 0.9.2
Bytes:	2150
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

On Sat, 17 Aug 2019 19:18:10 +0300
"Stas Sergeev (stsp2 AT yandex DOT ru) [via djgpp AT delorie DOT com]"
<djgpp AT delorie DOT com> wrote:

> Without this patch it is not possible to spawn a prot-mode TSR
> program like 32rtm.

You do understand that Borland's 32RTM is a DPMI host, yes?

I.e., it's not _just_ an example of a "prot-mode TSR program".

So, why do you expect 32RTM to execute properly when spawned?

I.e., another DPMI host is already loaded prior to performing the
spawn, e.g., CWSDPMI or Windows DPMI.

You can test this like so for DOS:

CWSDPMI -P
32RTM -X

Why do you need to use 32RTM with DJGPP code?

Why do you need to use 32RTM anyway?

It seems that 32RTM is bug riddled:

https://sourceforge.net/p/freedos/mailman/message/8956650/
https://sourceforge.net/p/dosemu/feature-requests/17/?page=1
ftp://retronn.de/dos/extender/hx/DOC/HDPMI.TXT
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/history.txt
https://vetusware.com/download/PowerPack%201.0a/?id=3726


Rod Pemberton
-- 
Let me say it yet again.  Reducing gun violence doesn't reduce
violence.  Dead is dead, whether by gun, car, hammer, club, or knife.

- Raw text -