This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: The setup-x86.exe can't be called by blocked way on Windows 10

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 <>:
> Greetings, kuaf!
>> I downloaded the latest setup-x86.exe (version, 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:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]