Hi, there is another issue with IF. This is not new to FreeCOM 0.85a and existed in previous versions.
An end user reported a problem with "the installer" basically getting stuck while creating new configuration files during installation and typing some stuff and pressing "enter" would cause it to move along. Even just running in normal mode, there are hundreds of possible scenarios that effect the installer in numerous ways by that point. Never encountering this myself, I could not replicate the issue. So, I was looking at that area of the code. Did some extra tests. Found a different bug in FreeCOM and patched the installer to avoid it.
MS-DOS:
C:>if "a" == "b" echo this | echo that
C:>
FreeCOM:
C:>if "a" == "b" echo this | echo that
that
C:>
At least this one is easy to explain and replicate.
Hi, there is another issue with IF. This is not new to FreeCOM 0.85a and existed in previous versions.
An end user reported a problem with "the installer" basically getting stuck while creating new configuration files during installation and typing some stuff and pressing "enter" would cause it to move along. Even just running in normal mode, there are hundreds of possible scenarios that effect the installer in numerous ways by that point. Never encountering this myself, I could not replicate the issue. So, I was looking at that area of the code. Did some extra tests. Found a different bug in FreeCOM and patched the installer to avoid it.
MS-DOS:
FreeCOM:
At least this one is easy to explain and replicate.
:-)