Cad, you don’t want to understand what the problem is, do you?
Yes, “Program Files” was introduced as a central location to store applications. But at the same time, “Documents and Settings” and the Registry were introduced, as two central places where the applications are supposed to store their configuration in.
mAirList failed to follow this schema, because it used to store everything - software and configuration - in “Program Files”. Because I think - for a power user like you - it is very convenient when you can just copy and move around different program folders with different versions and configurations.
With the introduction of the recent Windows versions, Microsoft has finally locked out this sort of “legacy application”. Well, not exactly locked out, but it redirects all dynamic files (e.g. the ini files) to a “VirtualStore” folder hidden somewhere deep in your user profile. (And what makes it even worse, it’s in the user profile, not in the common profile shared by all users, so when a different person logs in, mAirList starts with a blank configuration.)
This is why it is a very good idea for application developers like me to store the configuration in a “safe place” right away, and this is what the default installation of mAirList will do in the future.
If you want to have an “old style” installation, you can just copy the config folder into the program folder again. mAirList will notice that and behave exactly like it did before.
