Leaderboard

They fixed it in their code tree before you posted about it here. I don't know about that notification thingie causing high CPU usage, either it doesn't happen here (Pale Moon beta) or I'm missing something. https://support.microsoft.com/...No idea, but since I don't like messing with these things unless it's the last resort, I just added the rule to my Proxomitron to rewrite links to CSS in supported fashion... Name = "Microsoft Support - no stylesheet preload" Active = TRUE URL = "support.microsoft.com/ $TYPE(htm)" Limit = 256 Match = "<link rel="preload" as="style" onload="this.rel=\'stylesheet\'" \0>" Replace = "<link rel="stylesheet" \0>" Just did it the way I know it can be done... Palefill as provided on martok's GitHub page will indeed still impact GitHub in a significant way even when Web Components are provided by the browser because some checks aren't there so some stuff still gets injected unconditionally, but even when certain injected code has checks to not do anything if not necessary, I suppose its code must still be parsed by the browser. I use modified version that more thoroughly checks browser features and prevents processing rules that polyfill functions that already exist in the browser. But if one must toggle web components between on and off, changes take effect after disabling/enabling extension in the new browser window, which you must open beforehand, or restart the browser. palefill-1.25.4.xpi

Notice: ( especially @adata and others ) Please don't report bug(s) of my browsers using forum's Message function (to me) unless you're providing login credentials for reproducing the bug, or your report(s) will be ignored.

Note - there is a known issue if you run this browser with a very long sub-folder file name. Please rename the downloaded file upon download, the names here are only to distinguish their differences. This thread is devoted primarily to WinXP and a Chromium fork based on Chromium v86. Any discussions regarding v86 and its "age" will be reported to the mods as "disrespect" and in direct violation of Forum Rule 7.b. 7.b This community is built upon mutual respect. You are not allowed to flame other members. People who do not respect personal opinions and/or personal work will be warned in first instance. If you ignore the warning and keep on flaming, you will be banned without notice. This project is my personal work that I share with MSFN because there is a need for a "relatively modern" web browser for use in WinXP and v86 has performed "reasonably well" in that regard. The user-base is perfectly aware that XP will not serve 100% of our needs, that v86 will not serve 100% of our needs, we know this and accept this, we are not here to be told to "move on" from XP and what works for us in XP. We The Community can respect this endeavor in the same manner that we respect content shared at MSFN threads devoted to Win98 and Win2000 without trolling such threads and citing "age". Many thanks to all that continue to support this personal work. There is a combination of several versions to choose from. Regular versus Ungoogled -- ungoogled intentionally breaks telemetry sent to the Chrome Web Store, this in turn breaks the "Add to Chrome" feature at the Chrome Web Store so extensions need added via other means. WebGL enabled/disabled -- WebGL may or may not work on older hardware, so mileage may vary. Translation enabled/disabled -- Chromium-based browsers have an embedded Google Translate context menu feature, I offer versions with and without this embedded feature. WinXP / Win10 skin -- I only use this browser in WinXP and therefore I prefer it to look-and-feel like everything else I run in WinXP. Others prefer the more "modern" Chrome GUI and the Win10 skin attempts to please that crowd. https://www.dropbox.com/s/wsch5owpc8yv184/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/fl9ureunhg2k2x7/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/whki7vldp655nx1/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/59561mewhx0ufzb/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/l3e5m48tzzb30bj/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/npnxobadg89m7uj/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/ithrm1ttt2nypb1/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/f2935ei6q5d0w3u/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/i9t2rul2t5g99ml/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/wqm2tzaum2088ph/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/wqzujgi97cyuf7u/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/tbt5g1pv9nazfo4/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/g4g0jdgogoexa3p/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/bcsexi8cm5tw2np/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/yz8usl2hgsbxtk0/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/pi43092cazygjz6/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-enabled_win-xp-skin.zip?dl=1

