This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Orphan minimized installer Not Responding
Started by
PeterBoucher
, Oct 29 2004 23:45
5 replies to this topic
Posted 29 October 2004 - 23:45
I click Finish and it minimizes but never actually finishes.
I don't have any code after SDFinish.
I made a verbose log (/L*v) and at the end it says that the verbose logging finished and stopped logging, so the installer hung AFTER closing the log.
If I kill the installer with taskmanager, I get a dialog that says the install failed with error 1628.
Any ideas?
I don't have any code after SDFinish.
I made a verbose log (/L*v) and at the end it says that the verbose logging finished and stopped logging, so the installer hung AFTER closing the log.
If I kill the installer with taskmanager, I get a dialog that says the install failed with error 1628.
Any ideas?
Posted 30 October 2004 - 06:43
/L*v only works for MSI projects. What project type are you using?
Stefan Krüger
InstallSite.org twitter facebook
Posted 02 November 2004 - 18:58
It's an Installshield X Installscript project.
QUOTE |
/L*v only works for MSI projects |
Not so. try
QUOTE |
Setup.exe /V"/L*v errlog.txt" |
Posted 02 November 2004 - 20:55
Quote from the documentation:
QUOTE |
/v : Pass arguments to Msiexec (Windows Installer-based projects only) The /v option is used to pass command-line options and values of public properties through to Msiexec.exe. |
I really don't think this would work for (pure) InstallScript projects.
Stefan Krüger
InstallSite.org twitter facebook
Posted 03 November 2004 - 20:49
Oops! My bad. I hadn't read the red text closely enough to notice the
QUOTE |
not even for "InstallScript MSI" |
FYI, we never did find out what caused it, but we narrowed it down to a certain section of the script being responsible, then re-wrote that section from scratch, and the problem went away.
Sorry to have posted on the wrong forum.
Posted 04 November 2004 - 14:18
Glad to hear that the problem is solved.
Both Basic MSI and InstallScript MSI are based on the MSI engine, which is completely difefrent from the InstallScript engine. Therefore it was important for me to know what project type you are using exactly.
Both Basic MSI and InstallScript MSI are based on the MSI engine, which is completely difefrent from the InstallScript engine. Therefore it was important for me to know what project type you are using exactly.
Stefan Krüger
InstallSite.org twitter facebook