Creating MSI Installer

I need to create an MSI installer rather than the setup.exe that LabVIEW creates. Is this possible please?
This suggests it is:
http://digital.ni.com/public.nsf/allkb/38E7B058DD6A2BB486256B3C004EDA4F
And this suggests it isn't:
http://forums.ni.com/t5/LabVIEW/build-MSI-of-labview-application/m-p/1649272/highlight/true#M591451
Thanks,
Martin

Hi Martin,
From looking into this so far, it doesn't appear like creating an MSI installer is possible? I'm investigating the suggestion provided by that KB, but can't seem to find the Installer Settings tab it mentions...
As far as I'm aware, the setup.exe is a bootlegger which calls the relevant installation msi's required once after checking if the system is compatible. A one-click installation msi appears to be a current suggestion in the Idea Exchange for the next iteration of LabVIEW, so hopefully it might get picked up as a suggestion for the upcoming release?
As far as I have been able to see so far, setup.exe seems to be the only option, but hopefully someone else might be able to point us in the right direction. I'll have another dig around and see what I can dig up

Similar Messages

PowerPoint add-in is not working when installed for All Users using msi installer.

Hi All,
I have created PowerPoint add-in using c#-vsto. I have created msi installer to install this add-in with following two options:
1. Just me
2. Everyone
However, add-in is not working properly (Events and custom task panes are not working).
I have created registry key as below
1. for "Everyone" : HKLM\Software\Microsoft\Office\Powerpoint\Addins\MyAdd-in
2. for Just me : HKPU\Software\Microsoft\Office\Powerpoint\Addins\MyAdd-in
But when I set InstallAllUsersVisible property to False (When add-in is installed only for current user ), then add-in works fine for current user.
Please let me know if anything is missing!!!
Thanks

Hi,
This is the forum to discuss questions and feedback for Microsoft Office, the issue is more related to develop the add-in, you'd better post your question to the MSDN forum for VSTO
http://social.msdn.microsoft.com/Forums/en-US/home?forum=vsto&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
George Zhao
TechNet Community Support

Deploying AAMEE 3.1 created MSI by double clicking it in UI mode

With the release of AAMEE 3.1, AAMEE created MSI supports both silent and UI based installation.
For UI based install of AAMEE 3.1 created packages, run the MSI as an administrator. If you are logged in as Admin user, you can double click it, otherwise right click the MSI and run as administrator. A minimalistic UI will be shown with just a progress bar. Any error during MSI install will cause a roll back and the user should check the logs to see what went wrong. You can also run the MSI in UI mode through this command line –
msiexec.exe /i <path of msi>
AAMEE still supports silent installation as the standard way of deploying the packages. Silent installation can be done only through the command line option –
msiexec.exe /i <path of msi> /qn.
Make sure that the command line is invoked with admin privileges. For users using SCCM 2007 for deploying AAMEE created packages, make sure to check “Allow users to interact with this program” checkbox in Environment tab of the SCCM Program for UI based installation. The corresponding checkbox for SCCM 2012 is “Allow users to view and interact with the program installation”.
For uninstallation of MSI in UI mode, there is only a command line option –
msiexec.exe /x <path of msi>
For silent uninstallation, add the /qn switch with the above command line –
msiexec.exe /x <path of msi> /qn
This UI based installation is only supported by the packages created using AAMEE 3.1. If you are using AAMEE 3.1 beta or AAMEE 3.0 for CS6 packaging, please download AAMEE 3.1 from http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html.
Feel free to mail me at [email protected] in case you see any issues.
Thanks,
Saransh Katariya | Member of technical staff | Adobe Systems | [email protected]

