Leaderboard

0. Use the newest versions of ESDI_506.DPR & AHCI.PDR too. 1. C:\WINDOWS\SYSTEM is not need, of course. 2. Literally few days ago when I solved problem of executing ATA commands (like setting PATA transfer mode for PATA device on SATA Host - PATA Device bridge) I made the dumper of IDENTIFY info without using smartvsd.vxd interface too, so for the first take: https://github.com/LordOfMice/Tools/blob/master/atainfo.zip unzip content and run DumpIDENTIFY.exe. You should get 3 .DAT files and no errors or warnings. 3. If success on step 2 then try to use SMARTInfo - this is the same thing as DumpIDENTIFY but with smartvsd.vxd interface using. You have to get IDENTIFY.DAT dumps too and no errors.

Hello everyone! Today, I changed the title of this thread. My new focus in this thread is on UC.JS loaders and the associated UC.JS scripts. I stopped using custom buttons with the 'Custom Buttons’ extension quite some time ago. UC.JS scripts are far more powerful than the legacy custom buttons. You have full access to the browser’s native (Vanilla) JavaScript. Since the beginning of last year, I have converted all my beloved, self-written custom buttons into UC.JS scripts and written many new scripts myself, initially targeting Mypal 68. Since last month, I began porting them to the New Moon 28 and Serpent 52 browsers. In the meanwhile, I have completely removed the Custom Buttons extension, including all custom buttons, from these browsers. I have reduced the use of other extensions to an absolute minimum and started to replace all missing functionality by UC.JS scripts. What interests me personally here is whether you have installed any UC.JS loaders in New Moon 28, Serpent 52 or Pale Moon, and if so, which ones, as well as how extensively you use UC.JS scripts in general.

@roytam1 Whatever changes you make with regard to the of threads or CPU cores, I sincerely hope that your SSE2 XPmod releases will continue to work on systems with a single-core CPU. And another little reminder: This now appears permanently in the Browser Console because your HTML document is not configured correctly.

Since 6/Oct/2025 use native mode and override for google and all ok. ps. Override for google recaptcha, otherwise Ok, that works too. Thanks! But switching to Firefox Compatibility is working too. So I think I am right in terms of my statement in my previous post. If Google discovers discrepancies between the engine used and the Firefox version, including the operating system version, then it will strike.

@roytam1 Google seems to have tightened its algorithms and heuristics. If compatibility mode is set to "Native", New Moon 28 is now classified as a bot and blocked. I could reproduce this behaviour in my installations. However, the captcha to remove this blockage can't be solved in this browser. Luckily, switching to "Firefox compatibility" mode resolves this issue. I therefore suggest to default it to this value from now on. Apart from that, you should now set a SSUAO for Google without any reference to Goanna or Pale Moon, to avoid being immediately flagged as a bot. Google is likely detecting a conflict between Goanna/Pale Moon and a more recent version of Firefox (version 128), possibly in combination with a very old operating system such as Windows XP, concluding this must be a bot.

Hello everyone! Today, I changed the title of this thread. My new focus in this thread is on UC.JS loaders and the associated UC.JS scripts. I stopped using custom buttons with the special legacy 'Custom Buttons’ extension quite some time ago. UC.JS scripts are far more powerful than the legacy custom buttons. You have full access to the browser’s native (Vanilla) JavaScript and don’t have to contend with constant compatibility issues when new updates from Mypal 78 are released. Since the beginning of last year, I have converted all my beloved, self-written custom buttons into UC.JS scripts and written many new scripts myself. I have completely removed the Custom Buttons extension, including all custom buttons, from Mypal. I have reduced the use of other extensions to an absolute minimum and replaced all missing functionality by UC.JS scripts. What interests me personally here is whether you have installed any UC.JS loaders in Mypal 78, and if so, which ones, as well as how extensively you use UC.JS scripts in general.

Many thanks for this ; it worked as described; still, this is a mitigation/a workaround, whereas the underlying UXP cause that now triggers the "incompatible" message remains unknown ... That's why I reported it to the Palefill issues. I see no reason for one to swear , is there? https://www.google.com/search?channel=entpr&q=TTBOMK That’s not swearing. It’s just a typical German habit to get annoyed by such abbreviations. Native English speakers use an abbreviation for every little thing, which is completely frowned upon here.

I meant the personal notifications. And what the hell is TTBOMK ... DKKWV (Das kann keiner wirklich verstehen)

Read my report here and you will fix it easily: https://github.com/martok/palefill/issues/109

I have all three browsers installed under Windows XP, New Moon 28, Serpent 52 and Mypal 78. At the moment, Serpent 52 is the only one who works without any serious problems on GitHub. Logging in, personal messages, downloading files, searching and reading contents or issues, and even commenting is working on my old single-core Pentium 4. New Moon 28 has always had issues with GitHub, and they’re getting worse and worse. GitHub’s web technology is rubbish.

New Moon 28 and even Mypal 78 don't work properly on Github. That's why I use Serpent 52 for accessing GitHub pages under Windows XP. @basilisk-dev and @roytam1 did a good job.