Thorium

[AstroSkipper]

57 minutes ago, NotHereToPlayGames said:

I really REALLY don't think it's that "easy" to deduce/conclude.

Have you ever MANUALLY edited the registry in your POSReady?

Have you ever ran Malwarebytes in your POSReady and it removed registry entries that a "default XP install" places there that Malwarebytes sees as "malware"?

Did you REPEAT those registry tweaks/fixes/cleans/optimizations in your non-POSReady?

Didn't you say your XP partition was first installed DECADES ago and that you do not reinstall often, that you can keep your XP running smooth by fixing registry entries?

Don't you really have to perform "all of that" in the non-POSReady before claiming that POSReady is the "only changed variable in this multi-variable equation"?

Both partitions were created by me in 2004. Since then, there has been no reinstallation due to a perfectly functioning imaging system. I correct all errors myself. The registry of both have been modified, cleaned and fixed by myself. The main difference between them is that I had to stop the updating of Windows XP with the last update in 2014 in one of them, and in the other, I applied the POSReady hack and performed updating until 2019.

PS: I never had an infection, which had to be removed by an antimalware programme, in both Windows XP installations. And don't forget there is an undetermined probability of type II error for accepting the null hypothesis H0. 

Edited August 13, 2024 by AstroSkipper
Update of content

[NotHereToPlayGames]

Nobody else has the same issue.  We have multiple users citing no issues with Thorium on non-POSReady.  You are the ONLY one.

By all means, track down WHY and keep us posted.  It seems to me that perhaps a BIAS is creeping in towards POSReady being your "saviour" yet it has saved no one else.

[AstroSkipper]

6 minutes ago, NotHereToPlayGames said:

You are the ONLY one.

Thorium is Chrome based. Search for the string " Chrome immediately closes when starting" or similar search strings, and you will see I am not the only one. My issue is a common error in Chrome. You should actually know that as a Chrome/Chromium fan.

[NotHereToPlayGames]

I am HIGHLY interested in the "root cause".

I am hereby on record claiming that your Thorium issus is NOT RELATED TO POSREADY.  *DATA* is inconclusive, but even you as a mathematician must admit that the *DATA* is steering in that direction.

Has the developer of Thorium been asked if s/he runs POSReady?

Has the developer of Thorium even TESTED on SSE2?

 

[NotHereToPlayGames]

My only suggestion, if you really REALLY want to PROVE that POSReady is the REASON for Thorium WORKING on your POSReady partition, then despite the time that this will entail, you must install those POSReady updates ONE AT A TIME and test Thorium before and after each and every one of them.

Scientific Method

[AstroSkipper]

1 hour ago, NotHereToPlayGames said:

Scientific Method

But too much time-consuming, considering that we are talking about 365 updates, as I mentioned earlier, although I am also interested in the cause of these sudden closes. After a deep research in the internet, I found out that many users suffer from this Chrome issue and have switched to Firefox as there seems to be no real solution. If this error also occurs on my Windows XP Pro SP3 + POSReady partition, I will immediately give up Thorium.

Edited August 13, 2024 by AstroSkipper
Update of content

[NotHereToPlayGames]

While I have no doubts of that (I myself used to be a DIE-HARD "Firefox Only") type of computer guy, for every "2.7" of those people that you claim have switched to Firefox, I can show you 65.4 that tried Firefox, hated it, and opt for Chrome.

Go to the computer store and look at the desktop icons.  Especially ACER computers - for the past eight years, those ACER computers come with FIREFOX PREINSTALLED!  Hasn't budged the needle one "millibtye" in Firefox's Doomsday Marketshare.

Again, I myself used to be a DIE-HARD "Firefox Only" type of computer guy.  Dating back to when it was called PHOENIX.

[AstroSkipper]

8 hours ago, NotHereToPlayGames said:

While I have no doubts of that (I myself used to be a DIE-HARD "Firefox Only") type of computer guy, for every "2.7" of those people that you claim have switched to Firefox, I can show you 65.4 that tried Firefox, hated it, and opt for Chrome.

Go to the computer store and look at the desktop icons.  Especially ACER computers - for the past eight years, those ACER computers come with FIREFOX PREINSTALLED!  Hasn't budged the needle one "millibtye" in Firefox's Doomsday Marketshare.

Again, I myself used to be a DIE-HARD "Firefox Only" type of computer guy.  Dating back to when it was called PHOENIX.

