E. C. Masloch
E. C. Masloch
By the way I got the same FreeCOM error prompt on lDOS when the 21.4B00 or 21.4B80 call has both the environment in the parameter block and the init PSP's...
I guess I just don't see what it buys us to do things this way rather than passing the environment the normal way, at least as an option. If I...
Like I wrote, FreeCOM doesn't actually need `%COMSPEC%` if it gets its own executable pathname in its own environment block.
From my reply to the user's bug report: > Yes, it appears that DR-DOS / dcommand (what I call its own command.com) have a special handshake to pass the dconfig...
> Creating a new env from the config env by the kernel and passing it to command would be better then. Yes, and that's exactly what happens if you put...
I tried out booting lDOS flavour EDR-DOS in my more recent (2024) dosemu2, loading FreeCOM. (This is also an environment I use for lDOS testing.) It produced the error prompt...
I had to remember to put `DOS=HIGH,UMB` after loading the `umb.sys` device driver in dconfig.sys
Different questions this test turned up in https://github.com/SvarDOS/edrdos/issues/138
> https://hg.pushbx.org/ecm/edrdos/rev/fe37cc2e8824 fixes this by passing the dconfig environment to the shell. User who reported the bug that another shell (PC-DOS command.com) ignores the dconfig SET directives has replied to...
Might be related that EDR-DOS has only 3 SFT entries at DOSDATA:00CCh whereas earlier DR-DOS probably had 5 (like MS-DOS). This changed because of the FAT32 and FAT+ extensions to...