Target System Folder finding

[bendrouet]

hi,

I tried but did not find a way to know from which directory the setup (generated with IA) is executed on the client computer.

I tried DATADIR, EXEDIR, EXEFILE, ROOTDIR but the results point to temporary directory of the user
...documents and settings\\my user\\...\\Temp

But I run my setup.exe from D:So is there any variable that can give me D:\\ ? The directory from which the setup on the client machine is ran.

I absolutely need this info for our customer installation.

Thank you

[casic]

If you run a self installing setup, all files will be decompressed to a temporary directory first. After this step, setup is executed - so the variable EXEPATH works correctly.

cu

Markus

[bendrouet]

Thank you for the response

I tried to use the EXEPATH variable that you indicate but I did not find a variable called EXEPATH in IA

What do you mean by EXEPATH variable ?
How to obtain it and use its value ?

Thank you

[MichaelNesmith]

I think you want to use SFXPATH...also, in the help index, type "pre-defined variables" to see a full list of each pre-defined setup variable and their values.

[casic]

Thank you for the response

I tried to use the EXEPATH variable that you indicate but I did not find a variable called EXEPATH in IA

What do you mean by EXEPATH variable ?
How to obtain it and use its value ?

Thank you

Sorry, I meant EXEDIR (should never write posts and emails at the same time...)

cu

Markus

[lorrymoller]

Just to let you know i've encountered that problem.
It used to work fine about a week ago; but this simple test of displaying all the variables in a newly created sample project yields the same results as above.

Steps:
- Create a new project
- Type: Single or Compressed
- Paste the following MessageBox code at the beginning:
~InstallAware Clipboard Data~
~MessageBox~
~{0FA9E976-FBB6-4150-82C6-A730A2100FDB}~
~check app requi~
~Filename: $EXEFILE$$NEWLINE$Curdir: $EXEDIR$$NEWLINE$MSIFILE: $MSIFILE$$NEWLINE$ROOTDIR: $ROOTDIR$$NEWLINE$SFXFILE: $SFXFILE$$NEWLINE$SFXPATH: $SFXPATH$$NEWLINE$~
~2~
~1~
~~

- build the test.
Run the sample executable and you'll notice it displays the temp folder.
IF you use a filename that is longer than 8 characters, it will get truncacted to a 8 character limit with a delta at the end (~).

We need the full long file name support.

If you rename the sample application, it still references the original filename.

I had tested this earlier with the above code and it worked as expected. Rename setup app, and it will display the renamed name; not the original.

Any help or suggestions is greatly appreciated as i'm at a loss to why this is happening.

I'm assuming the MSI engine in windows has something to do with it - but can't find anything to go on.

Help?!

[pstack12]

I'm having the same issue getting the original setup file's folder, prior to it being copied to the temp folder. I have some specific files that may or may not be located on the CD-ROM in the same folder as the Setup.exe. If they exist, I need to copy the files to the $TARGETDIR$. However, the $EXEDIR$ pre-defined variable returns the temp Setup folder, not the folder on the CD-ROM.

Has anyone figured out how to get the staring folder of the Setup.exe file, in my case this would typically be on the CD-ROM.

[Gareth Owen]

If you are using one of the compressed formats, then

[quote]SFXPATH: If an uncompressed directory layout is used, this variable is empty. Otherwise set to the full path of the folder containing the self extracting executable which bootstrapped the installer.[/quote]