ANSI Bomb

ANSI.SYS is a device driver in the DOS family of operating systems that provides extra console functions through ANSI escape sequences. It is partially based upon a subset of the text terminal control standard proposed by the ANSI X3L2 Technical Committee on Codes and Character Sets (the "X3 Committee").

As it was not installed by default, and was notoriously slow, little software took advantage of it and instead resorted to directly manipulating the IBM PC hardware. A number of third-party alternatives that ran at reasonable speed were created, such as , and to attempt to change this.

Usage

To use under DOS, a line is added to the (or under Windows NT based versions of Windows) file that reads:

: DEVICE=''drive:''\''path''\ANSI.SYS ''options''

where ''drive:'' and ''path'' are the drive letter and path to the directory in which the file is found, and ''options'' can be a number of optional switches to control the behaviour. may also be loaded into upper memory via /.

* use extended keyboard BIOS functions ( INT 16h) rather than standard ones This made the F11 and F12 keys work.
* force number of lines
* adjust line scrolling to support screen readers
* or set screensize
* support redefinition of extended key codes independent of standard codes

Functionality

Using this driver, programs that write to the standard output can write escape sequences to make use of the 16 text foreground colors and 8 background colors available in VGA-compatible text mode, make text blink, change the location of the cursor on the screen, and blank the screen. They could also change the video mode from standard 80×25 text mode to a number of different graphics modes (for example, 320×200 graphics mode with text drawn as pixels, though ANSI.SYS is not able to turn individual pixels on and off).

The standard is very slow as it maps escape sequences to BIOS calls (which managed to be designed so that ''two'' calls were needed to put a character on the screen and move the cursor right). Several companies made third-party replacements such as that interface directly with the video memory, in a similar way to most DOS programs that have a full-screen user interface.

checked if this driver was in use, and changed the command to use an escape sequence instead of a BIOS call.

Keyboard remapping

An interesting (mis)feature of is the ability to remap any key on the keyboard in order to perform shortcuts or macros for complex instructions. Using special escape sequences, the user can define any keystroke that has a character-code mapping to simulate an arbitrary sequence of such keystrokes. This was used to create simple trojans out of text files laced with nefarious keyboard remaps, known as "ANSI bombs". A number of products were released to protect users against this:
* Many replacements for support a command line switch to disable the key remapping feature, f.e. the option (Secure) in Datalight ROM-DOS or NANSI.SYS of FreeDOS. Other ANSI drivers like ANSIPLUS can be configured to disable the redefinition of keys as well.
* Some replacements were deliberately designed never to support the keyboard remapping functions.
* PKWARE produced a terminate-and-stay-resident program, PKSFANSI (PK Safe ANSI), which filters out keyboard remapping escape codes as they are written to the standard output. This has the advantage that the user can load some useful remappings from a text file and then run PKSFANSI to prevent further, possibly malicious remappings.

Occurrence

appeared in MS-DOS 2.0, the first version of the operating system supporting device drivers. It was supported by all following versions of MS-DOS. It is also present in many non-Microsoft DOS systems, e.g. IBM PC DOS and DR-DOS.

was required to run some software that used its cursor and color control functions. It could also be used to enable elaborate color codes in the prompt. These uses were overshadowed by the use of in BBSes; ANSI escape sequences were used to enable BBSes to send text graphics more elaborate than ASCII art, and to control the cursor in ways that were used in a number of online games and similar features.

Most versions of Windows did not support ANSI escape codes in any useful way (it could be used by MSDOS emulation in some versions). In Windows 10 support for similar escape sequences was built into the Win32 console (the text terminal window), but must be activated using the Windows API function by setting the flag.

Features

CSI (Control Sequence Introducer) is a placeholder for the common two-byte escape lead-in sequence "" (that is, ). The ANSI standard also defines an alternative single-byte CSI code , which is not supported by ANSI.SYS (this code instead drew a cent sign from CP437).

Standard DOS drivers support only the following sub-set of ANSI escape sequences:

There are also some escape sequences specific to the implementation of . They are not generally supported by ANSI consoles in other operating systems.

In some DOS implementations, video modes above 7 are not documented. Under Multiuser DOS, the only valid argument in conjunction with PCTERM is 7.

See also

* ANSI escape sequence

Notes

References

External links

*
* {{cite web , url=http://www.ansilove.org , title=A set of tools for converting ANSi/BiN/ADF/iDF/TUNDRA/XBiN files into PNG images , author-first=Frederic , author-last=Cambus , date=2017-04-19 , access-date=2017-09-11 , url-status=live , archive-url=https://web.archive.org/web/20170911084034/https://www.ansilove.org/ , archive-date=2017-09-11

DOS drivers
DOS files
DOS technology