X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=6W0qy4+ujq7G37kDc1B5RsNpqsv4dtxEvJHVNsySAQk=; b=PZ+To1+g7qP5dbrYXFhIcBh56Ih8jjz1BJWOnNt7K0RZO2bQFXc0rp9q+pVpuPBVTF 7yQ25UE/zRoCkL6saK+nxdVbdbFxiT0IVQMonyu05sUls78k9EKTmiWWyvyZ6/mPXCrf bUKPxJSkBV5qAFKzmGtCaKRIWgoL0lSsWioEKnjXt9+gjnqTOlV/obz8FM6sKmpGbAeR j/Qgm+iel18SmXoDcZ2bTEeT7j4TEuEa2QsE4eXuNXZSxCzYwgmuh4DZjutfZbo9nuF7 O/bVTJGbEiXbv9DDPCdVPpqaVsbwVLEPvgqoDrTNy6eATy6+Y40zF8UrfporbEvqtamF ALRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6W0qy4+ujq7G37kDc1B5RsNpqsv4dtxEvJHVNsySAQk=; b=HlQzlLYtPw75ALLB6xnwJX58maeRFzjZUa7c79WDZxbAaopmpbqZUQ5FkqPLf08IlM K8ajSYbCxGUykM7S8cUjttSsxHHeqSz8D8szGinugXC0mh45r7805vBcO7heYXeDcGkp 03HyMsf1WmG0SOY4IPQbbDYOx1HzqbpBoAKRHUNMZggw13ZKnTEUAcVtvErxtZb26Cbu LQxN8risR6rteRF0m+JAe2COEE3lqO7edNV6Ttf2VHosorz0VX5OKoOwhSrEWzew1cwc TedRCSE+zgyFGdthhIGNEd9XjIvsy572QvMlWbrrVOsd9il2bj2UnaAEkzHUiUEN9/pX XM5w== X-Gm-Message-State: AFqh2kpaZhjx3fQYkVN2BLWoVAWk8FFJ815vjHUNDP8Qi0oqhTUs3Rj/ lku/vImabECm45jM6/M7vcXZazCdQ/TOsw== X-Google-Smtp-Source: AMrXdXunIfXooopEekyWI8s4VAJvIfHcY/HZR35duYIMz0S6/aOV7auouhN9MEMxoFqGDMk21Jd7LA== X-Received: by 2002:a17:907:cbc5:b0:7ad:9455:d57d with SMTP id vk5-20020a170907cbc500b007ad9455d57dmr36998168ejc.74.1674681028808; Wed, 25 Jan 2023 13:10:28 -0800 (PST) Message-ID: Date: Wed, 25 Jan 2023 22:10:28 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH] stub: ignore host exit status Content-Language: en-US To: djgpp AT delorie DOT com References: <744f054f-9682-4a05-91ad-684b18c0122b AT gmail DOT com> <21e1aa0b-1511-0071-84c0-b20c6a3d1dae AT gmail DOT com> <5de28b44-10f2-c824-def1-d451035ecaad AT gmail DOT com> From: "J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 2023-01-25 00:36, Frank H. Sapone (emoaddict15 AT gmail DOT com) [via djgpp AT delorie DOT com] wrote: > I know you're looking for feedback but I dont use hdpmi32 and don't know of too many others that do except to run some windows console apps under dos.  Cwsdpmi works just fine for djgpp. > > In any case, someone who knows what they're looking at can hopefully chime in.  Just wanted to let you know we're receiving your messages. :) Thanks for the message! I think this is an important patch, hopefully someone can review it at some point. Although I suppose this should be fixed on the hdpmi32 side too, so newer hdpmi versions are compatible with old djgpp programs, and new djgpp programs can work with older hdpmi versions. As for why someone might want to use hdpmi instead of cwsdpmi, the simple answer is speed - on the few functions I benchmarked, it's over 20 times faster. That can add up on things like allocating memory or PM-RM switches. Plus it implements more (almost all) DPMI 1.0 functions.