Leaderboard

It's only updates that replace MSO.DLL that you have to worry about, all others seem to be OK, and should still be applied IMO.

I extracted the core folder from the firefox 53 installer and patched all .exe files with XomPie. You just have to install it and it adds xpatcher.cmd to the send to thingy when you right click and it only needs the kernel32 patch so you hit 1 and enter and then it just works. This won't patch any system files. XomPie: https://github.com/tumagonx/XomPie/releases Working Software: Firefox: https://ftp.mozilla.org/pub/firefox/releases/53.0.3/win32/ Extract, then patch all .exe files Sugar Sync: https://filehippo.com/download_sugarsync/3.9.5/ Install, then patch SugarSync.exe

The "best" browser for XP depends on your hardware. For pre-SSE2 processors, I agree with @looking4awayout: If your system is even older (pre-SSE) your best bet is probably @roytam1's no-SSE build of New Moon 27. For newer systems you have more options. The Chinese Chromium backports are OK if you like Chromium and can deal with the Chinese language. If you prefer a Firefox-based browser, I've had pretty good luck with @roytam1's Serpent 55. It supports more add-ons than his Serpent 52 and I almost never have problems with Web sites not displaying correctly.

Thinking back about the time when "you know who" made a lot of fuss about the branding of the forked browsers, I noticed mainstream Basilisk still contains strings where the browser is referred to as "Firefox".

Just stopped in to say thank you very much for keeping these browser forks updated and working well. A number of web sites are starting to turn their nose up at 27.9, but with the other two, I can still get to where I must on Windows XP. Although I hate how Mozilla messed up the title bar/menus in 52/Basillisk. Noticed that this moved to a new thread on the forum - you guys really need an entire subforum dedicated to this. :) Thanks!

Ciao @resistor83 ; first thing I needed to do was get acquainted with PEC e-mail, since it's not used over here ; the following two links proved helpful: https://en.wikipedia.org/wiki/Certified_email https://vademecumitalia.com/pec-what-is-it-why-should-you-need-a-pec-address-and-how-to-get-one/ Now, I would strongly advise you to implement TLS 1.1/1.2 on your machine, regardless; probably better use the newer MS update, as per @erpdude8 : I can't see any way it could harm your existing setup; BTW, you did not say anything regarding Windows Updates in your system (only official Vista SP2 ones, till Vista EOL?) ... You specifically asked about Microsoft Outlook (part of Microsoft Office Suite), but, again, as pointed out by @Vistapocalypse, you neglected to tell about the used version... I am using myself the native e-mail client under Vista, Windows Mail, which, AFAIK, uses IE9's internet settings - I just checked the headers in the source of a gmail e-mail I received recently and I can spot the following (some parts obscured for privacy): Received: from mail-yw1-fxx.google.com (mail-yw1-fxx.google.com [209.85.xxx.xx]) by MX-IN-05.xxxxxxxx.gr (8.15.2/8.15.2) with ESMTPS id x8TKAo60027571 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) so I believe I can receive e-mails over TLS 1.2; but, of course, as detailed in this thread, IE9 supports only a limited number of TLS 1.2 cypher suites... Another solution for you to try on Vista would be the latest supported version of Thunderbird (52.9.1?) ... As for Microsoft Outlook, @Vistapocalypse is probably right; versions 2007 and 2010 use the WinHTTP library to connect to servers; Windows applications using WinHTTP on WinOSes < 10 can't normally use TLS 1.1/1.2, even if these protocols are enabled system-wide in the SChannel library, because WinHTTP is hard-coded to use only TLS 1.0. Mom (!) Microsoft decided to not mitigate this under Windows Vista (and Windows Server 2008) SP2, but did so for its Win7+ children (!) - Thanks M$! https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi Installation of that update should be followed by manually creating some registry keys, as instructed in the KB article; most sadly, an equivalent Vista/WS2008 update was NEVER released ... Some relevant articles (but fixes applicable only in Win7+): https://jaapwesselius.com/2018/09/23/outlook-2010-disconnected-with-tls-1-2/ https://www.ryadel.com/en/enable-tls-1-1-1-2-windows-7-8-os-regedit-patch-download/ https://www.greengeeks.com/tutorials/article/how-to-enable-tls-1-1-and-1-2-in-outlook-windows-7/ Illuminating SO answer regarding Vista: (from https://stackoverflow.com/questions/49497058/ ) Regards.

UPDATE! I have updated all the versions of the UOC Patch, as I have applied some tricks that further increase hardware acceleration, making scrolling smoother and faster. The tweaks work on every codebase, so please update to the latest version of the UOC Patch. On the 45 ESR version, support for multithreaded image decoding has been implemented and it seems to bring benefits even on single core machines. Thank you and happy RDDin'!

