Thanks! That is what I had expected -> put everything under c:

directly as applications are still allowed to write into such folders.

For me this would mean that I have to copy my existing Mercury

installation from c:\programme\mercury to c:\mercury and therefor I

guess that I need to modify some configuration files due to the path

changes. I hope that this is possible at all!

With "virtualization" I meant the file virtualization technology from UAC like it is described here:

https://decibel.ni.com/content/groups/windows-7/blog/2009/10/02/uac-virtualization-and-how-it-affects-your-installers

Hi All,

I'm planning to upgrade my outdated Windows XP to Windows 7 or Windows Server. What do I need to consider while doing so? What about UAC? Can I install Mercury under C:\program files (or  c:\Program Files (x86))? If my understanding is correct, UAC should not allow Mercury as a 32bit application to write into its own folder if it is installed in "c:\Program Files" and therefor should apply the file virtualization technology.

Anything else to consider on a "modern" OS?

Thanks

Konrad

Hi Konrad,

I noticed no responses yet so thought I would share my experience.  I recently moved Mercury/32 from C:\Mercury on an XP machine to C:\Mercury on a Win7 machine.  It was as simple as copying from one machine to the other.  You mentioned virtualization technology which is a reference I don't understand but staying out of the \Program Files directories is all that is required for Mercury/32 to run fine under a Standard user.  You need to create your own shortcuts of course.

I also run ClamAV and POPFile.  ClamAV was a simple copy from/to C:\ClamAV but POPFile requires installation.  I copied its db from the XP machine to eliminate the need to retrain.

HTH!