Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.4.win32-git-20191130-013ef52ed-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.4.win64-git-20191130-013ef52ed-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.ml/palemoon/palemoon-28.8.0a1.win32-git-20191130-013ef52ed-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.8.0a1.win64-git-20191130-013ef52ed-xpmod.7z Official repo changes since my last build: - Issue #1300 - Clear the message manager script cache when updating and removing add-ons (f703f61ea) - Add crashtest for resolved bug 1558522. (1f36fcbb3) - Issue #1254 - Update embedded emoji font to 0.5.0 (Twemoji 12.1.3) for Emoji 12 support. (1a8fdf3c7) - Merge pull request #1301 from JustOff/PR_mm_script_cache (e8c40b0bc) - Issue #1302 - Add self-hosted implementation for string regex .matchAll (185a9a750) - No Issue - Use alternative packaging for Pale Moon and Basilisk (52cb294d2) - Issue #1303 - Add langpack generation targets for Pale Moon and Basilisk (064790189) - Fix typo in application./basilisk/build.mk (0b92b3e5d) - Allow Solaris to use alt packaging for Pale Moon and Basilisk (8fea22c95) - Issue #1304 - Make the second arg of insertRule optional (ea03043bd) - Issue #1258 - Remove remaining chat core bits (997be5d52) - Merge pull request #1305 from adeshkp/patch-13 (8f92e6117) - Simplify the overflow child frame reparenting in nsInlineFrame::DestroyFrom. (7070dddb4) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (013ef52ed)

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.rths.ml/basilisk/basilisk55-win32-git-20191130-0aabdf6ac-xpmod.7z Win64 http://o.rths.ml/basilisk/basilisk55-win64-git-20191130-0aabdf6ac-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - update libaom to rev 1f0a4746aa8bfcce3fe7fbd2092aef8fe247aef4 (without moz.build and aom_ports/aom_once.h) (0ae57e925) - applied NSPR Bug 1586070 - Read does not advance file position for files larger than 4GB on Win32. (See also bug 70765.) r=kaie (3f9dbaa13) - updated to nss-3.44.3 (6402431c7) - import change from tenfourfox: - #431: M1385165 (5b2393042) (736e52372) - port change from tenfourfox: - #579: M1218456 +backbugs -nsILinkHandler removal, with changes for 45 (5e0cd430c) (6d0cdf8b2) - import change from tenfourfox: - #375: M1352323 M1038099 (eb6f62648) (4fcfb5a3d) - import change from tenfourfox: - #375: M1334642 +efficiency patch (1d2b06b10) (faf6c5367) - import changes from tenfourfox: - #578: M1580320 M1584170 (216c8ff73) - #578: update pins, preload, TLDs (46acdd518) (7348a05a4) - import UXP changes: - Issue #1291 - Part 1: Ensure exp(1) returns e exactly (use a const) (ddb27ac3e) - Issue #1291 - Part 2: Stop using the lib's sqrt() function (b6c0bdd7d) - Issue #1291 - Part 3: Update fdlibm to Sept 2019 version (ddb1aaaee) (170c81c40) - import UXP changes: - Issue #1288 - Part 1a: Update brotli to 1.0.7 (729ee0f18) - Issue #1288 - Part 3: Update woff2 component to 1.0.2 (66b4db7c3) - Issue #1288 - Part 4: Update the OpenType Sanitizer component to 8.0.0 (207b043e1) - Issue #1288 - Part 5: Pass graphite fonts through OTS. (e266a1fc5) (bc341b23a) - import UXP changes: - Issue #1274 - Part 1: Adopt the cairo version as our own. (bc89f33a8) - Issue #1274 - Part 3: Update libpixman licensing (fd38014a6) - Issue #1274 - Part 5: Misc fixes and version update. (82d70c6ae) (0aabdf6ac)

you can get the experiment build here. Disclaimer: I'm not responsible for any crash/damage caused by this build. You should always test such builds on its own profile.

I wasn't sure if this was already in the archive, so I'll upload it just in case Rudy sent this to me on July 27th - It's an updated version of his AHCI driver to fix BSODs on AMD Ryzen B350/B450 chipsets unzip with 7zip AHCI.PAK

