Hi Guys,
How do I stop a Wise script from creating an INSTALL.LOG?

Cheers
Charlie
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Either stop the 'Open INSTALL.LOG' action from executing or add a 'Close INSTALL.LOG', according to this hard-to-find PDF http://www.altiris.com/upload/wisescripteditor_005.pdf

Hard-to-find, in that it took me almost F I V E seconds... :)
Answered 06/05/2008 by: VBScab
Red Belt

Please log in to comment
0
Ok, ok, I'm a lazy cow... :P Thing is I can't get it to stop writeing the log; the first line in my script is 'Stop writing to installtion log'. Is that right or am I missing somthing stoopid?

Cheers
Charlie
Answered 06/05/2008 by: fuz_kitten
Second Degree Blue Belt

Please log in to comment
0
ORIGINAL: fuz_kitten
Is that right or am I missing somthing stoopid?
I don't know, I never use WS. The PDF implies (page 37) that each action has an 'Add text to INSTALL.LOG' "property". Maybe you need to blank those?

I am wondering, though, why you don't want that file: it's my understanding that it's used by the script actions when uninstalling...
Answered 06/05/2008 by: VBScab
Red Belt

Please log in to comment
0
If you're using the wise script package editor to modify this wisescript, just go into the Installation Expert section and on the left hand pane under Target System highlight Installation Log and select 'Do not create installation log'.
Answered 06/05/2008 by: danr29
Purple Belt

Please log in to comment
0
Hey,
I'm using a Wise script to tidy up after a messy wraped RealPlayer install, it just removes some shortcuts and moves some around. The INSTALL.LOG ends up being created in a Start menu group. The script doesnt need to be uninstalled so the log is not a concern.

Arrr! I've just compiled my script in Wise Installer and now I'm going to have to start again! Why do I never learn how important backups are!

C
Answered 06/05/2008 by: fuz_kitten
Second Degree Blue Belt

Please log in to comment
0
Ian,

Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.

you should change this to this..

Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you. Don't know where it is http://www.google.com will find it.
Answered 06/05/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
ORIGINAL: jmcfadyen
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you. Don't know where it is http://www.google.com will find it.
Thanks for the idea. How does it look now?
Answered 06/06/2008 by: VBScab
Red Belt

Please log in to comment
0
Having rewritten the script, the 'stop writing to installation log' now appears to have the desired effect. Maybe I messed up the first time around, maybe there was some other issue. However, no thanks to your sarcasm I now have a solution and I suppose that’s all that matters.

Till the next time, love ya!
Answered 06/06/2008 by: fuz_kitten
Second Degree Blue Belt

Please log in to comment
0
thanks so much for useful info

[url=http://globolstaff.com/]script install[/url]
Answered 08/09/2009 by: mcjohn87
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity