Leaderboard

These browsers also run on my main OS Windows 2003, and I use them under Windows 7 too for convenience, familiar interface, included video decoder, removed anti-features, and various small fixes. Everytime I posted on the XP forum because that is where most people were, I expected to be kicked out for off-topic because I don't have WinXP anymore. Recently YouTube changed something, which doesn't allow to go directly to Subscriptions from New Moon 28. A white page appears, and I must click the sidebar. Serpent still goes to Subscriptions, with a longer delay.

got some time to build it, and the missing of Services.telemetry breaks everything: 15:17:46.896 1637219866894 addons.xpi ERROR startup failed: [Exception... "Component returned failure code: 0x80570018 (NS_ERROR_XPC_BAD_IID) [nsIJSCID.getService]" nsresult: "0x80570018 (NS_ERROR_XPC_BAD_IID)" location: "JS frame :: resource://gre/modules/XPCOMUtils.jsm :: XPCU_serviceLambda :: line 230" data: no] Stack trace: XPCU_serviceLambda()@resource://gre/modules/XPCOMUtils.jsm:230 < get()@resource://gre/modules/XPCOMUtils.jsm:198 < checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:3713 < startup()@resource://gre/modules/addons/XPIProvider.jsm:2773 < callProvider()@resource://gre/modules/AddonManager.jsm:234 < _startProvider()@resource://gre/modules/AddonManager.jsm:787 < startup()@resource://gre/modules/AddonManager.jsm:968 < startup()@resource://gre/modules/AddonManager.jsm:3025 < observe()@resource://gre/components/addonManager.js:65 1 Log.jsm:753 App_append resource://gre/modules/Log.jsm:753:9 log resource://gre/modules/Log.jsm:389:7 error resource://gre/modules/Log.jsm:397:5 startup resource://gre/modules/addons/XPIProvider.jsm:2896:7 callProvider resource://gre/modules/AddonManager.jsm:234:12 _startProvider resource://gre/modules/AddonManager.jsm:787:5 startup resource://gre/modules/AddonManager.jsm:968:9 startup resource://gre/modules/AddonManager.jsm:3025:5 observe resource://gre/components/addonManager.js:65:9 15:17:47.001 TypeError: Services.telemetry is undefined 1 resource://gre/components/SanityTest.js:69:7 15:17:47.602 TypeError: telemetry is undefined 1 resource://gre/components/nsBlocklistService.js:701:5 15:17:57.151 A promise chain failed to handle a rejection. Did you forget to '.catch', or did you forget to 'return'? See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise Date: Thu Nov 18 2021 15:17:47 GMT+0800 Full Message: TypeError: Services.telemetry is undefined Full Stack: _updateTelemetry@resource://gre/modules/osfile/osfile_async_front.jsm:459:9 post/<@resource://gre/modules/osfile/osfile_async_front.jsm:438:11 TaskImpl_run@resource://gre/modules/Task.jsm:318:42 process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:931:23 walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812:7 scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:746:11 1 resource://gre/modules/osfile/osfile_async_front.jsm:459 15:19:24.963 TypeError: Services.telemetry is undefined 1 resource://gre/modules/PlacesDBUtils.jsm:56:9 15:20:04.063 TypeError: Services.telemetry is undefined 1 resource://global/content/viewSourceUtils.js:93:5 15:20:06.101 TypeError: Services.telemetry is undefined 1 resource://gre/modules/PageThumbs.jsm:223:7 captureToCanvas/< resource://gre/modules/PageThumbs.jsm:223:7 _captureToCanvas resource://gre/modules/PageThumbs.jsm:297:7 captureToCanvas resource://gre/modules/PageThumbs.jsm:222:5 capture/< chrome://browser/content/browser-ctrlTab.js:59:9 shouldStoreThumbnail resource://gre/modules/PageThumbs.jsm:266:7 capture chrome://browser/content/browser-ctrlTab.js:49:5 handleEvent/< chrome://browser/content/browser-ctrlTab.js:86:15

not surprised as 20211113 removed a big chunk of code, just a bit surprised that they didn't ever try to run compiled binaries before releasing.

they pushed something they don't want to be published, like first post-git source release. platform code of basilisk-2021.11.13-source.tar.xz is the same as pm29.4.2 while basilisk-2021.11.14-source.tar.xz's one uses same base as pm29.4.2.1. basilisk-2021.11.13-source.tar.xz removed telemetry, safe browsing, tracking protection (do not track, and more), and some building system code changes. see https://github.com/roytam1/palemoon-source-tracking/commits/tracking for details. while basilisk-2021.11.14-source.tar.xz only has some bugfix ported from pm29.4.2.1 and forced bundle emoji font and thats all, I can even just cherry-picking from tracking branch to complete this mini branch in https://github.com/roytam1/palemoon-source-tracking/commits/basilisk-20211114.

