This file lists bugs that may impede your use of PMView. Bugs in PMView are
listed first, followed by known bugs in OS/2.

PMVIEW BUGS:
There are no known bugs in PMView 0.86. Please help us find some. We
welcome any and all bug reports at sthiagar@nickel.ucs.indiana.edu.

                         *      *      *

OS/2 BUGS:
Everything from here on is a bug in OS/2 and *not* in PMView.

PROBLEMS WITH SPECIFIC OS/2 VERSIONS:
For best results, you should run PMView under the generally available
version of OS/2 2.1. This version fixes many screen driver bugs in
OS/2. The recently released second Service Pack for OS/2 2.0 is also
reputed to fix these bugs, but we have not tried it.

We do not recommend that you run PMView under other OS/2 variants.
While you cannot "damage" your system, the screen driver bugs may give
disappointing performance.

GENERAL OS/2 BUGS:
As of this writing, OS/2 does *not* recover very gracefully if you run
out of swap space. Running *many* copies of PMView while viewing big
images may get you in trouble. (Remember, a 1024x768x256 image
represents 768K of pixel data alone!) Also, turning on color counting
(on the "_Color" page of the options notebook) can increase your RAM
requirements significantly. (Even an "optimal" 24-bit color counting
algorithm can take up to 2MB RAM if it is fed an image with the maximum
number of colors.)

There's also a "feature" of OS/2's WPS that you might want to know
about. Suppose you associate *.GIF files with PMView. This means that
you'll be able to double-click on a *.GIF file (when you have a drives
object open, for instance) and PMView will start up and display that
file. The "feature" is this: If you start up PMView this way and then
do a _File _Delete, OS/2 will kill PMView shortly after the file gets
deleted. Peter is thinking of a workaround, but I don't think that
"fixing" this is a high priority. Please let me know if you disagree.

OS/2 SCREEN DRIVER BUGS:
If you run under a screen driver that does not support Palette Manager,
you won't get very good results. As of this writing, the 32-bit
256-color drivers for the XGA, ET4000, Trident, and ThinkPad 700C are
known to support Palette Manager. (These drivers are available in the
Service Pack or OS/2 2.1.) I am told that OS/2 2.1 includes Palette
Manager support for several other adapters, including the 8514/a.

If you are running the release version of OS/2 2.1, you can stop
reading: ALL of the bugs listed below have been fixed. (Way to go,
IBM!) If you are still running OS/2 2.0 + SP, or an OS/2 2.1 beta
version, keep reading. The surest fix for these bugs is to acquire the
release version of OS/2 2.1. A lower-cost alternative might be to
acquire the  second Service Pack for OS/2 2.0, but we have not tested
this ourselves.

THE UNIVERSAL BUG:
When you drop a menu down over a window that's using Palette Manager,
the obscured part of the window will later be redrawn with the wrong
colors. This is (partly) why we have the F5 function. 

THE FATAL ET4000 / TRIDENT SERVICE PACK BUG:
If you're using the Service Pack, and if you run a program (*any*
program, not just PMView) that changes the screen palette and then try
to move an icon on the OS/2 desktop, YOUR COMPUTER WILL HANG!!! Be
*very* careful if you want to try this out. This bug occurs on ET4000
systems using the Service Pack screen driver. It also occurs on Trident
systems using the Service Pack and the screen driver that was
distributed shortly afterwards. This bug is fixed in the December 2.1
beta and, of course, in the release version of OS/2 2.1.

This bug does *not* occur on the XGA, nor on the ThinkPad 700C.

ET4000 / TRIDENT / THINKPAD SCALING BUGS:
The screen drivers for the ET4000, Trident 8900C, and ThinkPad do not
scale paletted bitmaps correctly. This is why we have our own scaling
routines built into PMView. You can disable these routines (by
selecting _View S_ettings, going to the Spe_cial page, and unchecking
the "Use PMView's _own scaling routines") to see the bugs firsthand.

Raja Thiagarajan / BUGS.DOC / 10-26-93 release