- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The same thing occurs with any virtualized application, at least on WinXP SP2. As soon as you use the Open or File Save As... and maybe other common dialogs, you have inconsistent write access to C:\ whatever specified directory isolation modes are. Isolation modes for subfolders seems to be handled correctly.
To reproduce this inconsistent behavior:
- launch a virtualized app and open its File open or File save as... dialog box
- from there, go to C:\ and right click to create a new text file, don't change its name for now. Leave the dialog box open. (1)
- right click to create another text file, name it test1.txt. Leave the dialog box open. (2)
- On the virtual system, you have both files
- On the physical system, you have only test1.txt
- From the dialog box, delete test1.txt and try to rename the first text document to test1.txt
- Ooops, you can't
- Now, on the virtual system, you see only the first text document (3)
- On the physical system, you have only test1.txt (is has not been deleted!)
So, the isolation mode for C:\ in this "Common dialog" case is just something oscillating between WriteCopy (1), Merged (2) and not-really-Full (3)
Sorry to say that, but it looks like it's definitely a bug.
Regards,
John