Nothing new in this post; it's just a summary of what's been discovered so far about this issue. To play Instagram videos in your FF (or FF-derived) browser, you need three things: Most obviously, you need to be able to play MP4 videos. This won't be a problem with @roytam1's UXP forks (NM and Serpent) since he includes his MP4 video DLLs in the build. For FF 45 though 52 or SeaMonkey 2.49.5, you can install the Adobe Primetime CDM according to the instructions pinned atop this forum; either method works. (Those instructions were recently modified slightly to work with SeaMonkey.) You need to set your user agent to spoof FF 56 to instagram.com. You can either set the general.useragent.override preference in about:config to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0 or use an Instagram-specific user agent. FF versions before 56 work too, down to a point, but basically nothing on Instagram works at all if you spoof any version newer than 56. If you're not using NM, Serpent 52, or SeaMonkey, you need the following code in file userContent.css in the "chrome" subfolder of your profile: Note that this code is changed somewhat from @mixit's original fix; Instagram changed some of their random class names, requiring an update. Instagram will probably change them again someday, and we'll have to get @mixit to update his fix yet again.

I made a video guide on how to do so if you're interested in that:

I wonder if LineageOS has the option for good 'ol USB Mass Storage mode. For Sony Xperia E3 at least with stock OS based on Android 4.4.4, it's not an issue because it has the option in settings. It's still a fairly modern device, only 5 years old. I never used unrooted phone for long though, just find it too restricting. Banking apps often refuse to work on rooted phones and even some stuff in entertainment category... Sure you can unroot and certain modifications for which you needed root permissions stay, obvious exception being the apps that need root access to operate normally, but it's just an extra stupid barrier for the people who know what they're doing.

Just a general side note, regarding those 2 "application data" directories: C:\Documents and Settings\User\Application Data\...profile... C:\Documents and Settings\compname\Local Settings\Application Data\...cachedstuff... Those had confused me mighty for years, before realizing there's actually two appdata folders. And then was initially confused yet more: huh - two?? But it's a good idea to kepp the second folder in mind too. It's a strong suspect if sometimes the browser acts weird, as if it had a ghost cache somewhere... and that's exactly in LocalSettings where it's hiding. For example if an addon gets disabled but stubbornly still has some lingering effects or similar. XUL stuff is cached in the startup-Cache folder, as seen in the screenshot, and it can be deleted to clean up and refresh itself. Basically the profile folder is for user stuff, and the LocalSettings folder is for machine-related cached stuff, just for faster startups.

A fan that runs 24/7.

Methinks the UOC Enforcer file (user.js) hasn't been correctly installed, as both directories depicted are not the main profile directories of either New Moon 27 nor FirefoxESR 45! Page 1 of this thread says: To easily locate your main browser profile folder, use the browser's about:support internal tab, from there "Application basics" => "Profile folder" => "Open folder" button... E.g. for FxESR 45 it should be located at: "C:\Documents and Settings\Tualatin\Application Data\Mozilla\Firefox\Profiles\e0afyh62.default" Regards

New build of Firefox 45ESR SSE: test binary: https://o.rths.ml/gpc/files1.rt/firefox-45.9.17-20191026-5b83a3a16-win32-sse.7z repo: https://github.com/roytam1/mozilla45esr Changes since my last build: - update NSS to 3.44.2 (72099b2d0) - partly import change from tenfourfox: update pins, TLDs, miners (0ed2cf531) - import changes from tenfourfox: - #574: update EV roots for ESR68 rebase (a9d971bfe) - #574: M1581950 M1584216 M1577107 M1584907 M1558522 (71cf5b95a) - #574: new tzdata (842c3af2a) (8d1468759) - Addendum to 706b4d3150dbe901c92916bad8346d16ed6894aa (5b83a3a16)

The problem is with the MSO.DLL file. The updates which replace this file are now replacing it with a version that is not compatible with Windows XP. The last compatible version is 14.0.7214.5000, which is date stamped 14th September 2018, and was included in KB4092483. All later versions will not work, and there is no solution to this I'm afraid. Microsoft have been told about this, but not surprisingly have not done anything about it. I'm sure their line now is that none of their software is now supported on Windows XP, even if it was originally.

Have new build generated by ProxHTTPSProxy v1.5 (Rev3c), python module cryptography-2.6.1 with openssl-1.1.1b (Thanks to @Mathwiz) updated. If anyone has interest please write a PM to me. Info: At Python 3.44 the support ends in March 2019. With the latest official cryptography module version 2.6.1 (Feb 28, 2019) ProxHTTPSProxy does not work on Windows XP anymore. Last official working version 2.4.2 (Nov 21, 2018).

Have new build generated by ProxHTTPSProxy v1.5 (Rev3b), various python modules updated (cryptography-2.6.1_openssl-1.1.0j), config.ini supplemented by some entries, CA certificates (cacert.pem) updated and alternativ cacert.pem from MSCerts (Cert_Updater) 11/28/2018. If anyone has interest please write a PM to me. Info: At Python 3.44 the support ends in March 2019. With the latest official cryptography module version 2.6.1 (Feb 28, 2019) ProxHTTPSProxy does not work on Windows XP anymore. Last official working version 2.4.2 (Nov 21, 2018).