From: "Alexander Odinokov" <shura AT mapobank DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Detecting win95: the hard way
Date: Mon, 1 Mar 1999 18:13:56 +0300
Organization: Sovam Teleport public server
Lines: 16
Message-ID: <7beav6$l0a$1@news.sovam.com>
References: <8D53104ECD0CD211AF4000A0C9D60AE35C4BCB AT probe-2 DOT acclaim-euro DOT net>
NNTP-Posting-Host: h1.mapobank.com
X-Trace: news.sovam.com 920301350 21514 194.67.31.2 (1 Mar 1999 15:15:50 GMT)
X-Complaints-To: abuse AT sovam DOT com
NNTP-Posting-Date: 1 Mar 1999 15:15:50 GMT
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-Mimeole: Produced By Microsoft MimeOLE V4.72.3110.3
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


>I need a way to detect when a djgpp program (Allegro) is being run
>under win95.
------- skipped ----------
>Surely there must be _something_ that I can look for? Some obscure
>feature of the DPMI implementation, or some other interrupt service
>that works differently to on other platforms? Any ideas would be
>very much appreciated...


mem /c under Win95/98 lists modules WIN, vmm32,IFSHLP.

May be scanning of MCB's and detecting such modules is a right approach?
(not the easiest and bulletproof one)