Hi, We are digging for a slow installation, which was reported to occur only on Spanish Vista OS (not on English Vista). The log file showed that there is a big time jump (4+ min). Can anybody explain what happened during the time and how to reduce it or investigate to shorten it? Thanks MSI (s) (A0:68) [15:51:17:924]: Executing op: ActionStart(Name=RegisterUser,Description=Registering user,Template=[1]) MSI (s) (A0:68) [15:51:17:924]: Executing op: UserRegister(Owner=Admin,,ProductId=none) MSI (s) (A0:68) [15:51:17:924]: Executing op: ActionStart(Name=RegisterProduct,Description=Registering product,Template=[1]) MSI (s) (A0:68) [15:51:17:924]: Executing op: ChangeMedia(MediaVolumeLabel=DISK1,MediaPrompt=Please insert the disk: 1,MediaCabinet=Data1.cab,BytesPerTick=0,CopierType=2,ModuleFileName=C:\Windows\Installer\47619.msi,,,,,IsFirstPhysicalMedia=1) MSI (s) (A0:68) [15:51:17:924]: Executing op: DatabaseCopy(DatabasePath=C:\Windows\Installer\47619.msi,ProductCode={F52E6DC5-E735-4A58-A280-AEA3DED1679F},CabinetStreams=Data1.cab,,) MSI (s) (A0:68) [15:51:18:080]: Executing op: ProductRegister(UpgradeCode={4EB823EB-27D7-4E7B-9469-961E2B0634D0},VersionString=2.03.26.002.25,HelpLink=www.nvtl.com,,InstallLocation=C:\Program Files\CompName\,InstallSource=C:\Users\Admin\Desktop\NvtlDriverSCRTME_V2.03.26.002MSI\,Publisher=CompName,,,,NoModify=1,NoRepair=1,,,,,,,EstimatedSize=3385,) MSI (s) (A0:68) [15:51:18:111]: Executing op: ProductCPDisplayInfoRegister() MSI (s) (A0:68) [15:51:18:111]: Executing op: ActionStart(Name=InstallDrivers32.5F1DC02E_0598_4666_8B42_4C5AA41526BB,,) MSI (s) (A0:68) [15:51:18:111]: Executing op: CustomActionSchedule(Action=InstallDrivers32.5F1DC02E_0598_4666_8B42_4C5AA41526BB,ActionType=3110,Source=set oShell=createobject("WScript.Shell") pth=Session.Property("CustomActionData") oShell.run pth, 0, true,,CustomActionData="C:\Program Files\CompName\Drivers\Setuphelper32.exe" /install 0 /installdir "C:\Program Files\CompName" /relflags GEN_USB_MDM,GEN_USB_NDIS,USB_CD_FILTER,RM_NET_NDIS,ENABLESCR,GEN_USB_SCR,GEN_CDC_NDIS,TME_USB_MBNET) MSI (s) (A0:9C) [15:51:18:111]: Generating random cookie. MSI (s) (A0:9C) [15:51:18:126]: Created Custom Action Server with PID 760 (0x2F8). MSI (s) (A0:DC) [15:51:18:158]: Running as a service. MSI (s) (A0:DC) [15:51:18:158]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (A0:68) [15:55:33:522]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing product features,Template=Feature: [1]) MSI (s) (A0:68) [15:55:33:522]: Executing op: FeaturePublish(Feature=GenUSBInstaller,,Absent=2,Component=ls$,MEa4X9Kf([q63sv9J$rdR,l68=f3HPsdV8D.$nyr+I03X?9FEmUNe{FA6HD@Secyl?38X^4HK34?9[j%aXk6{=9GAQC+'&nfM0+`67MJ]=GH~=w&Nh?2%m+o1I8wQ=[pZr7NR2G1x0*)NfYyc?y.F=J(B{-9@@xce@VEZ8x_zs*vSS@2jQ(4V@OMI=F.(m*WYVJ=N]K&%?71x898P9W-H_Vh!Zk2[eyeo8}3k~*0_4Q'0g1Al7V*t@re8THzMsL%HnAz]nCg@?AFFV=bC+O+%m=2,K$rY8'p%qz6?Pm5u9klX8{xh92tYJ%Vcy31QMA~UM9E{9HO!`9+qVwrzLR_EG!Sj8$aI97IKZh*e'uk?'XuB=KeG,6s,{pT_P4YT9].}9^G64,(VZn3H)=GK,ozj8I^Nwlx8Em,qwj)StaYM9Ru0)Yhu=Jeeo{.Qpb8k?--Y1T)75'8_r4v)CWw8@Cm(2qR4zX0z^iPRzH&^A9TLB*&5*ubO1HkSn`VXAy(kel3}zANsTqZ_bT`7=_xEe=4kf%VYg8UT5~Ec?,?2ge{6{RYx-O%^*XEb?YcvQUAy-^1?Es@u'Y]{?YPm0!riJG(+,tR_UCK*AS6i}JHW=BZ{MhjEcVAF@T]&pt}rS{,v{uwe-T3n=wo-Z@EzZVA) MSI (s) (A0:68) [15:55:33:522]: Executing op: FeaturePublish(Feature=SmartCardRegKey,,Absent=2,Component=f$_sW{]}H=)zU0Z.7M*t) MSI (s) (A0:68) [15:55:33:522]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,) MSI (s) (A0:68) [15:55:33:522]: Executing op: IconCreate(Icon=ARPPRODUCTICON.exe,Data=BinaryData) MSI (s) (A0:68) [15:55:33:522]: Executing op: CleanupConfigData() ... View more

Hi, I would like to create a log file to contain some information like when (date & time) the install starts and finishes, what commandline is invoked (e.g. setup.exe /v"bla bla bla") Is there any existing properties I can use to retrieve the information? I am planning to use VBS. Thanks ... View more

Hi, I am using IS2010 Basic MSI. What I need to do is to install the exact same package twice on a system. In order to do that, I blocked (using conditions) all "FindRelatedProducts" and "RemoveExistingProducts" standard CAs. Now the second install runs without error. The problem is that we have a group of features which drop files to certain location (determined by a path variable from commandline). If I define the property in the command, it worked fine in the first install, but not in the second time. Comparing the two log files, I can see that the features have the following logs: 1st install: Feature: my_feature; Installed: Absent; Request: Local; Action: Local 2nd install: Feature: my_feature; Installed: Absent; Request: Null; Action: Null I am running the exact the same commandline with the property set to the same location, how could the second time didn't work? Please note that after running the first install, I uninstalled it and then a full UI install, and then ran the second command install. It seemed the full UI install blocked the features from being installed with the second command run, even though the property was defined in the command run. Can any help on this? Thanks ... View more

We recently decided to add autorun to our products. When media CD is inserted, it will automatically display an interface (dialog/window/form, etc.) to display certain (list of) URL links to files/websites, and some buttons that users may click to launch programs (app/setup etc.). There could be multiple ways (eg. MFC) to do it and the program (files/exes/etc.) needs to be called from Autorun.inf. What is the most straight forward way to implement that? Does the program (called by inside Autorun.inf) depends on the installer project types (we have Basic/InstallScript MSI and InstallScript projects). Thanks, PB ... View more

I am an InstallShield user and most of my work has been for Windows so far. Now there is a chance that I need to deal with other OSs like Linux (and probably also Unix/Mac). I would like to get in touch available packaging/installation tools for different OSs now days, since I am an InstallShield user, the first one jumping in my mind is InstallAnywhere, but I never used it and want to know what other are there, and what's the advantages and disadvantages of each. Links to articles/descriptions/blogs are also very appreciated. Thanks ... View more

Hi, I haven't used minor upgrade for long time. But recently I happened got a chance to try a small project (Basic MSI IS2010) with minor upgrade. The result is interesting and I have some questions. I didn't touch either Upgrade table or Upgrades panel. If I configure the image to a compressed single setup.exe, both small (same version - just run another build which only changes Package code) and minor (change version and run another build) seem work - at least the dialog (mentioning a upgrading is running and if user wants to continue) showed and (upgrade) installation completes. But if I configure the image to a compressed single .msi file, I always got error message "Another version of the ....", even though I have package code and version changed. Is this normal? I kind got impression that minor upgrade should also work with .msi image (i.e. only need to change package code and version, a new build should run with upgrade). Then I found in IS2010 help (titled "Creating Minor Upgrades") below: Running a Minor Upgrade Without Using Setup.exe If you intend to distribute your installation without wrapping it in Setup.exe, there is a manual process that your end users must follow to start the installation. For this reason, you should consider using Setup.exe; however, you can achieve similar results without it. The Installer properties REINSTALL and REINSTALLMODE must be set from the command line to start an installation in upgrade mode. In all but the most advanced scenarios, the property REINSTALLMODE should be set to vomus and the property REINSTALL should be set to ALL. A typical command line can look like the following: msiexec.exe /i \product.msi REINSTALLMODE=vomus REINSTALL=ALL If the update contains features that you do not want to update, you should set REINSTALL to a comma-separated list of the features that you want to update, as in the following command: msiexec /i \product.msi REINSTALLMODE=vomus REINSTALL=F1,F3,F5 The feature names you use in the REINSTALL property are case-sensitive. Two questions with the above description: 1) This description seems like a major upgrade to me, especially with "REINSTALL=ALL", is that right? If so, does that mean there is no clear difference between all the upgrade types (small/minor/major) with .msi image? 2) The description says that user needs to pass the commandline parameters for the upgrades to execute, what if a user just double click the .msi file? So there is no way to execute the upgrade by clicking on .msi file? You can't simply set all the properties in Property table since the very first setup will not work. I also tried to create image with both setup.exe and .msi files in it, and the result still the same - running setup.exe can excute small/minor upgrade, but not by running .msi file. I tended to avoid minor upgrade, but this time I have to deal with it and hope that my questions be answered and get myself clarified. Thanks, PB ... View more

Hi, I need to set a registry entry to contain the OS name, is there a property (like [Date] for date] so that I can use it without tweaking any code? Thanks, PB ... View more

Hi, I am playing around with the 'View the readme file' check box and text on the SetupCompleteSuccess dialog. Now I want to make the box and text only display for fresh install and upgrade install, but not other cases such as repair and remove. I turned 'Visible' for the two (box and text) to 'Ture' so fresh install can show it at the end, but repair and remove now also display the box and text. I have set conditions that repair and remove will not run launch readme even the box is checked, but it's odd to have that option for repair and remove. How can I hide (or turn 'Visible' off) the box and text conditionally for repair and remove cases? My project is MSI Basic. Thanks, PB ... View more