From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygstart regression [Was: Re: on the road to 1.5.19 - snapshot testing needed]
Date: Fri, 30 Sep 2005 20:58:00 -0000 [thread overview]
Message-ID: <20050930200515.GA7222@calimero.vinschen.de> (raw)
In-Reply-To: <433D62A7.7090207@cwilson.fastmail.fm>
On Sep 30 12:07, Charles Wilson wrote:
> Christopher Faylor wrote:
> >On Fri, Sep 30, 2005 at 09:17:06AM -0600, Aaron Humphrey wrote:
> >
> >>I just did some version testing on the cygstart .mdb problem I reported a
> >>few
> >>days ago(http://cygwin.com/ml/cygwin/2005-09/msg00923.html), and it is
> >>indeed a regression from 1.5.18. Cygstart works fine with 1.5.18, but as
> >>early as the 20050909 snapshot(as far back as I have)it fails on MDB
> >>files.
> >
> >
> >Sorry but I don't have Microsoft Access so I can't check this. I don't
> >consider
> >this a show-stopper either, unfortunately.
> >
> >cygstart comes from cygutils. I don't remember the genesis of this
> >utility (just because it is in cygutils doesn't mean that Chuck is
> >responsible for it) but it would be nice if the person who supports this
> >utility would comment here.
>
> cygstart was contributed by Michael Schapp, who is still around but
> doesn't post often. cygstart, aside from its option handling, is a very
> simple app. The core routine just uses the Windows 'ShellExecute'
> function on the specified file. Windows is then responsible for looking
> up the associated application in the registry, starting it, and causing
> it to load the specified file. I don't see how anything in cygwin
> itself can affect that.
>
> The ONLY thing I can think of is changes in path handing (conversion
> between 'unix' and 'windows') as cygstart tries to prepare the target
> file's pathname for passing into the ShellExecute function -- variable
> name 'aPath' in the code below.
>
> But I'll defer to Michael for futher analysis.
FWIW, I (my spouse, actually) just tested this with Access 2003, like
this:
$ cygstart /cygdrive/c/foo/bar/database-file.mdb
once with 1.5.18 and once with 1.5.19 from current CVS (== latest
snapshot) and both invocations happily started the database in Access.
Maybe the OP should show us how he starts the mdb file when it fails.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat, Inc.
--
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/
next prev parent reply other threads:[~2005-09-30 20:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 2:37 on the road to 1.5.19 - snapshot testing needed Christopher Faylor
2005-09-30 3:29 ` Yitzchak Scott-Thoennes
2005-09-30 3:40 ` Gary R. Van Sickle
2005-09-30 12:13 ` Eric Blake
2005-09-30 13:37 ` Eric Blake
2005-09-30 13:44 ` Corinna Vinschen
2005-09-30 15:25 ` Aaron Humphrey
2005-09-30 15:54 ` Christopher Faylor
2005-09-30 16:31 ` cygstart regression [Was: Re: on the road to 1.5.19 - snapshot testing needed] Charles Wilson
2005-09-30 20:58 ` Corinna Vinschen [this message]
2005-10-01 3:28 ` Eric Blake
2005-10-03 0:07 ` Michael Schaap
2005-10-03 0:01 ` Michael Schaap
2005-10-03 16:56 ` Aaron Humphrey
2005-10-03 17:41 ` Michael Schaap
2005-10-03 17:47 ` Christopher Faylor
2005-09-30 18:08 ` on the road to 1.5.19 - snapshot testing needed Brian Ford
2005-09-30 23:54 ` Brian Ford
2005-10-01 2:10 ` Volker Quetschke
2005-10-01 16:51 ` Christopher Faylor
2005-10-03 17:49 ` Christopher Faylor
2005-10-04 5:12 ` Volker Quetschke
2005-10-12 19:46 ` Volker Quetschke
2005-10-13 1:33 ` Volker Quetschke
2005-10-13 4:47 ` Christopher Faylor
2005-10-13 5:03 ` Volker Quetschke
2005-10-13 5:09 ` Volker Quetschke
2005-10-25 2:26 ` Igor Pechtchanski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050930200515.GA7222@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).