It looks like the "Build UTF-8 Database" release setting was our problem. Thanks for the help! ... View more

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

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

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

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

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

I tested further without including the /V"/passive" parameter, and the problem still occurs. ... View more

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

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