Path: utzoo!censor!geac!jtsv16!uunet!tut.cis.ohio-state.edu!ucbvax!pasteur!helios.ee.lbl.gov!nosc!logicon.arpa!trantor.harris-atd.com!trantor!dsampson
From: dsampson@x102a.harris-atd.com (sampson david 58163)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Word For Windows
Message-ID: 
Date: 8 Aug 89 12:34:10 GMT
References: <2106@csuna.csun.edu>  <3567@mentor.cc.purdue.edu>
Distribution: usa
Organization: Harris Gov't Aerospace Systems Division
Lines: 33
In-reply-to: tmp@mentor.cc.purdue.edu's message of 4 Aug 89 20:55:31 GMT
Posting-Front-End: GNU Emacs 18.47.1 of Thu Oct 15 1987 on x102a (hcx/ux)

My original comment about the bug I found in Word 5.0:

>The Word upgrade from 4.0 to 5.0 ...
>
>There are bugs though.......
>
>I have a keyboard with stand alone cursor keys.  If you hold down the
>down arrow key (or any other arrow key) until you hear the first
>click, then release it, the cursor starts "free running" through the
>document.  

Tom Putnam (tmp@mentor.cc.purdue.edu) adds:

#I experienced this same phenomenon under Word 4.0 and spent much time
#trying to find out what was causing it.  I finally found, quite by
#accident, that removing Sidekick removed the problem.


Good point Tom.   TSR's are usually a main point of contention.
However, the only TSR I run is CED.COM (the command line editor).  To
date, this TSR has never conflicted with anything I have run.

As an experiemnt, I removed ced.com from my autoexec.bat file and
re-booted.  I then loaded Word and tried it again.  With no TSR
present, the cursor goes into the free running mode.  Must be a bug
for sure.
--



David Sampson                                         Harris Corporation
dsampson@x102a.harris-atd.com                   Gov't Aerospace Systems Divison
uunet!x102a!dsampson                                    (407) 729-7068