Bernd Böckmann
Bernd Böckmann
Bonus exercise: System crashes if "exit" is entered at the FreeCOM (process 0) command prompt, probably because the shell terminates, which it should not.
For this to work FreeCOM had to be modified to accept the config environment stored containing COMSPEC.
> When you wrote "had to be modified" Replace it by "has to" :) SvarCOM has already implemented SOME processing of the kernel initial environment: https://github.com/SvarDOS/core/blob/2c639bddbe07560603d611f56a409a98abe586a3/svarcom/trunk/command.c#L127 From this initial environment,...
See also: https://github.com/SvarDOS/edrdos/issues/88 (initial environment relocated to segment 0x60 to reduce chances that it gets overwritten too soon).
> If I understand correctly, the special config environment doesn't contain the executable pathname that FreeCOM wants to locate itself. The config environment should include COMSPEC with absolute path as...
But the config environment should be processed to upper-case the variable names if it is reused by FreeCOM, I guess.
I think the current config environment should not be changed by appending the executable file name, as the EDR COMMAND.COM expects the F5 / F8 flags after the 0x1A byte....
Well, appending the program file name to the config env might indeed work, as 0x1a character is at offset 0xfc. So there should be plenty of space for appending the...
Ok, nice. I think I got it :)
Great! I will check if svarcom still works and then import the change.