|
|
Microsoft Windows NT Build 511 (DDK SDK) 11-01-1993
Two things need to happen to properly run a 120 DPI display driver:
1. You need to build a 120 DPI driver with the 120 DPI resources
found in this directory. In other words, the ulLogicalPixelsX
and ulLogicalPixelsY of the GDIINFO structure returned by DrvEnablePDEV
must both be set to 120. In addition, the driver's .RC file should
reference the 120dpi resources (bitmaps, icons, and cursors) found in
this directory.
2. You need to install the 120 DPI fonts. There are two REGINI scripts
in this directory, 120dpi.ini and 96dpi.ini. They convert the installed
fonts to 120dpi and 96dpi, respectively. They are invoked as:
REGINI <ini-file name>
For example, to convert your system to 120 dpi fonts, type on the
TARGET machine:
REGINI 120dpi.ini
What the 120dpi.ini script does is replace the 96 dpi bitmap fonts
(*e.fon, vga*.fon) with the 120 dpi bitmap fonts (*f.fon, 8514*.fon).
The 96dpi.ini script does the same thing, but in the opposite direction.
It may be necessary to copy these fonts into the font directory.
---------------------------------------------------------------------------
96 dpi fonts:
vgasys.fon system font
vgafix.fon system fixed font
vgaoem.fon default OEM (console) font
sserife.fon MS Sans Serif bitmap font
coure.fon Courier bitmap font
serife.fon MS Serif bitmap font
symbole.fon Symbol font
smalle.fon Small font
---------------------------------------------------------------------------
120 dpi fonts:
8514sys.fon system font
8514fix.fon system fixed font
8514oem.fon default OEM (console) font
sseriff.fon MS Sans Serif bitmap font
courf.fon Courier bitmap font
seriff.fon MS Serif bitmap font
symbolf.fon Symbol font
smallf.fon Small font
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.