Leaderboard

@Dietmar @reboot12 @Mov AX, 0xDEAD I discovered this today. https://github.com/FlyGoat/csmwrap Hopefully this means we can boot XP x86 on UEFI class 3 systems now.

MS updated the msstyles file and explorer.exe One doesn't work without the other unless you use ONE or a mod for explorer to work properly I had to redo the theme based on the latest update

About the xiaoxiaoflood script loading method in Mypal 68.14.8b With Mypal 68.14.8b, @feodor2 has unfortunately retired the best script loader forever. The Nuchi-Sporif script loading method as well as all other Nuchi based script loading methods no longer work in this Mypal 68 browser and logically in upcoming releases. This means that the first three script loading methods from my ranking list are no longer available in Mypal 68.14.8b and up. @feodor2 recommends the xiaoxiaoflood script loader from the seventh and last place of my ranking list for users of xiaoxiaoflood's stuff. I have therefore taken another look at this method in Mypal 68.14.8b. As already mentioned, I am currently using the Alice0775 script loading method in this browser, which I put together, fixed and modified myself. It has a good compatibility with existing scripts comparable to the Nuchi-Sporif script loading method. Of course, I first adapted my scripts to the JavaScript changes made in Mypal 68.14.8b. I now have all my important scripts, 24 in total at the moment, running successfully with this script loader. Due to a further, small modification I made to the Alice0775 script loader, all my scripts are again located in a chrome subfolder called Scripts. BTW, more than half of these scripts were created by myself and written to be as compatible and universal as possible. Now to xiaoxiaoflood. I downloaded the version of this script loader @feodor2 recommends on this GitHub site: https://github.com/Feodor2/Mypal68/releases/tag/68.14.8b. After setting up the xiaoxiaoflood script loader in a fresh installation of Mypal 68.14.8b with a brand new profile, I copied all my 24 scripts into the chrome folder. Unfortunately, only less than half of them were ready to use after starting the browser. The xiaoxiaoflood script loader can't do anything with my most important scripts , which in contrast work perfectly with every other script loading method . Besides the already mentioned Alice0775 script loading method, also with the Aris-t2/Ardiman-Endor8 or pure Endor8 script loading method. Furthermore, it reports in the Browser Console that certain variables such as gClipboard are not defined and does not understand some JavaScript commands such as style.backgroundSize and so on at all. In addition, problems with scripts that cannot be loaded are not logged in the Browser Console. No information! Nasty! All in all, the xiaoxiaoflood script loader failed my test once again and cannot be recommended by me for general use. All other script loading methods are much better. To be unbiased and fair , I also tested this method with xiaoxiaoflood's own scripts. These special but very few scripts basically seem to work fine. But when using external scripts with this method, the xiaoxiaoflood version of the rebuild_userchrome.uc.js script, for example, is not able to handle them correctly. It is able to disable non-xiaoxiaoflood scripts but can't enable them again. Spoken for me only, I do not consider most of the very few xiaoxiaoflood scripts on offer to be particularly useful. The xiaoxiaoflood version of the extensionOptionsMenu.uc.js script, for example, which is actually a great one, is far behind the version I use which provides much more functionality. One thing is clear. There are much better scripts available outside the xiaoxiaoflood world. In general, the following should apply to a good script loader: It should be able to successfully load as many scripts as possible, taken from different sources. Needless to say, these scripts have to be compatible with the JavaScript engine of the browser used. Conclusion: The xiaoxiaoflood script loading method has very poor script compatibility for scripts that have not been written specifically for this method, does not understand some standard variables, also does not recognise some JavaScript commands and does not log successful respectively unsuccessful loading of scripts in the Browser Console. The latter is particularly annoying when scripts cause problems and the cause needs to be investigated. An error message would be desirable and helpful. This script loading method can therefore not be recommended for Mypal 68 as a general script loading method. Especially not when much better script loading methods are available. However, for those who only want to use xiaoxiaoflood's stuff, it is ok. For all others, the xiaoxiaoflood script loading method is definitely not to be recommended. Greetings, AstroSkipper

British Gas, Nvidia gaming site, Twitch TV and all those that needed "experimental features" fixed?

What are we looking for? I didn't notice any particular warnings about filterlist incompatibilities. When updating filter lists in the legacy extension, you will see many entries in the logger considered invalid filters by uBO. At least, I see them.

In theory yes but practically no. And who will do that? As @UCyborg and me already stated, uBlock Origin is one of the most complex extensions. He called it rightly a "beast" that is difficult to tame. And it is hard work to implement or port such improvements from the webextension. And it is not even certain that they will work as expected.Therefore, we have to use more and good filter lists to get similar results in blocking at the moment when using the legacy extension. This is my assessment so far. We will see what happens in the future. In any case, I didn't get such ads you observed on the website www.ovagames.com.

To block most elements or objects whatever they are, you surely need more filter lists in the last legacy versions of uBlock Origin than in the webextension. A lot of filters are consindered invalid by the legacy extension due to the old filter engine which lags almost 6 years behind the webextension in terms of development. Open the logger and perform an update of your filter lists in the legacy version! Then you will see what I am talking about. In any case, I get a lot of notifications about invalid filters when checking the logger. But one thing I can say without any further proofs. You are using too few filter lists to block as much as possible with the legacy extension.

Just what I say. I use much more filter lists than you. Two of them you have enabled are not used in my installation. When I am back at my desktop computer, I will provide a screenshot of my current configuration for better comparison. What I definitely know at this moment is that in my uBlock Origin Legacy installation of New Moon 28, I have enabled 21 filter lists plus my self-created filters under the tab "My filters".

And another variant based on Kepler. NVIDIA GeForce GT 710 GPU Name GK208B GPU Variant GK208-203-B1 Architecture Kepler 2.0 Foundry TSMC Process Size 28 nm https://www.techpowerup.com/gpu-specs/geforce-gt-710.c1990

It's because there are two different variants of GT 710. GPU Name NVIDIA GeForce GT 710 GF119S GPU Variant GF119-300-A1 Architecture Fermi 2.0 Foundry TSMC Process Size 40 nm https://www.techpowerup.com/gpu-specs/geforce-gt-710.c2614

Possibility to get their original Windows system files modified by Kaspersky into the hell knows what?

Bad Omen: Windows Millennium is missing.