X-Spam-Check-By: sourceware.org
Message-ID: <2fc802c00602031305p7574f255g5e67e44cd8b754e@mail.gmail.com>
Date: Fri, 3 Feb 2006 21:05:45 +0000
From: David Picton <djpicton AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: strange cygstart bug with current Cygwin versions
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k13L5prt021115

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.

The two affected computers use different software versions - one has
Win2000 with Office 2000, but the other has WinXP with Office 2003.
Strangely a third machine with WinXP/Office 2003 is not affected. 
However, it does seem likely to me that other people will be able to
reproduce the bug, as it clearly isn't tied to one particular version
of the software.

--
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/