All Activity

Pale Moon only has layers.acceleration.enabled AFAIK, which is a master switch for webpage compositing to use GPU and is also exposed as a checkbox in browser's settings. I assumed roytam1's version could be different, so I didn't say anything as his releases tend to deviate from upstream in random ways. Mozilla still uses layers.acceleration.disabled, so works the other way around, though newer versions have a bunch of related or not so related (depends on how you look at it) WebRender prefs, the traditional layers acceleration in considered legacy. The *prefer* prefs, these always made automatic selection of D3D9 on XP in UXP browsers in my experience, although I remember when I was messing with Mypal68 last time, you had to explicitly enable the D3D9 one. layers.acceleration.force can be used in addition to layers.acceleration.enabled to try force-enable it for unsupported configurations.

I don't keep a running log, per se. I run each and every new release for about FOUR MINUTES and fully delete after those FOUR MINUTES. For me, it's because I compare directly to OFFICIAL UNGOOGLED and Thorium still makes some GOOGLE connections. Supermium CRASHES my system within NINETY SECONDS so from a stability standpoint alone, Thorium kicks Supermium's "arse". And from what I am seeing in the last 24hrs, BOTH are being flagged for "suspicious security vulnerabilities". I suppose it is the stability standpoint that has the Thorium thread so active here at MSFN but "nothing" on the Supermium thread - because it's too UNSTABLE for ANYBODY to actually USE.

Tells me everything I need to know. People keep giving Supermium a "free pass" but flog Thorium every chance they get. Despite Supermium clearly being reported as having a trojan!

Does anyone maintain a systematically logged, screencapped observation of Thorium connections?

@NotHereToPlayGames, found this for you. "Windows Defender is acting like every other Anti-Virus ... I get the same thing with BitDefender. Saying "trust me it's fine" is not a way to reassure people. Please determine what in your code is flagging and get it whitelisted." https://github.com/Alex313031/Thorium-Win/issues/75#issuecomment-2062321661

"Thorium detected as threat by Norton 360 aswell..." "Suspicious process attempted to modify attributes of a file protected by Data Protector" "Target file was a system..." https://github.com/Alex313031/Thorium-Win/issues/75#issuecomment-1768473145

Well, there's such possibility, of course! But then why doesn't the author of Thorium clear this whole situation? He simply ignores. Just read yourself. When Supermium had false positives, they cleared it up pretty quickly.

That would be a good idea. I also kept a few addons/installers on an old external HDD that I could contibute.

AstroSkipper said: "These are the preferences layers.acceleration.disabled, which I now set from true to false," Hello AstroSkipper, I use PM28: (https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20240525-d849524bd-uxp-f8f3b3ee43-xpmod-sse.7z) My PM28 default setting is: layers.acceleration.enabled; true Is the name of your PM28 preference correct ? layers.acceleration.disabled or is the name layers.acceleration.enabled

haven't check, just imported it to a local repo with official 38.8.0esr as base to see how many differences there. may try to work on it(either try to build it and fix errors that encountered, or even put some NM27 bits on top of it to produce a pseudo-NM27) later.

Since I cannot guarantee the source code compiles properly, I should ask, does it work for you?

https://codeberg.org/Nicholas_McAnespy/FxVC10Mods/releases

https://www.virustotal.com/gui/file/96585bab134e3011bb25b7310243e5d384575e76408fb8adfd036f045b1013a0/detection BTW, this is with latest Supermium 122-R6 32-bit release ...

I no longer have Supermium on my computer. Everything removed. Unfortunately, Supermium ran poorly on my hardware, at least in the previous versions.

since VC5 and VC6 uses same runtime (MSVCRT.DLL) so it won't crash. 1.5 or later since they have real tabs, not layers. BTW I wonder if you can upload the sources of your 38ESR-VC2010?

Do you mind also scanning the notification_helper contained in Supermium? I know this is not the Supermium thread, but a comparison still seems to be in order.

That thread also mentions "Floorp". I think it has been mentioned here at MSFN also. I have not tried it yet.

This is the scan result of the notification_helper.exe file uploaded to VirusTotal from my Thorium SSE2 122.0.6261.168 WINXP x32 installation: At least, the version 122.0.6261.169 of the file notification_helper.exe seems to be inconspicuous, but it is not version 123.0.6312.133 either.

As far as that goes, Supermium also has this "notification_helper.exe". These projects seem to me at least to be very closely related. If one has a trojan (which I cannot verify), then I would suspect the other to have the same trojan.

I have to call "BS". I installed latest Thorium then installed last Malwarebytes for/on XP! NO SUCH TROJAN:WIN32/ZNYONM DETECTED! NONE! From my perspective, most of these "reports" come from Supermium fans that wants to see Thorium die. I'm down to only two XP laptops. But I use them regularly and even promoted one of them to the master bedroom (meaning it runs email programs for XP 24/7/365). For my XP laptops, SUPERMIUM is the one "not for me". So far, I've had great success with Thorium. Though NO, it has not become my default XP browser (Serpent 2023-07-31 is). That said, I am NOT a fan of Malwarebytes! I do not keep it on my system and I nuke every remnant after these types of "verification checks". I do have to assume that a BRAND NEW DOWNLOAD includes the most up to date definitions - because the LAST XP VERSION did not seem to want to check for updates. I WOULD LOVE TO SEE SCREENCAPS OF ANYBODY THAT DID SCAN VIA MALWAREBYTES AND DID FIND A TROJAN. Otherwise, "hype and propaganda" shall be my mantra.

There were reports of the same (or similar) malware before, in this topic. So, looks like it's not only in Win 10 versions. I remember, I suggested to simply delete that file. So, apparently, they read my advice and moved that malware into another *.exe file.

Does any MSFNer even use Win10+ version? xD

Good for you! For me ... well, it kinda sucks, almost all extensions I used were free, but now are paid with the Manifest V3.

The warning is there for ages. If you go to "manage extensions", click any extension and under "errors" you will see.

The same Windows 7 Fix works for KARM: Headbang Edition v1.0.1 How to play on Windows 7: Install KexSetup_x64Rel.exe. Open “KARM\Binaries\Win64\KARM-Win64-Shipping.exe” file properties in Explorer, then “VxKex” tab. Check “Enable VxKex for this program” and “Report a different version of Windows, Windows 10” checkboxes, Apply.