X-Spam-Check-By: sourceware.org
Date: Fri, 3 Feb 2006 16:29:07 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: David Picton <djpicton AT gmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: strange cygstart bug with current Cygwin versions
In-Reply-To: <2fc802c00602031305p7574f255g5e67e44cd8b754e@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.0602031614330.3425@access1.cims.nyu.edu>
References: <2fc802c00602031305p7574f255g5e67e44cd8b754e AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Fri, 3 Feb 2006, David Picton wrote:

> I have encountered a strange bug when starting Microsoft Word when it is
> started by the cygstart command, e.g. "cygstart Index.doc", with the
> current version of the Cygwin dll.
>
> The symptoms are as follows:
>
> 1.  Word appears to start normally, and the file can be edited on screen.
>
> 2.  However, when Word should be autosaving, a message appears to the
> effect that the auto-recovery save has been postponed.
>
> 3.  Attempting to save the file gets no response.  The only way to close
> the window is to exit without saving!
>
> To attempt to reproduce the bug, you need to open a Word document using
> cygstart, change the document, then try to save it.
>
> I have seen this bug on two of the three computers which I use - all
> with the latest release of Cygwin.  Reverting to the previous version
> doesn't help, but the bug goes away if I restore a pre-January version
> of Cygwin.  It also goes away if I invoke the Word binary (winword.exe)
> directly from the command line or a shell script.

Sounds like an instance of
<http://cygwin.com/ml/cygwin/2005-05/msg00587.html>...  Does it work if
you "cygstart cmd" and then start word from that cmd shell?  If you get
the same symptoms, please run "set" in that cmd window and compare the
output with the same in a cmd started via "Start->Run"...

Do you get the same problem if you use "run winword.exe filename"?  Which
version of Word are you trying to use?

I know that Word uses /tmp for temporary files when started via Cygwin.
Check permissions on your /tmp.  Otherwise, we'll need more details, as I,
for one, can't reproduce your problem.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/