Deamon,

I've been enjoying your rant about InstallShield. I had a similar situation with this vendor several years ago.

Regarding the 'first time flag' file at startup - we place our flag file in our startup folder, but perhaps a better place to put this file might be the user's Windows folder or Temp folder(??!). You could also disguise the file name by using a stem different than your main application or hiding the file (installing it as a hidden file). Another tact may be to have your setup create a 'first time flag' key in the registry or an INI file. If you see this key on startup, delete it and then run your post installation logic and/or executables. Or use both techniques.

Good luck!
Malcolm



>Yes, this is one avenue we considered. It may be the way to go, thanks for the re-inforced opinion.
>
>The only negative aspect that we could think of is that we don't want the flag to be able to be reset by the user. We do liscensing stuff in this code so we only would want this behavior to occur once.
>
>Thanks again.
>
>G