Hi.
I have version 3.48 (registered).

My Sandboxie.ini file has a content as shown below:



Note the FileRootPath entry under [Flashdrive]. It's nothing wrong with the folder at all.
But trying to run any program under the Flashdrive sandbox, every program I run, see all files (or most of them) as read only. Result - most programs is heavily disabled and won't run properly.

[edit]
The defaultBox works as expected

Did you intend to have your main Sandbox Container folder on the flash drive (G: ), as well as the [Flashdrive] sandbox also on flash drive G:, but in a different sub-folder on that drive? It shouldn't be a problem except perhaps for the slow operation of a flash drive.

I tested with my main Container folder and a flash drive sandbox folder on different drives, running Firefox and saving and deleting bookmarks, and had no problem with read-only operation with the flash drive.
[GlobalSettings]

FileRootPath=K:\Apptemp\Sandbox\%SANDBOX%


[Flashdrive]

FileRootPath=V:\myDocs\CompactCard128\%SANDBOX%

(I should also mention that I'm using 3.49.10, but I don't know if that makes any difference with my results)

Can Flash drives be formatted as NTFS and/or have NTFS-like permissions?

My point is this, perhaps either the myDocs or CompactCard128 folders have permissions that prevent Sandboxie from writing anywhere below these folders.

Hi.

The flash card is formatted as FAT. I've tested it (exessive file copy operations over time) and confirmed nothing is wrong with the flashcard.

The main Sandbox Container folder is located on a regular drive. As long as that's the ONLY container folder i use, then Sandboxie acts as expected.

After I running t.ex Google Chrome in Samdboxie and choose "Flashdrive", I expect that the G:\myDocs\CompactCard128\%SANDBOX% should be filled up with files that is created by Chrome. But it don't.
It just contains those files:
consuming only 257 kB disk space.

I would still like to see some clarification on this ^^
Your sandboxie.ini file shows:

[GlobalSettings]

FileRootPath=G:\Apptemp\sandbox\%SANDBOX%
----
and the FlashDrive sandbox shows:
[Flashdrive]

FileRootPath=G:\myDocs\CompactCard128\%SANDBOX%

Where G: is apparently the Flash drive - unless you have a G: hard drive and a G: Flash drive, too.
Since they both show G: drive, are you saying that the Sandbox Container folder is no longer on G: drive?
Have you changed the Container folder location since posting the .ini file above?

The flashdrive is mounted as a NTFS Folder. The G disk is a regular 30Gb disk in good shape. Same with the flash card.

This could be the cause of the problem.

I'm gonna try mounting the flashcard as a Drive letter instead.
Btw: the folders "user" and "drive" won't be created in the G:\myDocs\CompactCard128\%SANDBOX% directory.

// Now testing with version 3.50


[edit]
I mounted the flashdrive as T:

Created a new sandbox located as T:\%SANDBOX% and it worked fine.

tzuk suggestion that drive mounted as a ntfs folder is the cause shows to be correct.

Should be a point in the faq OR being fixed in next version (if possible).

Problem solved/workarounded

I'll look into this and see if I can fix it.

Sandboxie seems to have problems dealing with NTFS-volumes, which have been mounted into another volume's subfolder, e.g.:

There is a Volume1, that has the drive letter C:\, and a Volume2, that as no drive letter, but is mounted to C:\Backup. If the Container folder is set to C:\Backup\Sandbox, it is e.g. not possible to install any application into any sandbox anymore.

@tzuk: Maybe you could take a look into this? I would be happy to provide additional information.

--Frodo


Sandboxie: 3.54 (64-bit)
Windows 7 Ultimate (64-bit), Build 7601: SP 1

I am aware of this problem and I have it on my to-do list:

http://www.sandboxie.com/phpbb/viewtopic.php?t=9086

I'll get to it at some point, I just can't promise when. In the mean time, a workaround is to (also?) mount the same volume as a drive letter, of course.

If you can't mount a volume in two places, then maybe you could mount the volume as a drive letter, and use a directory junction point where the volume is now mounted as a folder.

I am using version 3.56 on XP 32bit SP3

I have mounted partitions from an external USB hard drive to several folders on the C: drive.
I did this using the built-in disk manager in windows XP.

Partition one is pointing to c:/a/
Partition two to c:/b/
and so forth..

Access from unsandboxed apps is as it should be. I can read and write to the folders.
The same applies to sandboxed apps without full access, since they use their own file system.

When attempting to WRITE, using a sandboxed app that has full access to these NTFS mounted folders, access is denied. An easy way to verify is starting explorer.exe sandboxed and then attempt to create a directory.
Sandboxie can READ from the actual file contents without a problem, whether sandboxed with or without full access.

Obviously this has to do with the NTFS mounted folders and sandboxie not getting along.

Yes, this is a known incompatibility. I hope to have a solution to this problem at some point, but I'm afraid I haven't been able to look into it yet.

Sandboxie 3.56
Windows 7 Ultimate 64-bit
(If it makes any difference, the Sandbox directory is on my F drive)

Hi, I've been having problems using Sandboxie with volume point points.

I have a partition mounted on C:\Data, and another mounted on C:\Software. Every program I have tried in Sandboxie cannot save files anywhere in these areas, both in the root directory and sub directories.

When saving a new file in the sandbox, most programs (e.g. Notepad, Paint) give "C:\Data\<filename> File not Found. Check the file name and try again" or some variant of. If I try to create a new file or copy a file using Sandboxed explorer, I get "Could not find this item. This is no longer located in C:\Data\<subdir>. Verify the item's location and try again."

When saving a file that pre-existed outside the sandbox, I get some variant of "Access denied". In explorer, trying to move or delete pre-existing file gives "An unexpected error is keeping you from moving the file. If you continue to receive this error you can use the error code to search for help with this problem. Error 0x800700C1: <filename> is not a valid Win32 application"

However, most of the time if a sandboxed program running with UAC privileges creates a file, the volume mount point then begins to appear as a normal folder in sandboxed explorer and new files can be created as they should be. But the issues with pre-existing files still exist, and sometimes other strange behaviour sometimes occurs instead (e.g. one time, creating a file with UAC notepad resulted in an inaccessible Windows directory appearing in the location instead, although the sandboxie directory tree displayed the file as it should).

I found this somewhat related thread. Junction points to directories are handled fine (at least from the limited testing I've done), however the solution in the final post of that thread suggesting to make junction points to the mount points did not work. I would like to avoid the junction workaround as it would still mean having two unwanted drive letters.

Thanks

Sandboxie doesn't support mount points very well at this time, but I plan to address this in a future update.