From: kuaf <kuaf.lee@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: The setup-x86.exe can't be called by blocked way on Windows 10
Date: Thu, 07 Apr 2016 14:15:00 -0000 [thread overview]
Message-ID: <CAFLqW4Ng-H-csLb3_sFsamKKHsbGBsGsjJ--ii1hzM_Py2VX0Q@mail.gmail.com> (raw)
In-Reply-To: <245532336.20160407161600@yandex.ru>
I found this issue is related to administrator rights on
setup-x86.exe. It works right now, thank you.
2016-04-07 21:16 GMT+08:00 Andrey Repin <anrdaemon@yandex.ru>:
> Greetings, kuaf!
>
>> I downloaded the latest setup-x86.exe (version 2.8.7.3), attempted to
>> install through automation interface on Windows 10 OS. But the batch
>> file can't call it by blocked way, .e.g.
>
>
>> test.cmd
>> ----
>> @echo off
>
>> rem step1
> start "Cygwin setup" /wait "setup-x86.exe" --quiet-mode --local-install --local-package-dir
>> "C:\my-packages" --root "C:\my-cygwin\cygwin" --no-shortcuts
>> --no-startmenu --no-desktop --packages
>> alternatives,aspell,aspell-en,attr,automake,base-cygwin,base-files,bash,bc,bzip2,chere,coreutils,cron,crypt,csih,ctags,curl,cygutils,cygwin,diffutils,dos2unix,editrights,findutils,gawk,gcc,gcc-core,gettext,git,git-svn
>
>> rem step2
>> echo OK
>
>> In the actual test execution on Windows 10, step1 and step2 were
>> running in parallel, instead of sequence step.
>
>> I had tested this scenario on Windows 7, it worked ok.
>
> By a pure coincidence.
>
>
> --
> With best regards,
> Andrey Repin
> Thursday, April 7, 2016 16:15:16
>
> Sorry for my terrible english...
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-04-07 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 11:58 kuaf
2016-04-07 13:20 ` Andrey Repin
2016-04-07 14:07 ` kuaf
2016-04-07 14:15 ` kuaf [this message]
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=CAFLqW4Ng-H-csLb3_sFsamKKHsbGBsGsjJ--ii1hzM_Py2VX0Q@mail.gmail.com \
--to=kuaf.lee@gmail.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).