Jason Hood 4e84582f02 Fix running directly via ansicon
A program run directly by `ansicon` should always be hooked, regardless
if it's GUI or excluded.  This was broken in v1.84 due to the DLL being
imported.
2018-08-23 17:26:52 +10:00
2010-11-15 21:51:38 +10:00
2018-08-23 17:02:47 +10:00
2018-08-23 17:26:52 +10:00
2018-08-23 17:02:47 +10:00
2011-03-03 17:23:45 +10:00
2017-11-29 11:42:47 +10:00
2018-05-09 11:37:34 +10:00
2018-05-11 22:14:50 +10:00
2018-05-11 21:52:02 +10:00
2017-12-30 11:13:03 +10:00
2018-05-09 11:37:34 +10:00
2017-12-23 22:04:44 +10:00
2018-08-23 17:26:52 +10:00
2017-12-30 11:13:03 +10:00
2018-08-23 16:54:42 +10:00

ANSICON Latest release

ANSICON provides ANSI escape sequences for Windows console programs. It provides much the same functionality as ANSI.SYS does for MS-DOS.

Requirements

  • 32-bit: Windows 2000 Professional and later (it won't work with NT or 9X).
  • 64-bit: AMD64 (it won't work with IA64).

How it Works

ANSICON injects a DLL into a process, hooking its functions.

Injection

One of three methods is used to inject the DLL.

  • LoadLibrary via CreateRemoteThread for a running process.

  • LdrLoadDll via CreateRemoteThread for a 64-bit .NET AnyCPU process.

  • Adding the DLL directly to the import table, otherwise.

Hooking

Hooking is achieved by modifying import addresses, or the return value of GetProcAddress.

Description
No description provided
Readme 522 KiB
v1.89 Latest
2025-01-21 16:37:28 +08:00
Languages
C 99.7%
Batchfile 0.3%