> Hi. I've done some optimizations for size to FreeCOM and I'd like
> people to test it to make sure that I didn't create any new problems.
> I've tested it myself and it seems to work well.
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/command/0.84pre/testing/
Hi Blair, I tested as well and it works badly :-(
MKDIR / MD, RMDIR / RD, CHDIR / CD and POPD are all broken. Maybe
because you try to use LFN functions. I tested in plain DOS without
LFN drivers. Please make sure that LFN functions are only
used when some LFN install test is okay for THAT drive. It
can happen that you have LFN support only on SOME but not ALL
drives so FreeCOM has to check for that.
Other problems:
MEMORY reports that "used" is bigger than "max" for history
VER still does not display the kernel version STRING on FreeDOS,
please read the CALLVER source code to see how that works:
if OEM is 0xfd then int 21.33ff returns pointer DX:AX...
VER also calls the kernel 0.0.36 - that should be "2036" or "36".
CHCP messages are a bit strange, why "(properly)"?
And: FreeCOM behaves as if I had pressed ^C when my VOLINFXL
accesses an empty cdrom drive. In other words, when it happens
in autoexec, FreeCOM asks if I want to abort autoexec, and when
it happens on the prompt, the next char typed after that is
dropped from the keyboard buffer. That's a really annoying bug,
certainly in autoexec processing.
Talking about 8086 compatibility: The 0.005% remaining 8086 users
should absolutely use CALL/S FreeCOM. The 99.995% of 286+ users
should use the XMS SWAP FreeCOM, WITH 286 optimizations.
Eric
PS: Did you manage to fix / add COPY ... + ... "append" mode?
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
