Menu

"Windows cannot find 'setup.exe'...

Wanda Wang
2011-02-24
2012-12-07
  • Wanda Wang

    Wanda Wang - 2011-02-24

    I created setup.exe by:
    copy /b 7zS.sfx + config.txt + vic.7z vicexe
    Then I start vic.exe, always get the error as title.

    config.txt is saved in UTF-8:
    ;!@Install@!UTF-8!
    Title="VIC"
    BeginPrompt="Do you want to install VIC?"
    ExecuteFile="setup.exe"
    ;!@InstallEnd@!

    vic.7z including 1 folder and 2 files, and setup.exe is one of these 2 files.

    I tested setup.exe, and it run correctly without being compressed.

    Why? Can anybody help? Thanks a lot in advance!

     
  • Wanda Wang

    Wanda Wang - 2011-02-24

    Sorry, there is a type error in the first note:
    The cmd is: copy /b 7zS.sfx + config.txt + vic.7z vic.exe
    And the problem is the same.

     
  • Igor Pavlov

    Igor Pavlov - 2011-02-24

    Probably your setup.exe starts another exe file.
    call
    setup.exe /?
    or look help file for setup.exe
    to find the switch that makes setup.exe keep running all the time.

     
  • Wanda Wang

    Wanda Wang - 2011-02-25

    Hi ipavlov, my setup.exe is output of windows setup projects, it will not call other exe, it just call .msi file at the same path with it. I have compressed the .msi with setup.exe already.

    Do you mean change ExecuteFile="setup.exe" to ExecuteFile="setup.exe \?", it did not take effect, also reported similar error.

     
  • Wanda Wang

    Wanda Wang - 2011-02-25

    The problem has been resolved: I did not compress the setup.exe at the root path, so vic.exe can not find it.

    But now I got another error popup by Windwos Installer: "This intallation package could not be opened, Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer packge."

    I checked by uncompressing vic.exe to a folder, and manually start setup.exe inside it, no such problem.

    Then why?

     
  • Wanda Wang

    Wanda Wang - 2011-02-25

    The second problem is also resolved.
    I googled by this error and find some clue, so I changed ExecuteFile="setup.exe" to ExecuteFile="my.msi", then ok.

    One more thing, I still worry about the execution level, so I will test my vic.exe with UAC on, to check if the application be installed to the right place.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.