Leaderboard

Windows 8.1 kinda need them... it's just less than a year the EOL would come... and Windows 8.1 it's not a major success and app dev could discontinued app right away..

as you see, I cherry-picked some GRE changes (without crazy file rearrangements and code removals) and new release (with revision version number bumped) will be released in this weekend.

Right now, there is probably no need for an Extended Kernel for Windows 8. Windows 8 was treated differently than Windows Vista. Software Support for Vista was mostly depended on XP‘s Software Support, as companies often ended support for them simultaneously. Most of the current software still supports Windows 8. There are just a few applications like iTunes, Office 2019+ or OneDrive, who ended their support. However, there are workarounds in how to install the latest versions, with some modifications to the installers. I think Firefox for Windows 8 will be supported for at least 2024, as Mozilla hasn‘t said anything regarding EOL yet. Furthermore, if you pay attention to details, Mozilla itself still develops Firefox on Windows 7/8 machines, as Firefox 98 release notes show a screenshot from a W7 machine running Firefox, rather than a W10 machine. All common Antivirus programs are also still supported. So, is there any need for an Extended Kernel yet?

(howto waybackmachine url parameters) soggi wrote: > When visiting https://web.archive.org/web/*/www.cmd.com on NM27/28 it looks > like on the screenshots below. I think I have to move on and make NM28 to my > daily driver, the Way Back Machine is really important to my soggi.org work Yeah, sadly it stopped working for me many years ago already (old OS), real killer prob. Until finally (!!!) discovering it can alternatively be used by typing URL parameters :-) This works even with the most ancient browsers (if no fallback available): 1) If URL is known, this gets the LAST version: https://web.archive.org/web/https://www.example.com 2) If URL is known, a CROPPED DATE (any length) gets the CLOSEST version, e.g.: https://web.archive.org/web/19990401/https://www.example.com 3) Therefore, this gets the OLDEST version at all, first one after Jan 1 1000 ;-) https://web.archive.org/web/1/https://www.example.com 4) This creates a NEW archive of the current page: https://web.archive.org/save/https://www.example.com (And if a URL is not known exactly, there are also strings to get a plain txt list, but more complicated)

Maybe, but then you still have JS out there that Babel doesn't stomach and inline scripts in HTML and so on and so on. It's a holy mess.

Maybe a fork of Decentraleyes (or something similar) could be employed to serve these modified files?

More like a Windows 7 theme. I got it right here: https://www.deviantart.com/ebhefgyxp/art/Aero-7-XP-807725030

@AstroSkipper Your contribution is excellent. However, I still have one request for you. I would like to ask you to mention me in step 4,5,6,7 and in step 8, as it was a hard work for me to figure out especially the 4 updates. You can check here: And here: And that was my first post:

I get similar Javascript Console errors in 360EEv11 (chr69-based): Uncaught SyntaxError: Unexpected token . in https://www.rb.cz/scripts/main.9082edf4740251c6.js And this is by simply loading the page; clicking the blue button produces an additional (CSS?) error: problem calling custom script: ReferenceError: $ is not defined at HTMLDocument.<anonymous> ((index):14) Their "main" script uses no less than 110 (!) invocations of the optional chaining operator (?.), an ECMAScript2020 feature (first implemented in Chromium 80/Firefox 74)... The master villain is, again, a Bank URI; perhaps they "feel" using the latest and greatest JS "goodies" makes them look "more safe" in the eyes of their otherwise "clueless" clients ; I'm of the opinion the @NotHereToPlayGames route should be pursued here, too...

Yep. But so far it's mainly been on web sites I kinda don't care about anyway. With only ONE exception - my local water bill payment, which I can't "replace" with another website offering "similar" content so I'm stuck with v13 for it, fingers crossed that it can eventually be polyfilled.

so new javascript syntax again: 22:27:38.490 SyntaxError: expected expression, got '.' 1 https://www.rb.cz/attachments/applications/scripts/apps/cookie-wall.js:9:20992 22:27:40.325 SyntaxError: expected expression, got '.' 1 https://www.rb.cz/scripts/main.9082edf4740251c6.js:1:21569

You beat me to it - nothing happens in my default 360v11 - nor serpent 52. Starting to look like we have have to start using v13 and that struggles on my systems.

Same here. Nothing happens in 360Chrome v11 even with @InterLinked's polyfill from https://github.com/InterLinked1/chromefill

This is a bit off-topic but where did you get this Windows Vista theme? Btw. It looks really nice.

The Explorer shell is the thing everyone has a problem with. Alternate shells would solve the issues.

Doesn't work with: Chrome 49, FF 52.9, Mypal 28.17.0, 360Chrome v12. Works with 360Chrome v13.

Wow! I feel "fortunate" that I was traveling and only trial-ran (what I will call) POS PM 30 from a hotel room on an experimental labtop with an experimental VM, both of which have already been deleted. Hint - POS does NOT stand for "point of sale" !