some little experiment: tried to build non-SSE2 build of UXP, binary built but it doesn't run (not crashing but quits without showing any UI/console window and no error messages) on my Mobile Celeron 650MHz. EDIT: it seems to be chromium's zlib doesn't like non-SSE2 environment, reverting it back to stock in its branch. EDIT2: commits pushed to its branch. (Notice: even it is pushed to its own branch, no regular builds will be created as whole thing is actually walking a tightrope and anything can be happened)

not neglected but missed since my logs mixed up with long upstream's logs, added back.

On a sad note mozillazine is shutting down. The owner kerz posted last September it was the end so it could be anytime unless they can work out some way of keeping it going. That used to be the go to site for everything Firefox but it's become a casualty of Quantum. After v57 the traffic went to a fraction of what it was.

I didn't miss the point; I just thought folks might like an idea of how much the license would cost if this goes through, and what they'd get for their money. It's reasonable to assume the cost for an XP license would be the same as for the Win 7+ version, or at least close to the same. After all, the answer to "would you be willing to pay?" usually depends on the answer to "how much?" Probably wouldn't get many responses without that tiny bit of info....

Out of curiosity, I downloaded that MS update from the link in the KB article; that fetched file "excel2010-kb4484164-fullfile-x86-glb.exe", sized 36.1 MB (!). I can confirm this is only SHA-2 code-signed: You'll have to test file code-signing signatures in a fully updated Win7 system (or higher) or, in my case, in Vista SP2 with one of the WS2008SP2 updates which give the OS SHA-2 code-signing verification support... Trying the Windows Update Catalog link (mentioned in that same KB article), http://www.catalog.update.microsoft.com/Search.aspx?q=KB4484164 I ended up with a different file, excel-x-none_a5b150722cca4d6d9b062063747b02df0eaaaf51.cab (sized 19.8 MB); extracting it yields an excel-x-none.msp file (Windows Installer Patch, sized 40.3 MB), which is also only SHA-2 code-signed; notice that on the MUC, only a generic version is offered, regardless of the OS on which Office 2010 is installed ; perhaps the .exe and .msp files check OS version when launched, but it didn't occur to M$ that XP+Vista don't support SHA-2 code-signatures; there was a specific update on Vista (KB2763674) that allowed for .exe file execution even in the case the .exe was only SHA-2 signed, I guess a similar one might exist in XP (as part of the POSReady ones?) ... The deal breaker here is that Windows Update on both XP and Vista was never patched to deliver updates signed with only sha-2 code signatures - for WS2008SP2, such an update does exist, but when that's installed on Vista, it changes the build number of Vista to 6.0.6003 - but that cuts off Vista completely from WU servers , because they were only configured to serve Vista 6.0.6002 builds; it emerges that WU servers are intelligent enough to tell apart Vista 6.0.6003 (blocked) from WS2008 6.0.6003 (supported); so, starting with Nov 2019 (and for the remaining updates till Oct 2020), users of Office 2010 SP2 on XP/Vista should manually install applicable updates from either MS Download Center/MUC... ( ... and you thought M$ would screw Office 2010 only on XP, by sending incompatible mso.dll files... )

That's good; your last post had me worried! My yellow shield was there this AM with the three Office 2010 updates. Since manual installation still works, here are links to their support pages: https://support.microsoft.com/kb/4484164 https://support.microsoft.com/kb/4484127 https://support.microsoft.com/kb/4484160 You can go to each support page, scroll down to "Option 3: Microsoft Download Center," and find links to the standalone installers for both 32- and 64-bit versions of Office 2010. (I would assume the vast majority of folks have 32-bit systems, but just in case....)

Microsoft Update didn't take anywhere near as long to complete its scan as it did when we had the issue before, it wasn't hours and hours like it was then! It just took several minutes, which is unusual now. I did get a yellow shield with those Office updates this morning, but they failed again when an attempt was made using that interface. I have now installed them all manually and all seems fine, but what a PITA! I guess we will always have to do that in future if what @Mathwizsays is correct. The second update (KB4484160) seemed to take forever to install, but it got there in the end!