🚀 go-pugleaf

   Well, I've installed Windows 3.1.  Everything looked OK-- I had
none of the problems others seem to have had with startup, mouse
cursors, display, etc.  However, my big test was to see if my own
application-under-development ran.  So, I started up QuickC/Win,
and started my application.  It looked good, until it tried to put
up my OpenFile... dialog box, at which point it UAE'd (an old-style
UAE, i.e. without the extra info that 3.1 is supposed to provide).
On a whim, I tried running the same application outside the QuickC
environment, and it worked!  I was able to get to my dialog box,
open files, display graphics, etc., from within my program.  Also,
while trying to trace down exactly where the problem is, I reliably
hang the machine while tracing the dialog-handling function.  After
doing the Windows-intercepted ctrl-alt-del, the culprit is pegged
as being WINDBG.  One final note on this problem is that other
dialogs (e.g. the ubiquitous About... entry) in my program work
fine.
   I tried doing most of the suggested things like rebooting with
"vanilla" autoexec and config files, but the symptoms remain the same.
My last attempt, to be made this weekend, will be to totally remove
Win3.1, restore 3.0, and do a custom reinstall to a different directory.
  The only other anomaly I've noticed so far is that when I run with
the new 3.1-specific Tseng ET4000  256-color drivers, I get a UAE
from GDI.EXE upon exiting my application.  This doesn't show up when
I install the MS-supplied SVGA 16-color driver, so I suspect that
problem is display-driver specific.
   Meanwhile, if anybody else had has seen and solved problems like
this already, or even just wants to commiserate, I'd like to hear about
it.
--
Joel Plutchak, Research Programmer/Analyst
plutchak@porter.geo.brown.edu -or- PGGIPL::PLUTCHAK (VMS: Just say NO!)
Favorite sci.geo.meteorology quote: "Joel dissipated over China on 7 September."