EditorNavigation setting change does not work
-
- KVRist
- 160 posts since 6 Aug, 2009 from UK
I agree it's a complete mess.
It should be transparent to the application though. If the app is performing file operations windows should present the files in virtualstore as if they are in the actual location.
When you browse Program Files with explorer though you won't see the updated files unless you select "Compatibility Files" on the explorer menu.
One of the problems is if you delete the files or directory's from Program Files it does not delete the files from virtualstore so you end up with a big unsynchronized mess.
One way to get round it is to run the application as Administrator. It then has access to update the files in the real location without taking a copy.
With MU.LAB I just run it from another directory away from Program Files.
Here's a possible way to disable it but I have not tried it
http://www.jondavis.net/techblog/post/2 ... Store.aspx
It should be transparent to the application though. If the app is performing file operations windows should present the files in virtualstore as if they are in the actual location.
When you browse Program Files with explorer though you won't see the updated files unless you select "Compatibility Files" on the explorer menu.
One of the problems is if you delete the files or directory's from Program Files it does not delete the files from virtualstore so you end up with a big unsynchronized mess.
One way to get round it is to run the application as Administrator. It then has access to update the files in the real location without taking a copy.
With MU.LAB I just run it from another directory away from Program Files.
Here's a possible way to disable it but I have not tried it
http://www.jondavis.net/techblog/post/2 ... Store.aspx
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
I am not on W7 yet but someone told me what cytone suggested which is
"With MU.LAB I just run it from another directory away from Program Files."
"With MU.LAB I just run it from another directory away from Program Files."
ABEFLGMOPPRRST 
-
- KVRist
- 131 posts since 10 Jan, 2010 from York, UK
Yep, that's what I do too, on Windows 7.cytone wrote:........ With MU.LAB I just run it from another directory away from Program Files.
For all my MU.LAB related stuff, I steer well clear of any 'Program Files' folder.
Just creating a parent folder such as "C:\Music Creation" , or even "C:\Programs", - and nesting all my MU.LAB stuff within it has always worked well for me, without any problems, over the past 4 years.
If, at some future time, MU.LAB ever requires the use of an 'installer' program, hopefully it would not 'force' us to install into the windows "Program Files" folder (!).

- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
The MUTOOLS Downloads page and the MU.LAB Troubleshooting doc page have been updated and now include a note about this Windows probem. I'll keep an eye on this issue and will do some extra tests in the future.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
There is a Windows call that can be made to tell the OS you need Admin privs. (This in windows 7 makes the screen go dark whilst the user is deciding whether to allow it or not, seen on installers and when running stuff as admin.)
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Thanks. I've been reading some info about this topic and will digest it more, and do some tests. Calling such function from within the app may be a solution for some of the issues, but what uke encountered would still be there: Simply editing one of Mulab preference files doesn't always work 
-
TheGuysanIdiot TheGuysanIdiot https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=213066
- KVRist
- 308 posts since 10 Aug, 2009 from United Kingdom
Spelling
web site "mechanisms" not "mecanisms"
OZ
web site "mechanisms" not "mecanisms"
OZ
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
