Leaderboard
Popular Content
Showing content with the highest reputation on 10/29/2022 in all areas
-
New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20221029-3219d2d-uxp-a6338caef-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20221029-3219d2d-uxp-a6338caef-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-20221029-3219d2d-uxp-a6338caef-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-20221029-d849524bd-uxp-a6338caef-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20221029-d849524bd-uxp-a6338caef-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20221029-d849524bd-uxp-a6338caef-xpmod.7z Official UXP changes picked since my last build: - Issue #2019 - Do not dispatch keypress event for non-printable keys. (1392f5f22) - Issue #2019 - Follow-up: Adjust content spellchecker to use keydown (5699d9673) - Issue #2019 - Follow-up: Make autocomplete and satchel listen to keypress events in the system event group (808332c2c) - Issue #1375 - Don't mark nodes in the shadow tree as orphan nodes (9277c9418) - Issue #1829 - Follow-up: Mac-specific shortcut key for closing the developer tools toolbox window should not be excluded from other platforms (d02383072) - Issue #58 - Remove leftover rust build files from /js (1a55f1832) - Issue #1793 - Follow-up: Fix incorrect media query (1ae5f60a1) - Issue #21 - Remove panning/tab animation performance measurements (2e944692c) - Issue #2022 - Part 1 - Fix transparent windows on MacOS 13 Ventura. During the BaseWindow creation contenView is nil on Ventura... So create a NSView with the requested dimensions and set is as the contenView. (069b11c14) - Issue #2022 - Part 2 - Add Ventura version detection. Also add Monterey and Ventura to the graphics driver blocklist. (70727d0a0) - Issue #1824 - Remove dependency on libdemangle. (8b8084f66) - Hold some strong references on nsRefreshDriver (e69b52eac) - [XPCOM] Fix Base64 off-by-one issue and safeguard against this mistake in the future. (3fccd404f) - [WebGL] Implement webgl.max-size-per-texture-mib (2f0acd868) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes since my last build: - fill static_assert() message added in rev 3fccd404 to fix build (a6338caef) 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.2 points
-
Notice: These projects have no affiliation with any upstream community code sources or organizations. Please direct all support or related questions to here. "Serpent", "New Moon", "MailNews" are generic debranded names and they are subject to change in the future. Archive directory names and archive filenames will only be changed once generic debranded names are not used in the future. Latest changelog is available here as well: http://rtfreesoft.blogspot.com/search/label/browser for people who can't register here, there is another place you can create post for asking/help besides in github and blog: https://forum.eclipse.cx/viewforum.php?f=33 Serpent/UXP browser (MCP reforked 52ESR as new base), and NM28XP releases: Binaries are moved to here: (I'm lazy to edit all previous posts) https://o.rthost.win/palemoon/?sort=date&order=desc BOC and hyperbola related binaries: Binary list: https://o.rthost.win/boc-uxp/?sort=date&order=desc ------------------------------------- NewMoon 27 build: ------------------------------------- Serpent/moebius browser (deprecated by MCP, forked by me), and also 26.5 as playground : And NewMoon 26.5 and K-Meleon 74 with Goanna 2.2 (newmoon-26.5) for vanilla Win2000 build: ------------------------------------- K-Meleon browser with Goanna/Tycho engine: It has its own sub-forum in K-Meleon official forum! http://kmeleonbrowser.org/forum/list.php?19 Latest build: ------------------------------------- Firefox ESR 45 with TenFourFox fixes for IA32/SSE-only machines: ------------------------------------- K-Meleon Original cross-post is here: ------------------------------------- ArcticFox XP win32 test build: https://github.com/rmottola/Arctic-Fox/releases ----previous post----1 point
-
Invalid configuration. Post-v4.5.2 updates are not yet ready for end users.1 point
-
Thank you VERY much, @XPerceniol!.. "We hope you don't leave us away suddenly again." - I hereby subscribe under this of course!1 point
-
Dang, there is a big padlock icon in v3! Good, now the v5 is solved. I still wondered if v4 is already fixed1 point
-
Thanks, I hope you're fine. It's good to see you back. We hope you don't leave us away suddenly again.1 point
-
1 point
-
1 point
-
FAQ: Q: Having audio distorted when watching Twitter/etc.? A: Please try turning on "Firefox compatibility" in options dialog or either "general.useragent.compatMode = 2" or "general.useragent.compatMode.firefox = true" in about:config and reload the page. Q: Can't play H264 clips? (for PM27/KM76/FF45) A: Download following packages for your browser edition(32bit/64bit) and extract DLLs to same place as palemoon.exe lives. 32bit LAV dlls are in separated package (extracted from K-Lite codec pack 13.5.5) https://o.rthost.win/palemoon/lav.7z Just in case if you have an older processor which has no SSE instruction set support: 32bit NoSSE (ffmpeg 3.1.1 lite build) https://o.rthost.win/palemoon/lav-dll-lite-mmx.7z 32bit No ASM (ffmpeg 3.1.1 lite build, if build above doesn't work on your processor) https://o.rthost.win/palemoon/lav-dll-lite-noasm.7z 64bit LAV dlls are in separated package (LAV Filters 64bit 0.70.2) https://o.rthost.win/palemoon/lav64.7z Q: AV1 Support? (for UXP-based applications except mailnews) A: You need to enable "media.av1.enabled" in about:config Q: VP9 Support? (for PM27) A: VP9 works if async MSE option is unchecked and "Enable MSE for WebM Video" checked in options. Q: Extensions/Themes not working after updating binaries. A: If you encounter extensions not showing icon, clicking options button of extension causing browser unresponsive, etc. please try following actions: 1.a Kill palemoon.exe process(es) 1.b Copy whole extensions folder out of profile folder (to somewhere else for example, desktop) 1.c Restart browser without restoring previous sessions 1.d Goto about:addons page 1.e Drop XPI files from the copied-out extensions folder to about:addonss page One-by-One. 1.f After all XPI files are dropped and installed/updated, restart browser Q: Virus detected? A: Tell your anti-virus program to exclude palemoon.exe and/or plugin-container.exe. Some anti-virus heuristic engines (for example symantec's sonar engine) is too sensitive to palemoon.exe/plugin-container.exe network activities. Q: Where's your patches for compiling my own? A: Please visit the link above "FAQ:". Latest source patch files are named "sources_patches_YYYYMMDD.7z" in that page. Q: basilisk browser showing basic pages in GMail? A: set these to "true" in about:config general.useragent.compatMode.firefox general.useragent.compatMode.gecko Q: Should I let official Pale Moon and "New Moon" both using same profile (at the same time / alternatively)? A: it is not recommend to do that, as they have different NSS security library, which has different encryption procedure to the saved password database. Same profile being "touched" by different gecko/goanna applications may cause unexpected behaviors. If you want to launch both Pale Moon and "New Moon" / Basilisk and "Serpent" / etc. at the same time, one of them should be in "--no-remote" portable mode. Q: How to change User Interface language? A: Please see this post: Q: Portable Loader? A: You can always use official portable launcher with my binaries, or you can use my simple portable loader written in NSIS: Q: How to install extensions/themes in BNavigator browser? A: Please check this post out: (EDIT: you may need to change minVersion to 0.9.0a1 as upstream changed version to a lower value after this guide existed) Q: I want to verify if archive is not changed by others! A: from 30 October 2019, new archives will have ".asc" GPG detached signature. You can download signature separately by appending ".asc" (without quotation marks) after the archive URL. You can get my public key by following instructions in this post: Q: I'm getting 0xC000001D error when starting Serpent/UXP-ia32 or NM28-ia32 browser! A: your processor does not support CMOV instruction. VC2015 IA32 build requires CMOV instruction support. here is a list of processors with CMOV instruction support: - Intel: Pentium Pro or later - AMD: K7 (original Athlon/Duron) or later - VIA: C7 or later - Transmeta: all CPUs are capable to run SP52-ia32/NM28-ia32. - Cyrix/IBM: 6x86MX or later, MediaGXm(MediaGX-S) or later - National Semiconductor/AMD: Geode GX or later - DM&P/Vortex86: Vortex86DX3 or later Q: I need WebAssembly support! A: for NM28/SP52, go to about:config and enable javascript.options.wasm Q: Why you still keeping on version 28? will you have a version 29 build? A: please have a look on this post: Q: but is it up to date? A: please have a look here:1 point
-
WinCopy will create a copy of windows installation. For example, move the current installation into a VHD. The first 6 modes are using wimlib (with optional WOF compression). It's like capture and apply without actually creating a WIM file. File exclusion using a WimScript.ini are possible as well using MinWin by clicking on the Mode label. The VOLUME COPY option is more like Drive SnapShot, it copies the entire NTFS File System (used clusters only). It's much faster than the other modes, but does not offer any options. Destination drive can be smaller as the source drive, but the last used cluster must fit in it.1 point
-
I'm sorry if I forgot and tried to look at my notifications and I have a million. Love you guys.1 point
-
That's a good idea, @Dave-H! I always bristled a bit at the "abruptness" of the switchover from one "My Browser Builds" thread to the next. It makes more sense to start the next thread with the next set of builds. To be clear (and fair to Google), it's not so much their Chromium engine (I use Chromium-based browsers - albeit "unGoogled" - when necessary) as it is Google's "predatory innovation" cycle: Google thinks up new "features" that Javascript "needs." (And again to be fair, these "features" often are real improvements that make Javascript programming a bit easier for Web developers - but that's not the point of them.) Google updates Chromium (and Mozilla and Safari update their own Javascript engines) to correctly interpret the new "features," so if you stay current on Safari, Firefox, SeaMonkey, or one of the many Chromium-based browsers, nothing ever seems amiss. Google and "friends" (e.g., Microsoft) then use the new "features" as much as humanly possible, not only on their own Web sites (e.g., GitHub), but also in the "frameworks" used by most Web sites these days. (Nobody codes entire Web sites in raw HTML and CSS anymore; it's too labor-intensive. Everyone uses frameworks.) Web developers update their sites to use the new "frameworks" - often unwittingly, as they may simply link to a CDN that always serves, say, the latest JQuery version. Even if browser developers outside the "Goog collective" (like, say, MCP) are able to add support for the latest Javascript "features," by the time they do, so the cycle begins again, thus preserving the Apple/Google/Microsoft/Mozilla oligopoly.1 point
-
Windows Update v4 is currently experiencing problems due to getmanifest.asp, so it will come in a moment. But v3 is working and v5 too! WinFX and maile3241 did a very great job.1 point
-
I was a Firefox fan from the beginning in 2002. I used to surf a lot on websites that were very insecure and should actually rather be avoided. You could quickly catch malware, and the antivirus programs of that time were not really good. Internet Explorer was defenceless against these nasty websites. When the Firefox browser appeared and was constantly improved, I was thrilled. Ad blockers, script blockers, and the many useful extensions made Firefox my favourite browser. It was like that for years. The jump to versions 43+, 46+, and even worse to 52+ and finally, the disaster at its best, 57+ was the reason for me to turn my back on Firefox due to the well-known, worse changes coming up with these versions. I found an interesting alternative in Pale Moon. And so, Pale Moon quickly became my default and favourite browser. I never really liked Chrome and always avoided it as much as possible in Windows XP. In newer operating systems like Windows 7 and higher, however, there is no escaping the Google monster. Truth be told, I love to surf the internet and read articles on a tablet wherever I am. Since I detest Apple even more than Google, my tablet is based on the Android operating system, a choice between the devil and the deep blue sea. Anyway, my Android tablet is Google in its pure existence, and all Googlized crap, which does not work on my Windows XP computer, is processed here. I totally agree. Moreover, Internet Explorer died several deaths. First, it was Firefox , then the inability or listlessness of Microsoft to develop this browser meaningfully and keep it up to date, and then came Chrome, which ultimately imposed its browser engine on most browsers. All attempts by Microsoft to counteract this with Internet Explorer versions 6, 7, 8, 9 and 11 were too late and doomed to failure. Ultimately, Google and its Chrome engine stifle alternative browser developments. Yes! That the old Firefox code is freely available and could form the basis of Pale Moon and roytam1's browser editions was indeed a stroke of luck for which I will always be grateful.1 point
-
I'm sorry, but that just makes no sense at all. IE was alive and well less than 10 years ago in 2013, when IE 11 was released for Windows 7 and 8.1. Officially, IE was replaced by Edge in 2015 with the release of Windows 10, but if IE had used a "major.minor" version numbering system like most software, Edge would probably have just been the next "major" version of IE. With the "major only" version numbers all the big Web browsers have chosen to curse themselves with, though, "IE 12" just didn't capture the extent of changes from IE 11; hence the new name and logo (which looked much like the old IE logo). BTW, Edge's new UI looked more like Chrome than Firefox. (In 2015, Firefox looked like Pale Moon does now.) So "classic" Edge is really just the final version of IE. Web designers test their designs on all major browsers: Chrome, Firefox, Edge, and, until recently, IE. What actually killed IE off was the same thing that now bedevils us: IE 11 couldn't handle all the Googlescript showing up in Web site frameworks, and classic Edge took a lot of development to keep up. Microsoft didn't want to spend money chasing Chrome, so in 2019 Microsoft released "New Edge" based on Google's Chromium. (You'll get the references if you were drinking American soft drinks in 1986.) Even the logo changed to some kind of ambiguous e/c blend, to signify the Pepsi - I mean Chromium - in Edge! This was the cause of IE's death, not Mozilla-loving Web designers casting shade on it back in the Bush Administration. And in late 2017, Mozilla switched Firefox to Quantum and the Photon UI, making it a rather obvious Chromium clone. "New Firefox" now lives in name only! Sure, it renders all the latest Googlized Web sites perfectly, but it tastes just like Chrome! So if Mozilla were somehow responsible for IE's death, it took them so long to carry out the murder that their own products died off first! No. The evidence is much stronger that it was Google that drove both Microsoft and Mozilla to abandon their own code bases. IE's code was proprietary, and so is locked away in a Microsoft safe somewhere. But thanks to Mozilla, at least Firefox's abandoned code base lives on in the UXP platform.1 point
-
1 point