Okay here is the deal: I am trying to sequence SEL 5601 Analytic Assistant. Everything sequenced fine and dandy, the only problem being a post configuration license file. Basically the user must download a license file from the SEL website. This license would normally be placed in the folder structure of SEL Analytic Assistant:

C:\Program Files\SEL\Analytic Assistant\License

Or something to that effect. What I have been trying to do is have the user create that folder structure on the local system and have the App V package merge with the local file system (this can be done in the VFS tab when further configuring your package). I would think that this would suffice and the program would peek at the license file stored locally.

What am I missing??

0 Comments   [ + ] Show Comments


Please log in to comment



Hi Flag,

use procmon to find out, why the Application did not pick up the file. May a prelaunch script, wich copy the license file into the virtual enviroment is another way.



Answered 07/11/2012 by: vkleiner
Orange Senior Belt

Please log in to comment

First, make sure the SEL, Analytic Assistant and License directories are set to merge rather than override in the Virtual File System view of the sequencer.  That should allow visibility through to the files on the real C: drive.

As an alternative, you can run a pre-launch script to prompt the user to browse to this license file if it does not exist and copy it into the bubble.  Of course, this will not be suitable if the license file is tied to the hardware and the user either uses multple machines or a random server in a terminal server environment.

Answered 07/11/2012 by: packageologist
Orange Belt

  • Hmm... I tried both those things. Didn't work, even though it seems like it should. Here is what I did:

    1. First I tried merging local file systems. I had the vfs set to merge for the place where the license file was supposed to be. The license file is post config by the user, and they just create a directory mirroring that of SEL had it physically been installed (like normal). I tried with the package being on the C:\ drive and the V:\ drive. No dice either way :(

    2. Then I decided I would get my hands dirty. I did a direct copy of the file into the bubble using sfttray. This would work for sure (or so I thought). For whatever reason, it doesn't. You can look through the files in the bubble and the license is exactly where it needs to be, but when you try to open the program, it doesn't read the license file.

    Perhaps this package is destined to be traditional :'-(
Please log in to comment
Answer this question or Comment on this question for clarity