This is a package issue. Not a toolkit issue.
1- You are installing blind. Tack on something like /f2"C:\Setup.log" to get a log file.
2- Simplify and isolate. Try to install without the toolkit. If it doesn't work with
3- Where did the setup.iss come from? Did you created it with XP and now you expect it to work on Win8 or Win7?
Installshield ISS files are a built-in way to "drive" the installation dialog boxes and are only able to handle only ONE scenario.
If the setup.exe does something on Win7 that it didn't do in XP, the ISS files will not work.
4-WTH is the -isw64 switch for? It's not documented anywhere. (it's mentioned here if you know Russian! http://blog.not-a-kernel-guy.com/2007/01/12/133 )
5-There are some package that are so badly done that you have no choice but to repackage.
1- You are installing blind. Tack on something like /f2"C:\Setup.log" to get a log file.
2- Simplify and isolate. Try to install without the toolkit. If it doesn't work with
setup.exe /s /f1"$dirFiles\setup.iss" /f2"C:\Setup.log"3- Where did the setup.iss come from? Did you created it with XP and now you expect it to work on Win8 or Win7?
Installshield ISS files are a built-in way to "drive" the installation dialog boxes and are only able to handle only ONE scenario.
If the setup.exe does something on Win7 that it didn't do in XP, the ISS files will not work.
4-WTH is the -isw64 switch for? It's not documented anywhere. (it's mentioned here if you know Russian! http://blog.not-a-kernel-guy.com/2007/01/12/133 )
5-There are some package that are so badly done that you have no choice but to repackage.
