Minor issue with updating PM. Topic is solved

[BenFenner]

Which exact processor is in that machine? Are you running on bare metal?

I'm sure you've surmised by now, but for the record I am on bare metal and the processor is an Intel Core i7-3770 3rd Gen Ivy Bridge (Part number BX80637I73770)

Yeah, I just have to wrap it in only checking it on Win10 or later

EDIT: This version does that:
https://ftp.palemoon.org/publicbeta/palemoon-33.5.0a1-2.win64.installer.exe

Downside is that it won't give the error on Win 7 or 8, because it simply can't check on those OSes through the Windows Kernel call used.

That version does now begin the install process properly on the AVX-capable machine running Win7 that I tested with prior.

Let me go check on my non-AVX machine and edit this post in a moment with results.
Edit: Yep, as predicted I guess, the installer doesn't check on Win7 so I was able to begin the install process on this non-AVX machine. Sorry for the wild goose chase. Back to your regularly scheduled program.

[Moonchild]

Sorry for the wild goose chase. Back to your regularly scheduled program.

It wasn't! If it wasn't for you checking AVX, I wouldn't have realised the issue before the next update, most likely, and it would have caused headaches for people not being able to install on otherwise capable hardware.

[Enobarbous]

well.. that means I can't check for AVX in the installer unless people are on win 10 or later. Not sure how useful it even is then, considering old hardware where this is important is much more likely to run Win 7 or 8.

Because I don't see the point of creating an account in the repo for the sake of this:
In #1970 you write "I don't know how that can be done from NSIS which is restricted to using Windows API calls. I know how to do it in C(++) but not NSIS scripting."
Wouldn't Nsis CPUFeatures plug-in solve the problem?

[Moonchild]

Wouldn't Nsis CPUFeatures plug-in solve the problem?

If it was maintained and not dependent on an age-old CRT library (with probably considerable security issues), maybe. But I'm not really confident including arbitrary decade-old binary components to begin with. Then we might as well make a custom installer not using NSIS.

[Enobarbous]

I agree that it's not the best choice. It's a quick and dirty solution, but it will work here and now. And given that the "browser not working" questions still going on...

[Moonchild]

Sorry but I'm not going to cut corners here.