There isn't much to say , I have to use 32-bit Vista on the damn Haswell . Luckily , I have another platforms to run 64-bit versions. Nothing fixed and it won't be . And even if it will , I'm gonna dump the haswell very soon anyways. A slight off-top , @win32 wrote something about Kaby Lake : "In a series of reboots, all services started and there were no issues with application execution." Kaby Lake (which I now have at my disposal) is not Haswell , of course ! But he didn't tell which update exactly . Win32 , could you join us here and name this update for kabylake , I'll test and write back here, thanks. https://msfn.org/board/topic/183035-will-windows-vista-work-on-amd-ryzen-3-3250u/?do=findComment&comment=1206474

This thread has been branched off from the Extended Kernel thread as to not bog that one down. For discussion about the Extended Kernel, go here: Anyways, it is widely known that installing Windows Vista on Intel Haswell and later causes bugs to appear. These can range from many things such as "The Interactive logon process has failed" error message after the startup orb is shown to several services not starting and requiring a restart, sometimes several, in order to get them working (there is no way to start these manually from within Windows). Also, several other errors may occur within Windows itself. These include User Account Controls not showing up and instead throwing an error (redoing what prompted the UAC will get it to pop up normally) to many other errors. If one takes a look at 6003.20489.vistasp2_ldr_escrow.190320-1700, it will show that the problems that plague Haswell and later are fixed by way of new HAL driver, however, this is only partially true. While I did get less errors in relation to the Haswell+ issues, I still got errors such as the aforementioned user account controls error. So, if we want a chance at even getting these issues fixed once and for all, it will probably be worth it to investigate the HAL.dll as BetaWiki claims a new version of this fixed the issues. Even if we get the issues fixed (which should definitely happen down the road), there is still the issue of getting most drivers (most of which are 7+) working, although after getting Realtek Ethernet working, I ran Driver Booster and it found a fair chunk of driver, including SATA drivers, shockingly. Intel graphics obviously do not work, although you "might" be able to work the XP Haswell drivers.

That was it! Thanks!

It's actually a fun hobby so it doesn't really bother me how long it takes. To be honest, my XP Theme took some time also but I had more of a vested interest in it and it was something I took on as a side project long before deciding to upload rebuilds. The whole rebuilds project has admittedly been a bit of an eye-opener. I *need* 360Chrome - NOTHING else compares as far as a "one-stop shop" for browsing from XP. An eye-opener as to just how "dead" this "dying breed" really is. Holding out 'til the very end -- Long Live XP.

@Tomcat76: Have you tried to update CTR v1.6.9.1 to the Basilisk-specific version 1.7.8.2019.10.27 ? https://github.com/Aris-t2/ClassicThemeRestorer/releases/tag/1.7.8.2019 I'm not seeing the AOM breakage you report (still on St52 2021-10-08 here); it probably has to do with an extension/setting of yours that affects the AOM; does it happen on a fresh St52 profile, after installing a test extension? if not, the culprit exists within your current, dirty, profile... Sadly, I have to leave now for a few hours, thus not able to offer anything more substantial as help...

Not to poke the bear, but how is that any different from any other browser discussed herein? When did consumers become satisfied with labeling any "weekly" as 'stable' but reserve the 'beta' label for "nightly"? Why should any of us have to update our browser "weekly"? We don't gain anything by "weekly" updates outside of establishing some sort of "habit". We are creatures of habit, but when did the consumer become satisfied with "It's Saturday, time to update my browser" ???

... Nah, not surprised myself... ; the Pale Moon unstable channel was terminated last September (in fairness, not many were using it ) and official Basilisk is in a perpetual BETA status; so, the end recipient is expected to be the guinea pig... Plus, I think MCP's judgement has been impacted lately, namely with their semi-psychotic perception of enemies everywhere, and dealing with this "threat" is what consumes most of their energy currently (e.g. alienating former co-devs, moving to private repos, DMCA-ing fork repos, etc.) ... I recollect saying in these threads that MCP were "good" at removing existing (inherited) code - like WinXP/WinVista/Android/MacOS/EME/WebRTC/WebExtension/Container/Firefox legacy extension/FUEL/marqee support (and probably other things I forget about), but not that good at writing original new code to tackle the demands of the Chromium-dominated web... This latest blunder negates the first part of my assessment... But, I guess, I shouldn't be that harsh; everyones's entitled to a "bad day"/"happens in the best of families"/etc.

I still have more work to do on it but here is a preview. Still to do -- Correct Settings left column tab icon positions and selected tab color (corrected below only via Developer Tools) Several default dark theme text files are not shared with global en-us locales file - isolate which ones and move to global en-us locales file or translate direclty within dark-theme skin file Remove Mute Audio and Tab Foreground/Background icons from Status Bar (these never did work and will be removed from standard XP theme also) Correct default red text for certificate errors - default green on gray for valid certs is legible but default red on gray for invalid certs is not Correct sub-setting backgrounds for nested setting panels - do not like a dark gray background turning into bright gray when that panel becomes secondary Incognito tab needs changed to dark but not in a way that effects non-dark themes Change white buttons for items such as "Manage exceptions" ... I'm sure there is more but those are what comes to mind offhand

