Advanced Installer Community

srm2710

many thanks, i have 50+ user generated registry values to contend with though. i read the help topic about using a script to preserve files by moving them to a temp location, but, as far as i know, i can't access the HKEY_CURRENT_USER\Software\ section of the registry with vbscript. In any case, i a...

srm2710

Hello, We use AI to distribute a networked piece of software that has a core network drive install, and attached users that can be 'rolled out' using msi /qn /norestart switches. To create shortcuts to the central .exe we set up property called[SD], then give it the value of the [SourceDir] in the '...

srm2710

I have the same problem. I have removed the tick from 'Delete (if present) on uninstall' from the Key's properties dialog, that does not seem to alter anything. If I upgrade an existing installation, existing user generated registry keys are removed from the registry. I have even removed all install...

srm2710

this illustrates how painful trying to control an installation has become under msi. if you were to add the option to set a default companion file for ALL other files in the install it would save us a lot of tedium. what ever happened to an program update just beind a subset install of the full prog...

srm2710

yes, i get: "The selected file could not be registered". I had assumed that this is because it is an activeX exe and not an OCX/DLL.

srm2710

Microsoft's KB article: http://support.microsoft.com/kb/297279 states: "If you use the Package and Deployment Wizard or the Application Setup Wizard to distribute your ActiveX EXE, the EXE is registered automatically during application installation." Does advanced installer offer this now?...

srm2710

Thanks for this. Rather stupidly, at the beginning of all this, I overlooked the simple workaround of using " ..\ " in the path construction! d:\application\setup\..\app.exe works fine (also when creating registry values). We have now purchased the product and are very happy with it. Sugge...

srm2710

As a footnote, this seems not to work when the install takes place on a win98 PC using the <InstMsiA.exe> etc support files. In this event, the shortcut points to: \setup\application.exe - i.e. it does not point 'up one level'.. I assume the custom action that transforms [SourceDir]../ is not trigge...

srm2710

cancel this

srm2710

Works! Many thanks for your excellent support. Great product.

Cheers

Stephen

srm2710

Thank you for this, I have included your last alteration, but the resultant shortcut still targets: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\my.exe If a set the shortcut to target the [SD] folder directly, I get: C:\Documents and Settings\Administrator\Local Settings\Temp The source Directory is d:\app_na...

srm2710

Thank so much for replying - great product. I implemented your advice but the resultant shortcut points to c:\(app name.exe), as if the [sourcedir] property didn't "take". The [sourcedir] \setup folder is not immediately the c:\ root; it is someway 'up' the d:\ drive folder structure. In C...

srm2710

This is also of importance to our use of the product to create a client-server install package. We have seperate installs for server files and client files, the latter being installed from a \setup directory. Ideally, the shortcut should point one level 'up' (ie closer to the drive root) from the \s...

Suggested Articles

User Guide

Videos

Search found 13 matches

Vista: pointing shortcuts to [SourceDir] property

writing a dll/code is crazy

suggestion on file versioning

i am also registering activeX exe

Resolved

footnote

cancel this

Many thanks

shortcut point back towards directory containing setup files

Caphyon Products

Company

Product

Resources

Free Tools

Connect