Run Blue Iris as a Win32 service ?

[Homer]

Hi, since I normally run BI as a 64 bit program, would there be any reduced functionality if I used it as a service ? Does "Win32 service" mean 32 bit ?

I tried it for a day, but had issues with UI3 on client pc's not being able to get the clips list. Not sure if that was as a result of using BI as a service. Changed it back and results were unclear for a few days, but it seems OK now

 

[Zanthexter]

TLDR: Stick with 64 bit, there's no practical benefit to 32 bit on a modern system.

Details: The main practical difference between 32 bit and 64 bit programs is how much memory they can make use of. 32 bit programs get capped around two or three gigs. 64 bit don't.

An additional benefit on particularly old or under powered systems is that 32bit programs are smaller. They take up less of the 3-3.5 maximum GB an old system can access. Or the 1-2GB a cheap tablet comes with.

Some software has to work with other software that was written to the old 32 bit code and running 64 bit breaks compatibility with some 3rd party stuff. Microsoft Office for example. If you need that old 3rd party thing, you might need to run 32 bit for compatibility.

Oh, and a 32 bit virtual machine takes up fewer resources. So there's that for the advanced tech hobbyist.

Anyway, a normal run of the mill BI system won't benefit from 32 bit. Just stick with 64.

 

[Homer]

Hi Zanthexter, to be clear, I am not talking about running the 32 bit or 64 bit versions of BI. I am meaning the BI built in selector to run it as a service, which is on my 64 bit version of BI. I have seen it called "Win 32 Service" in some posts, and so yes, I was concerned if that is the case, that memory limitation would result. Is the BI built in "Service" a "Win32 Service" in all cases, or is it a 64 bit service with the 64 bit version of BI ? I guess this is really a question for the BI author !

 

[Tinman]

I tried running BI as a service a long time ago and while it works it just didn't fit my particular needs. If you run a headless BI system I can see where it might be better to use it, but I really can't tell you pros and cons of running ether. This would make a great POLL survey as to what users here run though

 

[Zanthexter]

Hi Zanthexter, to be clear, I am not talking about running the 32 bit or 64 bit versions of BI. I am meaning the BI built in selector to run it as a service, which is on my 64 bit version of BI. I have seen it called "Win 32 Service" in some posts, and so yes, I was concerned if that is the case, that memory limitation would result. Is the BI built in "Service" a "Win32 Service" in all cases, or is it a 64 bit service with the 64 bit version of BI ? I guess this is really a question for the BI author !

Unless you download and install the 32bit version it is running as 64 bit.

When they're referring to "Win32 service" it's programming terminology that hasn't changed over the years even though the capabilities have.

Microsoft doesn't like to force big corporations to chose between spending millions to upgrade 3rd party software or millions to upgrade Windows. Sometimes that means keeping names unchanged so that the old software will continue to work.

 

[Zanthexter]

I tried running BI as a service a long time ago and while it works it just didn't fit my particular needs. If you run a headless BI system I can see where it might be better to use it, but I really can't tell you pros and cons of running ether. This would make a great POLL survey as to what users here run though

The main goal of running it as a service is reliability. Running as a service is more reliable than auto-run after auto log on. I prefer to change the BI service to "delayed start" to bump that reliability up a bit more.

Running headless and doing most things via the new web interface remotely also requires less resources as best I can tell.

Just wondering, how did it not fit your needs? For most folks it's the preferred way to run it, but there are always exceptions.

 

[Tinman]

The main goal of running it as a service is reliability. Running as a service is more reliable than auto-run after auto log on. I prefer to change the BI service to "delayed start" to bump that reliability up a bit more.

Running headless and doing most things via the new web interface remotely also requires less resources as best I can tell.

Just wondering, how did it not fit your needs? For most folks it's the preferred way to run it, but there are always exceptions.

I have never had any reliability issues with my dedicated BI system. I simply allow BI Tools to start BI when windows boots. Of course I don't use any UAC to interfere as well. My system also has a dedicated monitor that resides on my desk and is always displaying the feeds, so I can monitor my shop and when a customer shows up. The last time I tried w32 service mode I also had issues with a 3rd party app that links my cams and alarm system that would not work correctly when BI was running as a service. I may try to running it at a service someday....but as long as mine is stable I probably won't mess with it.