(Please note that putty works fine in conemu on Windows 10 Home for me)
In Windows 7 Enterprise none of the following work - all of them open putty in an external window.
putty.exe -load "veragld"
opens putty in a separate window.
putty.exe -new_console -load "veragld"
With Features->Inject ConEmuHk
enabled, this gives me an "injecting hooks" error, then opens putty in a separate window. With Inject ConEmuHk
disabled (but with Process '-new_console'...
enabled) conemu does not parse -new_console and I get a putty error. Ditto for -cur_console.
Any permutations of the above give me either the hook injection error or putty in a separate window. On Windows 10 Home it all "just works" with -new_console.
Could the corporate McAfee crapware be blocking somehow? Any suggestions?
ConEmu 170402 preview
Thanks!
Edit: @Maximus - I get this in the original conemu console after the hook injection error:
Process was not attached to console. Is it GUI?
Current directory:
C:\Users\me
Command to be executed:
"c:\Program Files (x86)\PuTTY\putty.exe" -load "veragld"
Press Ctrl+Break to stop waiting
Press Enter or Esc to close console, or wait...
Same results, though, whether I run it from the console or as a task.
Edit #2: > notepad -new_console
works just fine. Dunno why.