Re: [Freedos-devel] FreeCOM 0.84-pre5 prerelease

2018-08-21 Thread Rugxulo
Hi again, On Mon, Aug 20, 2018 at 12:25 PM Tom Ehlert wrote: > > 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*

Re: [Freedos-devel] FreeCOM 0.84-pre5 prerelease

2018-08-21 Thread Rugxulo
Hi, Tom, I know this was not a great bug report. In fact, I wasn't trying to be too specific, just mentioning that some random and confusing stuff was happening. I didn't have time to isolate it yet. It was just a warning that things weren't quite perfect yet. (But I appreciate your work, Bart.)

Re: [Freedos-devel] FreeCOM 0.84-pre5 prerelease

2018-08-21 Thread C. Masloch
On 2018-08-21 22:23 +0800, TK Chia wrote: > However, both the intr ( ) implementation in Open Watcom, and the intr ( > ) implementation in suppl/src/intr.asm used when compiling with > gcc-ia16, will _not_ try to load any flags --- including CF --- from > reg.x.flags, so int 0x21 basically gets

Re: [Freedos-devel] FreeCOM 0.84-pre5 prerelease

2018-08-21 Thread Bart Oldeman
Hi TK, > However, both the intr ( ) implementation in Open Watcom, and the intr ( > ) implementation in suppl/src/intr.asm used when compiling with > gcc-ia16, will _not_ try to load any flags --- including CF --- from > reg.x.flags, so int 0x21 basically gets called with CF in an undefined >

Re: [Freedos-devel] FreeCOM 0.84-pre5 prerelease

2018-08-21 Thread TK Chia
Hello all, Meanwhile, for some reason I am also getting this error when starting commandg.com under DOSBox (0.74-4.2 on Ubuntu):   [Out of memory loading STRINGS.]   Failed to load the strings resources into memory, the location   pointed to in %COMSPEC% seems to be invalid. Please specify

Re: [Freedos-devel] FreeCOM 0.84-pre5 prerelease

2018-08-21 Thread Tom Ehlert
Hi Bart, > 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