Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hafro!isgate!krafla!frisk
From: frisk@rhi.hi.is (Fridrik Skulason)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Checking for ANSI.SYS...
Message-ID: <1547@krafla.rhi.hi.is>
Date: 28 Feb 90 08:17:45 GMT
References: <AUSTIN.90Feb26194024@bucsf.bu.edu>
Reply-To: frisk@rhi.hi.is (Fridrik Skulason)
Organization: University of Iceland (RHI)
Lines: 25

In article <AUSTIN.90Feb26194024@bucsf.bu.edu> austin@bucsf.bu.edu (Austin H. Ziegler, III) writes:
>	A couple of days ago, I posted requests for methods to check for
>ANSI.SYS.  I have received many useful tips on how to send ANSI control
>sequences to check to see if ANSI.SYS or a variant was installed.
:
>However, if at all possible, I would
>prefer checking low memory so that there is no screen color.

	Step 1: Get the address of the first installed device driver
	        INT 21, function 52H. ES:[BX+22H] (in DOS 3.x) is the
		start of the NUL driver, which is always first.

	Step 2: Get the pointer to the next driver. If it is one of the
		original drivers (located at 70:x) quit - no ANSI found

	Step 3: Check the name of the driver - if it is "CON" then you have
		found ANSI.SYS or another replacement "CON" driver.  If not
		just go to step 2 :-)



-- 
Fridrik Skulason   University of Iceland     |     
Technical Editor Virus Bulletin (UK).        |
E-Mail: frisk@rhi.hi.is   Fax: 354-1-28801   |