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=1566165841;
	bh=z8WBQETNqBk2mWb9ImdKQ8JEdnwWFhJvwiaZxVIZZtw=;
	h=X-UI-Sender-Class:Date:From:To:Subject:References:In-Reply-To;
	b=T7F15l1KWe/LyVG086K2qjIfwL9S209QPDdzdWAWPWmggFe0S39K+kdY0kx6bemZ2
	yWafTajl/b2L/5yq1LbqQwshVLWAAWDZ/y5wr0Hb8K2q+1Alyq7xztxUSz20TrGEPW
	TGpjIZ1jhJJJ5dKVLbbedxt3s2ddB9aEpxSZciLw=
X-UI-Sender-Class:	01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Message-ID:	<5D59CB52.5040809@gmx.de>
Date:	Mon, 19 Aug 2019 00:04:02 +0200
From:	"Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" <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> <CAA2C=vCoQth+AZc9FsEqX2A2STx9kVMvJ8moYHLzjgP=uc1cMQ AT mail DOT gmail DOT com> <b9b8c99b-39aa-b451-f7fa-8ba812f29503 AT yandex DOT ru> <5D56EA51 DOT 3010509 AT gmx DOT de> <a507b2e5-3c52-ab52-6b2f-4622b6f40e01 AT yandex DOT ru> <5D59BA31 DOT 90305 AT gmx DOT de> <a7d6213a-6609-30ba-967a-99b7fcfb8663 AT yandex DOT ru>
In-Reply-To:	<a7d6213a-6609-30ba-967a-99b7fcfb8663@yandex.ru>
X-Provags-ID:	V03:K1:EvFaDR8ENJPGtYJo810pZrQyGH4rCgUCwfeDMZGURsOaJMShFDX
	Xw8gbfs9K74GwN+ViAr0T2Vq42YSeA0TQ2I41Pj7qSynT3J/N3sqAx/JgV0Hk4Nm25I057m
	MRrt6r33AO3esUU8k4k8aBkV+eLY6UY1/v+1eL8qjAEBzG1KtTWgqY/XARADyjf4EKGWldb
	POmZp3cphR9qTB/JGbugA==
X-Spam-Flag:	NO
X-UI-Out-Filterresults:	notjunk:1;V03:K0:h0htaxLyM0I=:n9SYMy2y2kDOqcKaiZnmwE
	E6enK73ETDKrx+w8SwScXBNbAEKQTDAodg0T10RN+CqFWeWSjLfRJ0nQ6XKcHony0swUMkdHw
	ab8DUnVBcmNqWUByiakfjCrR3+wSWOstmUyRdL4/nr+RfzVwAzbHJ0tscV8sH143AswU6BVxR
	LZAtm3V4A1hIq9ClX738yS+QipiDEcV81iP9YSKh6qhlHPKk02Z/XWJAU7JGDoK5te7yYpd7O
	Rsl1Nvpr6JNWfiuzAbmK1HdMD7OPkZsZ6J8jPtoto6EQYH4cJNW3VvFYxx8XysnwHWopsROWF
	hKqC15DEgVA+39Jg8QVfnv3e53K+tMmxEP1+zVAZDIx/jyVQVYL6q4n2fJ/x/09bZ8nSflYJU
	heuaxemVemiK6jaOpGT4y44jwxy0fjKR9JuHuA7GB56cGWOSefc3DsRuTG8PKYWpWFRVtAMtB
	MicCwndesn9NV2JLVDRFBAyQ60UpXjg8epLKm5xPtNSlCuXKGUpOEQSzIVfpsXW9Y+4GuDlbr
	VsUevPa60ded0j/4Z0gQoKnrkCSbH3ftdr/yp1aZvu42e2xEqu/L6WRy8El7XED+TOGM1VkDX
	WxXx3SeHW+hGI5oKHLwpG6eH11vQQ5sAPHwwdFRIopOAmfEhpI3vDqzpWTj7hyscgj98NMHax
	tUZi3HmzhtBERvuwpTXh66fjV6P5U045ijsljby5JT+BDSZ7dA+ShP4gHhWbqhWFdY9HJarG+
	cq/8A2aYvYd5ZUMRyKqgsXnC6JzOt1zyWxxPkJt9wg8YlqZP+/4jvtnbPafbrGxGsjvft9kTv
	LqpTiw6ySodKN6Bb3DZCrLbVJhCw4e64MxiRd8Fb9m/xuron73ltyog67L1nnjpHkyfJJ9ZFQ
	BGdyfGPChdZlU+LPvgncVuGFpBhuLwe5bgQO+EkWlmGYxlJiIeNmwEhmx1Mn8d9yEcH6fFEnq
	0VS+ESSY5MhkgpZ4+HU06XX8VA/wTE/anV9XBirT/fJ3QwrkqfvgsUcNSOdUQrwppCE9DqU0Z
	3zX5JSCH39csPTGVN3HOm89H7yYEhzo3D9RTPB8s9/mr0NFLdwhMMIvaHECFlWb8SzhD1PGxy
	w3y98jltp8VUuKUToVo2eegOEUvgLmeuZ3j22zMF1r5RaOw9ObvjwLBYtshJ2sD7n94XP5top
	wvsTA=
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id x7IM4pKC003212
Reply-To:	djgpp AT delorie DOT com

Am 18.08.2019 23:20, schrieb stsp (stsp2 AT yandex DOT ru) [via djgpp AT delorie DOT com]:
> 18.08.2019 23:50, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] пишет:
>> 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  |                                    |
[snip]
>
> You mean really nothing, even not a command prompt?
> That would be strange, but otherwise perhaps DOSes
> above 6.22 got that bug fixed. As for Windows - it definitely
> wouldn't have an empty env, so on windows I don't suppose
> this problem can be reproduced. Its only about plain DOSes
> (but in your case plain 7.10 doesn't show any problem too).

Sorry for creating confusion.  On Windows comcom32 works fine.
This means it produces a prompt and you can run commands when
the environment is large enough.
My intention was to report that no error like in MSDOS 6.22
is produced by Windows versions so it looks to me as if this
issue is really DOS specific and has been fixed in later Windows
versions as you noted already.
Even on plain MSDOS 7.10 I have experienced no issue. To be
sure that comcom32.exe is really used at booting on 7.10, I have
renamed the command.com installed in c:\windows\.  On plain
7.10 I get no message like on 6.22 and comcom32 works and
runs programs when the environment is large enough.

Regards,
Juan M. Guerrero

- Raw text -