From: "Jay K (jayk123 AT hotmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To: "djgpp AT delorie DOT com" <djgpp AT delorie DOT com>
Subject: Re:  command line length problems? (win10)
Thread-Topic: command line length problems? (win10)
Thread-Index: AQHYFNfWWufuR513F0y9O4pOz99u4w==
Date: Sat, 29 Jan 2022 06:17:06 +0000
Message-ID:
 <MWHPR1401MB195164FBEACF3251815116EFE6239 AT MWHPR1401MB1951 DOT namprd14 DOT prod DOT outlook DOT com>
References: <202201290505 DOT 20T552Cj016531 AT delorie DOT com>
In-Reply-To: <202201290505.20T552Cj016531@delorie.com>
Accept-Language: en-US
Content-Language: en-US
suggested_attachment_session_id: 02ffbbf0-2e38-6600-ae33-6874489f4e98
x-tmn: [ZYVbh5Nh3kJ5fv46T4/TWPSMxnVKUsXWm8Fd1z6xWx+tJZHtglxvTnOPLwnmX6PB]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4c61cf00-fdd3-45df-ca39-08d9e2eef959
x-ms-traffictypediagnostic: BYAPR14MB2742:EE_
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 YRaqA5qh32eFPbji+5wASQFkv1XjGyQEW8hHSlquSuDzEIylPzJnS7X+o24Iob+poXK58bubNaE3YNC2BEScQO5KPHWXxJFQOL36FHoRKApR18tAYCfDunXbjBq1vilkaY2UCfAQV8IY0KMbCw0dMTrI5TwW24H/0ReOpqy4Iea4i+8YwDTFUVRlVaMCNwSpJq8MIj1UP/Tg9mRHkwZOkub12FKBf0PEd6EBkuqQWv3arLb9IHAlvQWTu+FndLO5Hh6CEHOdEg+CntZtwbuKnNyGF/ZFg1zi1WF9APpl9QeSbeGKhR7ZMWxIdwUB+UtYLU4tSWKBF5p11i8fGqcOc8Enb5m7F9w6AzD1zR+2iNntfjQVH5JXDQZMeA4XhDr7BmerZBeCqBTkSFprs5siNPL8UdLwZh095bgiM+LYm82YzJoc5K9aK1Bxc96ko3PEhDhufTj3Mj8WEPP68zQULfXqGv+ZFJIeEQTq+wIf071jwLe0z+SvyTQdaHhkCyfvYzBiZJDe3lx/6nZ0mT0zmMd/bMtOGgSn0hdjUZKL5dBgQyL/CVUjjh1SDBi0qi/LRttWo6+DHgy9VplxL9yKKA==
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0:
 =?iso-8859-1?Q?j2z3YBX2hsx8idDSZ1IO29TFolX2BBKAEcmPC1PgGYdJvNgPc8W863eFRo?=
 =?iso-8859-1?Q?v4nwvIXXOwanHnIbH5xiPS7CE7sdUCbzNjuj3txChg09oVm/T9z/FP3x1y?=
 =?iso-8859-1?Q?h++vghL5yNy6KOJ4UTGsvpxsMe/PPK01wyjAJsjccfpW54E0qRq087f9DD?=
 =?iso-8859-1?Q?yHlOs/5DD84uz9vHy3FebFJG7uI5cdhaV4ItVSm500+j1nAp6ckCAXcdTf?=
 =?iso-8859-1?Q?ASZFpxtc6+IYfMixegDmMmkzL40TxEDjNnxvHKhAszelfOQYMtK0bsZ27v?=
 =?iso-8859-1?Q?urEAsoM8zJpJeY44ONx1qSc1f2Cx8J6hly+yUIi+oqv8O48UFuRCrJMUUb?=
 =?iso-8859-1?Q?TluGN7HnH2rdpdTJXQeVxjA2Fe/0eN6KlDFfvCJ4vh9mmSGV56KrV99ii6?=
 =?iso-8859-1?Q?lO4mS6MnGpUNnxtAi4ThFwxNz0B3eePwbRPZQVs6II1m282uV+LTQryNNB?=
 =?iso-8859-1?Q?ZbOgFp8dvyIPZYMJdiQBOx64NHucjz0AhZB5qjL5alwSK5L1YUzFyDMfUy?=
 =?iso-8859-1?Q?pc3RrmyjEuOgTzJEI54hch1tQO74XAi5DGWRrWnAMe1sAtyabfAbut0yJi?=
 =?iso-8859-1?Q?Uf7moEqmEX1L1TQfDiER+YWCtNeA6rxc10rYEqqZn8da3EGfN4afZdQuiP?=
 =?iso-8859-1?Q?YswweNLDy5XGuMXssdxykdiv66c9UCde0Sh/HL6ysCBgZphQAatea3I7F6?=
 =?iso-8859-1?Q?gA4wnieTvG8tXX8fCLw0+7gZ92JoqKI1nC4labo2FQK5IkuJxaRZ280AgU?=
 =?iso-8859-1?Q?d9LABp8w4van9yH8+0vL7oajcsCofQjliK8C7dC5GSTqiNY8c/gmQnHM3S?=
 =?iso-8859-1?Q?FA8tHjvFLJzbvDC0FjVOX1sFzej66ZIBvgReXrcKXS9TMyQHAfj/otJB/J?=
 =?iso-8859-1?Q?yL5V3FtjBfsVwLkHgZlDWhKK0n6WJwXzXpjPAGCQxtEeHnNJID5PRXG8O1?=
 =?iso-8859-1?Q?v/a7kRK9YTHZQe+eAjY2WRxOpGK49Ncvj4r11kKMgGZa4XhAGZ2omR0P2w?=
 =?iso-8859-1?Q?oCfPgSa4rxudlLhv0q4vrmLFuV+Rby7q/3xgqj?=
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
X-OriginatorOrg: sct-15-20-4755-11-msonline-outlook-cd57b.templateTenant
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MWHPR1401MB1951.namprd14.prod.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 4c61cf00-fdd3-45df-ca39-08d9e2eef959
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jan 2022 06:17:06.2359
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR14MB2742
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 20T6HCbx028920

