AstroSkipper

Yep! A clean, genuine Windows XP Professional. Only the service pack SP3 and all post SP3 updates until 2014. POSReady stuff has never been applied to this partition.

Thanks for the nice compliment and for the tip! There is definitely nothing I wouldn't try to solve these crappy crashes. Strangely, Thorium works perfectly in my Windows XP SP3 POSReady installation, i.e., without any crashes. And there, these DLL files exist from the very first.

I tried both. The last try was native Thorium without anything. No extensions, no additional flags and no Chrome XP API Adapter from IDA-RE-things, following the main principle to go back to the roots if it doesn't work.

Sometimes high, sometimes low. I can't recognise any particular pattern.

That's good to know. In both systems, all runtimes have been installed.

Any ideas what can cause these sudden closings of Thorium? My hardware can't be the causer, though. Has anyone had similar problems?

I added bold and underline to be sure that everyone is asked here. This has nothing at all to do with your answer, for which I have already thanked you. You should calibrate your sensor a little. It is set too sensitively.

Thanks for replying! And yes, I know very well your opinion about POSReady updates for Windows XP. But on my computer, Thorium only works in my Windows XP system with all POSReady updates. Maybe by accident, and there is another causer for my described issue. That's all a bit strange. Are there any specific requirements for Thorium in terms of system software, especially regarding runtime libraries and so on?

Now, a question to all who are running Thorium under Windows XP Professional SP3 with all updates after SP3 but without any POSReady updates. Does Thorium work under these conditions? I have two Windows XP installations, one with and one without POSReady updates. When I start Thorium on Windows XP without POSReady updates, it crashes randomly without any messages. With crashing I mean a sudden closing of the browser without any actions by me, either directly when starting the browser or seconds respectively minutes later.

@Dave-H If your plan doesn't work, consider my strategy then. The steps are necessary for further steps I wanted to perform. And I don't know whether they work with an old Chrome as default. The Internet Explorer is automatically set as default browser by Windows XP if no other has been set by the user.

You can make any other browser, which has already properly been installed in your system, the default, of course. Important is to get rid of everything related to Thorium. When done, check if the old Chromium correctly works as your temporary, default browser.

@Dave-H The strategy I would like to recommend to you is to set the browser settings in your Windows XP installation back to Internet Explorer as default browser. Open the Internet Explorer options and set it as your default browser! After doing so, remove all entries related to Thorium using Registry Workshop! Search for Thorium and ThorLoad! The reason for this strategy is that I assume something browser related has been messed up. It is difficult to find the error as there are many registry keys in terms of registering a browser and its corresponding extensions. Revert everything you tried to make Thorium as your default browser! I have seen you are using the SSE4 release. Does it work properly in your system? Maybe, you could give the SSE3 release a try only to see if it is working better than the SSE4 one. Just an idea, of course! You know the higher is not always the better. In any case, be careful when purging your registry! Perform a registry backup first! Everything else after that. What do you think about this approach?

Can you describe the quoted issue more detailed? You can't open internal pages or the setting page in Thorium? Did I understand you correctly?

You are not thick. If at all, a little forgetful. We had the problem back then in the beta test of my ProxHTTPSProxy package. I called the problem the "space bug". Search my proxy thread for "space bug"! Normally, if a space is inside a path, the string needs quotation marks when it comes to coding. Especially when using command line commands or programming batch files. Maybe, this loader allows such spaces when defining variables. Personally, I have no spaces in my user folder for Thorium. So, I have no problems with that. Long story short. Just remove the quotation marks in the line where the $Profile$ variable is defined! But what about my questions? So, I have checked this, and you are right. No quotation marks are necessary for defining a variable if it contains spaces. A bit strange, though. I wouldn't have thought so.

