VistaLover

"Add-to-Search-Bar" is indeed an invaluable extension , nothing cumbersome about it, really... It enables adding search engine(s) even for pages for which no standalone XML plugin files exist/are available, just by placing the cursor inside a page's search input field (e.g. here in MSFN) and adding (via context menu) that search facility as a new browser search engine: No need to analyze page's code and/or craft manually a new XML search plugin... OTOH, even if you make one yourself, you'd need the second extension I mentioned for "search.json.mozlz4" enabled browsers, because these don't have a human-readable searchplugins directory inside their profiles ...

For "search.json.mozlz4" enabled browsers (mostly Serpent 52.9.0/UXP + Serpent 55.0.0/Moebius), I'd recommend the following "legacy" Fx extension: XML Search Engines Exporter/Importer v0.4 (should be also available from within CAA). Instead of having to deal with modifying .mozlz4 databases (a Mozilla-proprietary compression format), you can export standalone XML-format search plugins from within the search.json.mozlz4 file, edit them to your heart's content and then import back the edited plugin ; of course, you can also import already archived, standard, XML search plugins extracted from other browser profiles (e.g. from New Moon 27/28) or downloaded from specialised search-plugin repos...

In UXP-based latest St52 (2022-02-25) (32-bit), the left/right arrows on the top header, that are used to move between previous/later captures of the selected URI, are no longer functional : Error Console Log: Timestamp: 21/03/2022 02:29:58 Error: TypeError: t.getRootNode is not a function Source File: https://web.archive.org/_static/js/bundle-playback.js?v=poeZ53Bz Line: 2 Timestamp: 21/03/2022 02:30:02 Error: TypeError: e is null Source File: https://web.archive.org/_static/js/bundle-playback.js?v=poeZ53Bz Line: 2 ... which suggests UXP-incompatible code (ShadowRoot, first implemented in Fx63) is used now...

That extension started originally as a github-wc-polyfill fork , i.e. ONLY supporting initially GitHub/GitLab; unlike the upstream maintainer (JustOff) not wanting to support other sites beyond those two, the German maintainer (martok) of this fork will accept support requests for other sites broken in current UXP and will explore the possibility/feasibility of applying the necessary polyfills (where available) to address the breakage on those requested sites... At this very moment, the only additional (to GH/GL) site supported is "godbolt.org", while a request for "*.notion.*" URIs is still pending (but supposedly very difficult to materialise) ... https://github.com/martok/palefill/issues?q=is%3Aissue+sort%3Aupdated-desc+is%3Aopen ( ... of this "open issues" group, #3 and #6 aim to add user-side configuration options ) https://github.com/martok/palefill/issues?q=is%3Aissue+sort%3Aupdated-desc+is%3Aclosed

aus.palemoon.org forum.palemoon.org rm-eu.palemoon.org are at this time BACK ; related: https://forum.palemoon.org/viewtopic.php?f=1&p=225096

https://msfn.org/board/topic/182647-my-browser-builds-part-3/?do=findComment&comment=1214463 ... But let me save you the trouble and point out that ONLY official Pale Moon (currently < 30.0.0), official Basilisk (currently EoS'ed with v2022.01.27) and SeaMonkey are being supported; in the recent past, requests for FxESR 52.9.0, New Moon 28 and Serpent 52.9.0 support had all been rejected by JustOff, so I think you get the drift ... M$ employees brought in much breaking code, starting with autumn/fall of 2021 and continuing well into 2022, that "Moebius" simply can't cope with... Also, as you say, Moebius is lacking many recent Web APIs required by the gh-wc-pf extension, it'b be a nightmare, implementation-wise, for that extension to support it... ... probably because MCP had less time to move things around and worsen the performance levels attained originally by Mozilla ... What you can still do is use St55 for everything besides GitHub/GitLab and for these two "villains" use a minimal fresh St52 profile with just uBO+gh-wc-pf extensions...

