Windows 7 "Compatibility Files"
-
No you missed my point. I said nothing about read/write. Where did I mention that. I even clarified to you "The app creates a backup folder and then opens the new folder with windows explorer when backup is complete. But this backup folder is some-reason "Compatibility Files" and it throws an error that the folder can not be found. [even though it was successfully created]"
Jon Rista wrote:
My post before was just to let you know, since your not very familiar with Vista/Win7, that even if your logged on as admin, programs don't "run" as admin by default.
I think everyone knows this which is why I mentioned it so no one would bring it up. I don't remember seeing this "Compatibility Files" button on windows explorer in Vista.
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
JoeSox wrote:
text files and folders my application creates doesn't allow access.
I interperated that to mean that your application couldn't access text files created in your folders. I figurd my assumption could have been wrong, which is why I asked for more clarification of why/what/how in my first response. So the question still remains...WHAT/WHO can't access the files and folders? Your app? Other users? Your currently logged in user? Other apps?
JoeSox wrote:
I think everyone knows this which is why I mentioned it so no one would bring it up.
You mentioned you were an administrator...under Vista/Win7, if you want to make sure your readers fully understand the context your app is running under...say it was "Run as administrator". That completely removes any chance for misinterpretation. You can be an administrator and run an app and the app runs under a context with limited privs, which could cause the kind of problem your having.
JoeSox wrote:
I don't remember seeing this "Compatibility Files" button on windows explorer in Vista.
I havn't seen a "Compatibility Files" button in any version of windows...including Win7. Could you maybe take a screenshot or something of this button? Communication has obviously broken down...I don't think either of us understands what the other is saying at this point.
-
JoeSox wrote:
text files and folders my application creates doesn't allow access.
I interperated that to mean that your application couldn't access text files created in your folders. I figurd my assumption could have been wrong, which is why I asked for more clarification of why/what/how in my first response. So the question still remains...WHAT/WHO can't access the files and folders? Your app? Other users? Your currently logged in user? Other apps?
JoeSox wrote:
I think everyone knows this which is why I mentioned it so no one would bring it up.
You mentioned you were an administrator...under Vista/Win7, if you want to make sure your readers fully understand the context your app is running under...say it was "Run as administrator". That completely removes any chance for misinterpretation. You can be an administrator and run an app and the app runs under a context with limited privs, which could cause the kind of problem your having.
JoeSox wrote:
I don't remember seeing this "Compatibility Files" button on windows explorer in Vista.
I havn't seen a "Compatibility Files" button in any version of windows...including Win7. Could you maybe take a screenshot or something of this button? Communication has obviously broken down...I don't think either of us understands what the other is saying at this point.
Jon Rista wrote:
WHAT/WHO can't access the files and folders? Your app? Other users? Your currently logged in user? Other apps?
System.Diagnostics.Process.Start(Common.backupRootFolder);it was created byDirectoryInfo dinfo = Directory.CreateDirectory(Common.backupRootFolder);it works in WinXP and VistaJon Rista wrote:
I havn't seen a "Compatibility Files" button in any version of windows...including Win7. Could you maybe take a screenshot or something of this button?
http://farm4.static.flickr.com/3528/3202437651_d786f2b1fa_o.jpg[^]
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
-
Jon Rista wrote:
WHAT/WHO can't access the files and folders? Your app? Other users? Your currently logged in user? Other apps?
System.Diagnostics.Process.Start(Common.backupRootFolder);it was created byDirectoryInfo dinfo = Directory.CreateDirectory(Common.backupRootFolder);it works in WinXP and VistaJon Rista wrote:
I havn't seen a "Compatibility Files" button in any version of windows...including Win7. Could you maybe take a screenshot or something of this button?
http://farm4.static.flickr.com/3528/3202437651_d786f2b1fa_o.jpg[^]
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
Ok, I might know what is going on. Windows Vista and Windows 7 both changed how user-data created by applications is handled. They REALLY don't want programs writing to C:\Program Files\, and prefer that all applications write to C:\ProgramData\ or C:\Users\[user]\AppData\[app-specific-folder]. I have not encountered it for a while, but Vista and I assume Win7, since its based on vista, have a file virtualization feature that keeps user data isolated from program/system data in protected locations (C:\Windows, C:\Program Files, C:\System Volume Information, C:\Boot). I am guessing that your programs data is being virtualized, and that Compatibility Files is appearing so you can see the virtualized data. Usually virtualization like this happens when the account executing a program doesn't have the right permissions to write, but does have permissions to execute, in a given location (which still makes me wonder if you have tried running the application with "Run as administrator"...which should have solved the problem). Only recommendation at this point is to write that data to some subdirectory in C:\ProgramData (for application global data), or C:\Users\[user]\AppData (for user-specific data). Under Users, you can store data in Local, LocalLow, or Roaming. The .NET framework has direct support for storing user-specific data, called Isolated Storage. It will automatically handle creation of a unique folder under C:\Users\[user]\AppData for you, and allows you to choose the profile (local/roaming). I am not exactly sure how to store data under C:\ProgramData...I've never tried before, as I always opt for Isolated Storage. Its entirely possible that its automatic...and that ProgramData is where files are automatically virtualized when you write to C:\Program Files. EDIT: This might help: http://support.microsoft.com/kb/927387
-
Ok, I might know what is going on. Windows Vista and Windows 7 both changed how user-data created by applications is handled. They REALLY don't want programs writing to C:\Program Files\, and prefer that all applications write to C:\ProgramData\ or C:\Users\[user]\AppData\[app-specific-folder]. I have not encountered it for a while, but Vista and I assume Win7, since its based on vista, have a file virtualization feature that keeps user data isolated from program/system data in protected locations (C:\Windows, C:\Program Files, C:\System Volume Information, C:\Boot). I am guessing that your programs data is being virtualized, and that Compatibility Files is appearing so you can see the virtualized data. Usually virtualization like this happens when the account executing a program doesn't have the right permissions to write, but does have permissions to execute, in a given location (which still makes me wonder if you have tried running the application with "Run as administrator"...which should have solved the problem). Only recommendation at this point is to write that data to some subdirectory in C:\ProgramData (for application global data), or C:\Users\[user]\AppData (for user-specific data). Under Users, you can store data in Local, LocalLow, or Roaming. The .NET framework has direct support for storing user-specific data, called Isolated Storage. It will automatically handle creation of a unique folder under C:\Users\[user]\AppData for you, and allows you to choose the profile (local/roaming). I am not exactly sure how to store data under C:\ProgramData...I've never tried before, as I always opt for Isolated Storage. Its entirely possible that its automatic...and that ProgramData is where files are automatically virtualized when you write to C:\Program Files. EDIT: This might help: http://support.microsoft.com/kb/927387
Jon Rista wrote:
(which still makes me wonder if you have tried running the application with "Run as administrator"...which should have solved the problem).
That works. Thanks. It doesn't make my job any easier however.
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
-
Jon Rista wrote:
(which still makes me wonder if you have tried running the application with "Run as administrator"...which should have solved the problem).
That works. Thanks. It doesn't make my job any easier however.
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
-
I've skipped over Vista so please excuse me if this 'feature' nugget is found there also but even if I "show all hidden files" darn text files and folders my application creates doesn't allow access. What gives?:confused:?
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
Has Vista virtualised your file-writes? because they are going to locations that are normally only accessible by an administrator. You can embed an application manifest in your executable that specifies at what level your app should run at (asInvoker/asAministrator etc). When Vista sees the manifest it will disable virtualisation and your file-writes will fail (rather than being virtualised) if you try to write somewhere without having permission.
modified on Saturday, January 17, 2009 7:54 AM
-
Jon Rista wrote:
and choosing "Run as administrator"
It's a freaking folder. a folder for crying out loud.
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
I can't imagine why you got a 1. Sounds like I will be using XP for a long, long time.
Christian Graus Driven to the arms of OSX by Vista.
-
I've skipped over Vista so please excuse me if this 'feature' nugget is found there also but even if I "show all hidden files" darn text files and folders my application creates doesn't allow access. What gives?:confused:?
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
-
I've skipped over Vista so please excuse me if this 'feature' nugget is found there also but even if I "show all hidden files" darn text files and folders my application creates doesn't allow access. What gives?:confused:?
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
first.... WHERE is the folder in question... is it a subdirectory of the installation directory (program files...) or user directory? or elsewhere?
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
-
first.... WHERE is the folder in question... is it a subdirectory of the installation directory (program files...) or user directory? or elsewhere?
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
El Corazon wrote:
it a subdirectory of the installation directory (program files...)
http://farm4.static.flickr.com/3528/3202437651_d786f2b1fa_o.jpg[^] Subdirectory of the program files installation folder.
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
-
El Corazon wrote:
it a subdirectory of the installation directory (program files...)
http://farm4.static.flickr.com/3528/3202437651_d786f2b1fa_o.jpg[^] Subdirectory of the program files installation folder.
Later, JoeSox CPMCv1.0 - Last.fm - MyFriendfeed - Joesox.com
okay... the gist.... remember when you first ran XP and tried to view the program files and it asked you if you really wanted to do that? It was part of the first steps trying to move people away from using the program files as read-write-update-add data systems. The primary reason is for security, you don't want your programs free run of the system directories. Under vista and above they cannot be "upgraded" to administrator on the fly. The preferred way is with "run as administrator" even though you are administrator, your user account still can't run willy nilly through the OS directory structure. Root system drive, Windows, and program files are off limits withought explicit upgraded privlidges (as apposed to implicit given by your login) -- i.e. you have to ask for the ability. There are cheats that work well, for instance creating a shortcut to a job schedule that runs your project can give admin privledges once a login ID is assigned to the task.
