10/3    Can anyone recommend a self-extractor on Windows that:
        1) Shows progress while it is unzipping
        2) Can be built inside a build (not using IDE)
        3) Allows you to run a command (EXE) packaged inside the .EXE *AND*
        4) Allows you to pass in arguments to that EXE
        Winzip self-extractor meets all these reqs except for #4.  I don't
        care if it is freeware or costs money.
        \_ There are commercial installer products that should be able to
           do what you want which seems to be to distribute an installable
           compressed .exe file.  If one of them doesn't do exactly what you
           want, ask them how much for a custom mod since money doesn't
           seem to be an issue for you.
        \_ Why not use a batch file?
           \_ Because my customers don't want to have to read a README and
              download files and batch file and type shit in.  They want to
              double click an EXE.  And if there's problems I'd like to be
              able to parse command line arguments.
        \_ What are the flags you want to support, and what do you want each
           flag to do?
        \_ Let's say you have pkg.exe, and when you run it, it unzips files
           to a temp directory, then runs a file "setup.exe" inside.
           Feature 4 means you want "setup.exe" being run with some flags
           that are always the same?
                \_ No winzip self extractor supports that.  I want:
                   pkg.exe -flag to run: setup.exe -flag.  So the arguments,
                   if any, are not known ahead of time but chosen by the
                   user.
                   \_ I'm gonna go out on a limb and say "this is dumb."
                   \_ Why do you want a self-extractor to do this? Just
                      write a setup program to do it. Let the
                      self-extractor simply extract.
                   \_ I'm gonna go out on a limb and say "this is dumb."
                      \_ This IS dumb and it breaks the UI rules for Windows.
                         Under Windows user interaction with a setup program
                         is done through the setup UI, i.e. installshield
                         or MSI's GUI scripts. So do it properly and have
                         the user interact with the setup UI, not through
                         some sort of nonstandard command like B.S. What
                         works for UNIX doesn't work for Windows.
                         \_ The question wasn't "is this a dumb thing to do".
                            The question was "does anything support this".
        \_ what about nullsoft's nsis?
        \_ Never mind everyone I've figured out a way of doing it.  It's
           stupid and usability will probably complain but it will work.
                   pkg.exe -flag to run: setup.exe -flag.