MBAE production version 1.09.1.1261 will not run on pre-SSE2 processor but MBAE beta(?) 1.09.1.1254 can

[hake]

Oh dear! MBAE production version 1.09.1.1261 will not run on pre-SSE2 processors but MBAE beta(?) 1.09.1.1254 can.

The version numbers for 1.09 are confusing. I will hang onto the 1.08.1.2572 installer for the time being.

Edited November 15, 2016 by hake

[Arthi]

Hi hake,

Pre-sse2 processors compatibility is still not part of our automated build process. We will manually create a build for users requiring pre-sse2 support with all the latest fixes in a day or two and provide an update on the forum. Hang in there. We apologize for the inconvenience caused.

 

[hake]

Thank you Arthi. I inferred that the version numbering indicated that 1.09.1.1261 was the successor version to 1.09.1.1254 which I am presently using.

[hake]

Thank you in advance, Arthi, for creating a solution for pre-SSE2 processor users. That will be much appreciated. I guess that you will eventually have to cease support of our old hardware so might you be considering that the final version which does support pre-SSE2 processors will be equipped to recognise the presence of pre-SSE2 processors and so selectively disable automatic updates to future versions of MBAE?

Edited November 16, 2016 by hake

[Rsullinger]

Hello Hake,

Just as a test, can you try to do a clean re-install to that 1261 (not an upgrade) and see if it fixes it? I just want to test something that was reported to me. If that does not fix it still, try this new build 1264 and see if it fixes it:

https://malwarebytes.box.com/s/83akrg3qny018gnjs20txz242148hy67

[hake]

Message received. I will do this in about 12 hours time (it's 10pm here) and will then let you know what the outcome is.

[hake]

I have attempted to do as requested and my following comments are about what happened.

The installer/uninstaller mbae-uninstaller.exe for both MBAE 1.09.1.1261 and 1264 seems to require a SSE2 compatible processor. On my pre-SSE2 processor equipped PC it fails twice with illegal instructions and so is unable to create MbaeSvc among other failings.  However, the MBAE beta 1.09.1.1254 mbae-uninstaller.exe does work (almost). It also fails with an illegal instruction BUT it is able to create MbaeSvc although it cannot start it. I do not know the options required to manually create MbaeSvc but at least I can manually start that service.

If I edit my hOSTS file to prevent mbae-svc.exe from accessing the Internet to update to the latest production version, MBAE beta 1.09.1.1254 is usable but I guess that being a beta it will only work for 6 months.

If the installer executable for MBAE 1.09.1.1261/1264 were to be modified to be capable of running without 'illegal instruction' errors, I could then attempt to check if the actual MBAE software comprising versions 1.09.1.1261 or 1264 is capable of running on pre-SSE2 processors.

[hake]

I have to correct myself.  The installer/uninstaller mbae-uninstaller.exe for MBAE beta 1.09.1.1254 works properly. I must have got my versions mixed up.

[CeeBee]

On 11/16/2016 at 0:04 AM, Arthi said:

Pre-sse2 processors compatibility is still not part of our automated build process. We will manually create a build for users requiring pre-sse2 support with all the latest fixes in a day or two and provide an update on the forum...

Any chance pre-SSE2 compatibility will be made part of your automated build process?  Sooner rather than later, as, as it stands now, I'll keep my 2 legacy (SSE) computers on v.1.08.1.2572 with automatic updating unchecked and my Hosts file modified!  I can't see a manually created pre-SSE2 build as something of lasting value...

[hake]

Will MBAE 1.09.1.1254 time-out after 6 months? Hope it doesn't. I guess that it is reliable. It behaves that way.

[CeeBee]

On 11/18/2016 at 0:34 PM, hake said:

Will MBAE 1.09.1.1254 time-out after 6 months? Hope it doesn't. I guess that it is reliable. It behaves that way.

As mentioned in another beta-thread, MBAE 1.09.1.1294 works on my legacy PC with SSE only CPU.  Just installed it and .. so far .. it's all good. Hope it stays that way, as I have dropped 1.08 in favor of this 1.09 version .. fwiw.