ash: don't convert path delimiters for certain environment variables

The SYSTEMROOT and COMSPEC environment variables are known to
cause problems for Windows applications if they contain forward
slashes rather than backslashes.  So don't convert them, even
if the -X flag isn't present.

1 files changed, 1 insertions, 1 deletions

diff --git a/README.md b/README.md
index 69c991ae9..d9988c45e 100644
--- a/README.md
+++ b/README.md
@@ -18,5 +18,5 @@ Then just `make`.
  - Don't do wild things with Windows drive or UNC notation.
  - Wildcard expansion is disabled by default, though it can be turned on at compile time.  This only affects command line arguments to the binary:  the BusyBox shell has full support for wildcards.
  - Handling of users, groups and permissions is totally bogus.  The system only admits to knowing about the current user and always returns the same hardcoded uid, gid and permission values.
- - Windows XP and Windows Server 2003 sometimes have trouble with forward slashes in environment variables.  The -X shell option (which must be the first argument) prevents busybox-w32 from changing backslashes to forward slashes.
+ - Some crufty old Windows code (Windows XP, cmd.exe) doesn't like forward slashes in environment variables.  The -X shell option (which must be the first argument) prevents busybox-w32 from changing backslashes to forward slashes.  If Windows programs don't run from the shell it's worth trying it.
  - Currently only 32-bit builds of BusyBox work.  If you want to install 32-bit BusyBox in a system directory on a 64-bit version of Windows you should put it in `C:\Windows\SysWOW64`, not `C:\Windows\System32`.  On 64-bit systems the latter is for 64-bit binaries.