1,885 changed files with 168,699 additions and 191,064 deletions. Was that just to make things extremely painful for fork-maintainers or did it serve some other agenda? Both of them are Basilisk/Serpent52 exclusive features (GMP/EME - as in functional DRM - broken for ages, but still useful to detect media sites that implement WidevineCDM; also useful for those few that prefer Adobe Primetime CDM's patented decoders over the ffvpx ones, on WinXP; WebRTC, despite claimed to be specs-compliant, fails to work on most WebRTC-enabled sites currently ); what are your thoughts about them in "our" UXP? ... Your thoughts on this, too, please? Let me reassure you, for the Nth time, that your constant efforts to "untangle" what MCP (currently a one-person-team) produce don't go unnoticed ; thanks once more...

Saw the following posted elsewhere a while ago, it concerns "upstream", so relevant to these forks, too: https://old.reddit.com/r/palemoon/comments/ti1okk/ntpmat_hes_done_finally/ https://web.archive.org/web/20220322141859/https://forum.palemoon.org/viewtopic.php?f=65&t=28003 Later EDIT: PM forums are back on-line: https://forum.palemoon.org/viewtopic.php?f=65&t=28003 23/03/2022 EDIT: Above PM forum thread hidden from non-members ; see: https://forum.palemoon.org/viewtopic.php?f=65&t=28058 Currently, the following hostnames are inaccessible: aus.palemoon.org (checks for/delivers updates to official PM browser) forum.palemoon.org (official PM/Bk user support forum, with tons of invaluable info accummulated over the years - much of it also applicable to the forks...) addons-legacy.palemoon.org (extension repo for PM<=29.4.4) addons.palemoon.org (extension repo for PM>=30.0.0) rm-eu.palemoon.org (European CDN that delivers binary releases[installers, 7z packages, portables]) addons.basilisk-browser.org (extension repo for Basilisk)

@roytam1 : I've left NM28 behind me several months ago, now exclusively (from the browsers you are compiling) using Serpent 52.9.0 (32-bit) in this Vista SP2 x86 laptop; what is the future for Serpent 52 with the advent of GRE ? Could platform enhancements implemented in GRE be still backported to St52's UXP? And I don't know whether NM28 users are aware, but GRE fully removes the Pale Moon GUID (also used in NM27/NM28) and a restructure of MCP's add-ons site is currently in progress, will you also adopt this change for future NM28 versions? https://www.palemoon.org/releasenotes.shtml

Here's my copy of file "polyfills.js" inside my local fork of your extension: var actualCode = ` // https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis // implemented in Chrome 71 // https://mathiasbynens.be/notes/globalthis (function() { if (typeof globalThis === 'object') return; Object.defineProperty(Object.prototype, '__magic__', { get: function() { return this; }, configurable: true }); __magic__.globalThis = __magic__; delete Object.prototype.__magic__; }()); // https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/fromEntries // implemented in Chrome 73 // https://stackoverflow.com/a/68655198 // https://gitlab.com/moongoal/js-polyfill-object.fromentries/-/blob/master/index.js // -> https://vanillajstoolkit.com/polyfills/objectfromentries/ if (!Object.fromEntries) { Object.fromEntries = function (entries) { if (!entries || !entries[Symbol.iterator]) { throw new Error('Object.fromEntries() requires a single iterable argument'); } let obj = {}; for (let [key, value] of entries) { obj[key] = value; } return obj; }; } // https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/any // implemented in Chrome 85 // https://github.com/ungap/promise-any // copied from github-wc-polyfill if (!('any' in Promise && typeof Promise.any == 'function')) Promise.any = function($) { return new Promise(function(D, E, A, L) { A = []; L = $.map(function($, i) { return Promise.resolve($).then(D, function(O) { return ((A[i] = O), --L) || E({ errors: A }); }); }).length; }); }; // https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/allSettled // implemented in Chrome 76 // https://95yashsharma.medium.com/polyfill-for-promise-allsettled-965f9f2a003 if (!('allSettled' in Promise && typeof Promise.allSettled == 'function')) Promise.allSettled = function (promises) { let mappedPromises = promises.map((p) => { return p .then((value) => { return { status: 'fulfilled', value, }; }) .catch((reason) => { return { status: 'rejected', reason, }; }); }); return Promise.all(mappedPromises); }; // https://developer.mozilla.org/en-US/docs/Web/API/queueMicrotask // implemented in Chrome 71 // https://stackoverflow.com/a/61569775 (function() { 'use strict'; // lazy get globalThis, there might be better ways const globalObj = typeof globalThis === "object" ? globalThis : typeof global === "object" ? global : typeof window === "object" ? window : typeof self === 'object' ? self : Function('return this')(); if (typeof queueMicrotask !== "function") { const checkIsCallable = (callback) => { if (typeof callback !== "function") { throw new TypeError("Failed to execute 'queueMicrotask': the callback provided as parameter 1 is not a function"); } }; if (typeof Promise === "function" && typeof Promise.resolve === "function") { globalObj.queueMicrotask = (callback) => { checkIsCallable(callback); Promise.resolve() .then(() => callback()) // call with no arguments // if any error occurs during callback execution, // throw it back to globalObj (using setTimeout to get out of Promise chain) .catch((err) => setTimeout(() => {throw err;})); }; } else if (typeof MutationObserver === "function") { globalObj.queueMicrotask = (callback) => { checkIsCallable(callback); const observer = new MutationObserver(function() { callback(); observer.disconnect(); }); const target = document.createElement('div'); observer.observe(target, {attributes: true}); target.setAttribute('data-foo', ''); }; } else if (typeof process === "object" && typeof process.nextTick === "function") { globalObj.queueMicrotask = (callback) => { checkIsCallable(callback); process.nextTick(callback); }; } else { globalObj.queueMicrotask = (callback) => { checkIsCallable(callback); setTimeout(callback, 0); } } } })(); queueMicrotask(() => console.log('microtask')); console.log('sync'); // https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replaceAll // implemented in Chrome 85 // https://vanillajstoolkit.com/polyfills/stringreplaceall/ if (!String.prototype.replaceAll) { String.prototype.replaceAll = function(str, newStr) { // If a regex pattern if (Object.prototype.toString.call(str).toLowerCase() === '[object regexp]') { return this.replace(str, newStr); } // If a string return this.replace(new RegExp(str, 'g'), newStr); }; }; // https://developer.mozilla.org/en-US/docs/Web/API/ParentNode/replaceChildren // implemented in Chrome 86 // https://github.com/XboxYan/dom-polyfill // copied from github-wc-polyfill (function() { if (Element.prototype.replaceChildren === undefined) { Element.prototype.replaceChildren = function(...nodesOrDOMStrings) { while (this.lastChild) { this.removeChild(this.lastChild) } if (nodesOrDOMStrings.length) { this.append(...nodesOrDOMStrings) } } } }()); `; var script = document.createElement('script'); script.textContent = actualCode; (document.head||document.documentElement).appendChild(script); script.remove(); As you can see, it's a patchwork of code "borrowed" from you, various polyfill authors and portions from github-wc-polyfill extension, by JustOff; I couldn't be arsed to make a proper fork and publish on GH... FWIW, I use a different (smaller) version of that file for my 360EEv12 (Chromium-78-based) copy (only the polyfills for JS code implemented in Chromium > 78.0). But I fear I'm derailing this thread...

In my 360EEv11 (Chromium-69-based) copy, to get GitHub (that I use a lot...) fully functional, I had to polyfill: globalThis (implemented in Chrome 71) Object.fromEntries (implemented in Chrome 73) Promise.any (implemented in Chrome 85) Promise.allSettled (implemented in Chrome 76) queueMicrotask (implemented in Chrome 71) String.replaceAll (implemented in Chrome 85) replaceChildren (implemented in Chrome 86) I'm using a local fork of your original extension, BTW, so many thanks! However, even those 7 polyfills won't be enough, it seems , because, over the last couple of months, those M$ employees have been trialing ECMAScript2020/2022 syntax with unsupported (by both UXP+Chromium<85) operators (Nullish coalescing, "??", and optional chaining, "?.") which can't be polyfilled; thus, GitHub becomes severely broken (to the point of unusable); at the time of this writing, they have reverted that breaking code, but it's dead certain it'll come back (since it's supported by M$'s sweet child, ChrEdge) ... NM28 is UXP-based, to get GH functional, use any of https://github.com/JustOff/github-wc-polyfill https://github.com/SeaHOH/github-wc-polyfill https://github.com/martok/palefill Those only support officially Pale Moon (but NOT v30.0), so to install in NM28 you have to modify maxVersion inside install.rdf; GH+GL break the extension constantly, so make sure you're always on the latest stable/beta build...

Much obliged ; for transparency purposes, though, perhaps you'd be kind enough to let us know of the reason(s) the original binary broke and what measures you actually took to restore intended functionality... Just sayin', thanks all the same!

360EEv12 (Chromium 78) on VistaSP2 x86: Problems Detected for Hardware GPU Hardware video decode is only supported in win7+: 159458 Disabled Features: accelerated_video_decode All Intel drivers before 8.15.10.2021 are buggy with Stage3D baseline mode: 172771 Disabled Features: flash_stage3d_baseline Accelerated video decode interferes with GPU sandbox on older Intel drivers: 180695, 298968, 436968 Disabled Features: accelerated_video_decode Disable GPU on all Windows versions prior to and including Vista: 315199 Disabled Features: flash_stage3d, gpu_compositing, gpu_rasterization, flash3d, metal, accelerated_webgl2, accelerated_2d_canvas, protected_video_decode, oop_rasterization, accelerated_video_decode, android_surface_control, accelerated_webgl, flash_stage3d_baseline GPU rasterization should only be enabled on NVIDIA and Intel and AMD RX-R2 GPUs with DX11+ or any GPU using ANGLE's GL backend.: 643850 Disabled Features: gpu_rasterization Disable use of D3D11/WebGL2 on Windows Vista and lower Disabled Features: accelerated_webgl2 Old Intel drivers cannot reliably support D3D11/WebGL2: 363721 Disabled Features: accelerated_webgl2 Protected video decoding with swap chain is for Windows and Intel only Disabled Features: protected_video_decode Intel drivers older than 2010 on Windows are possibly unreliable: 72979, 89802, 315205, 977432 Disabled Features: flash3d, flash_stage3d, accelerated_webgl, accelerated_2d_canvas Some drivers are unable to reset the D3D device in the GPU process sandbox Applied Workarounds: exit_on_context_lost Disable use of Direct3D 11 on Windows Vista and lower Applied Workarounds: disable_d3d11 Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args Old Intel drivers cannot reliably support D3D11: 363721 Applied Workarounds: disable_d3d11 On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565 Applied Workarounds: msaa_is_slow Framebuffer discarding can hurt performance on non-tilers: 570897 Applied Workarounds: disable_discard_framebuffer Direct composition flashes black initially on Win <10: 588588 Applied Workarounds: disable_direct_composition Zero copy DXGI video hangs on shutdown on Win < 8.1: 621190 Applied Workarounds: disable_dxgi_zero_copy_video Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent) Decode and Encode before generateMipmap for srgb format textures on Windows: 634519 Applied Workarounds: decode_encode_srgb_for_generatemipmap VPx decoding isn't supported well before Windows 10 creators update.: 616318, 667532 Applied Workarounds: disable_accelerated_vpx_decode Accelerated VPx decoding is hanging on some videos.: 654111 Applied Workarounds: disable_accelerated_vpx_decode Overlay sizes bigger than screen aren't accelerated on some Intel drivers: 720059 Applied Workarounds: disable_larger_than_screen_overlays Delayed copy NV12 crashes on Intel on Windows <= 8.1.: 727216 Applied Workarounds: disable_delayed_copy_nv12 Dynamic texture map crashes on Intel drivers less than version 24: 890227 Applied Workarounds: disable_nv12_dynamic_textures Raster is using a single thread. Disabled Features: multiple_raster_threads With chrome://flags/#ignore-gpu-blacklist set to Enabled (and browser restarted): and Problems Detected Some drivers are unable to reset the D3D device in the GPU process sandbox Applied Workarounds: exit_on_context_lost Disable use of Direct3D 11 on Windows Vista and lower Applied Workarounds: disable_d3d11 Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args Old Intel drivers cannot reliably support D3D11: 363721 Applied Workarounds: disable_d3d11 ANGLE crash on glReadPixels from incomplete cube map texture: 518889 Applied Workarounds: force_cube_complete On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565 Applied Workarounds: msaa_is_slow Framebuffer discarding can hurt performance on non-tilers: 570897 Applied Workarounds: disable_discard_framebuffer Direct composition flashes black initially on Win <10: 588588 Applied Workarounds: disable_direct_composition Zero copy DXGI video hangs on shutdown on Win < 8.1: 621190 Applied Workarounds: disable_dxgi_zero_copy_video Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent) Decode and Encode before generateMipmap for srgb format textures on Windows: 634519 Applied Workarounds: decode_encode_srgb_for_generatemipmap VPx decoding isn't supported well before Windows 10 creators update.: 616318, 667532 Applied Workarounds: disable_accelerated_vpx_decode Accelerated VPx decoding is hanging on some videos.: 654111 Applied Workarounds: disable_accelerated_vpx_decode Overlay sizes bigger than screen aren't accelerated on some Intel drivers: 720059 Applied Workarounds: disable_larger_than_screen_overlays Delayed copy NV12 crashes on Intel on Windows <= 8.1.: 727216 Applied Workarounds: disable_delayed_copy_nv12 Dynamic texture map crashes on Intel drivers less than version 24: 890227 Applied Workarounds: disable_nv12_dynamic_textures Raster is using a single thread. Disabled Features: multiple_raster_threads ANGLE Features disable_program_caching_for_transform_feedback (Frontend workarounds): Disabled On Qualcomm GPUs, program binaries don't contain transform feedback varyings lose_context_on_out_of_memory (Frontend workarounds): Enabled Some users rely on a lost context notification if a GL_OUT_OF_MEMORY error occurs scalarize_vec_and_mat_constructor_args (Frontend workarounds) 398694: Enabled Always rewrite vec/mat constructors to be consistent sync_framebuffer_bindings_on_tex_image (Frontend workarounds): Disabled On Windows Intel OpenGL drivers TexImage sometimes seems to interact with the Framebuffer add_dummy_texture_no_render_target (D3D workarounds) anglebug:2152: Disabled On D3D ntel drivers <4815 when rendering with no render target, two bugs lead to incorrect behavior allow_clear_for_robust_resource_init (D3D workarounds) 941620: Disabled Some drivers corrupt texture data when clearing for robust resource initialization. call_clear_twice (D3D workarounds) 655534: Disabled On some Intel drivers, using clear() may not take effect depth_stencil_blit_extra_copy (D3D workarounds) anglebug:1452: Disabled Bug in NVIDIA D3D11 Driver version <=347.88 and >368.81 triggers a TDR when using CopySubresourceRegion from a staging texture to a depth/stencil disable_b5g6r5_support (D3D workarounds): Disabled On Intel and AMD drivers, textures with the format DXGI_FORMAT_B5G6R5_UNORM have incorrect data emulate_isnan_float (D3D workarounds) 650547: Disabled On some Intel drivers, using isnan() on highp float will get wrong answer emulate_tiny_stencil_textures (D3D workarounds): Disabled On some AMD drivers, 1x1 and 2x2 mips of depth/stencil textures aren't sampled correctly expand_integer_pow_expressions (D3D workarounds): Enabled The HLSL optimizer has a bug with optimizing 'pow' in certain integer-valued expressions flush_after_ending_transform_feedback (D3D workarounds): Disabled NVIDIA drivers sometimes write out-of-order results to StreamOut buffers when transform feedback is used to repeatedly write to the same buffer positions force_atomic_value_resolution (D3D workarounds) anglebug:3246: Disabled On an NVIDIA D3D driver, the return value from RWByteAddressBuffer.InterlockedAdd does not resolve when used in the .yzw components of a RWByteAddressBuffer.Store operation get_dimensions_ignores_base_level (D3D workarounds): Disabled Some NVIDIA drivers do not take into account the base level of the texture in the results of the HLSL GetDimensions builtin mrt_perf_workaround (D3D workarounds): Enabled Some NVIDIA D3D11 drivers have a bug where they ignore null render targets pre_add_texel_fetch_offsets (D3D workarounds): Disabled On some Intel drivers, HLSL's function texture.Load returns 0 when the parameter Location is negative, even if the sum of Offset and Location is in range rewrite_unary_minus_operator (D3D workarounds): Disabled On some Intel drivers, evaluating unary minus operator on integer may get wrong answer in vertex shaders select_view_in_geometry_shader (D3D workarounds): Disabled The viewport or render target slice will be selected in the geometry shader stage for the ANGLE_multiview extension set_data_faster_than_image_upload (D3D workarounds): Disabled Set data faster than image upload skip_vs_constant_register_zero (D3D workarounds): Disabled On NVIDIA D3D driver v388.59 in specific cases the driver doesn't handle constant register zero correctly use_instanced_point_sprite_emulation (D3D workarounds): Disabled Some D3D11 renderers do not support geometry shaders for pointsprite emulation use_system_memory_for_constant_buffers (D3D workarounds) 593024: Disabled On some Intel drivers, copying from staging storage to constant buffer storage does not work zero_max_lod (D3D workarounds): Disabled D3D11 is missing an option to disable mipmaps on a mipmapped texture ... But my GPU isn't really up to the task , as I have artifacts (black rectangles) in page rendering: So, back to S/W I am...

One very important aspect of "v1.5_Rev3e" is that it contains internally "openssl-1.1.1d" (requires at least VistaSP2, ported to WinXP SP3 by @Mathwiz , IIANM, and then compiled with (XP_EoS) Py3.4 by @heinoganda), which bestows this "HTTPS Proxy" TLSv1.3 (final) capabilities (not present in openssl 1.0.2x/1.1.0x); while properly configured web servers do still offer fallback to TLSv1.2, some secure URLs are currently TLSv1.3 exclusive; so, if access to these must be realised via the IE web engine (e.g. an application dependent on system crypto libs/schannel), "Rev3e" is the way to go! ... Thanks @Dave-H for sharing

... Not quite ; JustOff is a Ukrainian national and he's now (most probably) fighting against his country's invaders (not gonna say more, as being OT to these forums)... Soon after the invasion took place, he shared maintainership of the github-wc-polyfill extension with a Chinese developer, whose GH username is SeaHOH (I don't know if I'm right but, based on my Chemistry background, I amicably refer to him as "seawater" ...) SeaHOH is a very competent master of Javascript (with a slightly worse command of the English language compared to JustOff, but, OTOH, my Mandarin is non-existent ); I've reported several bugs myself over in the GitHub issue tracker and he's been very helpful/successful at addressing them ; TL;DR: All beta and stable releases after 1.2.14b2 are the product of SeaHOH's efforts! The latest stable release, 1.2.16 , works wonders with latest Serpent v52.9.0 (2022-02-25) (32-bit); to install, visit the linked GH page, left click on the XPI link and accept the installation prompt from GitHub; else, if you want to first fetch the XPI to disk and then install, you'd have to modify manually the install.rdf file within the XPI (the maxVersion value); this has been explained repetitively inside these threads... NB: The extension requires very recent UXP browsers (New Moon/Serpent), it does nothing in Firefox ESR 52.9.x and close to nothing in recent Serpent 55.0.0 (if force-installed there). Loads and functions fine here: (latest St52+gh-wc-pf-1.2.16)

https://msfn.org/board/ What I don't know is how long that sum will keep things going for...

The following was posted today by the site's owner: After the on-going war in Ukraine, this is the second most distressing development for me, should it actually be implemented! With energy (electricity+natural gas+petrol) prices hitting all-time highs, I can understand server costs are also up, yet the very same reasons leave very little room for donations for the average MSFN member that struggles considerably as it is to cope with RL's current demands... Hard times, indeed...

Many thanks!

I think it's safe to say the PM feature is currently broken for all (it is for me, too, on latest St52); I can't even access my previously stored exchanges... @Dave-H , as an admin, could you please ask/troubleshoot this?

"Sky Broadband;" => Why/how would your ISP modify your IE UA? "BTRS111060;" => origin of this? "chromeframe/32.0.1700.107;" => as others advised, uninstall completely and restart the OS! "BRI/2" => origin of this? The rest look benign, related to Microsoft Office and installed versions of .NET Framework (1.1, 2.0, 3.0, 3.5, 4.0)

... Not to mention he's got ChromeFrame installed (reporting Chromium 32 in the UA) ...

OT: ...This isn't probably the right place to post this, but since I am/was most active in these threads, here comes my bad news: My cherished Toshiba laptop from 2009, that came with Vista OEM 32-bit originally, has died on me a little more than two hours ago... No previous signs of an impending doom, I was merely browsing (in 360EEv11) when the screen just started flickering on a frozen frame, just out of the blue, and I had to disconnect power to forcibly shut it down... After I put the power back in, the laptop simply won't start anymore, the screen remains permanently black, I can feel some disk activity by touching the laptop, but just that... Sadly, I'm completely clueless when it comes to H/W, can be anything from a dead integrated GPU, a dead CPU or something else (the HDD was in good condition, AFAIAA, replaced last in 2017... Of importance to me is 12 year-worth e-mails contained in Windows Mail, and a ton of other valuable things contained in the internal HDD (I don't have recent back-ups of...) This is me posting from sister's Win7 x64 laptop, via a portable Serpent 52 profile I carry on an external HDD... To add insult to injury, I painfully discovered that "portable" 360EE profiles do not carry with them saved cookies/account credentials for sites, unlike Mozilla browsers... Needless to say I feel very distressed now, this is still the Holidays period during an omicron exponential surge, PC repair shops are mostly closed/half-working... I'll probably have the laptop evaluated by a technician during the coming days, I don't hold high hopes for it to be brought back to life (and at what cost?), all I can hope for is that the HDD is OK and salvageable... This was just a "to let you know" post, 2022 apparently only brought havoc to me thus far... Yes, cr*p like this happens, but now that it has, I'm a total wreck inside... I wish all the best to you, despite...

