Path: utzoo!attcan!uunet!husc6!mailrus!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.windows.ms
Subject: Re: Windows 2.0x on the Tandy 2000?
Message-ID: <1086@cps3xx.UUCP>
Date: 15 Nov 88 14:45:51 GMT
References: <746@hemingway.WEITEK.COM>
Reply-To: kuan@frith.UUCP (Yik Pung Kuan {cpsvax spring })
Organization: Engineering, Michigan State University, E. Lansing
Lines: 43

Newsgroups: comp.windows.ms
Subject: Re: Windows 2.0x on the Tandy 2000?
Summary: 
Expires: 
References: <746@hemingway.WEITEK.COM>
Sender: 
Reply-To: kuan@cpsvax.UUCP (Yih-pyng Kuan)
Followup-To: 
Distribution: 
Organization: Michigan State University, Computer Science Department
Keywords: 

>From cps3xx!eecae!mailrus!uflorida!gatech!gitpyr!ccastgw Mon Nov 14 16:10:34 EST 1988
>Article 5 of comp.windows.ms:
>Path: cps3xx!eecae!mailrus!uflorida!gatech!gitpyr!ccastgw
>From: ccastgw@pyr.gatech.EDU (GREG WILLIAMS)
>Newsgroups: comp.windows.ms
>Subject: Windows and DrHalo III and other problems
>Message-ID: <6747@pyr.gatech.EDU>
>Date: 12 Nov 88 18:42:32 GMT
>Reply-To: ccastgw@pyr.gatech.edu.UUCP (GREG WILLIAMS)
>Organization: Georgia Institute of Technology, Atlanta
>Lines: 14

>I am running Windows 2.03, and I would like to know if it is possible to
>cut and paste into and/or out of DrHalo III.  Also, I've had some mouse
>cursor problems with Windows.  I run Windows, quit, run MS-Word, quit, and
>then start up Windows again.  At this point the arrow for the mouse is not
>drawn on the screen.  It is there because I can use it, but I have to use
>guesswork to figure out what I'm pointing to.  Any suggestions other than
>not quitting Windows and running MS-Word? (I'm not sure if this happens
>if I run Word from Windows.  I don't recall it happening, but I don't recall
>what I did yesterday either.)

-- 
>ccastgw@pyr.gatech.edu
>GREG WILLIAMS "Barbaric Penguin"
>Disclaimer: The usual stuff.                          


About the cursor not showing, I guess it's a bug of Windows.
You can remove the connector of the mouse and replug it again.
If this solve your problem, tell me.