Post here please if you want to talk about version 3.49.

But please do not post your problem reports here. Use the problem reports forum.

A request: Any possibility you could provide separate installation files for 32-bit and 64-bit (as in the past)

And a question: Is the dll file (sbiedll) the only (or primary) difference between the 32-bit and 64-bit versions of sbie?

Well if we were talking about the final builds of Sandboxie, I could understand your request, but seeing as these are just beta builds, I can understand if tzuk doesn't want to separate the builds into separate x86/x64 installers.

Anyways, I have a request.
Back in the old days when you released a new beta build, you used to have a mini changelog posted right beneath the download link, letting everyone know what has been added, fixed or changed in that build. However lately, you've only been posting the download link and below it a message alerting users that "You wont be able to post here, you can only respond to threads once I move them here, etc.." so as you probably guessed, my request is if you can post the changes in each beta build as you used to before.
I understand it can be time consuming to do this, or maybe you'd just rather wait til a final build to post the entire changelog, but if it isn't any trouble, it would be nice to see the mini changelogs make an appearance again.

Oh and a question.
Do you think the Forced User setting will make a return during this v3.49 beta run, or do you have the feature chalked up for a later date?

soccerfan, the DLL file is just about the one thing that isn't different between the 32-bit and 64-bit versions. Because that 32-bit DLL is also needed in the 64-bit version but everything else is built as 64-bit code.

As for separate 32/64 builds, I will probably still occasionally do that, it's a bit of a hassle though. What is the difference in terms of download for you? It's a pretty minor difference for me.

SnD, I prefer the approach I've adopted for quite some time now, where I move topics to this forum area. You can still get a pretty good picture of the changes, you just need to read a bit more to get it..

And yes the Forced User thing setting will make a comeback at some point.

Wow, actually, I always noticed that when there is a new beta section of the forum, there would always be some threads that carried over from "Problem Reports" but I never noticed why.
I assumed the threads were issues you planned on dealing with during that beta run, but now I noticed they are issues you have (or tried) fixing in a beta build. I feel dumb.

For the longest time, rather than a formal install, I have been upgrading sandboxie by stopping/deleting the driver and service, then rebooting, and pasting the following extracted files from the newest installation executable to my install directory:

KmdUtil.exe
SandboxieBITS.exe
SandboxieCrypto.exe
SandboxieDcomLaunch.exe
SandboxieRpcSs.exe
SandboxieWUAU.exe
SbieCtrl.exe
SbieDll.dll
SbieDrv.sys
SbieMsg.dll
SbieSvc.exe
Start.exe
Templates.ini
License.exe (since 3.47)

This method has never let me down and I would like to continue using it.

Now, the files extracted from SandboxieInstall-349-01.exe show two dll files: sbiedll.dll and sbiedllX.dll (the latter presumably for x64) in addition to the above files.

So (my real questions) would I be right in assuming that:

(a) the above listed files (except dll) are identical in the 32-bit and 64-bit versions.
(b) I do not need to copy sbiedllX.dll for my XP install.

The "universal" setup SandboxieInstall-XXX.exe bundles complete copies of two files, SandboxieInstall32.exe and SandboxieInstall64.exe. They are bundled into simple Windows EXE resources. You need to find a way to extract the resource with id=3232 (or id=6464) into a standalone file, then unpack that file.

Thanks for that lead

Well for me, it's so that I can "boast" about the Sandboxie installation file being still under 1Mb haha.

Petal. Your post had little to do with version 3.49, so I had to delete it. As for your comment, detecting Sandboxie and aborting, that hardly qualifies as a bypass.

Is the automatic check for updates function working during beta testing?
Thanks

No, it´s not. Check for updates function only works with official releases and even then I think tzuk waits like 2 week before the new official release is noticed.

The check for updates is still not finding 3.48.

Tzuk, I'm really liking the new ClosedFilePath=InternetAccessDevices - it reduces the chance for error and succinctly replaces 11 lines in sandboxie.ini. I'd been wanting to request this as a feature, but thought you might consider it too trivial.

Also, it's nice to see the UI now handling per-sandbox program groups. Good work.

Are status indicators for Sandboxie Control under consideration, by any chance? The new ClosedFilePath=InternetAccessDevices is just begging for an easy way to toggle on/off directly from Sandboxie Control...