I want to revisit this. You can also see my related posts here:
http://forums.adobe.com/message/5073735
I had contented myself that I would use a batch file and require users to right-click and run as admin on the batch file. This was so that I could get Acrobat 10 installed at the same time. However, now that I have Acrobat 11, and I can separate out the installers, I would like to get back to this "double-click" method. I've verified that my new package (without Acrobat) works using the msiexec command. However, it still doesn't work as a double-click.
Here are the key lines from PDApp.log:
3/8/2013 07:54:21 [ERROR] Setup - Error parsing command line arguments at - "DISABLE_CCM_DESKTOPSHORTCUT".
Expected arguments are -
--mode=silent
--overrideFile="<FilePath>"
3/8/2013 07:54:21 [FATAL] Setup - Administrative Privileges required to continue
3/8/2013 07:54:21 [FATAL] Setup - End Adobe Setup. Exit code: -10
However, I am an admin on the machine, just as I am on all the machines that I've tested this on. And when I use a batch file with the msiexec and right-click and run as admin, I don't have to put other credentials in, verifying that I am, in fact, an admin on the machine.
Thanks for your assistance.
Mark

I'm getting an "Error 1003 occurred at Open VI Reference in Dist Call Create Installer.vi- Build Application.vi." whenever I try to create an installer for my app.

I'm running LabVIEW 6.1 on Win XP Pro, and my application
builds fine, but I can't create an installer.

Dependency Walker will show all of the DLLs NIMSIDistKit.dll is dependent on. There is a tree view in the top but the flat list at the bottom will probably be more helpful. It should show the following dlls (at least on a Windows 2000 system):
ADVAPI32.DLL
GDI32.DLL
KERNEL32.DLL
MSI.DLL
NIMSIDISTKIT.DLL
NTDLL.DLL
OLE32.DLL
RPCRT4.DLL
USER32.DLL
If one of these DLLs is missing it will have an error message displayed beside it. I think all of them are regular Windows DLLs so if you are missing one of them your computer might be having other problems. You could try to reinstall LabVIEW to see if it will install a copy of the dll, but you might have to reinstall Internet Explorer or some portion of the OS to get all
of them.
Probably the most important dll is the MSI.dll. If it is missing or too old it might be the problem. I have version 2.0 but I think version 1.1 of this DLL will also work. If you don't have the dll or the right version run \applibs\distkit\redist\InstMsiW.exe (if on Win NT/2000/XP) or InstMsi.exe (95/98/ME). This will install/update MSI (Microsoft Installer) on your machine.
You can also press F9 to toggle showing just the filename and the whole path to the dlls. Besides NIMSIDistKit.dll all of them should be loading from your system folder. If not you may have multiple copies of that DLL and the correct one is not being found.

MSI installer closes with error 1327, Invalid drive on Win 7 Ultimate when My Documents is moved to a network drive

I have several computers with Windows 7 Ultimate installed here at the Pioneer Library System. We have ~20 workstations running XP Pro on a Active Directory domain and are planning on rolling out Windows 7 this fall. I am running Windows 7 to test our programs
(have since RC1) but I am running into an issue when installing software.
The problem I am running into is that when I try to install any program that uses the MSI installer on Windows 7 , it fails with a 1327 error at the point where it is preparing to install and says "Invalid Drive H:\".
All the users in our domain have the "Home Folder" on their active directory profile set to
H:\ (which is mapped to \\PrimaryDC\user$ in the same place). We have also moved the
C:\Users\user\Documents folder to H:\ so as to keep all documents on the server where they get backed up regularly.
If I move "Documents" back to C:\Users\user\Documents the MSI installer works fine. When I look into the registry as suggested in
this thread I found that in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders " and in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders " the key "Personal" points to "H:\".
But, H:\ is a valid connected network drive. Installing from the same account on an XP computer with
C:\Documents and Settings\user\My Documents moved to the H:\ drive works fine.
I have tried setting up another 7 machine and get exactly the same results on it.
Is there a workaround for this besides creating a admin account that does not have Documents mapped to the network drive
H:\ to use for installing programs?
Thanks
Aaron Z
PLS

