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/simple; d=gmx.net; s=badeba3b8450; t=1566161456; bh=0RS9gO8vMVkfVavnZt7FkWkebZg3HdfFuO2FVvubzGc=; h=X-UI-Sender-Class:Date:From:To:Subject:References:In-Reply-To; b=Lf94D8X8ErreC0rOjz3GmsOUogSJ9ldVqiQW/xlP5i/wVXwRlogNmbmN0qjfWUUcy qQcAmnQr9OEa2vG636d0ZZqlVsp9ogRBjW/DwEpM6GybHs/eGbOH15SbIEmCIILGhY MyUSOLURDiF/iz6ikasoge1C4+0fCOPPfHMcSa/s= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Message-ID: <5D59BA31.90305@gmx.de> Date: Sun, 18 Aug 2019 22:50:57 +0200 From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13) Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7 MIME-Version: 1.0 To: djgpp AT delorie DOT com Subject: Re: [patch] fix empty environment handling References: <93e55dbd-cbd4-9de1-2c29-c7bb08d872f0 AT yandex DOT ru> <5D56EA51 DOT 3010509 AT gmx DOT de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed X-Provags-ID: V03:K1:FCCzqnpHVRvvPTm7lyIZZjWKgdjIi2NYzq/anrLIQqaiYBRFnrQ l3+L0TxV+s+vh0QmF0Mv/g4zaPvO7H+fFdVRg7+qO3Bvbah2ibDJ7Z+wZDEoI9vGrbs6kFz aVINIbjAadTYg+ETYFjcY0OcOJQ2UFdLLK4ncS7OLlkapvJz2JMoCx614RGywOGN4hWZstF i9Kg6gp5yOScOs0e/cv5w== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:/ylY4IgFnkA=:zHQXP5bs0AAciCoJcalwIM ZsjmjVu6kDiYh7jCv9Z1hBD7ckjC0nsHsduNmLLpIk72DHj8chIZEhzqs4g7ALDJZZeF6l7tp qYldxmxv9wLLKuo9MfijRGWoUvQpxvjpvb2l2pU5uv9O7IrsceRF/WwOs7IPd5oaLGjp1MOsi BskBDEMjA33EsYs050mPkwxP70P04F6c5FDQeDAFi0UqG52Jx7S0FbcZATMjvTdo+zFh0DJh0 9dPz7u4zfmxOL603yQaDj4cUXKqjkWQdDQhBoETvVJblAwe9U0gJscMa00xChDCcc1Cf4iowF jE0cBcAwRio/ocBTh/5IzBIV7Kk2ndBffK9KPZ6J/hMguj2cKyPyIn2aSIyG7xqZQvXx9J94B TSCvzbQ1LCvfq7UnM8xCf0GCYyDImOgbZowuNDrXpH3chsV4DfxeKrKU/lQAk2QLN68FNKp9n d3sgYcukDTuAZL/QgM0by6/XFFIzm8Qj2bYAK2mz+rl0sXmz/BeSrNFRMGCGv53ar9xWOgxZz gKj9nDsxbntHPsVmwMfZKUkfSvB+1HbVBgG6obXs0prmFH7yKLgmztD4ZkTXgRolhs0AC0kQE Jsv5hpQYOM8j5flTUeMkHIn7rTepCx8oDiYMlQCoIjjbYLdoUXr1D5xkDp87EScRvDLlyVJ1X bauIJDdTKzoeWhVEs0z1X1puzVkYWAdhUdS1X4PaajnMHg7Ml0Hcy8dAE5gVFc2NwZzIzgEUI RlYZ615+peAM+74fl8eomdvPWTvmPBnANyimtHfhlWt3cfIN8SzqiXZznyGcokmo3fbH8Czi1 jQEaS3qXl7pTAgLXKoLVUXcD6lMnGf2Gv48bTkRS07RwH6ZURJ5HNnIVuEkwwlWuYCU+Qv3Aa taOmlzAXgrB5ZBooYRv7P6aBwhu3UBikWCnxNju/kggebYxq5VTfZhvML4UTZZmFWHr275P3e kHzf7xudTHkkGc1G+ORGWIj406+boyL/txtSJLBrNeP4LaPo08lMttv4rEYjqUCSng1UfxjYB bj3lBeHtSG4fV/+ZlsODkXp/64NcrXeBOvu9wlEngiGwTUc1PMpKjtRIBGd89bLE1BrDURrtQ juFb/jTL5GqeZ0/7UbKRTq0pfTv+/5Ua1L8TRjTRvnbbmC6Dd9HUkwmJFmBxUh1gojaGa5HFd D3Fkq7MVhwZ58JR2McNhEPjWPucc287Gn/Q9m7NigumWug6w== Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x7IKplje024271 Reply-To: djgpp AT delorie DOT com Am 17.08.2019 02:20, schrieb stsp (stsp2 AT yandex DOT ru) [via djgpp AT delorie DOT com]: > 16.08.2019 20:39, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] пишет: >> If there is same sample code that I be made available to me then I can test the changes on MSDOS 6.22, MSDOS 7.10, Win98SE and NTVDM from both Win2K and WinXP > > Yes, please use this binary: > https://github.com/stsp/fdpp/files/3486048/comcom32.exe.gz > It has the patch applied, so you are supposed > to see the "|Load error: no environment segment|" > message on most DOSes if you load it with > SHELL= directive of config.sys, and you should > see the normal start-up if invoked via the native > shell rather than from config.sys.| > | OFYI, I have tried the following OS of Microsoft all installed on virtual machines with the following result: OS | Loaded with SHELL= in config.sys | Calling comcom32.exe from cmd line | or using PIF file | of the running shell -----------+------------------------------------+-------------------------------------- MSDOS 6.22 | Load error: no environment segment | MSDOS 7.10 | | Win98SE | | Win2K SP5 | | WinXP SP3 | | The table shows the tested OS and the results. The second column shows the result for the case that comcom33.exe is loaded by the SHELL directive. The third column shows the results for the case that comcom32.exe started from the command line of the running shell usually COMMAND.COM or CMD.EXE. Empty entries mean that nothing has been printed by comcom32.exe. For the Windows versions the second column means that a PIF file has been created to start comcom32.exe. The table shows that apparently only MSDOS 6.22 has an issue. If I try to start an DJGPP application from comcom32 that has been started by a PIF file I get a crash like this: ENV buffer overflow (size 208) Exiting due to signal SIGSEGV General Protection Fault at eip=00020901 eax=00000001 ebx=000cacb5 ecx=00000004 edx=0000001a esi=000cacbe edi=000000d0 ebp=000cabd8 esp=000cabc8 program=D:\SQLITE\COMCOM32.EXE cs: sel=00af base=83122000 limit=000cffff ds: sel=00b7 base=83122000 limit=000cffff es: sel=00a7 base=00024b70 limit=000000cf fs: sel=0087 base=00024d50 limit=0000ffff gs: sel=00c7 base=00000000 limit=0010ffff ss: sel=00b7 base=83122000 limit=000cffff App stack: [000cb440..0004b440] Exceptn stack: [0004b35c..0004941c] Call frame traceback EIPs: 0x00020901 0x00002145 0x00006787 0x0002e0a6 This is true for all Windows versions. I have not investigated this further because it has not relation to the issue in this thread. If more information is required please contact me. Regards, Juan M. Guerrero