Planned System Requirements

[LAR Grizzly]

Operating system: Windows 7 Pro SP1
Browser version: Pale Moon 33.0.1
32-bit or 64-bit browser?: 64-bit
Problem: Future Updates
Browser theme (if not default): Default
Processor: AMD FX-8320 3.5GHz Eight-Core AM3+ Processor
Installed plugins: (about:plugins): Adobe Flash 32.0.0.371 (ask to activate)

I have an older machine, built in 2013. When the planned newer version of PM is released, what can I expect to see when updating? If my processor is incompatible, will I still be offered the update? Will PM detect my processor incompatibility and suggest the 32 bit version? Will the new version install and maybe I can expect some problems?

I like to be ready in advance. Please supply some guidelines. Thank you.

[therube]

(Assuming I pulled the correct one), this mentions AVX, https://www.techpowerup.com/cpu-specs/fx-8320.c1215.

In any case, download CPU-Z (Classic ZIP is fine), & confirm for us that your CPU supports AVX instruction set.


If not supported, hmm. Kind of a good question.
I'd imagine, PM would automatically update, though on doing so, it would fail to run (period).


(And of course, always have backups of your Profile folder.)

[Moonchild]

AMD FX = piledriver (post-bulldozer) so you'd be fine.

[LAR Grizzly]

In any case, download CPU-Z (Classic ZIP is fine), & confirm for us that your CPU supports AVX instruction set.

I found my CPU here. It says that my processor supports AVX.

Your link also says that my processor supports AVX. Also CPU-Z confirms AVX. So, I assume that I will be OK.

cpu.jpg

I have two spare machines and a laptop that are of unknown specs (until I delve into them). It would still be nice to know what to expect (if someone can enlighten us).

[LAR Grizzly]

AMD FX = piledriver (post-bulldozer) so you'd be fine.

Thank you, Moonchild. Would you elaborate on what can be the expected results on a machine that doesn't have the AVX compatibility?

[Moonchild]

It would still be nice to know what to expect (if someone can enlighten us).

If you get updated to a version that your CPU doesn't support, it will simply refuse to start with an error message.
I'll look into passing a CPU flag with update requests but I can't promise that will make it in or be 100% accurate if it does make it in. If you get updated to a CPU-incompatible version then, as therube said, it will just fail to start with an error message.

[LAR Grizzly]

If you get updated to a CPU-incompatible version then, as therube said, it will just fail to start with an error message.

I have two older machines and a laptop (that have the exact operating system copy of my current main Win7 machine) and may not be compatible. So, I now know what to expect. If I get the flag or the update won't start, I'll just switch those machines over to the 32 bit version. Would the 64 bit profile be compatible with the 32 bit version of PM? I share my current profile with the other three machines.

[therube]

Should be compatible.
But then you did make those backups, no .

[LAR Grizzly]

Should be compatible. But then you did make those backups, no .

Even my backups, have backups!

[Moonchild]

Profiles don't care about the bitness of Pale Moon.

[LAR Grizzly]

Profiles don't care about the bitness of Pale Moon.

Thanks, good to know. I should be good-to-go when you send us the new version! Kudos!

[athenian200]

I'm definitely considering creating a new automatic update channel for the AVX builds and discontinuing the old one for my application, because I am leery of auto-updating people to an incompatible build. Or actually, I could probably just withhold the update.xml file for the last SSE2 version, and require a manual update to the first AVX release, which will then be updated as normal, I may not need a new channel at all...

I'm sure some people will find it a little inconvenient to stop receiving automatic updates and have to manually download either an AVX version or a 32-bit version to keep getting them, but for me personally, I'd rather deal with people complaining they didn't get an automatic update and had to manually download a release one time, than people screaming at me that I busted their system and left them with no way to keep using Epyrus while they figure something out.

I think it's less of an issue for Pale Moon because MC does actually provide older builds people can roll back to if they get hit by something like this, whereas I don't like to keep a large back catalogue and just rely on my sources being tagged properly so people can reproduce the builds if needed.

But yeah, in general most systems should work with this because AVX is something that should be supported by every machine made in the last 14 years or so. Actually kinda surprised at how many systems older than 10 years are still kicking around, you didn't see that back in the day at all... people used to think I was nuts for running a 5-year old system in the early 2000s.

[Moonchild]

Or actually, I could probably just withhold the update.xml file for the last SSE2 version, and require a manual update to the first AVX release, which will then be updated as normal, I may not need a new channel at all...

It's a bit of a rock and a hard place. Either you break it for a small percentage of people who do not pay attention to any communication, or you have people not get important updates until they notice they are on an old version. For Epyrus that might not be too much of an issue, but for Pale Moon it would be.

[LAR Grizzly]

Actually kinda surprised at how many systems older than 10 years are still kicking around, you didn't see that back in the day at all... people used to think I was nuts for running a 5-year old system in the early 2000s.

For me, it's age and money. I'm 68. I don't have the financial resources to purchase a new machine, let alone, buy all new software. On the age end of it, I really don't feel like learning a new operating system along with learning all the new software I would have to purchase. It's not that I'm lazy, I just don't relish spending all of my time relearning things that my present system provides. My next big leap will be to obtain a smartphone. I'm dreading the experience.

[suzyne]

Off-topic:

My next big leap will be to obtain a smartphone. I'm dreading the experience.

I would say do it as soon as you can and don't delay.

My grandmother avoided getting a smartphone when she was fully capable of learning something new. But now, when it would be most useful for safety, health and other practical reasons, sadly her mental decline is making it much harder for her to use one. I really wish she had learnt the skills when there was still plenty of time for it to become habitual and automatic.

[LAR Grizzly]

Off-topic:
I would say do it as soon as you can and don't delay.

Off-topic:
I'm planning on getting one this fall. Trying to decide on which platform, iPhone or Android.