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.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Registry access problem with InstallScript & WinXP
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 12, 2010
07:49 AM
Registry access problem with InstallScript & WinXP
Hello.
I'm using IS2010 for creating a setup unter WinXP with InstallScript.
In the setup I want to check for installed .NET-frameworks.
Therefore i have to check the windows registry.
I used RegDBGetKeyValueEx and RegDBKeyExist and got the following problem:
sometimes the setup can find the keys and names and sometimes not (but they are there anywhere)
if the script can't find the things in the registry, i found out that there is a workaround: If I start "regedit.exe", the setup reacts correctly again.
did anyone have the same problems or a solution?
I'm using IS2010 for creating a setup unter WinXP with InstallScript.
In the setup I want to check for installed .NET-frameworks.
Therefore i have to check the windows registry.
I used RegDBGetKeyValueEx and RegDBKeyExist and got the following problem:
sometimes the setup can find the keys and names and sometimes not (but they are there anywhere)
if the script can't find the things in the registry, i found out that there is a workaround: If I start "regedit.exe", the setup reacts correctly again.
did anyone have the same problems or a solution?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 22, 2010
10:15 AM
why are you checking for installed frameworks? Would it be easier to just require the one you wish to use as a prereq? Then it will handle the logic and allow for options like install from location, etc?
And another issue would be if the user does this on Windows 7, 64 bit, or the old 64 bit XP version. You would need to test for those in addition to get the proper reg values, etc. Thus, making requring pre-req's a better solution. The only thing I don't like about IS2010 is that they don't manage Framework .NET 4 very well.
Why wouldn't it not find the registry everytime, that seems weird (i.e. different OS's, etc). Or you'll selected the wrong registry values to check (i.e. their not always installed). You could check the folders??
C:\WINDOWS\Microsoft.NET\Framework
They have to be there for it to work.
And another issue would be if the user does this on Windows 7, 64 bit, or the old 64 bit XP version. You would need to test for those in addition to get the proper reg values, etc. Thus, making requring pre-req's a better solution. The only thing I don't like about IS2010 is that they don't manage Framework .NET 4 very well.
Why wouldn't it not find the registry everytime, that seems weird (i.e. different OS's, etc). Or you'll selected the wrong registry values to check (i.e. their not always installed). You could check the folders??
C:\WINDOWS\Microsoft.NET\Framework
They have to be there for it to work.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)