Leaderboard

Thank you! I will give it a shot.

Sure if I could reproduce that

It's ok for me, 126R7,XP x86

Can you try: --extractor-args youtube:lang=en ? [Edit] Ignore that. That is for the title, not for the audio. Maybe first get the formats using `yt-dlp -F URL`. Then choose for example this to get this mr. Beast video dubbed in Russian: yt-dlp -f 136+140-1 https://www.youtube.com/watch?v=yhB3BgJyGl8 Or: yt-dlp -f "bv*+ba[language=ru]" https://www.youtube.com/watch?v=yhB3BgJyGl8

If you take the Anubis explanation (posted above by @VistaLover ) at its word, it seems to make sense. The idea is to make the user agent (browser or bot) do something rather hard, but not too hard; the idea being if you're just an ordinary user, the extra work is just a short delay in getting to the Web page; but if you're a bot crawling millions of pages, that extra work isn't worth the effort so you'll just abort the script after a few milliseconds and move on. But, then - why insist on "modern" Javascript and why force users to disable their privacy guards? I'm still somewhat skeptical that Anubis was telling us the whole story above.

I have a lot more run-ins with Cloudflare than I do Anubis. Both of them can get stuck in an infinite validation loop. Cloudflare can get insanely aggressive, it will quite happily lock your browser into an irretrievable Loop of Death (who would write code like that?). At least Anubis can easily be stopped. I think the thing I object to the most is that they focus on the way a browser looks rather than what it is actually doing. In civil society this is characterised as profiling rather than being intelligence led. All that will happen is that the bots will better disguise themselves and their behaviour will go unchecked. Ben.

The contents of the updroots.sst file have been changed; the contents of the other * .sst files are unchanged.

I must say that I couldn't see anything obviously wrong on reboot12's video either, no crashes or error messages. Is Explorer being sluggish the only issue? I've been using Explorer a lot since I applied the patch, and I've not noticed any difference in performance, apart from the USB issue I mentioned earlier, which now seems to be fixed. Incidentally, I've now determined what specifically is causing the out of memory problem on my browser. It's being caused by my Facebook Purity extension, which is why it was only happening on Facebook! If I disable the extension, the problem goes away. Of course, that isn't the answer. It works fine on the 64-bit version of the browser on Windows 10. The issue still is that although the extension might be causing high memory use in the browser, now that it supposedly has 16GB of RAM to play with, it shouldn't still be running out of RAM!

Is nothing sacred?!

"ATAPI", never heard of that "Slimtype" looks more like a product line of DVD drives for notebooks, not an actual brand name.

Because "TSSTCorp" is a joint venture company of Toshiba and Samsung Electronics (simply merged). "Toshiba Samsung Storage Technology". https://en.wikipedia.org/wiki/Toshiba_Samsung_Storage_Technology

Oh, and btw, I can't even look at it, it's locked to members only.

High and thank you! I meant a portable of DX9 pack that doesn't install into the system, only locally, to get this testing programme work. I don't own any DX9 games, I don't play them.

There's no script on the image, and the image is doctored, edited. What does it prove?

My investigation of all other drivers, which might be problematic in that partition, has been finally finished. After all these already performed measures and all this hypothesis stuff , here's now a little and in my opinion quite interesting proof (what else could you expect from me ): Prerequisites: A native Windows XP Professional SP3 32-bit without any POSReady updates, Thorium SSE2 122.0.6261.171 WINXP x32, Total Commander and Process Hacker. Assertion: Driver remnants from previously uninstalled programmes can cause spontaneous, irregular crashes of the Thorium browser under Windows XP Professional 32-bit. Proof: The current status at the beginning of this proof: Thorium is still crashing spontaneously, sooner or later, without any recognisable pattern. After a thorough investigation of all installed drivers in this Windows XP partition listed in the prerequisites, I found three drivers in the c:\WINDOWS\system32\drivers\ folder in the form of SYS files, which are loaded correctly after system startup, though. These files are avgntflt.sys, avipbb.sys and avkmgr.sys whose manufacturer is Avira. They are automatically loaded at system startup and logged in the Event Viewer as properly loaded drivers. That's why I didn't notice them earlier as I only looked there for errors. However, there are no programmes of this manufacturer installed any longer in this partition. This was indeed the crucial hint. After checking and unpacking all installation files that could have installed these drivers in the past, I was able to identify the culprit. It was the crappy Wise Anti Malware 2.2.1, which was installed for a short time for testing purposes only. With the help of Process Hacker and Total Commander, I was able to stop the associated processes and completely remove all three driver files, but only after restarting the system. Immediately afterwards, I opened the Thorium browser, configured it completely and restarted the browser several times. No first launch crashes anymore! Various pages were called up. The browser did not crash even once, no matter what actions were performed. Now, Thorium is working absolute stably in this partition as it is in my POSReady partition. So, these three drivers or at least, one of them (probably the avgntflt.sys driver as it is a filter driver and was more difficult to remove), were definitely the cause of the permanent Thorium crashes. q.e.d. PS: So, forget about my formerly created hypotheses H0! They all have to be rejected with an empirically determined probability of type I error of nearly 0. There is no indication that Thorium requires POSReady updates under Windows XP 32-bit, at least at the moment.

Regarding my issue with sudden Thorium crashes, I performed the following measures so far: Checking the file system for errors. Checking the integrity of the partition structure. Purging the partition in terms of trash/temp files. Complete defragmentation of the partition. Offline defragmentation of pagefile and registry files. Clearing and reorganising of the prefetch files. Checking the registry for errors and fixing them. Checking for missing updates performed by Legacy Update. Adding a couple of Windows updates which weren't offered by WU/MU. Installation of the Microsoft Visual C++ 2015 - 2019 Redistributable Package as it is also installed in the POSReady partition. Verifying the integrity of the DirectX 9.0c installation. Verifying the integrity of all .NET Framework installations. Uninstalling or disabling programmes which are permanently loaded and don't exist in my POSReady installation. Checking all autostart programmes and services. Fixing of all errors from the event log. Configuration of all services corresponding to my POSReady installation. Updating of programmes, which are permanently loaded, to the same version as in the POSReady installation. Update of the root certificates. Fixing a network error and adjusting all network settings. Graphics card driver completely uninstalled, all leftovers cleaned and more recent driver version installed. Now, my Windows XP Pro SP3 installation without POSReady updates is completely error-free except the issue with sudden Thorium crashes . The good is this Windows XP installation is now even fresher and faster than ever. My next measure is the check of all other drivers in that partition which might be problematic.

I checked my Thorium processes regarding loaded modules, and on my Windows XP Pro SP3 32-bit, the vulkan-1.dll is not loaded.

You should better use GPU-Z to see all features of your graphics card.

Today, I have installed Legacy Update 1.9 on my Windows XP Professional SP3 installation where POSReady updates have never been applied. It's just a pure Windows XP 32-bit. Due to the lack of POSReady updates, I decided to test Legacy Update in this XP installation. It was installed in seconds and calling up this service worked without any problems. It even offered to install root certificates and POSReady updates, which I didn't want and had to untick during the install process, though. The Windows Update search was performed in the Internet Explorer without any settings or actions by the user, and only few minutes later, it was done. Great service! I can definitely recommend it, especially to those who haven't use the POSReady hack. BTW, the result was the same I got in 2014 as all WU/MU updates have been installed at that time. I just wanted to be sure that no updates are missing.