Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!hub.ucsb.edu!ucsbuxa!6600wise
From: 6600wise@ucsbuxa.ucsb.edu (Mike Schmitt)
Newsgroups: comp.windows.ms
Subject: Re: Orchid ProDesigner Plus 800x600 mode and W4W problem
Message-ID: <8327@hub.ucsb.edu>
Date: 19 Jan 91 03:52:28 GMT
References: <4495@mindlink.UUCP>
Sender: news@hub.ucsb.edu
Lines: 29


Several people have posted about a problem with getting W4W to
recognize screen fonts.  Here's what I discovered:

Windows recognizes the resolution of any device in two ways: how
SETUP defines and how the device itself defines it.  For example,
if you look in SETUP.INF in the SYSTEM directory, you'll see under
the [Display] section (or whatever it is) the resolution - for
example, "100,96,96" (standard VGA resolution) and "100,120,120"
(8514/a resolution).  Setup will install the fonts based on the
SETUP.INF description - e.g. if you change the standard VGA
driver to "100,120,120" and run Setup, you'll get 8514/a fonts.
Nice and big.

However, W4W relies on the resolution reported by the -device-, not
the SETUP.INF file.  Thus, if the device (meaning the driver)
reports "100,96,96", then W4W will recognize it as VGA resolution
and attempt to use VGA fonts.  However, since Setup -removes- the
VGA fonts when it installs the 8514/a fonts, W4W is unable to load
the font and you'll get the system font.

I discovered this while first playing around with an Orchid Pro-
Designer II.  W4W displayed nothing but the system font.  However,
a new set of drivers I just got from the Orchid BBS (1-415-683-0327)
corrected the problem; the 800x600 driver now operates at 8514/a
resolution, and looks good, too!  :-)

Mike
6600wise@ucsbuxa.ucsb.edu