Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!spencer!akm
From: akm@spencer.cs.uoregon.edu (Anant Kartik Mithal)
Newsgroups: comp.windows.ms
Subject: Re: Wanted: List of known Errors in Windows 3.0
Summary: mouse problem can be worked around
Keywords: secondary copy of windows
Message-ID: <1990Jul31.021044.12643@cs.uoregon.edu>
Date: 31 Jul 90 02:10:44 GMT
References: <90.206.21:43:07@ira.uka.de> <56172@microsoft.UUCP>
Sender: usenet@cs.uoregon.edu (Netnews Owner)
Organization: Department of Computer Science, University of Oregon
Lines: 24

In article <56172@microsoft.UUCP> bruceki@microsoft.UUCP (Bruce KING) writes:
>  With that said, the only bug that I know about on the user level of windows
>is the one that causes your mouse to go away when you start windows twice.
>  e.g. start windows, start a dos command prompt task, start windows from
>that dos command prompt.  Your cursor is fine, and everything works great.
>  Exit that copy of windows, exit the dos command prompt task (returning
>you to the first copy of windows you started) and lo and behold -- your
>mouse cursor is gone.  Keyboard commands still work, system runs great, 
>but no mouse until you exit and re-enter.  

Hm.... Well, I've been running a real mode copy of windows inside my
386 enhanced mode. I've made a .pif which sets it up to run in full
screen, give it lots of EMS, and it works like a charm.... except that
it crashes occaisonally. WHen it does that, I ALT-TAB back to the
first version and terminate it. Ugly, but it lets me run some win 2 specific
applications.

kartik


-----------------------------------------------------------------------------
Anant Kartik Mithal					akm@cs.uoregon.edu
Department of Computer Science				akm@oregon.BITNET
University of Oregon