Jan 20, 2012
07:20 PM
Has anyone actually implemented any code successfully with these functions?
... View more
Jan 20, 2012
07:18 PM
Unfortunately, I cannot prototype the necessary windows API functions successfully in InstallScript. They don't work. Two are required, plus a struct. Installshield seems to be inadquate to the task of implementing the Windows API in this instance. As someone else pointed out, it does not understand string pointers. prototype BOOL Advapi32.LookupAccountSidA(POINTER, POINTER, POINTER, POINTER, POINTER, POINTER, POINTER); prototype BOOL Advapi32.ConvertStringSidToSidA(POINTER,POINTER); And the second function’s second parameter is a pointer to a SID structure.
... View more
Dec 23, 2011
04:20 PM
Here is the Windows API function that is needed. I was having trouble finding it on the Microsoft site, but eventually (with the help of someone else at work), it turned up: http://msdn.microsoft.com/en-us/library/windows/desktop/aa379166%28v=vs.85%29.aspx
... View more
Dec 22, 2011
10:28 PM
I need an InstallScript equivalent of the following function for getting the language-specific "User" group NAME from it's standard windows Security Identifier (S-1-5-32-545). I need to implement it in InstallScript in a software installer. The problem is that depending on than language of the operating system, the name of the "Users" group can be different. The company does not want to fork the installations to full language editions, since we don't have enough customers in each. However, if we can make small modifications (like permissions in the language of the operating system here), we can get by. Anyone of any help? Has anyone seen such a thing? What DLL would be called to engage the functionality? Does the function etNameFromSID() even exist outside of C Sharp? string GetNameFromSID( SecurityIdentifier sid ) { NTAccount ntAccount = (NTAccount)sid.Translate( typeof( NTAccount ) ); return ntAccount.ToString(); } .
... View more
Labels
- Labels:
-
InstallShield 2011
Sep 28, 2011
03:51 PM
This is not quite what I am looking for if the files still "have to be in source." What we are looking for is the ability to PULL some of the files OUT of the uncompressed source folder (deliberately) and NOT have the installer complain that they are missing. We want our users to be able to decide which of the "knowlege base" files they want to include in their installations. Our kbases configure default project type estimates based on historical data. Some types of kbases apply to some customers, others to other customers.
... View more
Aug 30, 2011
01:06 PM
I guess what I am looking for is a THIRD option to set in the File table attributes. There are only two options. One is file critical, in which case the installer quits if it is missing. The other is file missing but not critical, in which case a dialog pops that allows you to IGNORE. A third option would be file missing, but intentionally, and NO error dialog appears. File Table, Attributes column: Constant Hexadecimal Decimal Description msidbFileAttributesVital 0x000200 512 The file is vital for the accurate operation of the component to which it belongs. If the installation of a file with the msidbFileAttributesVital attribute fails, the installation stops and is rolled back. In this case, the Installer displays a dialog box without an Ignore button. If this attribute is not set, and the installation of the file fails, the Installer displays a dialog box with an Ignore button. In this case, the user can choose to ignore the failure to install the file and continue.
... View more
Aug 24, 2011
09:41 PM
My company wants to leave our knowledge base files in an uncompressed directory on the CD or media folder so that users can pick and choose which ones they wish to install. The only problem there is that when you remove a file that has been configured into an MSI component, the installer gives you a "file not found" (1308) error. That file not found dialog allows you to continue with the installation, but I know what they really want is to SUPPRESS the dialog in case CERTAIN files are missing. I'm trying to think that one through. Is there a way to capture the the 1308 error, tell WHAT file caused it, and then suppress the error dialog (let the installer go on as if the user pressed IGNORE?). I seriously DOUBT it. It seems like they are asking for something that is beyond the limits of starndard MSI installer behavior and that would require custom programming. (One liability of complete customization is that if you dispense with MSI and just copy files from a folder on the media, you toss away the ability of the installer to check and update files automatically).
... View more
Labels
- Labels:
-
InstallShield 2011
Jul 01, 2011
02:27 PM
It must have had something to do with migrate feature states during minor upgrade. The installer was not migrating the APPDATA directory value; it was resetting it as default INSTALLDIR. I don't know why. It might be because the one component that used that directory had only one file (the raw INI for the program, which the program then configures for individual users when they start up from their profiles). In any case, I did not notice that we had a problem migrating the directory in InstallShield 2008. The solution here was to just let the installer do what it wanted and then RESET the DIRECTORY as INSTALLDIR ^ "AppData" (this is always the value) with a directory custom action after MigrateFeatureStates.
... View more
Jun 30, 2011
10:29 PM
Here's the verbose log entry where the error is occuring. MSI (s) (0C:24) [20:13:51:148]: PROPERTY CHANGE: Modifying APPDATA property. Its current value is 'C:\Program Files\SEER\SEER-H 7.1\AppData'. Its new value: 'C:\Program Files\SEER\SEER-H 7.1'. My question is what action is that associated with? It Occurs after CostFinalize, when there are a bunch of property change actions. MSI (s) (0C:24) [20:13:51:148]: Doing action: CostFinalize Action ended 20:13:51: IsolateComponents. Return value 0. But nothing in the InstallScript actually SETS the APPDATA directory property to the application's ProgramFiles directory. It just seems to be "happening."
... View more
Jun 30, 2011
09:59 PM
I have converted an InstallShield 2008 InstallScript-MSI project to 2011. Without having done anything to Minor Upgrade, suddenly one of the directories is being RESET to the default INSTALLDIR during Minor Upgrade. It should be something like INSTALLDIR ^ "datadirectory" (properly defined in the directory table). What makes me think this is a giant BUG is that I tested resetting the "CUSTOMDIR" property during OnResumeUIBefore and the directory is being reset AFTER that. This was not happening in any of the InstallShield 2008 installers we have. It is a KILLER bug. It basically ruins any ability to convert 2008 installers without ruining Minor Upgrade in them. And that would mean having to rebuild all installers from scratch?:(
... View more
Labels
- Labels:
-
InstallShield 2011
Mar 07, 2011
05:25 PM
That's good to know. As you can see, we skipped Installshield 2010, or I would have found out about this earlier. Now I can see all the old dialog scripts in ISRTScriptDialogs.rul I notice that CONVERTED 2008 projects give the following error when you try to select the drop-down option for cloning (?) dialog scripts: "This Project does not define support for adding dialog sources from the InstallScript Editor. Attempting to add dialog source throught the event list may result in compile errors. Support for dialog sources can be added by adding _ISSCRIPT_NEW_SYLE_DEFS to the preprocesor defines in Build-> Settings." I guess that means that InstallShield Engineers figure that the presense of new custom dialog scripts in a converted project COULD cause compile collisions. So, it sounds like either you should dump your custom dialogs and recreate them using the new method, or you should keep the old method and save the old scripts and/or copy the new dialog functions to your own scripts and create new defines if you have trouble. But it sounds like the preferred method is to redo all of your custom dialogs using the event list functions.
... View more
Mar 04, 2011
05:22 PM
I was looking for a copy of the AskPathDlg.rul script in Installshield 2011. It seems that all of the Dialog scripts are missing now. They used to be in the Script\isrt\src directory. All that is left THERE is a pathetically small number of SQL dialogs. Only the object library is now supplied for the other standard installscript dialogs. This means that new InstallShield users are going to have more difficulty CUSTOMIZING dialogs. And the rest of us will have to grab our old (in our case IS2008) dialog scripts and hope that they work. Is there a reason that installshield decided to make life harder? Do users have to pay a hefty user support fee in order to get access to "proprietary" Installshield dialog scripts now?
... View more
Labels
- Labels:
-
InstallShield 2011
Jan 06, 2011
04:29 PM
Okay, here's what's up. "Run once" doesn't really mean "run once." It means "run once if you find the action scheduled in more that one sequence . . . but don't run at all if you find it scheduled in one sequence" (the retarded part). So, if you configure an action in only one sequence, watch out for leaving it configured to "run once." Your human logic will stare at it and say, "Okay, nothing wrong with that." But some idiot MSI programmer at Microsoft who lives in Wonderland, invented his or her own conception of logic in which "run once" doesn't really mean "run once."
... View more
Jan 06, 2011
03:50 PM
MSI (s) (90:CC) [13:34:32:366]: Doing action: WriteSEERMetricsXMLFile Action 13:34:32: WriteSEERMetricsXMLFile. Action start 13:34:32: WriteSEERMetricsXMLFile. MSI (s) (90:CC) [13:34:32:366]: Skipping action due to msidbCustomActionTypeFirstSequence option. Action ended 13:34:32: WriteSEERMetricsXMLFile. Return value 0. What is msidbCustomActionTypeFirstSequence ? That seems to be what is derailing the action. I have not encountered that before. http://www.ureader.com/msg/1653396.aspx http://msdn.microsoft.com/library/en-us/msi/setup/custom_action_execution_scheduling_options.asp This SHOULD NOT BE OCCURING. The action is scheduled to execute ONCE, but it exists ONLY in the Execute Sequence. It is NOT configured for the UI sequence and clearly ISN'T running there. And the fact that it ran okay during uninstall should be indication enough that it is NOT erroneously configured for execute only once. This looks suspiciously like a BUG in MSI. OR: I don't NEED "Execute only once" since it is already ONLY in one sequence. It seems like that may be what is confusing the MSI engine. But you can see WHY one would want to "execute only once," since you don't want to try to overwrite a file that you just wrote.
... View more
Jan 06, 2011
02:44 PM
I'm starting by using a "Not Installed" condition because I want the file to be written only during installation anyway. Perhaps having a condition will "wake up" the custom action from its lethargic sleep (it is like my pothead nephew in Northern California, who smokes weed all day, refuses to look for a job, and never pays his bills . . . a worthless dysfunctional parasite). Then if that doesn't work, I'll generate and and check out the verbose log. Sometimes that isn't very helpful, I have found. But I need to check it. Thanks
... View more
Latest posts by Peter_Kosenko
Subject | Views | Posted |
---|---|---|
1039 | Jan 20, 2012 07:20 PM | |
1039 | Jan 20, 2012 07:18 PM | |
1039 | Dec 23, 2011 04:20 PM | |
4212 | Dec 22, 2011 10:28 PM | |
1051 | Sep 28, 2011 03:51 PM | |
1051 | Aug 30, 2011 01:06 PM | |
3023 | Aug 24, 2011 09:41 PM | |
882 | Jul 01, 2011 02:27 PM | |
882 | Jun 30, 2011 10:29 PM | |
2960 | Jun 30, 2011 09:59 PM |
Activity Feed
- Posted question on InstallShield Forum. Jan 20, 2012 07:20 PM
- Posted Unfortunately on InstallShield Forum. Jan 20, 2012 07:18 PM
- Posted Get Name from SID on InstallShield Forum. Dec 23, 2011 04:20 PM
- Posted Get Group name from standard Security ID? on InstallShield Forum. Dec 22, 2011 10:28 PM
- Posted Not what I'm looking for on InstallShield Forum. Sep 28, 2011 03:51 PM
- Posted A THIRD option would be nice for the file table on InstallShield Forum. Aug 30, 2011 01:06 PM
- Posted Suppress file missing dialog with uncompressed media files? on InstallShield Forum. Aug 24, 2011 09:41 PM
- Posted Minor Upgrade Migration on InstallShield Forum. Jul 01, 2011 02:27 PM
- Posted Verbose log shows an unscripted change on InstallShield Forum. Jun 30, 2011 10:29 PM
- Posted Installshield 2011 Minor Upgrade Directory bug? on InstallShield Forum. Jun 30, 2011 09:59 PM
- Posted Thanks on InstallShield Forum. Mar 07, 2011 05:25 PM
- Posted Missing Dialog Scripts in InstallShield 2011 on InstallShield Forum. Mar 04, 2011 05:22 PM
- Posted Retarded logic on InstallShield Forum. Jan 06, 2011 04:29 PM
- Posted msidbCustomActionTypeFirstSequence ????? on InstallShield Forum. Jan 06, 2011 03:50 PM
- Posted Both good suggestions on InstallShield Forum. Jan 06, 2011 02:44 PM
- Posted Custom Action will not Execute on InstallShield Forum. Jan 05, 2011 11:53 PM
- Posted Prevent setup.ilg from being created? on InstallShield Forum. Nov 30, 2010 06:34 PM
- Posted Re: Error 1603 during update in InstallScript MSI on InstallShield Forum. Oct 25, 2010 05:50 PM
- Posted VerGetFileVersion() on InstallShield Forum. Oct 14, 2010 06:52 PM
- Posted Thanks on InstallShield Forum. Oct 14, 2010 05:07 PM