Windows Vista installation problem - Advanced Installer Community

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!

Epsilon
Posts: 25
Joined: Wed Dec 27, 2006 1:09 am
Location: New Zealand
Contact: Website

Windows Vista installation problem

A user installed my AI product (Paca-Man V5.0.0) on Windows Vista and it ran OK. He then uninstalled the product. The installation folder did not contain any of the installed files. All OK so far.

He then installed a later release of Paca-Man (V5.0.2) and this installation went OK. When the application was started the user found that the Version of the Paca-Man.mde file installed was still V5.0.0.
I don't understand how the installation can have installed the older copy of Paca-Man.mde unless Windows Vista has somehow decided to reinstate a cached copy of the file. Note that the timestamp of the original V5.0.0 Paca-Man.mde would be more recent than the V5.0.2 version because the user had started the first application and Microsoft Access updates the timestamp every time you open a database (mde) file.

Has anyone observed this behaviour on Windows Vista? It works OK on other platforms (Windows XP and earlier). Is there something I can do in the AI configuration to force installation of the files?

I emailed the user a ZIP file with the newer Paca-Man.mde file and he overwrote the file in the installation folder. The application ran correctly as V5.0.2 - not a very satisfactory solution though.

The install files can be found at http://www.epsilon.net.nz/Download/Paca-ManV5.0.0.exe and http://www.epsilon.net.nz/Download/Paca-ManV5.0.2.exe (Note you need Microsoft Access 2000,2002,2003 or 2007 for this to install).

Richard Williams
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi Richard,

I cannot reproduce this behavior on my Vista test computer. I followed the exact steps you have provided and the file (paca-man.mde) is different than the one installed by version 5.0.0 (the new size is about 12.3 MB, the old was about 9.73 MB).

Have you tried to reproduce this on other computer?

Let me know if the problem persist.

Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
Epsilon
Posts: 25
Joined: Wed Dec 27, 2006 1:09 am
Location: New Zealand
Contact: Website

Gigi

Thanks for your prompt reply. I don't have a Vista test machine but have had another user report the same problem! That's 2 out of 2 Vista users with the same problem.

When you installed the first version did you actually start the application? This would have set the timestamp for the V5.0.0 file to a later date/time than the later version. Perhaps this is why Vista did actually overwrite with the newer file.

You could try uninstalling now and running the V5.0.0 install again to see if that version is reinstated or you are left with V5.0.2. You would need to run the application (and create a new empty data file) in order to get to the Main Menu and select Help/About in order to check the version.

I will persevere with my testing once I can get my hands on a Vista machine. Perhaps there is some user option to do with caching that affects this behaviour.

If you hear of any similar problems I would appreciate being advised of it by way of an update to this post.

Thanks again

Richard Williams
Epsilon
Posts: 25
Joined: Wed Dec 27, 2006 1:09 am
Location: New Zealand
Contact: Website

Explanation found

I have found an explanation for this problem. Because Vista does not allow any updates to happen in the "Program Files" folder (and because my application is an Access Database that is always being updated when it is run) Vista virtualises (copies) the application file to the user's "VirtualStore" and runs it from there.
When a new version is installed, AI successfully updates the "Program Files" folder but, when the user runs the application, it is still using the 'old' virtualised copy of the file! Vista obviously can't tell that it should re-virtualise the application file.
My solution is to change the installation and put all files into the [CommonAppDataFolder]. Vista does allow this folder to be updated.

Now my problem is that during installation of the Update (V5.0.3) AI (or Windows Installer) remembers the folder that the application it is removing was installed in and doesn't force the new version to be installed into the new location.

So my question now is: how can I get AI to populate the install folder with the 'new' target location if it automatically removes the application during an update? Currently, it remembers the "Program Files" location and the user won't know that they need to change this. If the user manually uninstalls the application first it works OK. I have added a prerequisite to ensure that the application is not already installed but, when using 'Check for Updates', this always makes the automatic update fail because the application is already installed and now won't upgrade itself! Catch-22.

What I need is an option in AI on the "Install Parameters" page that gives me the ability to "Ignore previous installation folder" or similar.

Any help would be appreciated.

Thanks

Richard
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi Richard,

You can read more about Vista virtualization here:
http://www.advancedinstaller.com/forums ... =8704#8704
Currently, it remembers the "Program Files" location and the user won't know that they need to change this. If the user manually uninstalls the application first it works OK
Yes the old location is automatically detected and used. You can overwrite it by creating a "Directory Set With Formatted" custom action under "InstallUISequence->CostFinalize". Select the "Application Folder" and type "[CommonAppDataFolder]" in the "Formatted Text" field. Drag & drop (while shift key is pressed) this custom action under "InstallBeginSequence->CostFinalize".

Regards,
Gigi
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com/
Epsilon
Posts: 25
Joined: Wed Dec 27, 2006 1:09 am
Location: New Zealand
Contact: Website

That worked a treat.

Thanks very much for your help, your support is superb :D

Thanks, Richard

Return to “Common Problems”