We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

Jay_Timber
Posts: 8
Joined: Fri Sep 07, 2012 12:30 pm

64 bit Registry problems

As part of an installer i'm importing an AutoCad profile, this has many stings that contain paths like 'C:\Program Files\autodesk\autocad 2013\help' but when imported to Advanced installer, its changes every reference of 'C:\Program Files\' to [ProgramFilesFolder]. But this is a 64bit installer and system, so the complied installer when run puts incorrect paths in namely 'C:\Program Files (x86)\autodesk\autocad 2013\help'.

So...

1: Why is it doing this and can i make it use the correct [ProgramFiles64Folder] instead with out having to manually search the whole (huge) key and change it by hand.
or
2: Stop it changing every reference to 'C:\Program Files' and just leave the paths alone.

Many thanks
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: 64 bit Registry problems

Hello,

Please keep in mind that this is the normal behavior. I'm afraid that in order to avoid this you should manually set the related registries values with ProgramFiles64Folder property. Also, if your project contains a large number of such registries, then you can send us the .AIP (project file) to support at advancedinstaller dot com and we will edit it for you?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Jay_Timber
Posts: 8
Joined: Fri Sep 07, 2012 12:30 pm

Re: 64 bit Registry problems

OK I have manually searched and replaced all the [ProgramFilesFolder] with [ProgramFiles64Folder], although this took time it is working.

But I have a very urgent new related issue.

I have created a registry search which finds the install location of Autocad, the sting is finds contains the data/path of 'C:\Program Files\Autodesk\AutoCAD 2013' but again Advanced installer changes this! Although its set to Type: Raw Data. It changes the data to 'C:\Program Files (x86)\Autodesk\AutoCAD 2013'.

i hope this is not the correct behaviour of the software because it is wrong, The software in not installed in 'Program Files (x86)' its in 'Program Files'.

But if the search finds another location other than the default program file folder (D: or another drive) its leaves it alone and works correctly i.e 'D:\Program Files\Autodesk\AutoCAD 2013'.

I have to get this working so to correctly set some registry strings, otherwise the whole project cannot work.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: 64 bit Registry problems

Hello,

I'm afraid this is the standard Windows Installer behavior if you are using a 32-bit package type. The AppSearch standard action redirects all the 64-bit paths from search results to 32-bit paths if you are using a 32-bit package type. However, as a workaround you can use a "Mixed 32/64-bit Package" type or you should create your own custom action which will edit accordingly the related property (which stores the search result). Also, the custom action should be scheduled after "Wizard Dialogs Stage -> Searches" and "Install Execution Stage -> Searches" action group.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Jay_Timber
Posts: 8
Joined: Fri Sep 07, 2012 12:30 pm

Re: 64 bit Registry problems

The package type is 64-bit so I'm confused as to why it targets the 32bit application folder?

I have just change the package type to mixed, but the search still gives the C:\Program Files (x86), are there further step than just selecting the package type?

If I have to go down the custom action route can you provide a example of how this would work.

Thanks
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: 64 bit Registry problems

Hello Joe,

If you are using a 64-bit package type, then the related search should return the "C:\Program Files" location value.

This is important: Please keep in mind that if you are using our [Test Search] option to check the search result, then the related search result will contain the "C:\Program Files (x86)" location value because our "Test searches" option uses 32-bit package type rules. So, you should run the project package in order to check the related search result. If this is not the case, then can you send us a test case scenario or attach a sample reproducing the issue?

Also, in order to check the related search result (which is stored in a property, i.e. MY_SEARCH) when run the project you can add an "Execute inline script code" custom action with sequence, scheduled after Wizard Dialogs Stage -> Searches" and "Install Execution Stage -> Searches" action group, like this:
  • Source Type: Visual Basic Script (*.vbs)
    Script Text: MsgBox Session.Property("MY_SEARCH")
All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Jay_Timber
Posts: 8
Joined: Fri Sep 07, 2012 12:30 pm

Re: 64 bit Registry problems

Ok great i did not know that about the test, thats great I will compile the installer and test for real.

Return to “Building Installers”