Path: utzoo!attcan!uunet!samsung!emory!mephisto!mcnc!ecsgate!ecsvax!unbent
From: unbent@uncecs.edu (Jay F. Rosenberg)
Newsgroups: comp.windows.ms
Subject: Win3 lies to non-Windows apps about video
Keywords: Win3 Windows video EGA CGA problem
Message-ID: <1990Sep17.121104.18489@uncecs.edu>
Date: 17 Sep 90 12:11:04 GMT
Organization: UNC Chapel Hill
Lines: 33


	The weekend brought time for more diagnostic explorations.  Herewith
the amazing discoveries:

	My video card is a Paradise Autoswitch EGA 480.  EGA is what I told
Win3 during setup, and *when running in standard mode*, Win3 understands
that perfectly well.  It comes up in EGA resolution; Windows apps run in EGA
resolution, and, crucially, NON-Windows apps run in EGA resolution.  Null
problemo, as Alf would say.

	BUT, *when running in 386 enhanced mode*, Win3 lies to non-Windows
apps about the available video.  It still comes up in EGA resolution, and so
do all the accessories and other Windows apps.  But NON-windows apps are
being told that the available video is CGA, not EGA!  That, for example, is
what Norton (4.5) says I've got in the system when I query it from inside
Win3 in 386 enhanced mode.  (In standard mode, Norton gets it right!)
That's the mode in which First Publisher comes up when invoked from Win3 in
386 enhanced mode.  (In standard mode, First Publisher comes up in EGA.)
And *that's* why Word 5.0 won't acknowledge its (EGA!) video driver as valid
when run from Win3 in 386 enhanced mode, although the same video driver
works fine under standard mode.

	So the question now is:  How do I get Win3 running in 386 enhanced
mode to tell non-Windows apps *what it itself knows perfectly well* -- that
the available video is EGA, not CGA!

	Thanks in advance.	-- Jay Rosenberg   

-- 

JAY ROSENBERG  Dept. of Philosophy  CB# 3125  UNC  Chapel Hill, NC  27599
...{decvax,akgua}!mcnc!ecsvax!unbent         ...tucc!tuccvm!ecsvax!unbent  
unbent@ecsvax.UUCP      unbent@ecsvax.uncecs.edu     unbent@ecsvax.BITNET