... The breakage is due to JS scripts that are not palatable to the web engines that can be used on Windows XP/Vista... If, like me, you have uBlock Origin installed in your browser, just blanket-forbid all javascript on "web.archive.org" via the pop-up: and then reload the culprit WA page: Of course, WA will nag that JS is disabled, but you'll be able to load the bulk of that M$ KB content, in an easy and reproducible manner... I feel very lazy now , especially after a "full" dinner (in my timezone), but the masochist among you can determine which one (or more) of the 26 scripts uBO blocks is responsible for the breakage under "legacy" browsers... FWIW, my screengrab is from 360EEv11 (Chromium 69 based...). Best regards y'all

... This has happened to me as well, several times... The reason is the local .XPI file is being locked by the browser process after the initial, failed, installation attempt, and thus modifying it with 7-zip fails, too... Don't ask me for details , but if you first exit the browser, the local XPI file will be "released" and should be again modifiable with 7-zip, as expected... Cases for using MTT are basically two: 1. Install Jetpack SDK add-ons in Tycho-derived browsers, e.g. NM27 (these type of extensions were intentionally disabled in Tycho) 2. Install "legacy" Firefox-only extensions in official Pale Moon versions >= 29.2.0 (for which the dual-ID system was revoked); BTW, MTT doesn't install out-of-the-box in official PM (it's inside MCP's extension blocklist). AFAIK, NM28 has retained dual-ID and thus is able to still accept "legacy" Firefox-only extensions (red-dot inside the AOM). The "issue", if you will, with NM28 is that it's an "alpha" dev-channel app, as reflected in its appVersion (e.g. 28.10.4a1), so when an official-PM add-on has a <em:minVersion>28.0.0</em:minVersion> in its install.rdf file, it will still NOT install in NM28, because 28.10.4a1 < 28.0.0 ...

Right click on the install button->Save Link As... Old trick. You actually beat me to it by some minutes... Yes, this has been a long-standing practice in order to archive XPIs off of the "official" extension repo(s), but I bet some still remember a time (possibly a year ago?) when even that "trick" was intentionally disabled (by you-know-whom) via javascript; extension users had to first properly install the extension in their browser, then hunt it down (via Extension ID) in the Extensions directory of the browser profile, to be able to get their "hands" on an XPI (provided the add-on did not unpack upon installation); of course, no good a process if you're not even able to install the add-on in the first place... As you'd imagine, that change in an established behaviour caused un uproar in the official forums, nevertheless the person who implemented it remained adamant (as you'd expect )... It was when good ol' JustOff came to the rescue with WebInstall Ninja that the draconian measures imposed were able to be circumvented and users were, once again, able to store add-on XPIs without first installing them (and that was one more chapter in the "Bad History book" between JustOff and MAT...). ... At a later date, possibly after another "Add-ons Repo" overhaul, the "old" behaviour/trick was silently reinstated... The "Only in Pale Moon/Basilisk", UA-based, block was implemented a short while before the devs switched to Private code repositories...