#364 config.sys command version versus callver (bug or feature?)

[Anonymous]

Hi,
while working on the new help I just noticed a thing where I am not sure if the behaviour is correct or not.
When I enter "version=6.22" in config.sys and boot up the command: "ver /r" reports this version. So far ok. But when I enter "callver 9.99" (max allowed value) callver confirms 9.99 but the command ver /r still shows 6.22.
The same happens if I boot up without a config.sys version entry (ver /r shows 7.10 then) - and it stays at 7.10 when I run callver. This may make sense when callver only is used for one single command, but callver help says: run one program (in a new shell using comspec) with a fake dos version number or globally (only in FreeDOS) modify the reported DOS version (callver 0.00 reverts).
So my question: Is the callver version used for all files although ver /r shows another number? Or does it simply forget to give the version number to ver?

Thx

Fritz / Willy

[E. C. Masloch]

Just tested this with my callver fork. The version number field actually lives in the PSP (Process Segment Prefix, DOS's idea of a process). The ways to change the number globally actually affects a field in the kernel data segment. This value is used as the default contents of the PSP field when a new process starts up. Thus if you run another FreeCOM instance like command you will see the 9.99 version number.