Hi all! I'm Frances Walsh from the city of Austin. I am a girl who loves working with computers and technology, so I joined this community. I am here to share my knowledge and learn something new from other members. I'm hoping for interesting people and introductions with an individual passion for technology. I would be happy if anyone would like to chat with me or share their experiences !

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230318-3219d2d-uxp-85f6a4929-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230318-3219d2d-uxp-85f6a4929-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-20230318-3219d2d-uxp-85f6a4929-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-20230318-d849524bd-uxp-85f6a4929-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230318-d849524bd-uxp-85f6a4929-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230318-d849524bd-uxp-85f6a4929-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230318-d849524bd-uxp-85f6a4929-xpmod.7z Official UXP changes picked since my last build: - Issue #2135 - Follow-up: Check for aElement not being null (2249fbdf4) - Issue #2137 - Part 1: Modify :not() selector to accept a complex selector list (82fa9fb80) - Issue #2137 - Part 2: Implement SelectorParsingFlags and use it to pass info around (3bb3c193d) - Issue #2137 - Part 3: Don't always use the internal pseudo-class for handling negations (b257a71cc) - Issue #2137 - Part 4: Fix namespace regression (ef36c5659) - Issue #2135 - Destroy the host frame and restyle when there are content changes (18e693464) - Issue #2078 - Follow-up: Ensure empty selector lists aren't iterated when serialized (2be0261d5) - Issue #2046 - Follow-up: Fix deprot in RelativeTimeFormat. (77b618055) - Issue #80 - Fix deprot in js/ipc. (261dc37ad) - Issue #80 - Fix deprot in js/xpconnect. (0b039ff7a) - Issue #80 - Move implementation of CPOWTimer::CPOWTimer to header. (c2c95eff9) - No issue - Make content-type on JAR channels behave the same as HTTP channels (091a2aab8) - Issue #2046 - Follow-up: Fix deprot in builtin/intl (a2d6260cd) - Issue #2160 - Initial support for notarizing during DMG package. Added --with-macbundle-idenity configure option to set a codesign identity. If no identity is set or cross-compiling from Linux no codesigning will be done. Currently doing a full deep bundle v2 sign, instead of limited v1. (3d2a4f406) - Issue #2148 - Don't null out RegExpObject -> RegExpShared pointer on GC. (ad8d9639a) - Issue #2148 - Discard RegExpShared data tables when discarding regexp JIT code. (cdd91edd7) - Issue #2148 - Make Vector not use AlignedStorage for its inline element storage (0365f940f) - Issue #2148 - Shrink Vector from (usually) four pointers in size to three when no inline storage is used. (481069044) No official Pale-Moon changes picked since my last build. Official Basilisk changes picked since my last build: - [Basilisk] Add useragent override for instagram port of MoonchildProductions/Pale-Moon commit d641959f15cb1172f6f39130b579ccf6111a6f2f and 6d41a6139440a9c396308deca1725b0db823e127 (76cd3dfac) - [Basilisk] Port Pale Moon version of Tab fading Backport of roytam1/UXP commit https://github.com/roytam1/UXP/commit/2a32b18f465a8d068d1b1866d027374b4706cd5a.patch (4abf53728) - [Basilisk] add tab caption fading to CtrlTab backport of roytam1/UXP commit add tab caption fading to CtrlTab (78bb7159e) My changes since my last build: - Reverting rev b7e45308 and 9824659d again as I can still get a crash in `RegExpShared::finalize(FreeOp* fop)` (bb547a1b5) - Revert "Reverting rev b7e45308 and 9824659d again as I can still get a crash in `RegExpShared::finalize(FreeOp* fop)`" (0bfc6e378) Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * 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.

Sad to see that it isn't up anymore. I actually used some good info from there when I started searching these browsers. Forgive my ignorance but, what does OP mean? Cheers. EDIT: I think it is Original Post after thinking for a bit.

Any drivers designed for Windows 7 or higher can be backported to Vista using NTOSKRNL Emu_Extender. For the user-mode components, use Extended Kernel version spoofing.

Thanks for the list. With software of that kind, combined with an older OS, and particular use cases, versions matter a lot. As for HqMame. I noticed some other versions gave stuttering audio on a Sandy bridge laptop. And from 2012 to 2016 executable size grew from 60MB to a whopping 120 MB.

