logged install - problem

[jweksej]

Starting setup /l=log.txt simply hangs the installer without any message and log. I repeated it with fresh made 'default project' without any change from my side. Setup works fine if started without command line parameters - both install and uninstall.

How to start logged install from script level?

regards
Jarek

[CandiceJones]

Maybe you have a group policy or other similar effect on your system barring logged installs? Please double-check. You can also set the LOGGED variable to a file path from the script to turn on logging, but it seems this would fail as well.

[jweksej]

> group policy or other similar effect
what do you mean exactly. What I have to check? All access rights are allowed.

>LOGGED variable
it doesn't works. It is simply ignored, and install/uninstall goes smoothly.

[ken rentz]

I had a similar problem and it went away when I added a path to the log file and put it in quotes. /l="c:\\log.txt". I don't know why it worked, and I did not investigate further to see if it was reproducible. Also logging seems to slow things down a lot. I could see the log file growing so I knew it was doing something.

[CandiceJones]

I'm sorry I missed that. You have to specify a full path for the log file. And yes, logging will almost exponentially slow down your setup, this is just the way Windows Installer works.