Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220604-3219d2d-uxp-e8b114fe4-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220604-3219d2d-uxp-e8b114fe4-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220604-3219d2d-uxp-e8b114fe4-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220604-d849524bd-uxp-e8b114fe4-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220604-d849524bd-uxp-e8b114fe4-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220604-d849524bd-uxp-e8b114fe4-xpmod.7z Official UXP changes picked since my last build: - Issue #1742 - Part 1: Refactor rooting base class templates (80d7d4396) - Issue #1742 - Part 2: Add a class to encapsulate the possible results of a property lookup (c48b8e893) - Issue #1742 - Part 3: use JS::PropertyResult instead of Shape* (574b295d1) - Issue #1742 - Remove the ambiguous portions of gc that dealt with tagged pointers for shapes. (30a3ec27a) - Issue #1742 - Part 4: Don't trigger read barriers when comparing wrapped pointers types (e632fc1e8) - Issue #1742 - Part 5: Remove unnecessary GCPtr::unbarrieredGet (1cdbf6eb6) - Issue #457 - Remove the constructor from gfxShapedText::CompressedGlyph and make it a trivial class (c782076ad) - Issue #457 - Make GLContextSymbols a pure aggregate POD (f2cfb9997) - [network] SocketTransport2 cleanup (7f3a7225a) - [DOM] Don't allow internal MIME types to be assigned to DataTransfer (3bcd2ee36) - [network] Fix typo in nsSocketTransport2.cpp (6b3ab7099) - Issue #1909 - Guard against empty update manifest URL (7b3f9fb7c) - [DOM] Clip image data transfers. (9fa9622d5) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - [REDO] Bug 1222924 - Stop allowing webpages to link to moz-icon: (from aura-central) (86bd6632c) - image: sync with https://repo.palemoon.org/MoonchildProductions/UXP/commit/8e42fccca66d06b664ecc3c7345dc787a26ef4d9 (6ec59e798) - import from nss upstream: Bug 1767590 - Initialize pointers passed to NSS_CMSDigestContext_FinishMultiple r=#nss-reviewers,kaie (118b893f8e) (5618d02ca) * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

Note that now the fix was included into palefill 1.11 and does not interfere with any global setting: https://github.com/martok/palefill also fixes bunch of other websites on palemoon.

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 http://o.rthost.win/basilisk/basilisk55-win32-git-20220604-ea6e33cd0-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20220604-ea6e33cd0-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - Revert "partly imported from tenfourfox: #566 and #651: M1719215 (700da3e99)" (1ccc72b3c) - import from `custom` branch of UXP: [REDO] Bug 1222924 - Stop allowing webpages to link to moz-icon: (86bd6632) (df9d58971) - ported from UXP: Issue #1742 - Remove the ambiguous portions of gc that dealt with tagged pointers for shapes. (30a3ec27) (03824805f) - ported from UXP: Issue #457 - Remove the constructor from gfxShapedText::CompressedGlyph and make it a trivial class (c782076a) (ca5b2cb26) - import from UXP: Issue #457 - Make GLContextSymbols a pure aggregate POD (f2cfb999) (c518ebda1) - ported from UXP: [network] SocketTransport2 cleanup (7f3a7225) (e4f0e80d3) - import from UXP: [DOM] Don't allow internal MIME types to be assigned to DataTransfer (3bcd2ee3) (e2f3198be) - ported from UXP: Issue #1909 - Guard against empty update manifest URL (7b3f9fb7) (5600fe37e) - import from nss upstream: Bug 1767590 - Initialize pointers passed to NSS_CMSDigestContext_FinishMultiple r=#nss-reviewers,kaie (118b893f8e) (ea6e33cd0)

If you guys are in need of an Nvidia Graphics driver for your late-2000's to early-2010's Nvidia hardware for Windows 2000, you can find it here: http://windowsenthusiasts1.epizy.com/Downloads.html I've rehosted the graphics drivers to Media Fire in case the links in the "Running Windows 2000 on modern motherboards - USB Issues" thread die out (and the one for 258.96 has while the 257.21 has not, but may. 258.96 I was able to find through Internet Archive thankfully so it allowed me to download it to rehost it). The files are unzipped. If running the exe doesn't work, you'll have to mod the INF to include your Nvidia device. After doing so, it will warn that it did not pass WHQL testing, but you can safely ignore this. If, for some reason, it still does not work, you can Have Disk install this. After installing this, the boot time significantly increases during "Preparing Network Connections". This can be solved by disabling the NVIDIA display driver helper service, located in Control Panel->Administrator Tools->Services->NVIDIA display driver helper. After this is turned off, boot time will return to nearly normal speeds. Thanks to @win32 for this helpful tip (You can also find it in the aforementioned thread). There is also a new README included (alongside the original) that basically rehashes most of this info. I hope this helps someone out. Enjoy!

