SF6 Newbie.

[Kevin 92R/T]

Hey all, we just upgraded from SF5 a few days ago.

Our setups are per customer, meaning each customer gets a custom install.

For ease of generating the setups, we have a few configuration files that are stored with a common name (SETTINGS.TXT). So we can change that file, and have a new setup built for a customer.

The problem is there are customers that have more than 1 setup. So after the first time they run the setup, the SETTINGS.TXT file is always skipped.

What happens is SETTINGS.TXT is installed to the user's temp folder, and then moved to the the correct folder after installing.

So when SF6 tries to move that file it throws an error, since the file is skipped, and never installed.

How can I tell SF that I never want specific files skipped, no matter what?? The Files Properties are set to always overwrite, etc etc. But the problem is that there no sign of that file in the user's temp DIR. So there is something else causing the file to be skipped.

[Kevin 92R/T]

Anyone?

[Darryl]

I first want to make sure you are using the latest build of the product, 6.0.1.3. You can find build information under Help->About Setup Factory.

I have a few other questions for you:

1) Is this install a converted project from 5.0 or a new project?
2) Do you have any build time or runtime conditions set on that file that may affect its installation?
3) Are you generating an installation log file with your install? That often logs useful information as far as where the problem may be.


I'm not sure that I understand fully what is happening though.

Is the file successfully being installed to the user's Temporary directory in the first install, and the problem is on subsequent installs? If you compare the two project files, do you notice any differences as far as the Settings.ini file is concerned? Is this file archived inside of the install or referenced from the CD-ROM tab?

It may help to see a log file and a couple project files if you want to send that to our support department.

[Kevin 92R/T]

Originally posted by Darryl
I first want to make sure you are using the latest build of the product, 6.0.1.3. You can find build information under Help->About Setup Factory.


Yep its 6.0.1.3


Originally posted by Darryl

I have a few other questions for you:

1) Is this install a converted project from 5.0 or a new project?
2) Do you have any build time or runtime conditions set on that file that may affect its installation?
3) Are you generating an installation log file with your install? That often logs useful information as far as where the problem may be.


1. Yes it was converted from a 5.0 project.
2. The file has no conditions on it, it will always install as it is a required settings file.
3. The Log file just indicates (skipped) beside the file name, but I'll double check the logs again (they're on my laptop at the moment).


Originally posted by Darryl

I'm not sure that I understand fully what is happening though.

Is the file successfully being installed to the user's Temporary directory in the first install, and the problem is on subsequent installs? If you compare the two project files, do you notice any differences as far as the Settings.ini file is concerned? Is this file archived inside of the install or referenced from the CD-ROM tab?


Yes, the first install works fine, the subsequent installs are having trouble. The Settings file is always different as it contains connection strings specific to an individual customer. *But* one this is that the file is always the same *size*. As all the fields in the txt file are fixed length strings. The file is part of an archive.

Basically what happens is the file is copied to the users temp dir, and then after installing it is moved to the install folder as CustomerID.txt. Where the customer ID is stored in a variable.

Right now since, the file isn't there after the first install, it throws an error when it tries to move the non existant file.

Originally posted by Darryl

It may help to see a log file and a couple project files if you want to send that to our support department.

I'll snag the log file off my laptop once I get a chance.

[JimS]

This is just an idea, but it might work for you. What if you set it up so that during the initial install, CustomerID.txt was moved to a folder of your choice like %SysDir%.
Put an IF/Then statement, so that if CustomerID.txt isn’t present, your setup reads it from the %SysDir%

Another approach would be to write the info to a registry key and use the IF/Then statement to read the values from there.
Or at the end of your setup, you could write to the registry key, the path to the folder the program was installed, so using that same If/Then logic, you could read CustomerID.txt from wherever it is located.

I hope these ideas help.