United States of America
When I installed MP, I noticed a severe lag when attempting navigate the shares and databases throughout the various modules (movies, music, etc.). I didn't notice too many posts regarding this issue so I chalked it up to something odd with my install, or something to do with Vista's acceptance of the MP installation.
I run a limited user account in Vista with UAC enabled. Yes, I'm one of the few who DOES like UAC. Anyway, it is well known that to install anything in Vista you must do so as an admin. This is all fine and dandy. But, problems arise when you start to configure everything just after the install and running MP as an admin. With elevated rights, the configuration goes well and the database files are created in the windows\program data\ directory. However, if you finish the config as an admin, the database files are created with no write access to them by the users. This, is a very normal way of installing things. However, if the config is NOT fully completed, that is, you don't configure the music database for instance, you leave that for the limited user to create in the windows\program data directory. So, what you end up with are different files or databases, some with user write rights and some with only admin write rights in the windows\program data directory. This leads to a virtualization of those databases in the limited user's VirtualStore directory of those databases that were initially created by the admin. Again, all very normal. But, what is NOT normal is the fact that you end up with different databases with different rights.
This problem can be solved by deleting the contents of the program data\MP directory as well as the databases in the user's VirtualStore. Then, reinstall, but this time do NOT configure immediately after the installation. Instead, close out, and simply run the config as the limited user. That way, the user will have full rights to the databases that are created in the program data directory, and they will all be uniform in access rights. When I installed in that manner, the difference was like night and day in terms of overall responsiveness while navigating.
The way the whole installation procedure could be improved would be to have the install create ALL the databases and files that MP will ever need BEFORE one could possibly manipulate the databases. That way, although all the databases will only have admin rights in the program data, the user's databases will all be formed in the VirtualStore, and not distributed between the 2 locations.
I run a limited user account in Vista with UAC enabled. Yes, I'm one of the few who DOES like UAC. Anyway, it is well known that to install anything in Vista you must do so as an admin. This is all fine and dandy. But, problems arise when you start to configure everything just after the install and running MP as an admin. With elevated rights, the configuration goes well and the database files are created in the windows\program data\ directory. However, if you finish the config as an admin, the database files are created with no write access to them by the users. This, is a very normal way of installing things. However, if the config is NOT fully completed, that is, you don't configure the music database for instance, you leave that for the limited user to create in the windows\program data directory. So, what you end up with are different files or databases, some with user write rights and some with only admin write rights in the windows\program data directory. This leads to a virtualization of those databases in the limited user's VirtualStore directory of those databases that were initially created by the admin. Again, all very normal. But, what is NOT normal is the fact that you end up with different databases with different rights.
This problem can be solved by deleting the contents of the program data\MP directory as well as the databases in the user's VirtualStore. Then, reinstall, but this time do NOT configure immediately after the installation. Instead, close out, and simply run the config as the limited user. That way, the user will have full rights to the databases that are created in the program data directory, and they will all be uniform in access rights. When I installed in that manner, the difference was like night and day in terms of overall responsiveness while navigating.
The way the whole installation procedure could be improved would be to have the install create ALL the databases and files that MP will ever need BEFORE one could possibly manipulate the databases. That way, although all the databases will only have admin rights in the program data, the user's databases will all be formed in the VirtualStore, and not distributed between the 2 locations.