Update READMEFRP-4264-gc79f13025

1 files changed, 4 insertions, 2 deletions

diff --git a/README.md b/README.md
index 035d1f411..9e7ffbbf8 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,8 @@
 ### Status
 
-Things may work for you, or may not.  Things may never work because of huge differences between Linux and Windows.  Or things may work in future, if you report the problem on [GitHub](https://github.com/rmyorston/busybox-w32) or [GitLab](https://gitlab.com/rmyorston/busybox-w32).  If you don't have an account on one of those you can email me: [rmy@pobox.com](mailto:rmy@pobox.com).
+Things may work for you, or may not.  Things may never work because of huge differences between Linux and Windows.  Or things may work in future, if you report the problem on [GitHub](https://github.com/rmyorston/busybox-w32) or [GitLab](https://gitlab.com/rmyorston/busybox-w32).  If you don't have an account on one of those or you'd prefer to communicate privately you can email [rmy@pobox.com](mailto:rmy@pobox.com).
+
+Additional information and downloads of precompiled binaries are available from [frippery.org](https://frippery.org/busybox).
 
 ### Building
 
@@ -33,5 +35,5 @@ Then just `make` or `make CROSS_COMPILE=""` on Windows.
  - 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.
  - 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.
  - 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` as you might expect.  On 64-bit systems the latter is for 64-bit binaries.
- - ANSI escape sequences are emulated by converting to the equivalent in the Windows console API.  Setting the environment variable `BB_SKIP_ANSI_EMULATION` will cause ANSI escapes to be passed to the console without emulation.  This may be useful for Windows consoles that support ANSI escapes (e.g. ConEmu).
+ - The system tries to detect the best way to handle ANSI escape sequences for the terminal being used.  If this doesn't work you can try setting the environment variable `BB_SKIP_ANSI_EMULATION=1` to force the use of literal ANSI escapes or `BB_SKIP_ANSI_EMULATION=0` to emulate them using the Windows console API.
  - It's possible to obtain pseudo-random numbers using `if=/dev/urandom` as the input file to `dd`.  The same emulation of `/dev/urandom` is used internally by the `shred` utility and to support https in `wget`.  Since the pseudo-random number generator isn't being seeded with sufficient entropy the randomness shouldn't be relied on for any serious use.