You're on your own here, but this little Warp 3 hack gives me some of the nicest
parts of the Warp 4 desktop. All files are "as snagged" off testcase, and they
can be swapped into place in \OS2\DLL after renaming the previous version.

And rebooting, of course.

My particular configurations are all FP32. Non-AMD processors, one with a laptop 
SVGA and one with MGA display running 1280x1024x24bits.

DSPRES.DLL provides the Warp Sans and Warp Sans Bold screen fonts. These fonts can be
used everywhere you can manually change screen fonts, including Scheme Palettes, and
for the adventurous you can even change the System Default Font by editing OS2.INI
	Application: PM_SystemFonts
	Key: DefaultFont
	Value "9.WarpSans Bold."
As with any INI editing, save a copy of the previous version you can get to from the 
command line on a reboot, to swap back into place in case of trouble. It's hidden and
read-only, so you'll need to ATTRIB -R -H on it before copying it. 
 

PMMERGE.DLL provides Warp 4 window controls and scrollbars, including an automatic
Close button. The graphics are much sharper etched than the Warp 3 look.

PMCTLS.DLL provides some apps with the Warp 4 Settings Notebook look. This includes
Netscape and, for the first time, allows me to select WarpSansBold as my System Default
font without messing up the window geometry on Netscape's settings and other places. In
fact, the only place I find still messed up by choosing WarpSans Bold over System Pro-
portional is in the Color Palette adjustment panel in Galleria. I can still change the
colors with the sliders, but I lose the step adjustment provided by clicking under
or over the toggle.

Problems? Back 'em out. If you haven't done any of this before, you might want to add
them one at a time so you can isolate and see what they change.

Also included is a new BLDLEVEL.EXE which gives more information than the stock version.
It goes in \OS2, and lets you read the internal level of aware files by the command:
	BLDLEVEL PMMERGE.DLL
for instance.

Additional Note: The PMMERGE.DLL build is 9.28, and it works fine here. There is a
build 9.29 which appears to work just as well but which actually kills my FXPRINT
function, so if you're running Faxworks you probably want to avoid that one. Took me
quite a bit of hassle to figure out where that problem came from...

Buddy Donnelly
shagpage@concentric.net
