All Activity

Hi James, I made no further attempts on the Gigabyte boards; XP 32-bit runs really well on them, so that's where those have long stood. Likewise, I moved my MSI Z97 PC Mate on to other things way back. The driver I used was BWC’s 8.9d AHCI; I don't think driver version 11.2.0.1006 will work on W2K Pro, although it works fine with XP on my Gigabyte boards. I don't know why it does not work on your Gigabyte board. The trick with W2K Pro and AHCI is using an installation disc that has BWC's Extended Kernel integrated, thus the HFSLIP package tomasz86 made. Though layering BWC's kernel versions is not ideal, after installation you can update to a newer Extended Kernel version. The latest chipset I tried with Windows 2K Pro is the ASRock X99, where all is well. I have a couple of huge Lian Li PC-V1000L cases moving lots of air with different operating systems on individual NVMe and SSD drives. If I want to change operating systems I just power up, stop at the BIOS and make my selection. If I try the Z97 again it will probably be on a ASRock Z97 Anniversary board that is currently running XP Pro 64-bit. I very much like that platform and miss not having a Windows 2000 Professional operating system there. I would also like to attempt post-facto switch over from IDE to AHCI to avoid running one extended kernel version atop another.

When I started my test phase with the Thorium browser, the browser start was slow and the page loading behaviour was beyond good and evil. But for some time now, it has been running better and better on my old computer and one of the main reasons was the permanent improvement of the Chrome XP API Adapter. And on the other hand, all the time-consuming configuration work I did, of course. I think this is necessary on old, weak computers under Windows XP.

I'm using version 1.2.0.5035 on Thorium and Supermium. I will try updating it.

It's not just about looks, it is about stability and performance

I am still on 7 myself, although if I could I would main 2000

No problems here in Thorium. I have just logged into my Google account and Google Drive opens fine here. No crashes to observe. All seems to be normal. And it runs surprisingly quite fast on my old machine.

I guess technically I've never used either of them for more then four minutes at a time, lol. I do know that Thorium can last for four minutes. And Supermium only takes forty seconds or so to totally CRASH my single-core XP to the point of UNPLUGGING IT (it's an old laptop that doesn't even have a battery anymore). I've not seen any font issues in those four minutes, but that window wouldn't exactly be a good test case.

truce

What are you hardware specs? And which version of Thorium and the Chrome XP API Adapter do you use?

Which version of the Chrome XP API Adapter do you use for Thorium? The most recent one is 1.2.0.5057.

Here it freezes suddenly and does not react for several minutes. It also bothers me that I want to run it and just as it starts it shuts down 8 times out of 10.

My Thorium installation and configuration is very stable under Windows XP. I use the SSE2 edition which seems to be suitable to my Pentium 4 CPU with SSE2 instruction set at maximum. No browser or tab crashes, no problems with my USB hard disk which is currently connected. At the moment, I am writing this comment from Thorium on my XP machine.

Thorium (and Supermium) are very stable for me too. In fact, I don't think I've ever had a crash while using them unless they run out of memory, in which case only the current tab crashes, as designed. Occasionally I have had Thorium crash on start up. It appears for an instant in the taskbar, and then vanishes. Task Manager shows several thorium.exe processes still running. If I leave them alone, and just run the browser again, it then opens fine. That's on my main desktop. I've now put Thorium on the XP side of my very underpowered netbook, and that's very unstable. It opens fine, but trying to do anything often just produces a crashed tab with a 'status_access_violation' error. If I keep trying, however, the tab always eventually opens, and once the tab is open, it seems to be perfectly stable. Very odd!

Even though it's an older post, updating drivers and checking for Windows updates might still be worth a shot. Sometimes, those fixes can work wonders even with older issues.

Both Thorium and Supermium manage to destabilize my XP's USB stack to the point it's not detecting things being unplugged and plugged until the browser is closed. Thorium specifically is useless for Google Drive here as well, tab crashes as soon as I'm in. Both are buggy in fonts department (from disappearing fonts to incorrect rendering).

WTF now, M$? Github.com comes up fine in Edge or even 360EE. Edit: For information, the following pref is at its default value: network.http.accept-encoding;gzip, deflate, vary Edit 2: Hmm.... Works in St 52, not St 55. Could it be a profile issue? BRB.... Edit 3: Yep, it's a profile issue. Works in a clean profile, or even in my default profile with add-ons disabled. So, I just have to figure out which of my many add-ons is causing this Edit 4: Found it! It was Palefill 1.28, which, ironically, I don't think we even need any more! (I've instead been injecting polyfills with Violentmonkey as needed.)

Agreed! Same here.

What about a 24GB Quadro M6000?!

@chermany4ever You can't configure much in Thorium's Settings to improve its performance and running behaviour under Windows XP. What I actually meant was to change other things like updating the Chrome XP API Adapter, disabling animations and media autoplay, using a mobile user agent, setting suitable internal and external flags and so on. I did that, and now, this browser is running much better than before. PS: Also very important is a well-configured content blocker. Yesterday, I had to buy some articles on Amazon. Among other browsers, I also tested this website in Thorium. If uBlock Origin is not well-configured, the Amazon website does not load that fluently as it should. At the moment, I use uBlock Origin Lite as it consumes far fewer resources in Thorium and seems to be better suited to this browser.

The number of open issues probably has a lot to do with how long each browser has been available. R3dfox has only been around for about 2 months. (This thread is only 4 pages long so far.) So it hasn't had much time to accumulate issue reports. Also, I think it's harder to modify modern browsers to work on XP/Vista, at least without "help" from OCAPI or the Vista extended kernel, than it is to modify them to run on 7/8/8.1. Support for the latter was removed only recently, so there's not as much code to change - thus, not as much opportunity for Murphy....

My Thorium browser needs round about 260 MB for one opened tab and eleven enabled extensions. In my opinion, that's really low for a modern Chrome browser running under Windows XP. And don't forget my hardware is very old and weak, Pentium 4 single-core CPU and only 1.5 GB SD-RAM! Here is a screenshot: Personally, I can't confirm that this browser is unstable. Thorium never crashed here and is very stable. And the page loading behaviour is much better than at the beginning of my test phase.

I disagree. I myself would "ignore" these types of "reports" if I were win32. You see, in life, we all place our own "scale" on things like this. On a scale of 1 to 10, this "brightness difference" is a ZERO on my radar. A zero on a scale of 1 to 10. But the three people on this forum that love, love, love to talk "brightness", this issue is clearly a 12 to them. A twelve on a scale of 1 to 10.

In all honesty, I don't know if I have the knowledge to configure Thorium exactly for my machine but tried in Settings all the friendlier options and didn't get it to work much better, was still pretty unstable. Another thing that didn't convince me is that I got used to the fact that with Serpent the cache is stored in memory -not on disk- but between Thorium folder and the cache it ate more than 1gb! Too much for me for a program that works quite unstable. I'll pass for now, although of course I recognise the effort.

ENCRYPTED. The "padlock" display will not always display correctly in XP. Period. End of story.

<delete>