OldGrantonian

I said in an earlier post: This is ambiguous. Sorry about that. The statement should have referred only to Sandboxie. So the correct statement is: Within Sandboxie, you can configure which files are allowed to access the internet: All files. No files. A list of files (whitelist), which would include "Evernote".

The Sandboxie developers didn't say "no" to my suggestion. But they didn't say "yes" either: https://forums.sandboxie.com/phpBB3/viewtopic.php?f=17&t=25754 The important thing is that they didn't disagree with my description of how a sandbox handles files, and that the user has complete control over which files are allowed out of the sandbox (which of course is the whole purpose of any sandbox). If no files are allowed out of the sandbox, then the only communication between a sandbox and a laptop is synching via the internet - exactly the same as between a smart phone and a laptop.

Just one more thing.... (Columbo). Before posting on the Sandboxie forum, I tried running one non-Sandboxed EN and one SB EN. (After backing up my database.), I tried various combinations of the following tests. To speed things up, I used manual synch in the window being edited, followed by a manual synch in the other (SB) window. So I've exceeded my free monthly allowance for the first time. Each synch is an upload ? Create new note on non-SB Create new note on SB Edit a note on SB Edit the same note on non-SB Edit a note on non-SB Edit the same note on SB The behaviour, IMHO, is clear and understandable. Adding something in one note causes the same text to be added to the other note. Conflicting notes are shown in the left panel and in the "Location column". Q: How do you know whether you're working in non-SB or SB? A: (1) On the taskbar, the icons are the same, except that the SB icon is preceded by "[#]". (2) The SB window has a yellow border. (Presumably yellow is chosen as the colour of sand). Each instance has its own Trash. I don't know how Trash is handled if you have two devices (laptop + phone). But maybe you should check each Trash before closing the SB instance.You should try this with fake notes as soon as possible. And if you're still worried about conflicts, you can disconnect from the internet, and close SB after use. Don't accept the offer to overwrite any of the non-SB files.

I haven't tried to run a non-Sandboxie session and a Sandboxie session simultaneously. But AFAIK, there's no danger if the user does not actually change anything in the SB instance. AFAIK, here's how the process works. The non-SB EN uses all the normal files. When the SB EN starts life, all the current non-SB files are copied within the SB. After that, the files lead independent lives. If the user does not cause any files to be changed within the SB, the SB session can be closed at any time with no effect on the non-SB files. Assume that the user causes some files to be changed within SB. When the user closes the SB session, she is presented with a list of files that have changed during the session. She can then choose which of those files will overwrite the current non-SB files. IMHO, the safest options are either (a) to overwrite no files, or (b) to overwrite all changed files. In both cases, the result will be a consistent database, with no conflicts. Obviously option (a) would be chosen by the OP. Good point ? But, IMHO, the situation is no different to having one instance on your laptop and one instance on your phone. I admit that no-one is likely to make changes on both of these devices simultaneously. I'll run this suggestion past the SB forum, and get their opinions. Thanks.

I think you can open a second instance inside the free Sandboxie. The two instances are independent - unless you deliberately choose to allow them to communicate. https://www.sandboxie.com/

. The "Date Created" will remain at the date you created the note. But the "Updated" date will be the date that you restore it from Trash. I'm not a techie, but I can't understand why the developer thinks that deleting a note, and then retrieving it from Trash, should be considered an update rather than a restore. .