The main reason for the values in that stats is the fact that Windows computers have been extremely displaced by smartphones and tablets in the last 20 years. And if a normal consumer uses a notebook and, now rather rarely, a desktop computer, it will probably be a Windows 10 or 11 computer. And there, the normal user is more likely to install what they know from their mobile devices. Chrome or Chromium. The younger generation now only seems to know Windows computers from the stories of their elders.  But all that doesn't make Chrome and Chromium browsers any better. 

[NotHereToPlayGames]

Listen, BOTH you and I are no "dummines" when it comes to computers.

We BOTH know our way around computers!

Firefox is a telemetry nightmare.  Firefox forces the user to go through extreme firewall rules due to its "loopback" quote-unquote "feature".

MOST users are CLUELESS when it comes to FIREWALL RULES SETUP (I do NOT include you in this subset of "users").

MOST users when faced with a "firewall poppup" upon launch of Firefox just click the STUPID dialog where the firewall asks "is this a WEB BROWSER" or the firewall just ASSUMES "yes, this is FIREFOX, so I'll just use default "web browser" rules.

No offense to these "users", but this really is the STUPIDEST thing I have ever witnessed over the years - "just let Firefox make ANY connection it wants to, I'll accept the default firewall rules, I trust Firefox".

THIS TRUST IS MISPLACED!  Firefox really is the biggest telemetry nightmare I have ever come across!  AND THAT INCLUDES A CHINESE/RUSSIAN REPACK OF 360CHROME !!!

This "loopback" (1 byte several times each and every second) was referred to as a *BUG* in the days of Windows 2000, it's just "accepted" as 'normal behavior' by Firefox users today that DO NOT CARE (nor KNOW HOW to monitor these "loopback connections").

A CPU cycle is a CPU cycle.  Make it perform a task and that means other tasks are delayed.

I am NOT a Chrome/Chromium "fanboy".  This world is full of "lesser of two EVILS".

All OT regarding Thorium, of course.

But let's be perfectly honest, if THORIUM (or 360Chrome!) made the HUNDREDS (literally!) of telemetry connections that FIREFOX does (esp FIRST LAUNCH), none of us would turn a blind eye !!!

YET ALL FIREFOX USERS TURN A BLIND EYE REGARDING FIREFOX TELEMETRY CONNECTIONS !!!

Firefox users "today" really are VERY different from those that used it in the 90s.  Tout privacy and security but clueless that they have "sold their soul".  "Do as I say, don't do as I do."

 

But I digress...

Edited August 14, 2024 by NotHereToPlayGames

[Dixel]

On 8/13/2024 at 10:42 AM, NotHereToPlayGames said:

Regarding --enable-low-end-device-mode   ---  I have officially ABANDONED its usage. 

Just as soon as you were notified Dixel suggested that flag. 

I wonder how many others will be thrown out, if you knew I too suggested them, anyways, upvote for previous Firefox post, I like when you post factual information without bias. 

I like when everyone posts factual information without bias. 

[Klemper]

On 8/13/2024 at 12:03 PM, Dixel said:

Replace with empty stabs, see what it gives you. 

Thank you! Worked like a charm! I've always wondered what were those for.

[NotHereToPlayGames]

7 minutes ago, Dixel said:

Just as soon as you were notified Dixel suggested that flag.

No, sorry, you are reading too much into it.

It was only after running it for SEVERAL hours that I was able to WITNESS the NEGATIVE side effects (YouTube would pause all audio/video for half a second or so once per hour or so).

This is a great flag for sessions of one-hour or LESS.  But I cannot advocate "for" it for users that keep something like YouTube open for HOURS upon HOURS.

Edited August 14, 2024 by NotHereToPlayGames

[NotHereToPlayGames]

1 minute ago, Klemper said:

Worked like a charm!

What OS are you running?

[Klemper]

10 hours ago, NotHereToPlayGames said:

What OS are you running?

8.1

[NotHereToPlayGames]

2 minutes ago, Klemper said:

8.1

That's why!  These "vulkan" files (as far as I have WITNESSED) are only needed for XP x64.  They're not needed for XP x86.  They're not needed in Vista.  They're not needed in Win7.  They're not needed in Win10.

I do not have any 8.1 machines to test whether they are needed or not.  But it is a VERY SAFE assumption that they are NOT needed based on Vista/7/10.