About DemonPiggies

DemonPiggies · ‎Jan 05, 2011

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.

DemonPiggies · ‎Dec 27, 2010

Is there a tool, scraper or feature that can output (to a file of some sort) every file/component/feature and their intended path? I've built an installation verification app that checks to see if all files and settings have been installed properly. Whenever I add something to the installation I have to add it manually to my little application. I'm looking for something that can run through my installation project and output each filename (preferably with each component and/or feature) and it's intended install path. I'll even settle for just the feature/component and the filename if the path is irretrievable. My project is set to save a XML but I really don't have the patience to build a scraper to go through it...

DemonPiggies · ‎Dec 21, 2010

True but that would launch the app before setup was complete. In my application I ask if they want to launch the app in the Finish dialog and then in OnEnd() I check to see if they chose to or not and launch it if they chose to.

DemonPiggies · ‎Dec 15, 2010

Currently I'm using 'AddFontResource' and manually installing fonts to the registry. For whatever reason one of the fonts is now not printing. This may have to do with the embedding restrictions and we are looking into this but that aside what are we actually supposed to use in order to properly install a font on a user's system. In our old installer which was converted up from InstallShield 6 (which I later learned you can't really do because certain features that weren't in 6 and would be missing in the up-conversion...) these fonts printed correctly in XP, Vista, and Win7. Now after building the installer from the ground up in 2010, this font will NOT print at all. If we change the font to ANYTHING else it will print. This is a sample of my code: function RegisterFonts() . . . begin //--- Initialize KEY szKey ="SOFTWARE\\MICROSOFT\\WINDOWS"; //--- Determine Operating System GetSystemInfo ( OS , nResult , svResult ); if(nResult = IS_WINDOWSNT) then szKey = szKey+" NT"; endif; szKey = szKey+"\\CURRENTVERSION\\FONTS"; RegDBSetDefaultRoot ( HKEY_LOCAL_MACHINE ); //--- Make Registry entries //--- SampleFont.TTF RegDBSetKeyValueEx(szKey,"Sample FOnt (TrueType)", REGDB_STRING, "SampleFont.TTF",-1); //--- Add these fonts to the system font table szFontName = SampleFont.TTF; nResult = RemoveFontResourceA(szFontName); nResult = AddFontResourceA(szFontName) end; Searching the interwebs I found 'RegisterFontResource' and 'RemoveFontResource'. Are we now supposed to be using those methods or is my current code above still 100% valid here? Or is there some other way to correctly install (again using InstallScript so MSI options won't work here)? I'm going to test these other methods to see what happens but it won't explain the why or how...

DemonPiggies · ‎Dec 15, 2010

So if you include both and let InstallShield register them, you get the error, right? Check your options to see how InstallShield is registering them. Under the Preferences tab there is a section called 'Self-Registration.' You may need to try playing with those settings to see which one works for you. I had a similar issue with my project where non-.Net dlls were erroring out when InstallShield installed them. Originally we had to manually register these files in the script but after finding an explanation online about the 'Self-Registration' tab we pieced it together. Hope that helps abit...

DemonPiggies · ‎Dec 15, 2010

If you are using script to do this you can use the 'LaunchApp' method... /*--- code used in the OnEnd() method ---*/ //--- hh.exe is the microsoft help html file viewer... if (LaunchApp( "hh.exe", strPathToLaunch) < 0) then //--- Pop up error message if unable to launch application MessageBox( @IDS_ERROR_UNABLE_TO_OPEN_HELP_FILE, WARNING); endif; ... figured I'd add that in case someone using InstallScript or using script for a custom action read this post. For a more detailed description see this article.

DemonPiggies · ‎Dec 15, 2010

Currently I only do 'releases' not upgrades but I use the same project and just update the release numbers. There is no real reason to create a new project for each release. You could create an 'update project' and then a 'release project' but I believe somewhere in the 'settings' there is an option that allows your project to update and/or release. I think somewhere in the Help file there is a clearer explanation. I'm not saying 'rtfm' just that there might be a more readable answer there. I know there is an option because I once unwisely used it for my project and screwed everything up. You also use the Overwrite options in the components section...

DemonPiggies · ‎Jul 13, 2010

andy928, What type of project are you using? I'm using InstallScript and with that I unselected both Features (separate features for each file) and only selected them (in code) dependent on user interactions. I used this to determine which formated file the user was given... I can't really help you much if you're using a MSI project...

DemonPiggies · ‎May 26, 2010

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

DemonPiggies · ‎May 26, 2010

Then how would we update system components that need updating? Wait for Microsoft to patch it? I'm just wondering because of the DLLs and OCX's we need are version specific.

DemonPiggies · ‎May 26, 2010

Yeah I've looked through the Flexara site but I have yet to find a step by step guide to build a (all be it generic) release. The help file is useful if you already mostly know what you are doing. Unfortunately I agree with rittjc about there not being enough information in the forum and/or the help file (I agree with the argument but not the whole lazy American rant because that's just rude). Anyway if there is a tutorial on there please send me the link I would be most grateful since I still have questions about my current release project.

DemonPiggies · ‎May 25, 2010

I was wondering this too but the help file says: Only one splash screen is displayed to the end user during the installation. If you have more than one splash screen file in the language-independent area or for a specific language, the first file in the list is displayed at run time. I have a three differential releases and two require the same screen. The only real workaround is to add a file with a generic file name (e.i. "Setup.bmp") and rename the bitmap you need per release. Essentially using the same file but changing the actual graphic. 😞 not elegant but it works well. I even made a batch file to do this. You could create a exe to switch them when you make the installers in a specific sequence. I think that might be my next enhancement to my project.

DemonPiggies · ‎May 25, 2010

Not that I'm aware of. The included help file has a lot of information and there are tute.'s in there. Also http://www.installsite.org/ is a very good resource... If you find one let me know!

DemonPiggies · ‎May 25, 2010

Short answer is no. Found out the hard way that you cannot use a string (from the string table or path table) for use in naming the physical *.exe Thank you everyone for your responses...

DemonPiggies · ‎May 25, 2010

Though at this point there is no reason for me to do this but: I moved the XP only DLLs to their own component and used the options on the features to only install on certain OSs... Thought the issue was more the "Why suddenly is this happening on 2010 and not IS6?"

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Re: Verifying my installation...

Verifying my installation...

Re: InstallShield force applicatio launch

Proper way to install fonts (InstallScript)...

Re: Two self-registering dlls and InstallScript Setup Launcher problem

Re: InstallShield force applicatio launch

Re: "Noob" question - how you're supposed to work in InstallShield

Re: How to create a condition of installing one of two files

Re: Vista only issue after upgrade to 2010...

Re: Vista only issue after upgrade to 2010...

Re: Beginning-to-end tutorial

Re: different splash screen to different releases

Re: Beginning-to-end tutorial

Re: Using String in 'Single Exe File Name'...

Re: Vista only issue after upgrade to 2010...

Re: Signing Issue

Signing Issue

Re: [BUG?] Registering x86 .NET DLLs on a x64 machine

Re: [BUG?] Registering x86 .NET DLLs on a x64 machine

[BUG?] Registering x86 .NET DLLs on a x64 machine

Re: Is it possible to define a language transform for LoadStringFromStringTable?

Re: Customize uninstall of software

Re: Or Installation conditions

Re: Is it possible to define a language transform for LoadStringFromStringTable?

Re: InstallScript - Devs added/removed file from Component Directory...