I do not have the option with some of these files to pass parameters to the MSI installer. For example, if I download the Acrobat Reader installer from http://ardownload.adobe.com/pub/adobe/reader/win/9.x/9.3/enu/AdbeRdr930_en_US.exe and run AdbeRdr930_en_US.exe
it extracts the MSI file to C:\Users\USER\AppData\Local\Adobe\Reader 9.3\Setup Files and then runs it.
To reproduce this an a Windows 7 computer (does not have to be on a domain):
Prep Work:
Create a user (test1)
Create a folder on the root of C (C:\Test)
Set permissions on C:\Test to allow the test1 user to have full access to it
Share the C:\Test folder as test1 (again, set the permissions to allow the test1 user full access)
Set the "Home Folder" for the test1 user connect to Z: and point that to \\127.0.0.1\test1
Login as test1
Check that you have Z:\ mapped and that it works
Check that it works:
Install Acrobat Reader 9.3 from the link above
Note that it works
Uninstall Acrobat Reader 9.3 using "Programs and Features"
Break it:
Login as test1
Check that you have Z:\ mapped and that it works
Go to C:\Users\test1
Right click on the Documents folder and click on properties
Click on the Location tab
Click on "Browse" and select the Z drive
Allow Windows to move the files to the new location
Check that it is broken:
Check that you have access to the new Documents folder at Z:\
Install Acrobat Reader 9.3 from the link above
Note that it extracts itself to C:\Users\test1\AppData\Local\Adobe\Reader 9.3\Setup Files
and runs the MSI installer from there
Note that after the MSI installer is started it pops up an error saying Error: 1327, Invalid drive Z:\.
I also see this with various other install programs (VMWare vSphere Client, VMWare Player and Kaspersky Antivirus for example)
Is there any reason why this should not work? Is there something that I should be doing differently?
Thanks
Aaron Z

Issues with Shockwave 11.5.2.602 / 11.5.6.606 MSI installer

