Perhaps that is indeed simply an out of memory situation, as much of the
upper memory area is not usable when running JEMMEX under VMware
(segments dc00-efff are not usable)?
Also, is there any benefit of running FreeCOM SHELLHIGH with the XMSSWAP
build? I have 625K conventional available wit
Le mar., 18 févr. 2025 14:47:12 -0500 Bernd Böckmann via Freedos-devel a
écrit
> Does it work if you load FreeCOM via SHELL instead of SHELLHIGH?
Yes... not tested much, but Yes!
> If I modify fdconfig.sys to use 12=SHELL instead 12=SHELLHIGH for the
> first two menu options, Fre
Does it work if you load FreeCOM via SHELL instead of SHELLHIGH?
If I modify fdconfig.sys to use 12=SHELL instead 12=SHELLHIGH for the
first two menu options, FreeCOM also works with the JEMMEX NOEMS option.
Bernd
On 18.02.2025 20:42, Paul Dufresne via Freedos-devel wrote:
Le mar., 18 f
Le mar., 18 févr. 2025 14:31:04 -0500 Jim Hall via Freedos-devel a écrit
> I don't understand this code question, so I'll try to unwind it.
>
> 'malloc' allocates memory of size_t size, and returns a pointer to the
> allocated memory .. or NULL if it could not allocate the memory.
>
>
I don't understand this code question, so I'll try to unwind it.
'malloc' allocates memory of size_t size, and returns a pointer to the
allocated memory .. or NULL if it could not allocate the memory.
I didn't look at the shell/init.c code for what kind of variable
'cmdline' is, but I assume it's
Not evolving fast...
but I change FeeCOM shell/init.c to show cmdlen...
if((cmdline = malloc(cmdlen + 1)) == 0) {
printf("cmdlen=%d",cmdlen);
error_out_of_memory(); /* Cannot recover from this problem */
return E_NoMem;
}
And it now writes cmdlen=40 before the Out of memory e
