Leaderboard

The patched version of EE 360 browser has preference for displaying sites in Russian. How do I force it to English? Relevant items in Settings page seem to be missing. Edit: found solution. 360Chrome\Chrome\User Data\Default\Preferences With text editor, look for "accept_languages" Flip language order like: "accept_languages": "en-US,en,ru-RU,ru" Clear cookies or start with new Portable if sites are still RU.

Well, at least the 1.1.8.5 version works still fine with the latest Windows build for me so there's no need to rush him

It's an original, unmodified ASMedia driver, which was developed as a generic driver (doesn't do any device checks): - uses SCSIPORT.SYS, so it is compatible with Windows 2000/XP and doesn't require integration of STORPORT.SYS (possible on XP only). - performance is fine, seems stable so far, supports 48-bit LBA and maybe up to 8 ports (6 tested here). - original 32-bit (x86) device property sheet didn't support Windows 2000, so I've coded my own version to support the OS, plus it asks to restart Windows if setting is changed. There are only two limitations: - Optical drives are seen as "ejectable" drives and shown in Safely Remove Hardware icon. - If you disable AHCI port 0, ATA and SMART atributtes cannot be read in utilities such as AIDA64. Download at https://www.win-raid.com/t5753f45-Generic-SCSIAHCI-driver-for-Windows-XP.html

RoyFox +1, and element of HongKong in the logo.

Merry Christmas! http://o.rths.ml/gpc/files1.rt/K-Meleon1.5.4en-US.tls12.7z most of GRE components are replaced with Retrozilla-based build (but not all)

As long as you have plenty of RAM (at least 512MB IMO), Serpent IA32 works fine. Maybe there is issues, maybe not, but I certainly haven't seen any.

Arctic Fox is very similar to New Moon 27. But at present @roytam1 only has an SSE2 build available. New Moon 27 has an SSE-only build. MyPal is very similar to New Moon 28. Both require SSE2. So if you're looking for a browser for an SSE-only PC, I'd look at either New Moon 27, @roytam1's Firefox 45 build, or perhaps his SSErpent 52 build (that last one is still experimental though).

