public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* The setup-x86.exe can't be called by blocked way on Windows 10
@ 2016-04-07 11:58 kuaf
  2016-04-07 13:20 ` Andrey Repin
  0 siblings, 1 reply; 4+ messages in thread
From: kuaf @ 2016-04-07 11:58 UTC (permalink / raw)
  To: cygwin

Hi,

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
"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.

Thanks

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: The setup-x86.exe can't be called by blocked way on Windows 10
  2016-04-07 11:58 The setup-x86.exe can't be called by blocked way on Windows 10 kuaf
@ 2016-04-07 13:20 ` Andrey Repin
  2016-04-07 14:07   ` kuaf
  2016-04-07 14:15   ` kuaf
  0 siblings, 2 replies; 4+ messages in thread
From: Andrey Repin @ 2016-04-07 13:20 UTC (permalink / raw)
  To: kuaf, cygwin

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: The setup-x86.exe can't be called by blocked way on Windows 10
  2016-04-07 13:20 ` Andrey Repin
@ 2016-04-07 14:07   ` kuaf
  2016-04-07 14:15   ` kuaf
  1 sibling, 0 replies; 4+ messages in thread
From: kuaf @ 2016-04-07 14:07 UTC (permalink / raw)
  To: cygwin

Hi, Andrey Repin,

It's not a pure coincidence. You can did a quick test on Windows 10 only with:

1. start /wait setup-x86.exe
    This is a immediate return from parent process window

2. start /wait notepad.exe
    The child process will wait for the notepad.exe to be closed.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: The setup-x86.exe can't be called by blocked way on Windows 10
  2016-04-07 13:20 ` Andrey Repin
  2016-04-07 14:07   ` kuaf
@ 2016-04-07 14:15   ` kuaf
  1 sibling, 0 replies; 4+ messages in thread
From: kuaf @ 2016-04-07 14:15 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2016-04-07 14:15 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-07 11:58 The setup-x86.exe can't be called by blocked way on Windows 10 kuaf
2016-04-07 13:20 ` Andrey Repin
2016-04-07 14:07   ` kuaf
2016-04-07 14:15   ` kuaf

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).