Dec 18, 2013
06:16 PM
It looks like the "Build UTF-8 Database" release setting was our problem. Thanks for the help!
... View more
Dec 17, 2013
01:07 PM
I have an installer which includes a number of files with Japanese translated names (hence Japanese characters). I'm running 2013 Premier which is supposed to support Japanese among other languages for installation. However, upon installation on a Japanese Windows VM (Win 7 x64 or Win 8 / 8.1), these filenames have apparently been butchered. What ends up coming out are filenames that look like this: (apparently they can't be copy/pasted, but picture 4 rectangles squeezed together) I checked to see how these files are treated in the Direct Editor in IS. The FileName(s255) and ISBuiuldSourcePath(s255) tables show the Japanese, though the File(s72) key field is unable to handle these, so all the keys end up as something like "File5". This is quite a serious issue for our Japanese localized version which we plan to release soon. Any advice would be appreciated.
... View more
Labels
- Labels:
-
InstallShield 2013
Nov 05, 2013
12:42 PM
I've noticed some similar posts on this topic, but did not see any solution / explanation / etc. If this is one of those situations where InstallShield is doing the right thing, but Windows has the bug, I would appreciate knowing that. I'm using a prerequisite for .NET 4.5 in an MSI-Installscript project. The prerequisite is configured with the "Reboot the machine and resume on reboot" option (under the Behavior tab -> "If the prerequisite appears to need a reboot"). We're targeting Windows 7 and 8, and consistently seeing that after installing .NET 4.5, the computer reboots and the install fails to continue (even in Windows 7 where in theory there should be less OS bugs by now). In case people are more familiar with the XML of the prerequisites, here's the applicable XML: Is there a different way I should configure this prerequisite as a workaround to this problem? Any other suggestions? Thanks.
... View more
Labels
- Labels:
-
InstallShield 2013
Oct 23, 2013
07:27 PM
We've seen this occur on Windows 8 (and now Windows 8.1) test VMs. If shell properties are set for some start menu shortcuts (or use of "Pin to Windows 8 Start Screen" in IS 2013), the install will hang during shortcut creation (perhaps on about 5% of installs). This is with an Installscript-MSI project. I haven't seen much chatter on this topic online ... just wondering if anyone else has experienced this, and if you have any advice on addressing the issue (while still providing the necessary shortcuts to Windows 8.0 users in their All Apps screen). At least with Windows 8.1 the icons no longer install by default on the main screen, so the shell properties can be removed (using another set of components) based on OS check. Since this is likely the fault of Windows Installer and not Installshield, i'll include the msiexec version from the Win 8.1 VM I've most recently seen the issue on: V 5.0.9600.16384.
... View more
Labels
- Labels:
-
InstallShield 2013
Apr 30, 2013
04:05 PM
Hi Michael, My apologies, forgot to check back on the thread for a couple days. Yes, points 1 and 2 sound about right. I had hoped not to have to do a lot of additional work to handle new user dpi settings for these dialogs with radio buttons and check boxes. I suppose I could enlarge the buttons, but I would need to do this several times (we localize to 9 additional languages, so far), and then I'm concerned making such changes might disrupt the standard cases more widely in use right now (96/120 dpi). It would be great if Installshield handled scaling these buttons so they appear roughly the same at different user dpi settings. The checkboxes are wonky, but the radio buttons having top and bottom truncated seems worse to me (though it is a problem i could probably solve with some customizing if necessary). The font issue is probably something I could solve by scaling back a bit on the customization of that dialog. Several years ago I was asked to customize the SdSetupTypeDlg mainly to disable the "next" button until a user consciously chose one of the 3 product options (radio buttons), rather than setting one to be a default option (so they would ideally read the descriptions and understand the version they were choosing rather than quickly clicking-through). I was also asked to make the product names (next to the radio buttons) larger font. I took a look at my old script code, and here are some lines that are likely relevant to this problem: hFontProducts = GetFont("Arial", 11, STYLE_BOLD); ... CtrlSetFont (szDlg, hFontProducts, SD_RADIO_TYPICAL); I can send you the full .rul file if that would be helpful. These are all skinned dialogs. I'm afraid I haven't had a chance to explore this with unskinned dialogs yet. By your comment about the dialogCache, i'm guessing we lose the skin if we clear the cache? I remember at one point some years ago I disabled caching the installation in the release config, bit then uninstalls from ARP had no skin (while running the installer exe file again would still provide skins in maintenance mode). So yes, we'd like to avoid losing the skin, but the shifting in Windows 8 is certainly the greater of the 2 evils. Thanks, Brian
... View more
Apr 24, 2013
05:13 PM
Hi Michael, Thanks for looking into this. I asked our QA specialist who's been working with the Surface Pro, and he mentioned that he went to the dpi settings, selected Custom, then turned it up to 200%. I have a couple screen shots of dialogs with multiple checkboxes or radio buttons. Note that this is from an Installscript (no MSI) project, and it turned out both of these dialogs were customized, so that may be part of the root cause. The dialogs are SdSetupType and SdAskOptions (in the latter case I just needed to add a 5th checkbox). On a related note, there was also a 144 dpi Windows 8 issue I was reminded of where the Welcome maintenance dialog got shifted awkwardly within the Installshield window (this is actually in an Installscript-MSI project, and the dialog was customized to remove the modify option). Let me know if there's anything else you need. It sounds like you're already aware of text not being as sharp as perhaps it could be, so I'll leave those screenshots out for now. -Brian
... View more
Apr 19, 2013
06:44 PM
Our QA team has been looking at our product installations on the new Microsoft Surface Pro tablets. At standard resolution (144 dpi), the dialogs looked ok, but in high resolution mode (192 dpi), all the check-boxes, radio buttons, etc. really look quite bad in the standard Installshield dialogs (Installscript project type). It would be a great deal of work to customize all dialogs to try to manually fix this. Does Flexera plan to address this, and if so, when? Thank you.
... View more
Labels
- Labels:
-
InstallShield 2012 Spring
Nov 07, 2012
03:43 PM
In case anyone else comes across a problem like this, I learned (though use of registry capture and filtering/comparing) that the only keys Installshield was missing in this case were of this flavor: HKCR\.pdf\shellex\ContextMenuHandlers\{GUID} (where GUID is the actual GUID of our shell extension that is being registered) It sounds like this is a Microsoft bug (when running Regasm /regfile), so you can work around it by manually adding the additional reg keys to your project (or run Regasm via custom action, but I prefer the other method if the missing keys can be identified).
... View more
Nov 05, 2012
06:41 PM
Hi, I've searched the forums, and see this has been discussed in the past (see http://community.installshield.com/showthread.php?t=202935 for instance). However, I'd really like to hear from someone at Flexera as to whether this is considered a bug in IS and will be fixed, or what the official recommended workaround is. In the post referenced above, Chris mentioned a limitation with "regasm /regfile" ... can you guys elaborate further on this? We have many components using the ".NET COM Interop" flag, and these have generally worked fine in the past. We just added a new component which is a shell extension dll, adding some items to context menus in Windows Explorer, and this does not work during install, though manually running regasm on the file works fine. We were previously using IS 2012 and I just upgraded to the 2012 Spring edition, but no change in behavior. We also recently started targeting .NET 4.0 Client instead of 3.5sp1, but I made sure the InstallShield .NET tab in Options points to the v4.0.30319 folders (ie. C:\Windows\Microsoft.NET\Framework64\v4.0.30319). Not sure if this matters, but we're using an Installscript-MSI project.
... View more
Labels
- Labels:
-
InstallShield 2012 Spring
May 23, 2012
01:19 PM
sorry for the string of posts, but one last clarification -- when I initially referred to "the first dialog", I meant the "Preparing to Install..." dialog, which includes "Extracting: {my msi file}". You are correct that SdWelcome always matched the language of the later progress dialog. However, when I tested the sample program without /passive (which would have caused the SdWelcome dialog to be skipped), all dialogs from SdWelcome (inclusive) onward were displayed in English rather than my requested language (French, in this case) when /clone_wait was used.
... View more
May 23, 2012
01:12 PM
I also just checked it on a 32-bit Win7 VM, and the problem still occurs, so 32 vs. 64-bit OS does not appear to be a factor at all.
... View more
May 23, 2012
01:07 PM
I tested further without including the /V"/passive" parameter, and the problem still occurs.
... View more
May 23, 2012
01:02 PM
Hi Josh, Sorry for the delay - I was a bit busy for awhile and had to put this on the back burner. I just put together and tested a sample project with the same 9 languages enabled that my other project had. The sample project just has a script function with a 15 second delay so the evidence of the issue (which still occurs) won't flash by too quickly. I realized there were a couple details I left out earlier which may or may not explain why the issue didn't occur when you tried to reproduce it: 1 - It's a 32-bit basic MSI project, but I installed on Win7 x64 OS. 2 - I was also supplying the /passive command during install So, here's the cmd line I used for the sample program (from an Admin-elevated cmd window to avoid UAC prompts): > CloneWaitLanguageTestInstall.exe /L1036 /V"/passive" /clone_wait (take away the /clone_wait and it installed properly with French-translated dialogs, include /clone_wait and it reverts to English, including during the subsequent uninstall) I included my compiled setup exe at the root level of the zipped attached project in case it compiles differently for you and the issue somehow relates to my installer build process.
... View more
May 04, 2012
03:12 PM
I've narrowed this down through some experimentation. I have a pure installscript project which launches some other installation packages - basic MSI projects where a setup.exe launcher was created. I'm working on localized releases and found that even if I include the language parameter when running these installations from the launcher's installscript (ie. /L1034 for Spanish), the first dialog is translated, but the main progress dialog (where the message "Please wait while Windows configures [ProductName]" shows) will end up in English. When i test the same package by itself from a cmd window, I see the same behavior if I use /clone_wait. If I run it without /clone_wait, all the dialogs get translated correctly. From prior research awhile back on the forums, it sounded like we need to be using /clone_wait, particularly if the launcher will sometimes be run from a CD. I'm wondering if this is really the case, and perhaps that parameter could/should be dropped so we can get a properly localized installation.
... View more
Labels
- Labels:
-
InstallShield 2012
Dec 01, 2011
06:09 PM
Ok, I guess it didn't turn out to be rocket science just manually creating the file type association reg keys for the alternate product. I needed to include the .ico files, and then set (Default) of the DefaultIcon key to something like [INSTALLDIR]MyIcon.ico,0 (instead of the crazy C:\Windows\Installer\... path which usually gets created).
... View more
Latest posts by BrHartmann
Subject | Views | Posted |
---|---|---|
958 | Dec 18, 2013 06:16 PM | |
1680 | Dec 17, 2013 01:07 PM | |
4457 | Nov 05, 2013 12:42 PM | |
7408 | Oct 23, 2013 07:27 PM | |
1744 | Apr 30, 2013 04:05 PM | |
1744 | Apr 24, 2013 05:13 PM | |
5391 | Apr 19, 2013 06:44 PM | |
669 | Nov 07, 2012 03:43 PM | |
3106 | Nov 05, 2012 06:41 PM | |
1213 | May 23, 2012 01:19 PM |
Activity Feed
- Posted Re: Filenames with Japanese characters are corrupted during build or install (basic MSI) on InstallShield Forum. Dec 18, 2013 06:16 PM
- Posted Filenames with Japanese characters are corrupted during build or install (basic MSI) on InstallShield Forum. Dec 17, 2013 01:07 PM
- Posted Installation does not continue when a prerequisite forces an immediate reboot on InstallShield Forum. Nov 05, 2013 12:42 PM
- Posted Shortcut shell properties may cause installer to freeze at "Creating Shortcuts" step on InstallShield Forum. Oct 23, 2013 07:27 PM
- Posted Re: Need better dialog support for MS Surface Pro at 192 dpi on InstallShield Forum. Apr 30, 2013 04:05 PM
- Posted Re: Need better dialog support for MS Surface Pro at 192 dpi on InstallShield Forum. Apr 24, 2013 05:13 PM
- Posted Need better dialog support for MS Surface Pro at 192 dpi on InstallShield Forum. Apr 19, 2013 06:44 PM
- Posted Re: Why is '.NET Com Interop' option not performing Regasm correctly? on InstallShield Forum. Nov 07, 2012 03:43 PM
- Posted Why is '.NET Com Interop' option not performing Regasm correctly? on InstallShield Forum. Nov 05, 2012 06:41 PM
- Posted Re: /clone_wait breaks install UI localization on InstallShield Forum. May 23, 2012 01:19 PM
- Posted Re: /clone_wait breaks install UI localization on InstallShield Forum. May 23, 2012 01:12 PM
- Posted Re: /clone_wait breaks install UI localization on InstallShield Forum. May 23, 2012 01:07 PM
- Posted Re: /clone_wait breaks install UI localization on InstallShield Forum. May 23, 2012 01:02 PM
- Posted /clone_wait breaks install UI localization on InstallShield Forum. May 04, 2012 03:12 PM
- Posted Re: Associating a File Type with Multiple Executables on InstallShield Forum. Dec 01, 2011 06:09 PM
- Posted IsCmdBld and faulty exit code on InstallShield Forum. Dec 01, 2011 12:06 PM
- Posted Re: Associating a File Type with Multiple Executables on InstallShield Forum. Dec 01, 2011 11:48 AM
- Posted Re: Associating a File Type with Multiple Executables on InstallShield Forum. Nov 30, 2011 03:16 PM
- Posted Re: MSI package with conditional chained items MUST install at least one ? on InstallShield Forum. Nov 28, 2011 05:35 PM
- Posted Re: bug with multiple release flags and MSI chaining? on InstallShield Forum. Nov 28, 2011 04:25 PM