And I will tell you, once more, that FirefoxESR (Nightly) 45.9.18 (by Roytam1) doesn't come with h264+aac decoders out-of-the-box; you have to download one yourself (instructions about Adobe Primetime CDM are to be found in a stickied thread in the XP forums, instructions/links for the LAV Filters DLLs are provided by Roytam1 himself and are to be found in a prominent location in this thread (which I've also linked to...); SIMPLE AS THAT! (Unless you consider spending 5min to install one of these "solutions" as a major inconvenience that will further deter you/anyone for that matter from using the browser(s)...) (For the record, you were also previously advised to "install" an appropriate h264 decoder by @Mathwiz, a "solution" you obviously chose to ignore... ) As for uMatrix, stick to it if it's "indispensable" to you, but don't automatically assume it's the browser's fault (and by association the maintainer's bugged coding) when you keep facing various page-rendering/media loading issues; try to post such a similar issue in the official PM forums and you'll be immediately told (and not in a courteous manner) that it's not the browser's job to adapt to a particular extension, but the other way round (BTW, "legacy" uMatrix is an abandonware, as far as I am aware - a fork is available; and WE uMatrix, if that's the one you're using with FxESR45, hasn't seen any major action for quite a long time...). FYI, Roytam1 did not create his FxESR45 fork out-of-nothing, but it's mainly based on the original 45esr code by Mozilla; this is an old codebase, and there's only limited "things" one can do to improve it (Fx45 can't be turned into Fx52+ as if by magic); Roytam1 is focusing on improving TLS support there, plus other (minor) rendering fixes are backported from another fork; all these as a courtesy to members running old hardware that lacks SSE2 instructions set support; and it's often the case that those users are simply content when a specific page justs loads in the browser, having little or no desire to start in-page HTML5 MP4 playback (which could "fry" their old CPUs or just be practically unwatchable) ... Trust me, his life would be made much easier/simpler if he stopped maintaining these forks... And please, do not post any more HTML5 MP4 video testing sites, I have myself more than a dozen to suggest; all will work fine, as long as the browser they're tested on can use patented (h264, aac) decoders and the video sites are properly allowed to load their embedded HTML5 players... I am personally done with this specific issue of Roytam1's 45.9.18 fork not playing back MP4 video in OP's machine; anyone is free to pick up the baton and pursue it further... @msfntor : Joyeux Noël !

... Sorry for that ; though I did quote only you in my previous post, that bit about FxESR 45 & uB0-updater was still targeting the OP, @Vistaboy "uB0-legacy updater" (for "other" browsers, i.e. ) installed directly from GitHub ALWAYS instructs the browser it is installed on to look up on its GitHub repo for its own updates; that is why the special XML tag <em:updateURL> exists in its install.rdf file; that functionality was never broken by GitHub! "uB0-legacy" doesn't come with such a "special" <em:updateURL> XML tag; so, the browser it is installed on checks for its updates in the respective browser extensions store; for Fx 45-56 (and St55), that would be AMO; when uB0-legacy updater is co-installed, it first intercepts and nullifies those default update checks (for uB0) in the browser extensions store and then it itself searches (via page-scraping) the uB0 GitHub repo (which contains both XUL & WE versions), identifies the latest XUL version there and presents the browser with that version as the appropriate uB0-legacy version to update to; it was specifically that stage ("identifies the latest XUL version there") that got broken by GitHub on Tue Dec 17th ; I hope it's crystal clear for everyone now!

@msfntor I would expect Arctic Fox to require the same LAV video .dll's as NM 27 for video playback to work. (IIRC there's a FAQ in post 1 of this thread with the links to these .dll's.) But I haven't confirmed if they work with Arctic Fox myself. It wasn't clear whether that was addressed to the OP or to me. So just to clarify, I don't have uBO or uBO Updater installed in FF 45 at all. I only use FF 45 for testing, so I've kept the installation as "clean" as I can. I do have both extensions installed in Serpent 55, probably from GitHub (I know I got uBO itself from there), and both auto-updated fine. But it's certainly possible the OP installed uBO Updater from APO (I of course don't know). If the version on APO differs from the one on GitHub (I'm too lazy to download them and check), that could indeed explain its failure to auto-update on his system. That aside, what I think you're saying is that uBO Updater redirects update requests to GitHub not only for uBO, but also for itself. Which makes sense now that you mention it. Interestingly, uBO Updater not only auto-updated my uBO installation on Dec. 16, but also auto-updated itself on Dec. 18, presumably after GitHub made the changes that required the fix to uBO Updater in the first place. So now that I know the backstory, I'm rather surprised it auto-updated for me or anyone. (But I'm not complaining!)

The uB0-legacy updater extension was never hosted on AMO, to begin with... It's currently hosted on APO, though, https://addons.palemoon.org/addon/ublock0-updater/ Notice the advice on that page: So, for FirefoxESR 45.x.x, you should've have installed directly from the GitHub repository, not APO (although the OP did not specify the origin of its installation...): https://github.com/JustOff/ublock0-updater/releases The GitHub hosted XPIs check for updated versions of the extension via GitHub APIs, as can been seen in its install.rdf file, L12: <em:updateURL>https://raw.githubusercontent.com/JustOff/ublock0-updater/master/update.xml</em:updateURL> So, when FxESR 45 checks for extension updates, it is instructed by the extension to use for its update check: https://raw.githubusercontent.com/JustOff/ublock0-updater/master/update.xml and not check through AMO, since the specified <em:updateURL> value overrides the one inside Firefox (which, as posted, points to AMO by default ...) . Cheers

FF 45 probably looks at addons.mozilla.org, and uBO Updater is probably not hosted there any more. At least, a search doesn't bring it up, which would make sense because it's probably a pre-WebEx app (otherwise it wouldn't run on NM, PM, or official Basilisk, which are its primary targets) and therefore banned from AMO. I got lucky: my Serpent 55 (which also uses AMO) updated to the new uBO version on Dec. 16, when uBO Updater 1.6.7 was still working.

The @LoneCrusader is a dear friend and it grieves me to be pushed into arguing publicly with him about this, but I was never given any choice about it, since he seems to be the main (and, ATM, only) voice oposing the (re-)branding of the browsers. That said... True enough. But, while not forgetting, moving on is sometimes required, and I think this is one such case. There is a time for appeasing, and one for open confilct. I hope we won't keep arguing uselessly until we are beyond all possible compromise. Most of those in this thread are for the (re-)branding. I think that PoV has already won by acclamation. ... and you are the only one doing quite a strong effort to derail any compromise, when most of us don't see the facts in the same light as you do.

@Sampei.Nihira The major issue is Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module first, not the missing files ("question mark" inside a yellow circle); check for missing functions in XP's system files, like kernel32.dll; those files will be marked with a reddish square in the tree structure in the left side-bar; click the + signs where needed At least one other XP user has reported the inability to run that file, perhaps he could also investigate with DW and if a pattern is found and verified, perhaps the app's devs should be alerted their file doesn't run on ALL XP setups; just my 2 eurocents, ofc Buon Natale! EDIT: Beaten to it by mere seconds by @Nojus2001

I am a web developer, and I wish more sites could do what CNN does, they have a low-bandwidth version of their site. There was a trend of text-only websites back in 2017-2018. It was primarily done for critical situations, but it can also help us through our retro browsing activities. You can read about them here and here: https://www.poynter.org/tech-tools/2017/text-only-news-sites-are-slowly-making-a-comeback-heres-why/ https://www.maketecheasier.com/access-low-bandwidth-websites/ In case you'd prefer to go straight to the low bandwidth versions of some sites: https://lite.cnn.io/en http://text.npr.org/ Twitter and Facebook had one as well, but they $#*%$*%$ ported the experience to mobile apps only. EDIT: Adding some more that I haven't tested yet: https://en.m.wikipedia.org/wiki/Main_Page

Just choose the minimum amount available and that will do the job for you. The license is very cheap, you could also consider donating more so that you've extra keys available for you.