Re: commands not waiting, /wait not helping
- From: "Gary Chanson" <gchanson@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 24 Apr 2005 05:26:57 -0400
"bh" <bh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:381BF8DF-569D-4C48-B999-11979823F685@xxxxxxxxxxxxxxxx
> 2 questions:
> 1) Windows changed the behavior of running a GUI app from a batch file or
> cmd prompt so it no longer waits for the app to finish. But on one XP
> machine, running a gui app waits, and on another running that same app does
> not. Apparently there's a config option somewhere that controls this--anyone
> know where?
Nope. Windows *NEVER* waited for GUI apps run from batch files to
complete before continuing with the next command. It does wait for console
apps to complete though.
> 2) This came about because I'm trying to automate building several
> installers. But Wise.exe requires /c as a parameter. If I do
> start /wait wise.exe /c "path to .wse script"
> I get an error that /c is an invalid switch--apparently for the start
command.
> I've tried every possible combination of quotations around the pieces, an
> extra " " dummy arg, and avoiding the exe and just running the .wse via
> implied associations, and nothing works.
> Any ideas?
Something is probably fooling you with a confusing error message. START
will ignore everything after the name of the executable and pass it to the
target program. It's probably WISE.EXE which is rejecting the /c switch.
--
-GJC [MS Windows SDK MVP]
-Software Consultant (Embedded systems and Real Time Controls)
- http://www.mvps.org/ArcaneIncantations/consulting.htm
-gchanson@xxxxxxxx
.
- Follow-Ups:
- References:
- Prev by Date: How to use the ITextHost and ITextServices interfaces
- Next by Date: Re: commands not waiting, /wait not helping
- Previous by thread: commands not waiting, /wait not helping
- Next by thread: Re: commands not waiting, /wait not helping
- Index(es):
Relevant Pages
|
Loading