INSTALL.LOG keeps saving to System32, not %MAINDIR%
I'm currently scripting a small installer .EXE in Wisescript Package Editor for Wise Installation Studio 7.3.0.
I started the project by looking a the .WSE file for the software's previous version. What I found was that there were whole sections sometimes four or five versions old that had simply been commented out. I decided it needed a refresh so I re-wrote all the code worth keeping in a totally new, blank script as well as adding and improving some things along the way.
I have been working primarily in the main script window, and so far haven't made any changes to the uninstall tab or the rollback tab.
Now that I'm coming to the end of the project I've been testing the install and have found that everything is working beautifully except that for some reason the INSTALL.LOG keeps getting saved into windows\system32 no matter which OS I'm installing on. I've tested this on XP and VISTA.
I never specified a location, and everything I've seen online about using the "Project Settings" section to specify it's location doesn't work for me because in my project the only options available are "Compiler Variables" and "General Information"
I've been all over the forums looking for a situation similar to mine, but so far have not found one. Likewise, the user's guide simply points me back to the "Project Settings."
My question is this: How can I, using only Wisescript, instruct the installer to save the INSTALL.LOG into the %MAINDIR%?
[EDIT 10.07.09]
Okay, I've attached the script text file. If this isn't right, or you need to see something else, let me know.
Comments
Need to see your code
Writing the installation log to %MAINDIR% is pretty much default behaviour, so I am of the opinion that your code is not setting %MAINDIR% correctly, or your code is not opening the installation log in the right place.
Are you able to upload your code somewhere for us to look at, or edit your original posting to attach it (you can't attach code to anything other than your first posting in a thread).
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Have you ever used
Have you ever used http://pastebin.com/ for sharing code back and forth? It's a good option and you can choose how long your code stays posted there. It's an option...
Cheryl
Endpoint Management,
Endpoint Virtualization
Community Manager
www.twitter.com/EMnV_symc
Need Altiris help? IRC chat #Altiris
Success!
I'm not entirely sure how, but I seem to have solved this little conundrum all on my own.
While perusing the forums looking for a solution to this problem prior to my initial post, I had come across another article where a Trusted Advisor (it may or may not have been you Ed) warned someone to STAY AWAY from the ODBC configurator in the Wisescript Package Editor and just identify and create the neccessary registry entries manually. I took note of this, since with previous versions of the software we would consistently get a small percentage of customers who would complain about the exact same ODBC cofiguration error and the code I was overhauling had also used the ODBC configurator. However, since the problem I was currently dealing with appeared more pressing I decided to keep it in the back of my mind and post my INSTALL.LOG problem first.
While waiting for you to get back to me though, I got around to messing with my ODBC settings and working on identifying the individual keys as opposed to letting the configurator do it. Well, I just ran a test of my most recent iteration of the installer and not only does the ODBC data source install fine using just the manual registry edits, but the INSTALL.LOG is also showing up in the right place all of the sudden!
I'm not entirely sure what one has to do with the other, but it seems impossible to ignore the fact that once I made this ideological change to the way the code was written, another problem resolved itself as well.
Now I'm off now to test the installer on as many different setups as I can. My deadline approaches!
One more thing....
If you start a Wisescript project with a "Blank script" template, you will find that the Installation Expert left hand menu options are substantially abbreviated compared to starting with an "Empty Project" template. Try starting with each template option and see for yourself.
If you plan a project with installation logging, then always start with an Empty Project template - it is much simpler to remove stuff from it, than to start with a blank script and then try to remember what to include.
The blank script option is ideal for when you are writing simple utilities or custom actions where you don't want any rollback or install logging functionality. The empty project allows you to set an installation log path to wherever you choose.
I'm not entirely sure what you posted in the text file - if it was the WSE with a changed file extension, then there would appear to be a bunch of header information missing.
And yes - it was me who recommended the registry method of installing ODBC drivers rather than the less reliable ODBC wizard method. Should you need to create a USER DSN, the registry keys are in HKCU rather than in HKLM, where SYSTEM DSNs are recorded.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.