QUOTE (HardDriv'n @ Sep 20 2010, 04:17 PM)

It doesn't start the files, or folder. What worked was the keep this window open message, and the canceled all message.
Sure

, that's a TEST ( or EXAMPLE).
But you should see in the cmd window the ECHOed messages for each option when you select one an press next.
QUOTE (HardDriv'n @ Sep 20 2010, 04:17 PM)

The reason I had used the checklist option is because they might need to launch the utility folder, or links. Maybe I should have changed it so it was a close this window option, instead of keep it open option.
Sure

, but we were talking of RB, let's have it working BEFORE introducing a variation, OK?
QUOTE (HardDriv'n @ Sep 20 2010, 04:17 PM)

Does this mean I was supposed to put the executable's action on the same line?
Also what are the /W, and the "" for?
Yes, this is "lesson #2" in ANY programming or scripting language, the consequences of a conditional check should be INSIDE the conditional check itself.
For all that matters:
CODE
if "%waoutnum%"=="0" echo Run Advanced Installer: Windows 2K/XP/Vista& ECHO Start /W "" advance.exe&PAUSE
if "%waoutnum%"=="1" echo Run Original Installer: DOS, Windows 95/98/ME& ECHO Start /W "" install.exe&PAUSE
or this:
CODE
if "%waoutnum%"=="0" (
echo Run Advanced Installer: Windows 2K/XP/Vista
ECHO Start /W "" advance.exe
PAUSE
)
if "%waoutnum%"=="1" (
echo Run Original Installer: DOS, Windows 95/98/ME
ECHO Start /W "" install.exe
PAUSE
)
Are two different ways to write the same thing, actions are performed ONLY if given condition is met.
This (let's assume you chose option #0, then the value of waoutnum will be 0):
CODE
if "%waoutnum%"=="0" echo Run Advanced Installer: Windows 2K/XP/Vista
advance.exe
if "%waoutnum%"=="1" echo Run Original Installer: DOS, Windows 95/98/ME
install.exe
Will:
- echo "Run Advanced Installer: Windows 2K/XP/Vista" ONLY IF the value of waoutnum is 0 (it will execute)
- execute advance.exe NO MATTER the value of waoutnum (it will execute)
- echo "Run Original Installer: DOS, Windows 95/98/ME" ONLY IF the value of waoutnum is 1 (it will NOT execute)
- execute install.exe NO MATTER the value of waoutnum (it will execute)
Start COMMAND Syntax:
http://ss64.com/nt/start.htmlAGAIN, it depends on the actual OS on which the batch is run, the START "" /WAIT should be the most "compatible" form.
I introduced in the example the "wrong" :
CODE
START /wait ""
instead of the "right"
CODE
START "" /wait
to check if you would have spotted it

(but I expected for you to spot it as a syntax error, not as a "what is this")

You started the thread implying that you knew how to write a batch script, this seems like NOT the case.

No problem if you don't

, but there was this basic misunderstanding, if you know how to write a batch file, wizapp is a nice Pseudo-GUI tool, if you don't you need to learn some basic BATCH before being capable of using it.
QUOTE (HardDriv'n @ Sep 20 2010, 04:17 PM)

Is it supposed to be "&echo", "& echo", or " & echo" (space before &)?
It normally does not matter, "&" is simply a conjunction, the only exception is after a SET statement, like:
CODE
SET variable1=test1&DIR /s C:\
vs.
CODE
SET variable1=test1 &DIR /s C:\
or:
CODE
SET variable1=test1 & DIR /s C:\
the first one is right ad the variable value will be "test1", the other two are "wrong" as the variable value will be "test1 " or test1[SPACE]
There are also other exceptions, but they are quite rare, the "safest" is to use NO spaces before or after.
jaclaz