Jason Hood
Jason Hood
The problem within Bash is described [here](https://github.com/adoxa/ansicon/issues/82#issuecomment-126547360). That's the intention with regards Explorer. IIRC it did work with the Run entry, but I haven't tried through Startup. Your batch can...
`ansicon -p` is how the DLL gets injected into the parent CMD in the first place, so if that's no longer working, that would explain why it stopped working after...
> 1) uncomment "BITS = 64" in makefile.vc (otherwise it builds the 32bit app) `nmake BITS=64 makefile.vc` should do it. Is there no `%CPU%` or `%PLATFORM%` variable? 2010 has `%Platform%`,...
Can you try with [1.70](https://onedrive.live.com/redir?resid=D18DE9C2F9D17ED!127&authkey=!ADZkdErqDeWb2cg&ithint=file%2czip)?
[Here's](https://onedrive.live.com/redir?resid=D18DE9C2F9D17ED!127&authkey=!ADZkdErqDeWb2cg&ithint=file%2c.zip) the progress I made on 1.70 before getting sidetracked (and it'll be a bit longer before I get back to it). It uses yet another method of injection, which...
Are you using 32- or 64-bit Ruby (I'd rather only download one)?
Well, this is annoying - both 1.66 and 1.70 work fine for me. ``` T:\>ver Microsoft Windows [Version 6.1.7601] T:\>ansicon --version ANSICON (64-bit) version 1.66 (21 September, 2013). T:\>ruby --version...
> No log file is being generated. I find that hard to believe, since the log is created as soon as `-l` is seen and ANSICON has to at least...
The log is created before the process, so if there's no log, ANSICON is not creating the process, or you're not instructing ANSICON to create the log (it's `dash ell...
Sounds like a good reason not to install to `%windir%\system32`, since, as you've inadvertently discovered, Windows automatically redirects 32-bit programs referencing it to `%windir%\syswow64`.