Sandboxie Plus 0.9.7 Test Build

Exactly!

 

Ok, so to end the current confusion about any possible encoding-changes for the .ini-files (both Sandboxie.ini in the \Windows-Dir and Sandboxie-Plus.ini in the \Local\Sandboxie-Plus-Dir):

What is the EXACT DESIRED ENCODING for both of them? ASCII or Unicode or UTF8? And for the latter ones - with or without "BOM"?

And how do I properly comment out entries temporarily now? Until now putting a hash(#)-symbol before them did the trick. But as of lately, after putting a "#" before the current workaround-entry "InstantRecovery=0" in Sandboxie-Plus.ini I got some "%23%20" combination instead after re-opening the ini-file. Since those are the HEX-ASCII-values for hash and space I assume the ini-file must have been stored with the wrong encoding!

So precisely which encoding is the right one for the new?/changed? ini-format that will be used from now on? And is the hash-character still the proper choice for commenting out ini-statements temporarily?

 

The format is nto suposed to have changed, only the internal processing of it, hence if there are bugs than i need to sort them out, its not intended for the users to have to change anything about their ini file
# should still work and for me seams to work fine, can you provide an example of a file which will end up having the # rapleced ocne its re saved?

 

Interesting. I always choose the browsers under Applications and Web Browser/Mozilla Firefox. I'm going to try adding the apps directly in Forced Programs like you said if my way doesn't work on the latest build. I can't believe I didn't think of this before. Both ways basicly force starts the program but bypassing the Applications/Web Browser might be the answer to this issue.

 

Yea, I deleted all of the above and did a restart before reinstalling the next version. Never installed the Plus version (I'll do this in the future at some point). Getting ready to test the latest version now and try what GrDukeMalden suggested.

 

I saw it. I'm getting ready to test the classic 5.52.4 version now.

 

4th try. Everything works except for one minor issue.

Classic Sandboxie 5.52.4 (64 bit)

Did a clean install and went through the same setup process I always do with each version. Everything worked perfectly. I then removed the sandbox to see if I had the issue with the invisible options in the Sandbox dropdown menu. No issues. Everything works. Just to be sure, I uninstalled Sandboxie, deleted all files and folders, then rebooted and reinstalled 5.52.4 again. No issues and everything works perfectly.

Now for the minor issue. I still get the mixed settings in Applications/Web Browser/Mozilla Firefox. The settings should be grouped by app. Here's a pic of the mixed settings in 5.52.4:


Here's the grouped settings in 5.51.6:

 

Sure I can:

Line in question being:
"%23%20InstantRecovery=0"

Still, my initial question hasn't been answered:
What is the DESIRED, CORRECT ENCODING for those .ini-files, changed or not?
(ASCII/ANSI, UTF8, UNICODE, with or without BOM ?). Could you please specify?

 

ah its about the sandboxie-plus.ini not the normal sandboxie.ini
this is handled completely different using a Qt provided class, so if # does not work that find something else that works _ may be

 

? ? ? ? ? ? ? ?
Am I now supposed to try out all 256 ASCII-characters? Or are you telling me you don't know yourself if and how statements can be commented out temporarily in sandboxie-plus.ini at all?

And why can't you simply tell me/us what the correct/appropriate encoding for storing both of these ini-files would be? If I remember correctly there has been some talk of something having changed to UTF8 as of recently?

 

Rude and unnecessary. Without David's goodwill, where would we all be?

 

Unable to run Mozilla Thunderbird x64 (latest) - don't think this is new for me, but quite a while since I tried it.

WerFault.exe (12152): SBIE2101 Object name not found: Unnamed object, error OpenProcess (C0000022) access=001FFFFF initialized=1

 

True. But what's rude about insisting on a valid question (about the desired encoding) that has remained without an answer for 3 times now? Also the last reply sounded a little bit weird and confusing to me.

That said there can be no doubt about @DavidXanatos general merits with improving Sandboxie.

 

[QUOTE="algol1, post: 3039414, member: 164542"But what's rude about insisting on a valid question (.[/QUOTE]
Perhaps insisting is a sense of unjustified entitlement? A question being valid or not is irrelevant as David owes us nothing really

 

I tolled you use "_" to comment out stuff in the plus ini, about the encoding as I said the file is handled by a QT class so I would have to try out myself, just leave the encoding the file was created with.
I guess plain ascii will always work, I assume UTF8 may to but havn't tested it, I assume unicode will not work as qt is multi platform and this sort of Unicode is a mostly windows thing.


The normal sandboxie ini is handled by custom code and there were no changes to it in the last months with regard to encoding, only to internal handling of the values and parsing.

 

Thanks a lot for the clarification. My bad, I didn't recognize "_" (without quotes) as a suggested character for commenting out the first time around. As for the encoding the "no-change"-answer is recognized. Amazingly enough my editor shows the native sandboxie.ini in \Windows-Dir as "UTF-16 BOM" and since this editor can handle all customary encodings one can think of it probably may not be irrelevant which one to use after having made modifications to the ini-file manually.

Also I'd like to apologize if my last question seemed rude to you as some here have suggested. I certainly didn't mean to offend you as I had misunderstood your answer as not having answered my previous question at all.

 

posted for reference:
Current status of compatibility issues to fix #1076
https://github.com/sandboxie-plus/Sandboxie/discussions/1076

 

I have installed the new version on all my systems and it actually runs without any problems.

Only on one system there is a small problem. Whenever I open a file dialog (via "Open" or "Save") in a sandboxed program the following error message appears:

SBIE2101 CreateFile (C0000022) access=0012019F initialized=1

The program doesn't matter, it happens e.g. with Notepad, Firefox, Acrobat Reader... The error message can be ignored, everything still works. If the "Explorer" itself is opened in the sandbox, the error message does not appear. The problem occurs only from the current version 5.52.x (also 0.9.7x). With version 5.51.6 or previous versions the error message does not appear.

Any ideas what this could be related to? Thanks!

[Windows 10 21H1 (x64)]

 

but to clarify, it wasn't the question but the wordings used.

 

Addendum: The underscore ("_") seems to do the trick, albeit only without a space-character thereafter as that space will again be mis-represented as "%20" thereafter as soon as Sandboxie has stored that ini-file by itself. That may seem a bit strange as anything after a "comment character" is meant to stay as it is - but as @DavidXanatos has pointed out - that "Qt-stuff" (which I have no knowledge of) may not utilize the classic concept of comments at all.

 

Edge SmartScreen demo pages report wrong in Edge sbox with 0.9.7d
Edge SmartScreen reports downloads wrong in Edge sbox with 0.9.7d
Edge 94.0.992.38

Edit: Edge SmartScreen needs Default RPC Port Binding enabled.
Edge SmartScreen okay, now...with Default RPC Port Binding enabled.
0.9.7e

 

https://github.com/sandboxie-plus/Sandboxie/releases/tag/0.9.7e

signed

 

Cool, thanks.

Classic 5.52.5 installed over top after exiting existing Sandboxie. For my two boxes, it's good so far.

 

+1