Jason Hood

I did actually make a start on passing through SGR sequences, but got sidetracked and never went back to it. Bit busy atm, but I'll get there...

> @adoxa yes, but is sequences only one way to get colors in cmd, or I've missed something? I'm not sure what you're asking. If you want, e.g. cmd's `echo`...

``` A:\>ver Microsoft Windows [Version 10.0.19041.388] A:\>echo %ANSICON_VER% 189 A:\>curl --version curl 7.79.1 (x86_64-pc-win32) libcurl/7.79.1 OpenSSL/3.0.0 (Schannel) zlib/1.2.11 brotli/1.0.9 zstd/1.5.0 libidn2/2.3.2 libssh2/1.10.0 nghttp2/1.45.1 libgsasl/1.10.0 Release-Date: 2021-09-22 Protocols: dict file ftp...

The crash dumps don't have the ANSICON DLL, so are they not even loading? Please do `echo %ANSICON_VER%` to confirm ANSICON is loaded into `cmd`. Then do `ansicon -l2 path\to\curl`...

Alternatively, don't use ANSICON at all, try [termon](https://github.com/adoxa/ansicon/issues/115#issuecomment-501562132) or Windows Terminal.

Those timestamps aren't from mine, so have you built this yourself, got it from someone else, or ignored timestamps when extracting? Did you install it to `%windir%\system32` on a 64-bit...

Works fine for me (10 v2004 Build 19041.388). Try `cmd /d` in the run dialog and if that works, `reg query "HKCU\Software\Microsoft\Command Processor" /v AutoRun`. If there's no value, or...

If there's no `ansicon` present in `AutoRun` then ANSICON should not be active - one more test is `set ans`, which should show nothing if ANSICON is not installed and...

I'll revisit it after 1.84, which I hope to release in the next week or so.

Well, if it helps... There's no trojan, false positive, just ignore it. I didn't want to submit 1.83 for whitelisting when I thought 1.84 was imminent, but I got sidetracked....