From: "A. Wik (awik32@gmail.com) [via djgpp@delorie.com]" <djgpp@delorie.com> Date: Sun, 28 Jan 2024 17:05:17 +0000
On Sun, 28 Jan 2024 at 16:27, Eli Zaretskii (eliz@gnu.org) [via djgpp@delorie.com] <djgpp@delorie.com> wrote:
I increased the DPMI and XMS memory in the COMMAND .PIF file to 32768
KB, and now I don't get the error message
C:\proj\debug\tmp>gcc linecont.c
[no error message]
But the compiler fails to produce any output files:
What does go32-v2 report _after_ you increased the memory?
C:\proj\debug\tmp>go32-v2
go32/v2 version 2.0 built Oct 18 2015 09:41:08
...
DPMI memory available: 32209 Kb
DPMI swap space available: 0 Kb
From: "A. Wik (awik32@gmail.com) [via djgpp@delorie.com]" <djgpp@delorie.com> Date: Sun, 28 Jan 2024 19:21:05 +0000
I figured it out. I had created a "custom" version of the MS-DOS
prompt PIF, and I had set the DPMI memory explicitly. I tried
starting "command" with the "Run..." option from the Start menu, and I
found that gcc would work just fine. It turns out that it's best to
leave the DPMI memory setting as "Auto". To illustrate:
C:\proj\debug>go32-v2
go32/v2 version 2.0 built Oct 18 2015 09:41:08
Usage: go32 coff-image [args]
...
DPMI memory available: 226725 Kb
DPMI swap space available: 31959 Kb
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 484 |
Nodes: | 16 (2 / 14) |
Uptime: | 52:32:56 |
Calls: | 9,628 |
Calls today: | 1 |
Files: | 13,695 |
Messages: | 6,159,620 |
Posted today: | 1 |