I had my suspicions; after all, it's intended to test whether or not a feature is implemented; it isn't an exhaustive test of whether a feature is implemented correctly. It's all I had to go on, though. So, St 52's implementation of Custom Elements is still incomplete. It's probably the best we have until Moonchild puts some effort into it, though. As for Shadow DOM, html5test.com claims St 52 has partial support, and that St 55 has full support. We'd probably need to scour Bugzilla for relevant code (and might, perhaps, find more relevant usable code in FF 54 and 55. I doubt anything later could be merged into either Serpent version though). BTW, it turns out that setting dom.webcomponents.enabled breaks Chase.com in St 52 too, although it's not as badly broken as in St 55. Apparently the site is designed to work correctly if someone disables Web Components, but otherwise it expects a complete implementation. So my advice now is to leave the pref off in both browsers. If anyone discovers a specific Web site that only works with the setting enabled, make a copy of your main profile, and just toggle that pref on in the copy, so you can use that profile for the site that requires it. (Let the rest of us know what you find too.)

Sorted. Thanks Dave.

@roytam1 Moonchild has withdrawn the PM 30 branch (both releases v30.0.0 & 30.0.1) and now (only) offers, again, PM v29.4.4, while a "security-only" release v29.4.5 is in the works... The PM 30 milestone will be re-engineered, with a strong probability of the dual GUID system - as was in v29.1.1 - coming back, and a fresh v30.1.0 will (after v29.4.5) be released in "due course"... So, perhaps, it'd be prudent not to hasten merging "current" GRE into "our" UXP tree (as suggested by https://github.com/roytam1/UXP/commits/custom ) ; what are your plans? Many thanks!

I have a surprise for you : It works too with Firewall ON and with wuauclt.exe added as exception! I love you my man, you are the best! Thank you!

A small update: When I turned off Windows Firewall, Windows Update worked for me! Installation of updates is working as well!

Did you install a security program like Eset, Malwarebytes or Avast? These programs have a lot of features, one of them is a HTTPS Scanning feature and can be problematic if connected via HTTPS.

Yes, exactly. It is correctly activated. So we can rule that out as a source of error.

That is correct. I asked him to deactivate the proxy so that I can see if Tls 1.2 is correctly activated.

I wonder how long will ExplorerPatcher manage to keep some glimpse of sanity in this OS. Between out-of-the-box Win11 shell and original Win95 shell, I'd take Win95 shell, even if it's a bit simple for today's standards.

Sadly , that "format" of yours no longer produces the "calendar for a specific year" in Tycho-based New Moon 27, so users of that (e.g soggi) and even-older-engine browsers can't profit from it... Works OK, though, for UXP-based browsers ...

Firefox Quantum 63.0, to be exact (less finished implementations were behind a disabled pref in immediately previous Fx versions) ... I, personally, don't give that test the credence/importance others do... Have often found it to misrepresent browser features (especially when it comes to the non-mainstream browser engines), so my advice is to take its reported results "cum grano salis"... According to this UXP open issue, https://repo.palemoon.org/mcp-graveyard/UXP/issues/1361 Shadow DOM v1 is still marked as unfinished (further below in the issue, they cite Element.attachShadow() Element.shadowRoot() DocumentOrShadowRoot.activeElement as having been implemented...) Relevant GRE issue https://repo.palemoon.org/MoonchildProductions/GRE/issues/3009 signals Shadow DOM support is still not "FULL" and, of course, WebComponents support (of which both ShadowDOM+CustomElements are integral parts) is still marked as unimplemented... https://repo.palemoon.org/MoonchildProductions/GRE/issues/3011

A guide to install Microsoft Update manually Here is a complete guide to install Microsoft Update in Xp: First you need to download these files: http://download.windowsupdate.com/v9/microsoftupdate/a/selfupdate/WSUS3/x86/Other/mucltui.cab http://download.windowsupdate.com/v9/microsoftupdate/a/selfupdate/WSUS3/x86/Other/mucltui_en.cab http://download.windowsupdate.com/v9/microsoftupdate/a/selfupdate/WSUS3/x86/Other/muweb.cab Replace at mucltui_en.cab with your language. For example: mucltui_de.cab for German. Open the archives. Copy muweb.dll from the archive muweb.cab to system32. Copy mucltui.dll from the archive mucltui.cab to system32. Copy mucltui.dll.mui_? from the archive mucltui_? to system32. Register only the 2 files muweb.dll and mucltui.dll with regsvr32. Configure IE: Add the pages http://update.microsoft.com http://www.update.microsoft.com and https://www.update.microsoft.com to the Trusted Sites and set the security level to high. If it is not available, click Reset first. Call up this page now and follow the instructions: http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en If the Check for Updates button doesn´t work, close IE and click on Microsoft Update in the start menu. Don´t forget! You need httpsproxy or ProxhttpsProxy otherwise you will get error 0x80072EFF! Only tested under XP! Have fun trying.