Edge browser download page: https://www.microsoft.com/en-us/edge/download?form=MA13FJ do not work in Serpent 52

Nice findings! I recall 0.147 was (and is) quite a good version. Just about all the essential stuff was supported by then, with great accuracy and performance. I don't want to go too far off-track here, but to quickly sum it up, a few important versions of MAME for anyone who wants to tinker: -0.37b15 and 0.37b16 (the first releases with DirectDraw bilinear filtering and hardware stretching, last of the 0.37bX line) -0.57 (the first release with fixed protection for WWF WrestleMania and the first to include Revolution X, good for Midway fans) -0.61 (the last release tested on consumer-grade hardware of the time [2002] where it was confirmed that every game ran at full speed at maxed-out settings. Starting with 0.62 you now needed a processor far, FAR beyond anything on the market at the time to run all games at full speed) (I have a personal 'eight years' theory that starting with 0.62, you need a PC roughly 8 years newer than the MAME release itself to be able to run all games at full speed. So if your PC was manufactured in 2010, you're good to go with 0.62; if mfgd in 2014, you can run all games in MAME 0.106 [2006] at full speed.) -0.67 was the last release where the original coordinator (Nicola Salmoria) was still overseeing the project; starting with 0.68 those responsibilities shifted to a young David "Haze" Haywood. This is very important because under Haze's 'regime' there were various changes made that sent MAME on the course it's on today, including the removal of a lot of hacks that made it possible for most games to run well on modest hardware. This is a great version to use if you're on an older PC, such as a PIII or an early P4. Other notable versions, summed up a bit more succinctly: -0.69 (easy to find ROMs for, has some bugs from 0.68 fixed and runs well on 'trash picked' PCs) -0.72 (last release with DCS Sound System hacks that allowed 90s Midway games to run at full speed on weaker hardware) -0.78 (easy to find ROMS for, support was added for a few more cool games, some emulation improvements made with others) -0.84 (easy to find ROMs for, has more games supported and a few more emulation improvements, still runs well on older PCs) -0.92 (last version before the sound engine was rewritten) -0.106 (a very famous version that is still often referenced, and the last true 'classic' MAME before the video engine was rewritten) -0.139 (easy to find ROMs for; this was also one of the last versions before the MAME devs began adding mechanical games) -0.160 (easy to find ROMs for; by this point Raiden II/DX were now working, and other games had some emulation issues resolved; notably this is also the first version with OpenGL support, which improves performance for certain games) If I had to recommend one MAME version, JUST one, to stick with and not change, it would be a toss up between 0.106 and 0.160 (yes, swapping two numbers). 0.106 is a reliable old version that will run on pretty much anything you find laying out in the street, but you need a PC made in the last decade or so to be able to play all of the games at full speed. By comparison 0.160 needs far beefier hardware to run well, but all of the simple 68K and Z80 stuff should run fine on it, and by that point a lot of the loose ends had been sorted out for the games that matter. I honestly don't think anything of true significance has been added since 0.160. (However, a lot of emulation improvements have been made for games that 0.160 supports, so that balances things out a bit.) It's not to diss the hard work of the devs because I am impressed with how far MAME has come. But it's also a long ways removed from the lightweight, intuitive, fast emulator it used to be. It puts me in a quandary because on the one hand I do like to have a certain level of accuracy, but if you go too far in that direction you sacrifice speed. 0.106 & 0.160 are good balances in that sense. And that concludes my off-topic MAME 'rant'...I'll try to keep it on-topic from here on out.

Six months ago I was curious about some old arcade games. Which, as usual, got me tinkering with software without playing much I found it preferable to use the HqMAME fork, because it can smoothen the pixelation out nicely, and it does it internally to the sprites or layers for better effect. This one: HqMAME v2.2 based on MAME v0.147u3, dated 11-12-2012. Modded with HqMAME v2.16 scaler dlls, which seem to work fine. On Windows XP SP3 x86 that is.