Sorry I didn't see the reply.

> On what version of Windows is that?
>
> This is stack fault, not necessarily related to the command-line
> length.
>
> What does go32-v2 report there if run without arguments?
>
...
> Something is very wrong in the run environment: the SS segment has
> very small limit, ES is invalid...

C:\dos>bin\go32-v2.exe
go32/v2 version 2.0 built Oct 18 2015 09:41:08
Usage: go32 coff-image [args]
Rename this to go32.exe only if you need a go32 that can run v2 binaries as
 well as v1 binaries (old makefiles).  Put ahead of the old go32 in your PATH
 but do not delete your old go32 - leave it in the PATH after this one.
Set GO32_V2_DEBUG=y in the environment to get verbose output.

DPMI memory available: 602375 Kb
DPMI swap space available: 0 Kb

 > Is that under Windows 10 32 bit? 
 > GCC does not work in all recent builds of Win 10 32 bit. 

Yes exactly, "current" ("21H2", year 2021, second half).
Do you know when it stopped working?
Implied that 32bit Windows 7, 8, 8.1 and Win10 early releases all work?

Is it debuggable?
Any idea what changed?

Anyway..I've tried many environments/axes: FreeDOS, Hyper-V, DosBoxX, Qemu, Win98DOS, Win98..
Many don't work, but Win98 DOS under Hyper-V does work a lot or maybe completely.
Also, you know, you have released many versions of gcc and g++, and I have tried many.
Some are a bit failure prone, but some work.

I am not 100% sure of my code as well..I am context swapping in sigalarm as part of implementing threads.
It works an awful lot, but of course, maybe that is luck of timing or memory pressure (there is also a
garbage collector, working on very many systems..)


Thank you,
 - Jay