<UPDATE 8/3/09> Nearly all of the issues mentioned below are still present in the MSI installer for 11.5.6.606 - the only one that Adobe have fixed is the one where the MozillaPlugins 'Version' value is left blank by the MSI by default - this is now created correctly, but all of the other issues remain.
Personally I have given up trying to use this MSI package to deploy Shockwave until Adobe get their act together - instead I am using a wrapper to wrap the Shockwave executable inside an MSI file and deploying it that way, although this is not ideal.
I have created an MST file which will fix the MSI installer for version 11.5.6.606, which I will post to another forum shortly, but I am not planning to keep it updated for future versions as I don't really have the time.
Hi,
I've tried submitting the following via the Adobe Customer Support portal and via the Feature Request/Bug Report form, but the first told me that I needed to 'get in touch with Adobe Enterprise Solutions team for getting help' and that 'to get in touch with them you have to purchase a contract', and the second resulted in a bounced email address saying that '[email protected]' 'does not exist at the organization this message was sent to'.
In short, attempting to contact Adobe to report issues with their installers sucks, and I am posting this here in the vain hope that someone at Adobe might read this message and possibly forward it to the relevant people. Some of the issues have already been reported here on this forum, but some of them are new, and I guess others might be interested in them too.
Hi,
I would like to report some issues with most recent version of the Shockwave installer, available in MSI format from the following location:
http://www.adobe.com/cfusion/entitlement/index.cfm?k=4E6102EB-DA7C-2795-C744826EFDE2A098&l oc=en_us
This is the installer for version 11.5.2.602, with a digital signature dated 06 November 2009 10:52:21
When downloading this version of the installer in Windows Installer (MSI) format, the following issues manifest themselves, most of which are not a problem when using the Full EXE installer available from the same page.
First of all, when installing the MSI file using Group Policy Software Deployment, if you log on to the computer after the MSI file has been deployed and view a web page that contains Shockwave content, you receive the following errors in the Windows event log:
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 16/12/2009
Time: 16:51:23
User: CRGS\DefaultUser
Computer: ITO01
Description:
Detection of product '{7D0F2155-D7D3-42CE-903F-684ADD77FF89}', feature 'Adobe_Shockwave_Player_', component '{E89F323D-7BDB-46E1-A0FD-6227821F94EA}' failed. The resource 'C:\WINDOWS\system32\config\systemprofile\Application Data\Adobe\' does not exist.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 16/12/2009
Time: 16:51:23
User: CRGS\DefaultUser
Computer: ITO01
Description:
Detection of product '{7D0F2155-D7D3-42CE-903F-684ADD77FF89}', feature 'Adobe_Shockwave_Player_' failed during request for component '{3D3697FC-DB90-46D8-9ED4-5D54B4901F62}'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
If you are logged on as an Administrator, then the computer will immediately attempt to 'repair' the Adobe Shockwave Player installation in order to create the missing folder 'C:\WINDOWS\system32\config\systemprofile\Application Data\Adobe\', which leads to a significant delay in the initialization of the Shockwave content on the web page. If you are logged on as a non-Administrator, the errors will still appear, but the 'repair' operation will fail due to insufficient permissions to create the above folder.
I have done some testing and it seems as if this problem can be easily resolved by removing the code from the installer which tells it to create an empty folder in the 'Application Data' folder called 'Adobe\Shockwave Player 11'. This code seems to be entirely unnecessary, as no files are created inside this folder as part of the installation, and I have removed it successfully from my own copy of the MSI without it causing any issues. I have found some other people who are also experiencing this problem in the following forum post:
http://forums.adobe.com/message/2379350 (post number 8)
and since this 'repair' operation causes all customised registry settings to be reset back to defaults as part of the repair, it would be very helpful if this 'feature' could be removed from future versions.
Secondly, there are a number of registry keys which are created incorrectly by the MSI installer when the above 'repair' operation takes place, which need to be corrected to prevent further issues from occurring:
Under '[HKEY_CLASSES_ROOT\CLSID\{1F3CB77D-D339-49e0-B8E4-FECD6D6F8CB8}\LocalServer32]', the 'default' value is set to the following by the MSI:
C:\WINDOWS\system32\Adobe\SHOCKW~1\SWHELP~1.EXE"
(Please note that there is a double quotation mark at the end of the value, but not at the beginning)
Whereas the executable installer creates the value as follows:
"C:\WINDOWS\system32\Adobe\Shockwave 11\SwHelper_1152602.exe"
According to a forum post (http://forums.adobe.com/message/2379350, post 15), this causes DCOM errors when Shockwave is launched, if the MSI 'repair' has taken place as described above.
The above registry value should be set to the following in the installer's Registry table:
"[INSTALLDIR]Shockwave 11\SwHelper_1152602.exe"
so that the MSI installer works the same as the executable one.
Under '[HKEY_CLASSES_ROOT\TypeLib\{6EF568F4-D437-4466-AA63-A3645136D93E}\1.0\0\win32]', the 'default' value is set to the following by the MSI:
Adobe\SHOCKW~1\SWHELP~1.EXE
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Adobe\Shockwave 11\SwHelper_1152602.exe
Also, under '[HKEY_CLASSES_ROOT\TypeLib\{6EF568F4-D437-4466-AA63-A3645136D93E}\1.0\HELPDIR]', the 'default' value is set to the following by the MSI:
Adobe\SHOCKW~1\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Adobe\Shockwave 11\
Once again, the above registry values should be set to the following in the installer's Registry table to fix the issue:
[SystemFolder]Adobe\Shockwave 11\SwHelper_1152602.exe
[SystemFolder]Adobe\Shockwave 11\
Under '[HKEY_CLASSES_ROOT\CLSID\{166B1BCA-3F9C-11CF-8075-444553540000}]', the 'default' value is NOT SET by the MSI by default:
Whereas the executable installer creates the value as follows:
Shockwave ActiveX Control
This value should be set in the installer's Registry table to fix the issue.
Under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\common]', the 'default' value is set to the following by the MSI:
Macromed\common\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\common\
Also, under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\coreplayer]', the 'default' value is set to the following by the MSI:
Macromed\Shockwave 10\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\Shockwave 10\
Also, under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\coreplayerxtras]', the 'default' value is set to the following by the MSI:
Macromed\Shockwave 10\xtras\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\Shockwave 10\xtras\
The above registry values should be set to the following in the installer's Registry table to fix the issue:
[SystemFolder]Macromed\common\
[SystemFolder]Macromed\Shockwave 10\
[SystemFolder]Macromed\Shockwave 10\xtras\
The MSI installer does not create '[HKEY_CLASSES_ROOT\.dcr]', '[HKEY_CLASSES_ROOT\.dir]', or '[HKEY_CLASSES_ROOT\.dxr]'
Wherease the executable installer creates all three of these keys and populates them all with the following 'default' value:
"Content Type"="application/x-director"
These keys and values should be set in the installer's Registry table to fix the issue.
The MSI installer creates a value under the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponets\SwDi r]
However this registry key is obviously misspelt (missing an 'n' in 'OptionalComponets') and should read as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponents\SwD ir]
This key name needs to be changed in the installer's Registry table to fix the issue (also pointed out in the following forum post: http://forums.adobe.com/message/2379350 (post number 10)).
Under [HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer], the 'Version' value is left blank by the MSI by default:
Whereas the executable installer creates the value as follows:
1152602
This registry value should be set to the correct version in the installer's Registry table to fix the issue.
Finally, the MSI installer creates a number of registry values under the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer\Mime Types]
These values are *in addition* to the values created under the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer\MimeTypes]
(Note there is no space between 'Mime' and 'Types' in the second key path)
The executable installer *only* creates registry keys under the 'MimeTypes' key, and it seems as if this is the correct formatting for the key (also pointed out in the following forum post: http://forums.adobe.com/message/2379350 (post number 11)).
The unnecessary 'Mime Types' registry keys and values should be removed from the installer's Registry table to avoid any potential issues.
I am sorry that this is such a long list, but it seems as if a number of things have been changed in the transition from 11.5.1.601 to 11.5.2.602, and it would be very helpful if these changes could be put back to how they were before, so that the MSI and the executable installers function in the same way as much as possible.
Message was edited by Borgquite - added 11.5.6.606 update

Have posted an updated version of the MST to my webspace here:
http://homepage.ntlworld.com/minkus/shockwave/shockwave115606mst2.zip
This new version fixes the following issues (changes to this version in bold):
MsiInstaller repair & errors on first run as non-admin (removes 'AppData' directory entries)
DCOM errors once Shockwave is installed (adds double quotes to the beginnning of LocalServer32 value)
Incorrect TypeLib paths in the registry (fixed to use built-in [SystemFolder] property)
Default CLSID description value missing (set to 'Shockwave ActiveX Control', as per the executable installer)
Incorrect Shockwave 10 paths in the registry (fixed to use built-in [SystemFolder] property)
Misspelt 'OptionalComponets' registry key (renamed to 'OptionalComponents')
Missing .dcr, .dir, .dxr Content Type registry values (included in the executable installer)
Fixed incorrect AppID registry key (set to use installer's [VERSION] variable)
Removed 'Launch SWDNLD.exe' shortcut created in Programs subfolder (people don't want this - see here)
I have tested this on my network and it all seems to work fine. Unfortunately my original plan to use the executable installer didn't work out as it does not include the Shockwave 10 compatibility components described here and here, so it looks like I'll have to keep this MST file up to date with the latest versions until Adobe fix the problems themselves...
If you want to see the changes that I have made, load up Adobe's 11.5.6.606 MSI file in Orca, then use Transform / Apply Transform to apply the MST, and look for the entries in green.
Please post any feedback to this thread, and I will try to respond if I can help!
Chris Hill

Automaticly run Program\Script After and MSI Installation

Hi All,
Today I started looking into the use of Application Model in SCCM 2012.
It was easy to create an application by using the import MSI function, which automatically created the application, deployment type and detection rule. But I'm struggling with how to run a script afterwards, when the MSI installation was successful.
I've looked into creating 2nd deployment type making the first deployment type as it's dependency, but it's mandatory that I also need to make an detection rule. And this is where I'm stuck ass the detection rule I want to have the same as
for the first deployment type which will make it impossible to run because the condition will be evaluated ass already installed.
Is there a way to avoid the detection rule? If not is if possible trigger something after the first deployment type based on the errorlevel after the MSI installation.
My goal is to write a regkey somewhere in HKLM\Software\<company name> after an successful installation of an application. This location we've included in our hardware inventory for reporting purposes.
Any suggestions to achieve this goal are welcome .
Regards,
Daniel

I've resolved it with using the AddDploymentTypebyMISInstallerAuto function from the Add-CMDeployment command and provided an InstallationProgram parameter to override the default InstallationProgram.
The comman-line looks like
Add-CMDeploymentType
-ApplicationName <Name>
-AutoIdentifyFromInstallationFile
-ForceForUnknownPublisher $True `
-InstallationFileLocation
<MSI
File> -MsiInstaller
-DeploymentTypeName
Test1 –InstallationBehaviorType InstallForSystem
-InstallationProgram
< Custom
Script>
In this way I have the detection based on the MSI GUID and the ability to use a wrapper script.

Please help me with msi installer file for 11.6.8.* as this is our standard version which we use for all machines in our organization

please help me with msi installer file for 11.6.8.* as this is our standard version which we use for all machines in our organization

arai-c wrote:
I have full version of this software but I am not able to install it silently because it always gives Google toolbar pop up which We dont required
arai-c wrote:
the problem is we dont have msi file for 10.6.*.* and hence I am not able to create package for it
I don't understand; two days ago you wrote that you have it, now you don't...?
If you don't have it, then why not deploy the current version 12.1.3.153 - I don't see the point of installing an old, unsecure software version.

Is there Full Version MSI installer package for the last version of Adobe Reader?

Is there Full Version MSI installer package for the last version of Adobe Reader?
Where can we find it?
Thanks.

Hi,
The full MSI installer for the latest 9.5.0 release is available at:
ftp://ftp.adobe.com/pub/adobe/reader/win/9.x/9.5.0/en_US/AdbeRdr950_en_US.msi
However, there is no full MSI installer available for the latest 10.1.2 release, since it wasn't a single dot release. The Reader 10.1.2 installer is available as a MSP file which can be applied onto the Reader 10.1.0 or Reader 10.1.1 installation.
You could also create an AIP for the latest 10.1.2 release, which would give you a single MSI installer along with the extracted files. Please have a look at the below mentioned document for more details on the same:
http://kb2.adobe.com/cps/837/cpsid_83709/attachments/Acrobat_Enterprise_Administration.pdf
Hope this helps.
Thanks
Ankit

Msi-installation: no distribution-script window

Hello together
When installing a simple application a window is showed "running pre-/post-distribution script" with a progress bar. When installing a msi-application it seems that this window isn't being showed at all - only the progress-window during the msi-installation.
I'm running a long task in the pre-distribution script (uninstallation of the previous version). During the runtime of the pre-distribution script nothing is showed, so the user could think that nothing is going on and getting nervous... ;-)
I don't expect to have an output of my distribution script, just the usual distribution-script-window.
Am I doing something wrong, is it a bug or is the only way to prevent this behaviour to create a simple application that is run before the msi-installation?
Using Zenworks 7.0.1.4
kind regards,
Stefan

dtMsgBox is a good idea, but has a strange gui. I would rather place it in the center of the screen in this case than at the top and would like to change its outfit (text, color, ...).
I'd prefer if zenworks would behave in installing msi-packages as it does with simple applications.

Skype 7.0.0.102 msi installer

I would appreciate a link to download the 7.0.0.102.msi installer.
Thanks and regards,
Roy
Solved!
Go to Solution.

Complexity wrote:
Again the Skype automatic update (which can not be turned off - or you can try to turn off but it is not working).
Most recent up to data and easy to use version created a BSOD during install for me and NOTHING to fix it except an old Skype version MSFT keeps hiding over and over again !!!!
Really I am sick of your poor software.
Please, run the DirectX diagnostics tool (32-bit option).
Go to Windows Start and in the Run box type dxdiag.exe and press the OK button. This will start the DirectX diagnostics program. Run this diagnostics and save the results to a file. Please, attach this file to your post.
Be aware that you will have to zip this file before attaching it here.

How to build an MSI installer from ALP default installers

Hi,
I would like to know how can I build an MSI from the BAT+EXE installers offered by ALP?
When the install begins I can capture de .MSI bundled inside the EXE but when I have to transform that MSI in a new one with the parameters I need I can't do it...
Can somebody help me?
Thanks,
Carlos

You could create one 'installer project'
This installer project would have 4 auto populating folders, linked to each exe-folder.
With the installer you can add each autopopulating folder to your installer.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

How can I create an installer?

Hi!
I am working with LabVIEW Version 8.6.1.
After I have built an Application (exe) I would like to create an installer. Therfore I open the window "my installer properties" in my Project.
After I got the "product information" I go ahead to "source files". First question: Which files must be include in the "destination view" on the right site of the window???
The "builds" file???
If I do this and go ahead with "additional installers" I select "NI LabVIEW Run-Time Engine 8.6.1". After that I click the bottom "build".
The build status open. Than I get a default:
build errors:
the build was unsuccessful
The following file(s) are not found on the system:
I think it has to do with the source files which I have to include. But I do not now which one!!!
Can somebody help me???
Marc

You will indeed need to create an executable from your project first and then add this to your installer build.
Here are a few links on how to create an installer, could be very useful for your issue:
Distributing applications with application builder:
http://zone.ni.com/devzone/cda/tut/p/id/3303
Including additional installers:
http://digital.ni.com/public.nsf/websearch/E09BA0E2F31D304F86256A640070058E
Missing distribution:
http://digital.ni.com/public.nsf/allkb/C3666BA408F81E59862570D20056E692?OpenDocument
Best regards,
AdamF
Applications Engineer
National Instruments
Adam
Academic Product Manager
National Intruments

Comparisson to create PackageMaker installer

What would be the best way to capture the state of files on a Mac and then compare it to the state of files on a Mac after running several software installers in order to use PackageMaker to make a single installer? Maybe I'm a little out of my league here, but we've just spent two months upgrading 150 people to Mac OS X 10.4.x from Mac OS 9. We have 100 people left to upgrade before the end of the month (yes, it may not be possible). Of course, NOW it turns out that our image is missing several key parts that will need to be installed on each of the previously upgraded workstations. I can make a new image, that's not a problem. But, if I make a new image, is there a way to compare it to the previous image (a "diff" command in the Terminal?) and build a list of changes that can be used to set-up a PackageMaker installer? I would really like to be able to push out a single package using Apple Remote Desktop...
-Doug

The department has decided to upgrade from FileMaker Pro 5.5 to version 8. The version 8 installer is NOT a standard package and cannot be installed/distributed by Apple Remote Desktop. Also, there is already an update to 8.0.2 that is actually BIGGER than the original installer and requires 8.0 to be installed first (and is ALSO not a standard package file). So, I need capture the state of my workstation, install FileMaker Pro 8 and then the 8.0.2 update and then attempt to create an installer of my own that I can actually use Apple Remote Desktop to push out to everyone else. So, yes, it seems I will have to capture packages and their contents as well as individual files as well as some, potentially, invisible files that contain information, for example, about the registration/serialization of FileMaker Pro 8. Neither the main installer nor the 8.0.2 update create a receipt file. Thanks!
-Doug

Is there any way to create an installer for Mac OS and Linux OS once a stand alone application is created?

Is there any way to create an installer for Mac OS and Linux OS once a stand alone application is created? I have created an executable application that I want to distribute to Mac and Linux users (different applications were created in the respective OS). I was wondering if there is any way to create an installer? I think there probably isn't... If the user were to simply download the Labview Run-time Engine from ni.com would they be able to run the application or is it more complicated than that?
Thanks so much for your time.

I think Shane tried to say, that it is on the Mac OS X installation DVD, NOT the LabVIEW for Mac OS X installation medium. And that could very well have changed in recent Mac OS X versions as well. They used to have Xcode on it too, but that seems gone as well.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Creating MSI Installer

Similar Messages

Maybe you are looking for