Preset install folder for Vista
These programs are configured to install into C:\Programs as the preset for Vista. That's a better location for them than your Program Files folder if you have User Account Control switched on.
The reason is that like many programs designed originally for XP and earlier, the configuration files are located in the same folder as the program itself. The program folder is also intended to be editable by the user.
If you want to share these programs with other users of the same computer, you can install them into a folder shared amongst all the users. Or alternatively install them separately for each user.
In Vista however, every program is expected to work with three different folders - the program location, the program initialisation files and the current folder for files saved by the user (all of which are separated further into per user and global locations). This system existed already in XP but was optional to the extent that not many programs followed the model. In Vista the system is strongly enforced by the operating system.
It's recognised that many existing programs don't fit this model. So Vista deals with programs like this by creating a "virtual store" which contains the actual data for any files you attempt to save into your Program Files folder. The files don't actually exist in your Program Files folder at all. However you see these files apparently in that location if you look at them using the Open and Save As windows. If you do a search of your hard disk or explore the folder for the program, you find that the files you saw in the Open and Save As windows don't exist there. You will find them in your virtual store instead. The virtual store is hidden in Vista so to find your actual files from outside the program, you need to switch on the option to see hidden system folders, then navigate to your virtual store and the correct location with in the virtual store - and then you will see them.
This works well up to a point - users get the impression that they are able to modify the contents of the program folder and modify files there from within the program and so all goes well up to a point. But things aren't quite as they seem - and this on occasion can lead to confusion.
Disadvantages of relying on the virtual store for these programs include:
- If you search your hard disk for a file you just saved, you will often find that it isn't where you think it is.
- A backup of the entire program folder can omit the files that only exist in the virtual store. E.g. if you just copy the folder using your Windows Files Explorer, the copy will not include any of the files from the virtual store. (Though the backups you configure within the program e.g. in Activity Timer, will back up everything).
- If you uninstall a program from Program Files, the program itself is removed but any files you saved in its folder yourself using the program, or any new configuration files saved by the program still exist in the virtual store. So if you reinstall it into the same folder again, then all the old files "magically" reappear.
- If you uninstall and reinstall a program in order to get back to a "clean slate", this doesn't work in Vista with UAC and the Program Files folder because of the "reappearing files" issue. It only works if you reinstall into a different folder from the one you uninstalled from - or if you find and erase its virtual store before the reinstall.
- Files that are in the virtual store sometimes can't be found by other programs e.g. if started up by file association from a link in one of my programs.
These issues have arisen in support for my programs. They can puzzle users, and can be tricky to resolve.
It is best to avoid this whole situation if one can. One solution of course is to switch off User Account Control. Many however will want to keep it on for its extra layer of protection from malware.
I have been unable to find any recommended folder for such programs in the microsoft documentation. But I have found out that some other legacy installers install into - and that seems as good a preset as any for an "unofficial" standard. Others install directly into Drive C but that could lead to a proliferation of sub folders of the root C making navigation potentially confusing. So - though not perhaps ideal, c:\Programs seems perhaps the best alternative I can find so far.
An alternative some users may prefer is be to create a Programs sub folder of your My Documents folder. Some programs do use My Documents for things that rather stretch the notion of a document. E.g. Microsoft itself uses My Documents as the folder for Virtual Machines for Virtual PC.
I have considered other alternatives but not come up with anything convincing yet. A rewrite of the programs to follow the Vista model was one option I explored briefly. However the single folder type model has advantages for small programs especially if you want the program folder contents to be accessible to the user. For the type of programs I write, these advantages seem to outweigh the disadvantages, so even with new programs I still use this simpler all in one folder type approach.
You can change the install folder on the third screen of the installer for any of my programs. If you don't like to install in you could try installing into a sub-folder of My Documents, or some other location more convenient to you. Your selection is remembered for any future installs of the same program.
|
|
| Disclaimer |
| products - preset install folder for Vista |  |
 |
free of spyware etc | Site Designed with advice from Sojo Media (Thanks!)