Interesting bug. I wonder if this is because of FreeCOM command line parsing? For example, "dir.exe" would appear to be a request to run an external command called "dir.exe". That one seems obvious. I don't know that I'd call that one a FreeCOM bug.
I wonder if "dir .exe" (space between "dir" command and ".exe" extension) is similarly interpreted as a request to run an external command called "dir .exe" (with space) or even "dir.exe" (no space).
Not sure if that second one is a bug or not. Will need to reverify on FreeDOS 1.2 RC1. Similar example would be to use another internal command name, such as ECHO or REM.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is an incompatibility bug. I agree it is because command line parsing. dir.exe is not an external command, the same as cd.. (no space between cd and ..) is not an external command. Original MS DOS just make possible to type less.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh seems I can't use the asterisk symbol. Let's use X as a replacement.
In MS-Dos you can view all (for example) executables by typing "dir.exe", "dir .exe"or "dir X.exe". In FreeDOS only "dir X.exe" works.
Interesting bug. I wonder if this is because of FreeCOM command line parsing? For example, "dir.exe" would appear to be a request to run an external command called "dir.exe". That one seems obvious. I don't know that I'd call that one a FreeCOM bug.
I wonder if "dir .exe" (space between "dir" command and ".exe" extension) is similarly interpreted as a request to run an external command called "dir .exe" (with space) or even "dir.exe" (no space).
Not sure if that second one is a bug or not. Will need to reverify on FreeDOS 1.2 RC1. Similar example would be to use another internal command name, such as ECHO or REM.
It is an incompatibility bug. I agree it is because command line parsing. dir.exe is not an external command, the same as cd.. (no space between cd and ..) is not an external command. Original MS DOS just make possible to type less.
edited title to be more accurate/searchable
I hope this will be fixed in FreeCOM 0.84 before FreeDOS 1.3 Final is released.
If it is NOT fixed in FreeDOS 1.3, that means that some old batch files may NOT work properly.
Then, I may be compelled to switch back to MS-DOS.