sbieSvc process and Sandboxie service

[Unknown_User_549]

I bet this has been asked and answered: i couldn't find it though:

Why does the sbieSvc process need to be running all the time if I only invoke the sandbox on certain occassions?

And:

Again; why does the Sandboxie service need to be 'started' if I am using only on demand?

Can the service/process be stopped until manual start from either shortcut or shell extension ?

I'm a bit out of my depth here: be patient

It's not a biggie: just wondering.

I see that nearly every installed tool in Vista is needing a service running. (I am on XP home sp2)

[SnDPhoenix]

The answers pretty simple, its always running so that when you execute a sandboxie command, it can carry out the command immediately because the service is already there and running, for example, heres a (dumb) real-life example, its sorta like the way you keep food in your house so that when you want something to eat or drink, its there for you to eat/drink, (yes its a stupid example, but it gets the point across), same applies to software.

[Unknown_User_549]

OK yes got that

Just wondering whether the service can be set to manual and how that would affect process and function.

Just wanting to have 'services' at minimum.

( Its looks like Vista will/may have ~80 processes and more services running, depending on your extra tools, due to the 'new' security restrictions and UAC hence 2G ram?)

No plans to heh downgrade to Vista yet, just feeling my way forward.. slowly

[SnDPhoenix]

Well you could try starting the service manually, dont know how good it will work or not, but you could try it anyways, to do this, just goto start > run and type in "services.msc" (without the quotes) then go down the list til you find "Sandboxie Service", right click it and select properties, then in the window that popups look for "Startup type" and in the dropdown menu (which should be set to automatic) click it and change it to manual, then hit ok and restart your pc. from now on youll have to start the service manually. Now about your question about how it would affect process and function, the only thing itll affect is the fact that when you try to do a sandbox related function, youll need to make sure that the service is started first, other than that it wont really affect anything.

[laszlo]

You can set the Sandboxie service to "manual", if you want. When a sandboxed program is started, the Sandboxie service (and driver) should be loaded automatically. More here.

Alternatively, you could create two shortcuts pointing to "net start SbieSvc" and "net stop SbieSvc" (without the quotes) to comfortably and quickly start and stop the service (assuming you're logged in as an administrator).

[Guest]

Would a .bat file like this work to start the Sandboxie service and then stop it for you after you close Sandboxie?

net start "SbieSvc"
wait sandboxie.exe
net stop "SbieSvc"

If it would then you could just place the .bat file in the folder where the Sandboxie executable is at and then make a shortcut to the .bat file on your desktop and set the shortcut to open the .bat file "minimized". Whenever you clicked on the shortcut I think it would start the service, wait until you open sandboxie, and then stop the service after Sandboxie is closed. I am new to .bat files so I am unsure I am just throwing this idea out there for comment. I have seen similar used on another program.

[Unknown_User_549]

Thanks guys
.bat files are a bit beyond me
but I could prolly learn if I needed to

I am betting you know this already

Turning the service to manual has the service in 'stop' mode at boot, once Sandboxie is started the service stays started.

It really is no big thing the service uses only a tiny bit of memory.

I am just going through a phase of trying to get, LOL, "control" over my box

You are probably seeing what I am seeing: that every app now Blista compatible is starting some new service to comply with Blista UAC issues.
OK fine for Blista victims, but I have Xpee and dont really want any extra bits running if I can avoid it and can avoid multiple clicks just to get things started and stopped.

This has/seems to have implications for every "on demand" tool.
I really want my "on demand" apps to actually stop when I tell them too. heh.

Sorry tzuk for 'complaining'

Thanks for input.
Regards.

[SnDPhoenix]

Damn, seriously, theres nothing wrong with "Blista" (as you put it), it really kicks ass, i did beta testing for Vista all the was from the first Alpha release (which is before beta) all the way to the last RC release (which is before final build) and it is awesome, i have the Vista Ultimate OEM disc, and ill be installing Vista the next time i have to reformat my pc (due to installing so much stuff that junk accumulates and cause xp to go slow), its that good, my only gripe is that Vista has too many features, lol, it'll take while to fully get used to all the features, so next time someone wants to rip on Vista just remember the XP beta testing stage (*shudders* )