Open these four registry keys with your registry editor and post here via the export feature of Registry Workshop (I know you are using the same tool as I do. I need to know the exact strings in form of an exported key for better comparison ) what have been set for them in HKEY_CLASSES_ROOT\http, HKEY_CLASSES_ROOT\https, HKEY_CLASSES_ROOT\ThoriumHTM\shell\open\command and HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\Thorium\shell\open\command. Use the code feature of the forum editor for pasting the exported keys!

You are not thick. If at all, a little forgetful. We had the problem back then in the beta test of my ProxHTTPSProxy package. I called the problem the "space bug". Search my proxy thread for "space bug"! Normally, if a space is inside a path, the string needs quotation marks when it comes to coding. Especially when using command line commands or programming batch files. Maybe, this loader allows such spaces when defining variables. Personally, I have no spaces in my user folder for Thorium. So, I have no problems with that. Long story short. Just remove the quotation marks in the line where the $Profile$ variable is defined! But what about my questions?

@Dave-H This is what you seem to be using in the loader INI file at the moment: Edit: There is a space in the string of your user data folder but the syntax of this INI file seems to allow that. BTW, I asked you: You can first try this code if wanted: [Setup] AppName=Thorium [FileToRun] PathToExe=.\Chrome\Application\$AppName$.exe Parameters=--user-data-dir="$Profile$" --no-proxy-server /high-dpi-support=1 /force-device-scale-factor=1 --disable-component-update --use-angle=d3d9 --ignore-gpu-blocklist --single-argument [Environment] Profile=.\Chrome\User Data Edit: You defined the environment variable $Profile$, which you didn't use at all, though. Generally, a better approach is to use a string without spaces as, for example, @Dixel suggested: The string ..\data creates this folder in the root folder. If you want to create it relative to the folder where the loader is located, you have to replace that by .\data or in your case by .\chrome\data. But all that is not the solution for opening a link in your browser from a document successfully. For this issue, you have to check all registry values that you've set for the Thorium browser. All of them should point to your loader. Check all file type associations in terms of browsers such as .htm, .html and so on! You can do that from the Control Panel via the app "Folder options". Did you use the two REG files inside the programme folder for registering Thorium? Can you open a link from a PDF file in Thorium by left-clicking?

I totally agree. I assume you will still stay for a while with Malwarebytes Premium 3.5.1. Do you already have any preferences for what kind of antimalware programme you want to use under Windows XP afterwards?

And one thing should be made clear. The way Malwarebytes treats customers of older versions is beyond good and evil. To stop updating virus definitions without prior notice and simply present customers with a fait accompli, as seems to be the norm with this company, is a no-go. And being customer of Malwarebytes also means you have to pull any information out of these guys' noses every time such things happen. That's not how you win customers , that's how you lose them .

If you only check the Office 2010 option, you won't find updates for Office 2007 (v12.xxxx.xxxx). I said: So, look into the folder client\ofc\glb when only updates were enabled for Office 2007!

Thanks for reporting! Even if this is bad news. What is your last version of the definition updates you received via automatic update? My latest version is 1.0.39678 which was also mentioned in the thread you linked to.

The service LanguageTool https://languagetool.org/ doesn't work anymore in Mypal 68 (and, for example, in New Moon 28, either). An entered or pasted text is no longer analysed for errors. However, I don't know when this started.

As far as I know, Office 2010 was originally compatible with Windows XP but later updates seemed to have been somehow incompatible. But maybe, someone knows more as I have installed Office 2010 under Windows 7 only.

Thanks for the hint! I took a quick look at this. Looks interesting.

I already modified the 360Loader.ini. I changed the name of both files to ThoriumLoader.exe and ThoriumLoader.ini and replaced the Icon Group of the ThoriumLoader.exe by the one from the thorium.exe. This modified loader works well to call up Thorium. And due to its separate ini file, the command line flags set by the user can be easily changed at any time. Here is a screenshot taken from my current "Open with" context menu in Windows XP: Everything I have written so far proves that Thorium can successfully take up and load a link via a command line call, initiated from the registry, when using a loader such as ThoriumLoader. Cheers, AstroSkipper