New Sandboxie release question | Gen-Tech | Forums

Wheezer said:

I was going to download and install the new Sandboxie release tonight. It now supports windows 7, 64bit. But then I saw that there was a "Notes about 64bit edition" page.

I went to the page and read it. After taking two asprin for the headach I got reading the page, because of my inability to understand what I was reading, I found myself left with a question.

Is installing this version worth having? Or is it just going to make my computer crash? Or does all that other stuff they're talking about fix the stuff that doesn't work? Or maybe it's time to forget about Sandboxie and try something else?

The page is at: http://www.sandboxie.com/index…..BitEdition

Thank you!

Hi Wheezer!

The 2 aspirins were fully justified;  There are 2 reasons:-

1. the html is not written in a simple manner. It is "geekspeak"; not "plainspeak"
2. the html does not say if sandboxie "should" or "should not" be used. It says "can be used", it does not say "should be used". There is a huge difference between "can" & "should" as you know. The guy who wrote decided the "can" part. That was the easy part. Only Wheezer can define the "should" part………which is the more difficult part. 

Wheezer Sandboxie should definitely not be used on your Win7 64 bit machine. Having answered you, let me know throw out the jargons & explain.

Simple Stuff:-

1. There are only 2 things essentially – files & registry. Bad boy apps screw up both. AV's etc are nothing but sentries & medicines to catch & remove pests. Since some pests are cleverer than AV's they can neither be caught or cured.
2. Sandboxie is like a huge barricade. Whatever is downloaded inside that barricade can't get out of it. So "bad boy apps" inside the barricade cannot screw up your files or registry. So you are safe even if you have a "bad boy app" inside your barricade rather than outside your barricade. Barricaded aka Sandboxied apps have their file settings & registry settings totally seperate & different from the file settings & registry settings of your main comp. Got it?
3. So now there is only one simple question does Sandboxie provide you a good strong barricade or not?

It provides a lousy barricade in your context aka Win7 64bit. *Therefore avoid Sandboxie totally like you would avoid plague*. Again "simple stuff explanation":-

1. The innermost core of your OS is the kernel just like your innermost core is your soul. If the core gets screwed or the core goes nuts everything gets screwed up
2. 64 bit OS has a more secure core. It keeps out anything which tries to fool around with it – ironically it even interprets Sandboxie's helpful intentions as "tampering" or "intrusion". Ironical but true. So do not go for Sandboxie.
3. This core also can be fooled. To use an analogy if an app (aka Sandboxie) wears a perfume e.g. musk. All those workarounds are the "can" part rather than the "should" part. *Stay away from it Wheezer*.
4. Look at it logically. If the Microsoft team wanted the core to be buddy buddy with Sandboxie they would have coded Win7 64 bit core to behave accordingly & perhaps even live with Sandboxie as "man & wife". They (Microsoft) didn't.
5. Ok you'll ask – then why were the workarounds offered. The work arounds were offered for reasons not all of which were noble. Haven't you noticed the following things Wheezer:-
   1. Fewer apps run in Win7 on date vs Vista or Xp. Do you think the Win7 team is able to sleep well at nights? So what do those guys do. They try to find out how an app can "buddy up to the core" aka let it wear musk perfume, possibly a lovely red veil, hair styled this way rather than that etc etc. What a lot of BS!
   2. 64 bit Win7 is not performing as well as 32 bit Win7. Read what Ashraf himself has said on this. So the guys at Redmond get even more desperate & sleepless. They provide tweaks
   3. By tweaking Win7 64bit or Sandboxie or both you could screw up either or both. Why take the chance?
   4. You've read our forums & main blog. 2 people (Samuel) & (Conn09) say that it is safer to buy Win7 only after Win7 Service Pack is introduced. Samuel indicated in the European Vigilance case or was it the OS dottechie survey (I don't recollect – read Samuel's last remark at least; its on the end of that thread btw). Samuel is very sharp like other dottechies & he is also very simple in putting things.
   5. Similarly you could screw up things by running in compatibility mode & ratcheting down. Compatibility mode running is no magic remedy or snake oil btw – refer main blog O&O disk defrag for reference. Fiddling around with Kernel for security is pretty high fallutin stuff dear friend. Please avoid it.
   6. Why add to your problems? Why be a guinea pig (leave those animals only to Animal Planet). Don't let them into your home. Keep Sandboxie out my dear dear friend.

So now what to do. 2 solutions:- 

1. Use something else. Choose something which loves getting married to the Win7 64 bit core & which would not ever seek a divorce from it simply because it loves that core with its entire heart & soul. This is preferrable or
2. Use Locutus solution – partition your laptop for 2 OS. One would be Win7 64 bit. Another one could be either Win7 32bit, Vista or Xp. You are a careful & intelligent person. You also have dottechies by your side always. Chances of a bad boy app shafting you are bleak

Don't get carried away by nearby well meaning friends telling you that Win7 64 bit is a clever bloke who has a hopper which can hop from 64 bit apps to a 32 bit apps & back based upon a feature functionality. The best proof I can offer is even the US govt still uses WinXp. Even if no one else is smart the govt always is. Mind you they hadn't shifted to Vista either

OS "hopping between 32 bit & 64 bit" is better avoided for now till the OS stabilizes worldwide.

That's my suggestion dear friend. The humour was to only wipe off the after effects of the 2 aspirins rather than adding to them.  All the best

Ramesh