Upon further investigation a mere allocation of
orderArray = MK_SEG_PTR(void, DOSalloc(0x1000,2));
before the main dir code and deallocating it at the end without even
using orderArray for sorting already corrupts things.
I suspect that the memory block used for the message strings is
getting in th
This change seems to be the cause (which was motivated by the fact
that otherwise with large memory model regular malloc's would fail as
they bumped into the allocated memory block)
--- a/cmd/dir.c
+++ b/cmd/dir.c
@@ -1010,7 +1010,8 @@ static int dir_list(int pathlen
error_out_of_memory();
more experiments.
METADOS is a very advanced, very spaghetti BATCH project,
which in the end connects you with TCP, downloads components
(MEM.EXE below) from the internet and more interesting stuff.
unfortunately, *very* spaghetti.
anyway, FreeCOM 0.84-pre5 prerelease doesn't behave a) as expecte
Hi everybody,
>> Thanks for your efforts, of course, but ... it's still got some
>> bugs. The Watcom build runs faster (oddly),
> could you please enlighten the rest of the universe in what way you
> determined that 'The Watcom build runs faster'
ok, I enlightened myself, downloaded
https://
