🚀 go-pugleaf

In article <Bz5Hx0.7FJ@csugrad.cs.vt.edu> ceharris@csugrad.cs.vt.edu (Carl Harris) writes:
>From: ceharris@csugrad.cs.vt.edu (Carl Harris)
>Subject: Re: Detecting ANSI.SYS (was: Re: DOS text attributes)
>Date: 12 Dec 92 14:36:35 GMT
>wizard@archtwr.tower.nullnet.fi (Mikko H{nninen) writes:
>> I know I can detect ANSI driver by comparing an interrupt's and the CON
>> device's segment addresses (I think). But is this reliable? Are there any
>> other programs aside from ANSI that act as the CON device?
>
>The standard method for detecting the presence of the ANSI driver is to
>send a DSR (Device Status Report) sequence to the console.  If the
>driver is present, it will respond with a CPR (Cursor Position Report) via
>standard input.

I don't know what it really does, but there is an int 21 (?) ANSI.SYS 
installation check.


          /\           | I didn't say this.      | "When there's no 
        /    \         | My supervisor would     |  more room in hell,
      /        \       | kill me if i did.       |  the dead will     
    /    (<>)    \     |_________________________|  walk the earth."
  /                \   |Gunnar Horrigmo          |
/____________________\ |gunnarh@sofus.dhhalden.no|