This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
xrz1138
Level 3
- Revenera Community
- :
- About xrz1138
Oct 04, 2012
11:37 AM
This is a dead end it seems. There appears to be zero chance of preventing InstallShield Installscript installers from writing the Add-Remove program Registry data to the Windows 32-bit part of the Registry. I am working to make sure that the material in: HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall is the only mis-placed data. (and expecting windows to find what it needs when uninstalls run) Good luck all, Chris
... View more
Oct 02, 2012
04:30 PM
Yes, while I am waiting on confirmation from support, I begin to think that I have been handed what for all intents and purposes is an unsolvable problem. I am going to have to rewrite an InstallScript installer into an MSI-Installscript installer in a very short time period. I will post questions here. If the answers do not save me, then perhaps they will save the next poor soul. Thanks for the time. Chris
... View more
Oct 01, 2012
08:46 PM
Ugh....I take that back. It is not just the [Company Name] -> [Product Name] -> [Product Version] Registry keys that need to be redirected. There is the HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\GUID area that would have to be deleted and recreated in the 64-bit part of the Registry. ...then I see that the uninstall was installed to the: C:\Program Files (x86)\InstallShield Installation Information directory, and that this would have to be moved to the 64-bit folder. So, perhaps my manual approach is a dead-end. POINT: I am building an Installscript installer using InstallShield 2011 Premiere on a 32-bit Windows 7 box that intends to install 64-bit software onto 64-bit systems. How can I make such an installer consistently write to the 64-bit area in the Windows Registry? Thank you, Chris Hahn
... View more
Oct 01, 2012
07:01 PM
Let me re-phrase that... I have figured out how to make the Add or Remove keys in the proper place... [Company Name] -> [Product Name] -> [Product Version] Registry entries to HKLM\SOFTWARE. All I need now is how to STOP Installshield from making this same sequence of keys in the Wow6432Node sub-key. I made a new Registry Set and deleted the default one. Then I added this new Reg Set to every one of my Components. Everything looks good....except that we have the duplicate keys being made by IS down in the Wow6432Node area. Please let me know how I might proceed. I am under the gun and will have to release into the wild software that I am sure we will be dealing with in all future releases. Chris
... View more
Oct 01, 2012
04:08 PM
Hello, I am building an Installscript installer for a 64-bit program using IS 2011 Premiere on a 32-bit system. It seems that the fact that my installer is a 32-bit program is causing Registry changes to be written to the Wow6432Node sub-key of the Registry. Question: Why did adding disable(WOW64FSREDIRECTION); to OnBegin and adding enable(WOW64FSREDIRECTION); to OnEnd have zero affect on the Registry changes that this installer makes? (I am in a position where affecting the entire install is OK) Take care, Chris
... View more
Labels
- Labels:
-
InstallShield 2011
Oct 01, 2012
04:06 PM
Hello, I am building an Installscript installer for a 64-bit program using IS 2011 on a 32-bit system. It seems that the fact that my installer is a 32-bit program is causing Registry changes to be written to the Wow6432Node sub-key of the Registry. Question: Why did adding disable(WOW64FSREDIRECTION); to OnBegin and adding enable(WOW64FSREDIRECTION); to OnEnd have zero affect on the Registry changes that this installer makes? (I am in a position where affecting the entire install is OK) Take care, Chris
... View more
Oct 01, 2012
03:30 PM
I should add that I tried my own fix for this. I added my own "Registry Set" in the "System Configuration" -> "Registry" section of IS 2011, and in this new set, I added HKLM/SOFTWARE/COMPANY/PRODUCT/VERSION2 (with a value of VERSION that was slightly different from that in the General Information page of InstallShield) Saving and then building this yields an installer that correctly wrote: HKLM/SOFTWARE/COMPANY/PRODUCT/VERSION2 into the 64-bit part of the Registry, but it ALSO wrote: HKLM/SOFTWARE/Wow6432Node/COMPANY/PRODUCT/VERSION I also used IS's Direct Editor to remove the "Default" record from ISRegistrySet table. Doing this allowed me to specify just the new Registry Set that I created above would be used for all Components of this install. (by doing this, I found that I was unable to de-select the Default Reg Set so I took this additional step) No Joy. I am under the gun and am going to have to release 64-bit installers that my people will be having to worry about indefinitely. Yuck!
... View more
Oct 01, 2012
03:10 PM
Hello all, This one is a tad long, so thanks in advance to any who did not just click away... Problem: ========================= We are building the installer for a 64-bit application using IS 2011 on a 32-bit box. This is, and must be, a pure InstallScript installation. I find that some of our Registry changes are being written to the 32-bit area of the target 64-bit system. (Note: this is the HKLM/SOFTWARE/Wow6432Node sub-key) ========================= Note: this is a simple installer, defining only the OnFirstUIBefore, OnMaintUIBefore, and OnUpdateUIBefore routines. Now, we have explicitly added the use of the variable PROGRAMFILES64 in in defining TARGETDIR, to ensure that all files are installed into, for example, "C:\Program Files" and not into the 32-bit equivalent "C:\Program File (x86)". This is working fine. We have also added using the Registry related global to affect Registry changes. Specifically, I added this line to my installer: REGDB_OPTIONS = REGDB_OPTIONS | REGDB_OPTION_WOW64_64KEY; Now for the heart of the matter: ========================= Using the options above did make all Registry calls *that I make explicitly* in my code write to the correct location. It did not affect the Registry changes that InstallShield makes for me. ========================= Specifically, this code: #define INSTALL_REGISTRY_KEY "SOFTWARE\\Company Name, Inc.\\Installed Software" RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE); szKey = INSTALL_REGISTRY_KEY; nvReturn = RegDBSetKeyValueEx(szKey,"ApplicationCount", REGDB_STRING, szAppCount, -1); Did create the new key "ApplicationCount" into HKLM\SOFTWARE\Company... BUT I also ended up with the new key HKLM\SOFTWARE\Wow6432Node\Company\Product\version Where "Company" was *precisely* the installer "Company Name", taken straight from the ISM files "General Information" sheet. "Product" was similarly taken from the General Information sheets "Product Name". Same for Version. So, what is happening here is that InstallShield is taking the General Information settings and building default Registry settings, but it is writing them to the Wow6432Node 32-bit sub-key of the registry which is wrong. Basically, I need a method for ensuring that REGDB_OPTION_WOW64_64KEY will make ALL Registry entries be made to the 64-bit part of the Registry. Thank you all for the time and kind attention! Chris Hahn
... View more
Labels
- Labels:
-
InstallShield 2011
Oct 01, 2012
02:24 PM
If you want files to go to the 32-bit area, then use the variable PROGRAMFILES. PROGRAMFILES64 points at the 64-bit area. See here: http://helpnet.installshield.com/installshield17helplib/mergedProjects/installshield17langref/LangrefPROGRAMFILES64.htm Good luck, Chris
... View more
Latest posts by xrz1138
Subject | Views | Posted |
---|---|---|
7491 | Oct 04, 2012 11:37 AM | |
7491 | Oct 02, 2012 04:30 PM | |
7491 | Oct 01, 2012 08:46 PM | |
7491 | Oct 01, 2012 07:01 PM | |
3226 | Oct 01, 2012 04:08 PM | |
1900 | Oct 01, 2012 04:06 PM | |
7491 | Oct 01, 2012 03:30 PM | |
16616 | Oct 01, 2012 03:10 PM | |
1295 | Oct 01, 2012 02:24 PM |
Activity Feed
- Posted Re: 64-bit install writing to the 32-bit Registry area on InstallShield Forum. Oct 04, 2012 11:37 AM
- Posted Re: 64-bit install writing to the 32-bit Registry area on InstallShield Forum. Oct 02, 2012 04:30 PM
- Posted Re: 64-bit install writing to the 32-bit Registry area on InstallShield Forum. Oct 01, 2012 08:46 PM
- Posted Re: 64-bit install writing to the 32-bit Registry area on InstallShield Forum. Oct 01, 2012 07:01 PM
- Posted disable(WOW64FSREDIRECTION) does not work as e3xpected on InstallShield Forum. Oct 01, 2012 04:08 PM
- Posted Re: WOW64FSREDIRECTION not working? on InstallShield Forum. Oct 01, 2012 04:06 PM
- Posted Re: 64-bit install writing to the 32-bit Registry area on InstallShield Forum. Oct 01, 2012 03:30 PM
- Posted 64-bit install writing to the 32-bit Registry area on InstallShield Forum. Oct 01, 2012 03:10 PM
- Posted Re: Using ProgramFilesDir^ for 32bit machines on InstallShield Forum. Oct 01, 2012 02:24 PM
Contact Me
Online Status |
Offline
|
Date Last Visited |
Mar 18, 2019
12:11 PM
|