>> But IIRC, the common way to check for the presence of an ANSI >> device driver was to check via an INT 2Fh (multiplexer) call (don't >> recall the exact call value (AX/AH)).
... > I remember when Eric Auer added it to NANSI, so it should support > it: > > * https://docs.huihoo.com/help-pc/int-int_2f_0.html > > INT 2F,0 - DOS Multiplex Interrupt - Get Installed State > AL = 00 > AH = 1A for ANSI.SYS (DOS 4.0+) > on return: > AL = 00 not installed, ok to install > = 01 not installed, do NOT install > = FF installed To reliably test for ANSI.SYS, you should not rely on INT 2Fh. There are probably at least a dozen ANSI clones oput there, and only a few of them (maybe only MS ANSI.SYS and NANSI) will support INT 2Fh. PTS-DOS, for example, has an ANSI driver built into the kernel so you shouldn't even need to install a stand-alone ANSI driver. The only reliable way to test for an ANSI driver is to actually try to write something to the screen and see if what happens on the screen is something ANSI would do. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
