Surprisingly, this does not exist on github or I couldn't find it anywhere else by google either. Can you upload it on github? Or I can do that so it can easily be found and updated too. ... View more

The relinking issue I believe stems from using mapped drives. With Win7 there is an issue that the mapped drives don't connect immediately at startup due to network connection and Windows reports an error. I think it has something to do with that and how InstallShield tries to access the path. The past few releases this has stopped since using the absolute path and restarting the VM multiple times. The double UI issue may also stem from using a mapped drive path rather than the absolute path also but I'm not sure. I'm debating to test this theory... ... View more

I would think a little build automation could call regasm /refile, scrape and transform the data then use the IS Automation Interface to emit it into the project before building. I don't know that I'd spend the $ on that though. As for conversion, I just might know an affordable part time / remote resource to assist with that project. :cool: ... View more

So I've sort of figured out a workaround... and sort encountered another problem. Part of the issue is that I was using FeatureSelectNew( MEDIA, TRUE ) which only selects new features in the current running installer and then FeatureReinstall() which only plants the files from those already installed features to the system. This is why I had both the old deleted files and the new ones in the same installed directory. Removed that and figured out that I need to unselect those already installed features in order to remove those installed files and place in the new ones. I already had a method that came from bastardizing the OnMoveData() method into only uninstalling and handles nothing else. This is mostly so I could support installation logic in the spec... not a great idea but I needed it that way in order to bypass a few things... So I ended up with this more or less: //--- Uninstall current version (if failed then abort installation) if (!PerformActualUninstall()) then abort; endif; //--- Select all current feature FeatureSetupTypeSet(MEDIA, "Complete"); //--- Set up OS specific features if(!PrepareInstallation()) then MessageBox(@IDS_ERROR_PREPARE_INSTALLATION_MSG, SEVERE); abort; endif; So now my problem is that when I can FeatureRemoveAllInLogOnly() and then FeatureTransferData(MEDIA) it completely uninstalls the application even though I later call FeatureSetupTypeSet(MEDIA, "Complete") and then FeatureTransferData(MEDIA) again. By completely uninstall I mean that when I go to uninstall via Add/Remove, it gives me the error stating that it was already uninstalled. ANY HELP IS APPRECIATED... ... View more

DP, Hmm, just curious, since your automation would have to edit the contents of that tab anyway, so thought it might be able to write the value to a text file instead. If it's pure InstallScript, and passing arguments to setup.exe is an option, you can use the /z switch on the outside, and CMDLINE on the inside. If it's an option to use InstallShield's Automation interface before a build, you might be able to use the ProductVersion property of ISWiProject, or otherwise use ISWiStringEntry to set a string-table entry that the script can read with @SOMETHING_SOMETHING. Robert ... View more

So I stumbled upon OnShowUI(). I feel like a god now. Overriding OnShowUI() will give me full control over the installation. Now I do not have to rely on IS to throw these events in order to deal with them. Now I only need to figure out how to determine if this execution is a first-time installation, Add/Remove call to repair or uninstallation or a cmdline Uninstallation... This helps me suppress unwanted dialog and simulate a silent install/uninstall for when embedding this installer within another and still be able to pop-up error messages (as "/s" will suppress ALL dialogs even error messages). I will update soon for prosperity... ... View more

From the hlep manual (just found): Error code: -6653 A feature in the setup contains more than 800 components. There is a maximum limit of 1600 components per feature using Windows NT/Windows 2000 and a maximum limit of 800 components per feature using Windows 95 and Windows 98. So there is a limit but I literally have 50 features (never more than 3 deep) and 66 components. So it looks like I'm nowhere near the Feature Limitation. Also found a listing of (un)documented limitations of MSI but I'm not sure if all of these pretain to InstallScript projects too. I've still not found any original threads or postings about this issue. I do not believe this is something isolates nor something I 100% introduced since I built this from the ground up in 2010. Any help, hack, or even someone who has experienced this will greatly help me (or at least not drive me to drink, lol). ... View more

If it's an external command there is IA built-in support for that. If you need to connect to some SQL server, be that on the same machine, things get a little more complicated. ... View more

Maybe my post wasn't clear and I apologize for that... I want a tool that will output to a file (.txt, .xml, etc) of every file, component, and their intended installation path that I can then parse to determine what files need to be verified within an installation including the new files that I have added to the installation project. I can't really create a patch project on top of our installer. Plus then I would need to output those files to keep my verification application current and relevant. ... View more

You are a genius! I took your advice. I created a component containing the .ttf font files to deploy, just as I had before. The Destination property for this component is . Important note to others here, I used the Files and Folders view to drop files into the Windows\Fonts destination. This also creates entries in the Fonts table. Next I created a registry set for the fonts in the component and associated the set with the fonts component. It was simply a matter of creating the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts key and then dragging the correct font entries from the source computer's registry into the Destination computer's registry data for the key. Next I added code for the DefaultFeature_Installed event adapted as follows. //------------------------------------------------------------------------- // The Installed event is sent after the feature DefaultFeature // is installed. //------------------------------------------------------------------------- export prototype DefaultFeature_Installed(); function DefaultFeature_Installed() string szFontName; number nResult; begin szFontName = "SAMPLE.TTF"; nResult = RemoveFontResource(szFontName); nResult = AddFontResource(szFontName); ... Other fonts added the same way ... end; That is all it took! It works in both the 32 and 64 bit installations. Thanks - Richard ... View more

So I've basically ruled out the order thing since I've made the DLLs and OCX files the first to be installed and presumably the first uninstalled (these files do not need to be registered/unregisterd in a specific order and I have verified this with the my development team). The files appear to have been removed before the unregister takes place unless the errors are hidden until the removal process is complete but this seems far fetched. Does UninstallShield wait until the files are removed BEFORE unregistering them? Or am I missing something here or it this a setting somewhere? ... View more

No it's more for scripting the repair procedure. I don't want to fix environmental issue as we've seen with this issue. More like a brute force fix... ... View more

If nothing else, perhaps you could use the InstallShield automation interface to read property values and then feed them back to ISProductConfig.SetupFileName before building. ... View more

Forgive me for this large response. I figure someone out there may need a full answer because Gods know that if someone wrote this before me I would not have had to start this post. Aladdin's response was that there is no flag for a silent removal using HASP SRM Run-time Environment Removal Tool (aksinstdel_windows.exe). But they did give me an undocumented switch for HASP SRM Run-time Command-line Installation (Haspdinst.exe). The switch is "-purge". This command removes the HASP environment and can use the other optional switches for a silent or as close to silent as possible removal. Using "-purge -nomsg" or "-purge -criticalmsg" will work for a silent uninstall. 😄 YAY! This made my day! Thank you everyone for your responses! ... View more

Thank you, I appreciate the response. Now I can tell my boss that this wasn't something I did! ... View more