Re: commands not waiting, /wait not helping
- From: "Severian [MVP]" <severian@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 25 Apr 2005 09:00:44 GMT
On Sun, 24 Apr 2005 22:52:04 -0700, "bh"
<bh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>Thanks, yes I had come to the same conclusions.
>But have you ever seen wise actually wait even with
> start /wait ... ?
>for me it returns immediately even though the compilation happens a moment
>later, so I presumed it is spawning a second process and exiting.
>This all started because I have a main app installer that itself installs 3
>smaller install programs, and I wanted to ensure the included projects were
>current before compiling the main one. A programmer had put together these
>batch files, but apparently never checked to see that it waited and actually
>worked LOL.
>So much for saving some time with a quick batch file; Clearly I need to do a
>.mak script or simply have the main install script either prompt the user for
>each project or take the time to regenerate them every time.
>
>Thank you all very much for your time on this. I certainly know the Start
>command better than I used to!
start /wait wise9.exe /s /c setup.wse
is working fine for me. It does not return until Wise9 finishes
compiling. I tried a large (20MB) project and it worked fine on Win2K.
I have not installed Wise9 on any other O/S.
I have only tested this interactively.
>"Severian [MVP]" wrote:
>
>> On Sun, 24 Apr 2005 19:42:01 -0700, "bh"
>> <bh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>> >"Gary Chanson" wrote:
>> >> You should be able to execute something like:
>> >> START /wait "C:\Program Files\Wise Installation System\Wise9.exe" /c
>> >> "U:\path\Scriptfile.wse"
>> >
>> >you may think it "should", as I did, but in fact that is exactly what does
>> >NOT work.
>> >Start aborts with an "invalid switch" reply.
>>
>> (All of the below is on Win2k; I haven't tested on later OSes.)
>>
>> What seems like it should be the obvious solution gives me exactly the
>> same error. The START command hates the quoted parameters.
>>
>> Try this simple test:
>>
>> start "some text file.txt"
>>
>> It will open a new, empty command window, instead of notepad with the
>> file.
>>
>> For Wise, like most application, I always install it in a simple
>> folder (i.e., d:\dev\Wise9). Then, this works fine:
>>
>> start/wait d:\dev\wise9\wise9.exe /c /s setup.wse
>>
>> Another option is to add the wise installation folder to your PATH
>> environment variable; then you should be able to do:
>>
>> start/wait wise9 /c /s setup.wse
>>
>> Also, wise should really provide a separate command-line compiler, to
>> make it easy to use from Visual Studio and other IDEs.
>>
>> --
>> Phillip Crews aka Severian
>> Microsoft MVP, Windows SDK
>> Posting email address is real, but please post replies on the newsgroup.
>>
--
Phillip Crews aka Severian
Microsoft MVP, Windows SDK
Posting email address is real, but please post replies on the newsgroup.
.
- Follow-Ups:
- References:
- commands not waiting, /wait not helping
- From: bh
- Re: commands not waiting, /wait not helping
- From: Gary Chanson
- Re: commands not waiting, /wait not helping
- From: bh
- Re: commands not waiting, /wait not helping
- From: Gary Chanson
- Re: commands not waiting, /wait not helping
- From: bh
- Re: commands not waiting, /wait not helping
- From: Severian [MVP]
- Re: commands not waiting, /wait not helping
- From: bh
- commands not waiting, /wait not helping
- Prev by Date: Re: commands not waiting, /wait not helping
- Next by Date: Help changing a shortcut
- Previous by thread: Re: commands not waiting, /wait not helping
- Next by thread: Re: commands not waiting, /wait not helping
- Index(es):
Relevant Pages
|
Loading