Article View: comp.lang.modula2
Article #794Re: ANSI.SYS Install Detection
From: Jon Guthrie
Date: Sat, 09 Jun 1990 18:12
Date: Sat, 09 Jun 1990 18:12
21 lines
1455 bytes
1455 bytes
>>> Well, we know the names for the ANSI emulators which are likely to show >>> up in CONFIG.SYS, so why can't they all be checked? >> Your suggestion would break: >> 4) Where the user has renamed his ?ansi.sys file for whatever reason > Not true. The name of the device driver is not necessarily the same as > the name in the header of the code, which is what one would be looking for. Well, that's true, but the name in the header of the ANSI.SYS code is "CON:" because it's the console driver. The question then becomes, how do you tell an ANSI-compatable CON driver from a non-ANSI CON driver. (Well, I'll admit that non-ANSI con drivers aren't that common, but they ARE possible.) ...You trust them with your fortunes, let them guard your lives -- uucp: uunet!m2xenix!puddle!226!70.2!Jon.Guthrie Internet: Jon.Guthrie@p2.f70.n226.z1.fidonet.org
Technical Details
Message-ID:
<5384.2673196D@puddle.fidonet.org>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!usc!snorkelwacker!mintaka!ogicse!zephyr.ens.tek.com!tektronix!nosun!qiclab!m2xenix!puddle!p2.f70.n226.z1.fidonet.org!Jon.GuthrieShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!usc!snorkelwacker!mintaka!ogicse!zephyr.ens.tek.com!tektronix!nosun!qiclab!m2xenix!puddle!p2.f70.n226.z1.fidonet.org!Jon.Guthrie From: Jon.Guthrie@p2.f70.n226.z1.fidonet.org (Jon Guthrie) Newsgroups: comp.lang.modula2 Subject: Re: ANSI.SYS Install Detection Message-ID: <5384.2673196D@puddle.fidonet.org> Date: 9 Jun 90 18:12:34 GMT Sender: ufgate@puddle.fidonet.org (newsout1.26) Organization: FidoNet node 1:226/70.2 - Programmer's Connec, Columbus OH Lines: 21