Curently YES, until someone found another XP A5 BSOD ACPI.sys x64 is not much tested, it may have some undiscovered bugs

Agreed. For nostalgia, I was reading my own posts regarding "ssl padlock" and "secure DNS" and "certificate errors" over at the Proxomitron Forum and I find it hillarious that everything the Proxo community was saying way back in 2009 is still true to this day. Web browser "ssl" has been a FLAWED technology since its inception!

I would really love to understand where do people base their claims that accepting http, visiting certificate issue-ridden websites for a little while, using older operating systems, automatically risk you to a huge financial loss-private life damage-data loss-ransomware or whatever because well, it is said so. It seems to me like one of many dogmas and ideological tendencies inside computer science which are questionable, unilaterally imposed by companies in their half-cartels, and mostly to deal with simpler users and people who do not have a technical support in their homes to manage their machines or networks, or as a masquerading reason for obscure intentions. I can cite the idea of google to kill cookies.

please try again, should be available now

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20220604-3dbfc66a-uxp-e8b114fe4-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20220604-3dbfc66a-uxp-e8b114fe4-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20220604-id-181ea5d-uxp-e8b114fe4-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20220604-id-181ea5d-ia-c642e3c-uxp-e8b114fe4-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.

Tripredacus, thanks for the response. I really should have included more base info in the original post, like what browser we are using, what locations we are looking at, etc. Sorry about that. Anyhow, it started working again [after a ~2 week hiatus] sometime between the start of this thread and now... Maybe the fact that I asked about it on here jolted the folks at google into action? I'm joking, of course. Or maybe not... ;^) Thanks again, -Jim

It seems to work for me. Because you didn't post it. It is an option under Layers. It shown different shades of color on each county and a number and an up or down arrow. It doesn't have any sort of pop-up to say what the number means. Also it only seems to work for certain countries.

I wish there was a way to place three DOZEN upvotes! The BEST thing that Chrome ever did, in my opinion, was the --ignore-certificate-errors startup flag!

For that specific purpose, just follow @roytam1's initial advice: You can just paste in the URL from his latest post, delete the 's' from https:, press Enter, and save the .7z file. Then extract it where you please and use it instead of Chrome 49. (My initial answer was more along the lines of, if you want to use Chrome 49 for general browsing on XP.) OTOH, if you've been using Chrome this long, you may find one of the 360EE versions easier to get used to than Serpent. Unfortunately, this is a cipher suite mismatch, not a certificate error. Admittedly, I assumed 32-bit WinXP. That is by far the most common. For 64-bit installs a MITM proxy is your only hope for making secure connections with Chrome 49, but the OP has ruled that out for whatever reason.

Windows Update v5 was never supported on any 9x Version. Here is a small overview.

It has been more than a year since Windows Update v6 for XP was put into an infinite redirect loop by Microsoft. It has also almost been two years since the update servers for XP were discontinued. Without the efforts of @maile3241, Windows Update v6 for XP would have never seen the light of day again. Now we can use v6 normally again on XP and are working to making v5, v4 and v3 working again as well. Now is a good time to archive v6, since it is still on Microsoft servers.

Chrome 49 uses WinXP's built-in support for secure (https:) connections. You need to have WinXP fully updated, including the POSReady '09 updates, to support TLS 1.2 and AES, in order to have any chance at all of making secure connections to many of today's Web hosts, and even that may not be enough! For the best chance, use a MITM proxy:

The RC3 version can update you to RC4 2022. FYI it doesn't come with installer. IF you wish for a regular installed program, you can use Nirsoft Zipinstaller to create UniExtract windows-installed program with pertinent shortcuts and uninstaller.

Install Windows XP SP3 and MS Office 2010. If there is no issue, look for conflict between SP4 updates.