We should not forget that there is a further tool for updating Root Certificates in Windows XP. The creator was @Thomas S.. The tool is called CAupdater. Here is the link to its original post: It is also embedded in his HTTPSProxy package. In his original post, the download link of CAupdater as a single archive doesn't work anymore. BTW, both versions of my self-created Root Certificate and Revoked Certificate Updater are meant to be used in case no internet connection is available. Generally, @heinoganda's Certificate Updater 1.6 or @Thomas S.'s CAupdater is completely sufficient. All facts about Root Certificates can be read in the section 5.2 of my article "ProxHTTPSProxy and HTTPSProxy in Windows XP for future use". Greetings, AstroSkipper

True, but not in the sense discussed here; in 360EEv11, navigate to "chrome://settings/advanced", then scroll further down to "HTTPS/SSL": If you press the top first button (Manage certificates...), you are presented with an OS window: a clear indication it's using the OS cert store... Now, if you click the third bottom button (with Chinese characters), you do get access to its built-in cert store, but that is only meant to be used within China, for mainly Chinese sites: What's more, the user has no edit access whatsoever to that cert store, i.e. expired certs can't be deleted, nor new ones be imported... FYI, all variants of 360EE (v11/12/13/13/5) have the same cert stores structure (access to the MS cert store + QiHoo provided one); more info about the QiHoo/360 cert store can be found at below link: https://caprogram.360.cn/#plan (in the header, select "English") Regards.

My primary browsers in Windows XP are New Moon 28 and Serpent 52/55. I use 360Chrome 13.5 only for testing purpose in my Windows XP installation. It is great to have alternatives but I prefer UXP browsers under Windows XP. I am also an Android user, and there you have a pure Chrome/Chromium world offering the most recent browsers. Or I use Windows 7/10 to surf the internet with the more/most recent Chromium browsers. But no need to do that in my beloved Windows XP system, and 360Chrome 13.5 is not recent anymore, either. When starting my Windows XP system, I dive into another world and enjoy the recreation of all this Chrome/Chromium stuff. All Chromium browsers are extremely restricted, especially in terms of extensions, custom buttons, customizations and modifications. That's one of the reasons I love and prefer my UXP browsers New Moon and Serpent. And to have them at all, I am very thankful to our creator @roytam1! Welcome back and of course, a good decision! Cheers, AstroSkipper

... For starters, you shouldn't do that (when testing), as palefill conflicts/interferes with native WC: https://forum.palemoon.org/viewtopic.php?p=237202#p237202 From Moonchild himself: Second, I have always been talking about Serpent 52 (actually, its previous version of 2023-03-02); but just to humour you and be on the same ground as you, I did launch a quasi-fresh profile of latest NM28 [v28.10.6a1 (32-bit) (2023-03-10)], where I installed and enabled palefill-v1.26 and then restarted it, for good measure... My GitHub testing repo this time is https://github.com/violentmonkey/violentmonkey/commits/master At first load, the relative timestamps do appear (in the "hours" range) - this is now with both palefill+native WC enabled, as you suggested; now try and continuously soft reload that page (by clicking the "reload current page" toolbar button); soon enough you'll get (I did, on my 5th attempt ) the missing timestamps bug: If, like me, you spend hours inside GitHub, then you "can't miss it"; this bug exists, as I've tried in fresh profiles (mainly St52, but lately NM28, too) and combinations of: a) native WC+SR enabled, palefill disabled (recommended by Moonchild) b) native WC+SR enabled, palefill enabled c) either of the two above, being c1) logged-in to GH or c2) logged out from GH The only combination (for me) where the relative GH timestamps remain permanently fixed is d) native WC+SR disabled, palefill enabled FWIW, with the above combination, the (latest) NM28 with fresh profile used to generate above screengrab consumes virtually 0 CPU when being minimised here: Conclusion: Everyone's setup may behave slightly differently, in a stochastic fashion , and this makes troubleshooting and fixing bugs quite a daunting task on the part of the devs ... Best regards.

No, nothing new at the moment.

The Office Update website should be released, but there are still bugs.