could we use the hall dll present here? or at least compare the one in build 6519 and build 6003 and edit the 6003 one in order to try to fix this?

I believe I wrote about 6519, the first build of 7 x64 to have leaked in terms of a complete fix. There was a partial fix for Vista in that time (some of the timer discrepancies were fixed but not all). I am not sure which update introduced it, as the Server 2008 updates became cumulative rollups in the fall of 2018 and now that Kaby Lake laptop is in very poor shape.

... All I can tell you is that 2021.11.13 was BAD, https://forum.palemoon.org/viewtopic.php?f=61&t=27581 https://forum.palemoon.org/viewtopic.php?p=221571#p221571 thus, 2021.11.14 had to be rush-released... BTW, I never cease to admire you for your unwavering dedication to us all...

Official Basilisk 52.9.2021.11.14 has been released, a day after a botched 52.9.2021.11.13 release... ; platform-wise, I expect it to be on par with Pale Moon 29.4.2.1, but is there something application-specific we could port over to Serpent 52.9.0? http://archive.palemoon.org/source/basilisk-2021.11.13-source.tar.xz https://fossies.org/diffs/basilisk/2021.09.27_vs_2021.11.13/ http://archive.palemoon.org/source/basilisk-2021.11.14-source.tar.xz https://fossies.org/diffs/basilisk/2021.11.13_vs_2021.11.14/ @roytam1, what do you think?

Wrong , you just don't know how to do it properly , you need to inject it , not to use extensions and the such . Also , you need to block the platform tag in the browser itself . Do not disinform people . I remember our lengthy discussion in another topic where you couldn't cheat HTML5 test website, but I could and provided with the proof. Aren't you gonna say something about Firefox ?

Wow, i never knew how destructive is Moonchild and Tobin, they really destroying everything around them. Fascinating self-destruction. Autism really sucks.

I'm starting to feel MSFN is getting heavier and heavier , esp. when I type in the reply window. Is it only me ?

I submit that some will disagree with "change" for no other reason than it is "change". I googled (had to Google that out of curiosity, the "past tense verb" is not supposed to be capitalized) for XP Browser and MSFN.org shows up on Page 1 of the results. I googled for Vista Browser and MSFN.org shows up on Page 2 of the results. These will promote higher on the results pages because of how Google's algorithm works. The more ACTIVE these threads become the HIGHER they rank in ANY search engine list of results, not just Google, at least that's how I understand search engine algorithms. The web browsers discussed here are not really limited to XP. There is a large number of active users in the XP threads that don't even run XP.

Well win32 said August 27, 2020 back on page 2 that he was “working on a Haswell+-specific issue, which is completely unrelated to the Ryzen problems.” I may have “overreacted” a bit to your post, but I awoke in a generous mood.

People often tend to think that "newer" is "safer" or more "secure" - not always true, if I may be so bold. These are the folks that will run an anti-virus program and set it to update "definitions" every 30 minutes because they think their "identity" will be stolen at Minute #29 if they do not update those "definitions". Most of us that use 360Chrome are very secure-minded folks and have other security measures in place. In fact, most of us that use 360Chrome are running Operating Systems no longer deemed "secure" (doesn't stop us!). I'm not simply referring to us "die-hards" that refuse to let XP be buried, I'm also referring to Vista and Windows 7. XP, Vista, and 7 are all "dead" Operating Systems. But we have our reasons for continuing to use them. Most of us that use 360Chrome don't even use the v13 branch. Most of us prefer the v11 or v12 branch over the v13 branch (myself included, I prefer the v12 branch for my primary computers and use v11 exclusively in all VMs and secondary computers). Make no mistake, some "theorist" can always come along and find some "vulnerability" that exists in v11 that was fixed in v12, we don't care, we have other security measures in place. Some "theorist" can always come along and find some "vulnerability" that THEORETICALLY exists in v12 that was fixed in v13, we don't care, THEORETICAL and IN-THE-REAL-WORLD are two different things. And we have other security measures in place. Most of us that use 360Chrome, XP, Vista, and 7 are very much into efficiency - we want a web browser that can run effectively on a machine with 1GB of RAM. Sure, 360Chrome is pushing the limits at that - but again, that's why most of us use v11 or v12 instead of v13. Not trying to sound too blunt when I say this, but people that are truly concerned with "critical vulnerabilities" don't run XP, Vista, or 7 - they "bought in" long ago to the HYPE that the only way to be "secure" is to run the most recent OS. I "care" about "security", don't get me wrong. But lightweight and efficient will trump "security" every day in my little corner of the universe. It can also be said that "hackers" simply don't write viruses targeting 25 million computers running XP when they can target 1.3 billion running Windows 10 instead. But I digress...