AstroSkipper

Hope I've done what you ask correctly. By doing so a folder was created called %~dp0% which has more folders and files inside. Actually, a user data folder should be created with the name USER_DATA and not %~dp0%. The whole command starts the browser with some flags which were originally part of the batch file and creates the user data folder USER_DATA if not already existent.

Ok. What did you see when you applied the starter batch file? Open a command line window in the main folder of Thorium and execute the following command: thorium.exe --user-data-dir="%~dp0%\USER_DATA" --allow-outdated-plugins --disable-breakpad --disable-encryption --disable-machine-id What do you see now?

I use the THORIUM_PORTABLE.bat, too. I try to avoid installing those ported browsers. When you copied these three files of the Chrome XP API Adapter into your Thorium main folder, did you also rename the chrome-win7-xp-api-router.dll file to progwrp.dll?

My NVIDIA driver version is 307.83, the last official version I got via the updater from NVIDIA. This version is also the last officially offered one when performing a driver search on their homepage. However, I could update to the more unofficial 307.90 version which was offered by Microsoft but there was never any need to do that. And I don't think such a minor update could change anything. My DirectX version is indeed 9.0c.

If I understand you correctly, the NVIDIA 6200 graphics card is not supported. Am I right? BTW, I didn't see any notes about supported graphics cards or chips. Where are them?

Although my Thorium browser starts as usual, the new Chrome XP API Adapter 1.2.0.5058 in combination with the --use-angle=d3d9 and --ignore-gpu-blocklist flags causes black frames, wherever pop-ups, menus or preview windows are opened, and the disappearance of tool bar icons. Round about six extensions are affected. Unfortunately, this type of hardware acceleration doesn't help me at all. Thus, I will remove both flags.

I think I have already written enough helpful comments and articles. And I replied to a rather disrespectful statement. Thorium is also made for Windows XP. And there are members and readers here who are using this OS on old or very old hardware. You understand what I want to say? Anyway! I don't like such comments "Such old computer ..." which are therefore absolutely superfluous. Such as yours. Sorry to say that!

Not really. My computer is much older, my dear. It is from 2000. And TBH, such comments are not really helpful.

Especially the --ignore-gpu-blocklist flag leads to a disappearance of tool bar icons which belong to the extensions "User Agent Switcher and Manager 0.5.0" and "Window Resizer 2.6.4". I should mention that my my old computer is equipped with a NVIDIA GeForce 6200 graphic card with 256 MB. A very, very old graphic card, of course. Thus, I removed both flags from my installation. In any case, I will have to test this more deeply. Perhaps, other things are also negatively affected.

Thanks for providing your hardware specs! My on-board connectors are still USB 1.1 ports due to the age of the motherboard which was manufactured in 2000. Therefore, I had to retrofit USB 2.0. Since I have installed the expansion card from Exsys with the NEC chip, everything that has to do with USB runs like clockwork. And Thorium doesn't seem to have a problem with this chip, either. PS: By the way, it was rather a stroke of luck that I was still able to purchase this card via eBay classifieds. The Exsys USB 2.0 PCI card is more of a Mercedes among USB expansion cards and can no longer be purchased officially.

Thanks, I tried with an old Kingston USB flash 32GB (2013 year or so). I attached a Medion USB 32 GB stick to my machine while Thorium was running. No problems here. Attaching and removing the stick works as it should. Thus, I can't see any issues in my system. Maybe, it depends on the USB chip that is used. I had a lot of problems with the VIA chip in the past. I replaced my USB card one or two years ago by one with a NEC chip. No connection errors anymore. The NEC chip is very stable and simply great.

Ok. So far, I didn't attach a USB device while Thorium is running but I will do so the next time.

The last weeks, I have permanently attached an USB 2.0 hard disk to my Windows XP computer while using Thorium. It is shown correctly connected and functional. I will test connecting USB sticks the next time when I am back at my desktop machine.

For security reasons, I do not use the --no-sandbox flag, either.

Ok. Your hardware is much more powerful than mine. You are using the same Thorium release as I do. The first measure you can do is updating the Chrome XP API Adapter which you can get here: https://github.com/IDA-RE-things/Chrome-xp-api-adapter/releases

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.

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.

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.

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.

@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.

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.

Your comment is again offtopic. Read carefully what I have written here: No further discussions about 360Chrome issues in this thread. Post your 360Chrome issues in one of the corresponding Arctifoxie threads! A solution has been provided for you here in detail. And that means use ProxHTTPSProxy! And thus, we are finally on-topic again!

Regarding running Supermium under Windows XP on old, weak hardware, I definitely have to agree. This browser does not work properly there. On the other hand, Thorium does, though. But you have to exactly configure it suitable for your hardware. But TBH, my main browsers under Windows XP still remain New Moon 28 and Serpent.

@Anbima and @w2k4eva! Any in-depth consideration of certificate issues in 360Chrome are browser-specific issues and are actually rather off-topic here. In any case, this here is not a 360Chrome browser thread. Such issues should be discussed in one of the countless Arctifoxie 360Chrome threads. And just for clarification, this has happened several times there in the past, without any real solutions. 360Chrome 13.x had problems with certain sites and their certificates from the very first. This will never be solved as this ported browser has not been developed further for years. The only way to solve certificate problems in these browser versions is to use ProxHTTPSProxy. On some problematic sites, the Windows 2000 compatibility mode also helps to show the padlock and green, secure HTTPS connection under Windiws XP. I have tested all this myself, and it works. Or use a more modern Chrome browser in Windows XP as, for example, Thorium which does not show such issues!