A fresh install with my .msi will install the the font files as expected in a sub-directory of my installation, and register them with the system. But when I upgrade my product, which is a major upgrade, we uninstall the old software, and perform an installation with the new SW -- but in doing so the font files are not installed. As mentioned in the title, I am using the upgrade table (min/max, etc.). I'm really at a loss as to why this happens. Can any one shed any light on this phenomenon? ... View more

Hi have a single single .ISM Basic MSI project. Under releases I have 2 different targets: 64bit, and 64bit-BETA. Each release needs to target a differently named installation directory. For example: c:\program files\MYPRODUCT and c:\program files\MYPRODUCT-BETA What's the easiest way to accomplish this? I probably have glossed over the right way to do it and got mired in the wrong way ... but what I had done was to add different release flags to each of the releases: then during the install, if BETA -- add "-BETA" to the installation directory. But I'm sure you will spot the problem right away. Changing INSTALLDIR after CostFinalize doesn't update all properties derived from INSTALLDIR (not quite sure how the UI Dialog figures out how to do it when manually changing the install directory!). Before CostFinalize, I don't know what the base (or original) installation directory is. If I could extract before CostFinalize, I'm OK with that. Thanks, Wim ... View more

I inherited a number of basic MSI projects. One of the projects, after install, has an UninstallString of "MsiExec.exe /X{productcode}" while the other one has "MsiExec.exe /I{productcode}". Can anyone tell me what controls the generation of the switch /I or /X? What wouldn't I always want /X in the uninstall string? Thanks, Wim ... View more

I have moved all the heavy lifting of some security operations into a C++ DLL. I have put the dll into a binary table in the Basic MSI. I have created a MSI type 1 custom action, Immediate Execution, to call my DLL's only function. My question is because this is a C++ DLL, the name is mangled. The definition of the function is: INT __stdcall MSIHelper::SetSeLogon( MSIHANDLE hModule ) I've tried to use demangled variants as the custom actions function name: SetSeLogin MSIHelper::SetSeLogon I've also tried a mangled name (gotten from the VS linker dump of the .dll): ?SetSeLogon@MSIHelper@@SGHK@Z None work, and all give the same 1723 pop-up error. For completeness, here is a dump of the .lib and .dll portions that are relevant: Section contains the following exports for MSIHelperDLL.dll 00000000 characteristics 515DDF7B time date stamp Thu Apr 04 13:15:55 2013 0.00 version 1 ordinal base 1 number of functions 1 number of names ordinal hint RVA name 1 0 00011019 ?SetSeLogon@MSIHelper@@SGHK@Z = @ILT+20(?SetSeLogon@MSIHelper@@SGHK@Z) And the .lib: 5 public symbols 4 ?SetSeLogon@MSIHelper@@SGHK@Z 1 __IMPORT_DESCRIPTOR_MSIHelper 2 __NULL_IMPORT_DESCRIPTOR 4 __imp_?SetSeLogon@MSIHelper@@SGHK@Z 3 ⌂MSIHelper_NULL_THUNK_DATA ... Version : 0 Machine : 14C (x86) TimeDateStamp: 515DE308 Thu Apr 04 13:31:04 2013 SizeOfData : 00000038 DLL name : MSIHelper.dll Symbol name : ?SetSeLogon@MSIHelper@@SGHK@Z (public: static int __stdcall MSIHelper::SetSeLogon(unsigned long)) Type : code Name type : name Hint : 0 Name : ?SetSeLogon@MSIHelper@@SGHK@Z Exports ordinal name ?SetSeLogon@MSIHelper@@SGHK@Z (public: static int __stdcall MSIHelper::SetSeLogon(unsigned long)) I'm not sure what other options to try. Any suggestions is appreciated. Wim ... View more

I need to set a local account right. This uses the advapi32 LsaOpenPolicy(), LookupAccountNameA(), and LsaAddAccountRights(). I cannot figure out how to accurately prototype and use these functions. I've gone through a couple of incantations, but am stymied by the very first method LsaOpenPolicy() -- the behavior is that upon making the invocation, instead of returning, the function that contains this code is exited -- if I didn't know any better, I would suspect the invocation gets an exception, trapped by IS and then cleans up. So I have very little visibility as to what is going on. This is being done inside a Basic MSI project. The prototypes (currently) look like this: prototype LONG AdvApi32.LookupAccountNameA(BYREF STRING, BYREF STRING, BYREF STRING, BYREF INT, BYREF STRING, BYREF STRING, BYREF INT); prototype LONG AdvApi32.LsaAddAccountRights(POINTER, BYREF STRING, POINTER, LONG); prototype LONG AdvApi32.LsaClose(POINTER); prototype LONG AdvApi32.LsaOpenPolicy(BYREF STRING, POINTER, LONG, POINTER); The invoking code (currently) looks like this: nvOSResult = LsaOpenPolicy(IS_NULLSTR_PTR, &array, POLICY_CREATE_ACCOUNT | POLICY_LOOKUP_NAMES, &pPolicy); if (nvOSResult == 0) then szSIDsize = 255; // lookup on local machine -- this *might* have to change? nvOSResult = LookupAccountNameA(IS_NULLSTR_PTR, szUsername, szSID, szSIDsize, IS_NULLSTR_PTR, IS_NULLSTR_PTR, szUse); if (nvOSResult != 0) then unicode(0) = "SeServiceLogonRight"; nvOSResult = LsaAddAccountRights(pPolicy, szSID, unicode, 1); if (nvOSResult != 0) then _Logger(hMSI, methodName, "Failed to add service logon rights", INFORMATION, FALSE); endif; else _Logger(hMSI, methodName, "Failed to lookup account name to establish service logon rights", INFORMATION, FALSE); endif; LsaClose(pPolicy); else _Logger(hMSI, methodName, "Failed to open the LSA policy to establish service logon rights", INFORMATION, FALSE); endif; If anyone has had any success or experience with any of the LSA functions, please show me the way! Thanks, Wim ... View more