Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!ashing
From: ashing@milton.u.washington.edu (Al Shing)
Newsgroups: comp.windows.ms
Subject: Re: Wanted: List of known Errors in Windows 3.0
Message-ID: <5715@milton.u.washington.edu>
Date: 30 Jul 90 21:53:21 GMT
References: <90.206.21:43:07@ira.uka.de> <56172@microsoft.UUCP>
Organization: University of Washington, Seattle
Lines: 27

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.  
>  bruceki@microsoft

I have recently had problems with losing my mouse when I leave Win 3 after
a days usage, and enter PC Tools PC Backup to backup my system.  The mouse
cursor appears upon startup, but does not move with the mouse.  The keyboard
commands still work fine, and I am able to do my backups, but without benefit
of the (Logitech) mouse.

If I go back into Windows after my backups, the mouse cursor reappears, and
the mouse starts functioning again, even if I did not perform an intervening
boot to reload the mouse driver.

I have oftened wondered about the feasibility of bringing up Windows under
Windows, but haven't tried it, personally.  I doubt that MS would consider
it to be a supported environment.

Al Shing