Leaderboard

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190302-d0444154b-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190302-d0444154b-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190302-d0444154b-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190302-d0444154b-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from rmottola/Arctic-Fox: - Bug 1129223 - Remove local mozAfterRemotePaint events (a9aec8f51) - override -> MOZ_OVERRIDE (2de5b532c) - Bug 1129223 - Introduce new, more efficient mozLayerTreeReady event (9a363c950) - Bug 963921 - Clients of the JS API should use JS_DefineElement where appropriate (912f064c0) - Bug 1133746. Allow DOMProxyShadows to communicate to the JIT whether the shadowing is done by the expando object or not. (dbe537f12) (301eae9eb) - aboutDialog: always show build date (e2ac38931) - import changes from rmottola/Arctic-Fox: - Bug 1112164 part 0 - PrintUse: Use AnyRegister::name method for printing the name of Fixed register uses. (996f68005) - Bug 1112164 part 1 - x86/x64 lowerForFPU: Do not reuse the input register if the MIRType are different. (8722bfc62) - Bug 1112164 part 2 - Rename ReturnSimdReg to ReturnInt32x4Reg and ReturnFloat32x4Reg. (158171a74) - Bug 1112164 part 3 - Add {Float,}Register::Encoding to represent what can be decoded from the assembly. (64a7488e8) - Bug 1112164 part 4 - SimdReinterpretCast: Do not use redefine as the MIRType of the input & output are different. (441077b2b) (e9a10fb1a) - configure: remove restriction of redist DLL location (ba8924b6e) - import changes from rmottola/Arctic-Fox: - add X11 flags to allow building on NetBSD (72667df53) - Bug 1122856 - OdinMonkey: Split out the flag that says "bounds checks are unneeded because of signal handling" (36bb96c9e) - Bug 986981 - OdinMonkey: Optimize addresses with constant offsets on x86 and x64 (e0fd22c6e) - Bug 1138205 - use a reinterpret_cast instead of a static_cast after bug 986981, fixes build on OpenBSD/amd64. (5e1dd72a1) - Bug 1138180 - Make --disable-ion compilable again. (f835126ba) (d0444154b) * Notice: Due to a rewrite of git history, old git commit hashes are not matched. Please use corresponding commit message to search back the hash. Sorry for any inconvenience caused.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190302-e64dae886-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190302-e64dae886-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win32-git-20190302-e64dae886-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win64-git-20190302-e64dae886-xpmod.7z Official repo changes since my last build: - WIP fix 1 (c962e2051) - Move default-enable pref to application. (c08b490c5) - Update Basilisk FE code with HTTP Auth DoS protection. (f227feb6e) - Make the Auth prompt DOS protection a browser-element opt-in feature. (c1ece93c2) - Improve the http basic auth DOS protection heuristics. (e64dae886)

I installed the Windows XP Professional x64 operating system on a Samsung 970 Pro NVME SSD drive using an ASRock X99 Extreme4 motherboard. Really easy the second time. Download Kai Schtrom's driver here: https://sourceforge.net/projects/nvme-for-windows-2003-server/files/ Download KB932755 here: https://www.microsoft.com/en-us/download/details.aspx?id=11619 Download AOMEI Backupper Standard here: https://www.aomeitech.com/download.html Use diskpart in Windows 7 x64 to create the aligned partition on, and format, the NVMe drive (the Windows 7 OS must have an NVMe driver installed, or diskpart will not be able to see the NVMe drive). Use Device Manager in XP x64 to install Schtrom's driver, which makes the NVMe SSD available as a storage drive -- and the XP x64 operating system as such now includes the NVMe driver. Run the storport hotfix. Use AOMEI Backupper to clone the XP x64 disk to the NVMe disk (remember to align the partition). Reboot into the BIOS and set the NVMe drive to boot first. I don't know whether Kai Schtrom had Windows XP 64-bit in mind when he wrote his driver, but for those of you running that OS it does present the potential for significant performance improvement, to say the least.

Hey patching tribe! I'm making my regular backup, just to be prepared for any trouble with updates now. So just asking once again, to be triple sure - are Ferbruary patches ok to be installed now? KB4487085-v2 looks safe?

My unofficial installer is confirmed working with the latest builds for both new installs and in-place upgrades . Currently working on a new version of the installer: -any Basilisk branding changed to Serpent to better represent the product -adding support to download and install from windows 2000 with BWC extened kernel -maybe more, who knows As always, let me know if you guys find any bugs so I can fix them.

New regular/weekly KM-Goanna release: https://o.rths.cf/kmeleon/KM76.1.1-Goanna-20190302.7z Changelog: Out-of-tree changes: * update Goanna3 to git 2e31415af..d0444154b: - import changes from rmottola/Arctic-Fox: - Bug 1129223 - Remove local mozAfterRemotePaint events (a9aec8f51) - override -> MOZ_OVERRIDE (2de5b532c) - Bug 1129223 - Introduce new, more efficient mozLayerTreeReady event (9a363c950) - Bug 963921 - Clients of the JS API should use JS_DefineElement where appropriate (912f064c0) - Bug 1133746. Allow DOMProxyShadows to communicate to the JIT whether the shadowing is done by the expando object or not. (dbe537f12) (301eae9eb) - aboutDialog: always show build date (e2ac38931) - import changes from rmottola/Arctic-Fox: - Bug 1112164 part 0 - PrintUse: Use AnyRegister::name method for printing the name of Fixed register uses. (996f68005) - Bug 1112164 part 1 - x86/x64 lowerForFPU: Do not reuse the input register if the MIRType are different. (8722bfc62) - Bug 1112164 part 2 - Rename ReturnSimdReg to ReturnInt32x4Reg and ReturnFloat32x4Reg. (158171a74) - Bug 1112164 part 3 - Add {Float,}Register::Encoding to represent what can be decoded from the assembly. (64a7488e8) - Bug 1112164 part 4 - SimdReinterpretCast: Do not use redefine as the MIRType of the input & output are different. (441077b2b) (e9a10fb1a) - configure: remove restriction of redist DLL location (ba8924b6e) - import changes from rmottola/Arctic-Fox: - add X11 flags to allow building on NetBSD (72667df53) - Bug 1122856 - OdinMonkey: Split out the flag that says "bounds checks are unneeded because of signal handling" (36bb96c9e) - Bug 986981 - OdinMonkey: Optimize addresses with constant offsets on x86 and x64 (e0fd22c6e) - Bug 1138205 - use a reinterpret_cast instead of a static_cast after bug 986981, fixes build on OpenBSD/amd64. (5e1dd72a1) - Bug 1138180 - Make --disable-ion compilable again. (f835126ba) (d0444154b) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76 ** Notice: Due to a rewrite of git history, old goanna3 git commit hashes are not matched. Please use corresponding commit message to search back the hash. Sorry for any inconvenience caused.

As we started using a bit of lawyerese in this thread, I'd suggest this might be violating paragraph 7.b of MSFN forum rules as long as you act like that in here, but what do i know... Glad it turned from rage and anger to constructive discussion and all's on track again.

@LoneCrusader Yes, I did do Pale Moon for Windows XP starting with XP64. Windows XP 64bit was actually NT 5.2 so it's code lifetime was in line (even if Microsoft fudged it) with Server 2003. I did expand to doing XP32 as well and I decided I would provide builds specifically for Windows XP since the codebase we used in combo with the compiler optimizations didn't like NT51 compile targets running on NT6x with that combo of optz so I had to use more conservative optimizations. So the mainline binaries started targeting NT60 with the aggressive optz and I provided the NT51 targeted ones with more conservative optz. Now the use of the Pale Moon name and branding as well as the Pale Moon for Windows XP splash image on the page were done with full permission from Moonchild so they were not unofficial, they were officially endorsed builds under the Pale Moon branding and redist license. I always leave in a way out in any kind of software commitment which was that I would produce these binaries until the end of life for Windows NT 5.2 (5.1 already ended but I ignored that since issues between both with rare exception would apply or not across the NT5x spectrum). See: https://web.archive.org/web/20150414135447/http://binaryoutcast.com/projects/pm4xp/ Once NT 5.2 EoL'd which was conveniently after the last version of the 26.x series it was done. Tycho would target Vista and I would not be doing PM4XP binaries anymore. I had my way out and XP was not a consideration anymore.. Cause we knew many libs would start dropping support as well and it was holding back certain technological advancements and also has quite a respectable number of alt code paths. For us it was the best decision to move forward. See: https://web.archive.org/web/20151022140405/http://binaryoutcast.com:80/projects/pm4xp Now the REASON I did it originally.. Well back in those days I was far more glory seeking and wanted to attach my self and my brand to Pale Moon's greatness for selfish reasons. That is almost never a factor in what I do today though. It did have the benefit of providing what was needed at the time when the issues of running a Mozilla-style application targeted to NT5x on NT6x at the code state it was in was discovered but PM4XP was not as pure as what I have done since then. So there that is. Explained.

@dencorso I had my rant and anger spell.. Time for something more constructive so ye. @Dibya Vaguely. I still think using Windows XP in today's world outside of very extreme and edge cases is a bad idea but this stuff exists so I may as well be constructive rather than destructive. Obviously, @roytam1 is doing more than the shameful rebuilds for XP leeching off our names or whatever it was I said.. He is creating something unique as we have done.. SO I am committing my self to helping him succeed in whatever way I can contribute toward. That way we all get what we want and it isn't just an angry Tobin busting down the door looking for logos or whatnot. A real project or projects such as these deserve their own name and support from others just as ours do.. So that is why I am changing gears here. However, and you won't like this but if I feel the person in question is a moron I am gonna call them a moron regardless.. Call it a personality flaw. Though, that status can always be re-evaluated

Plus isn't Matt just using SeaMonkey and altering it into a browser-only product? By the way, everyone knows I'm not stuck on the continued use of XP. BUT .... BUT .... as it stands, native Seamonkey can still run on XP, can't it? Now if Borealis can't, then isn't Matt doing the same thing to the Mozilla code that he accuses Roytam1 of doing to Borealis and Interlink? Here's the way I see it. Even if I shake my head at those still using XP, I'm not going to put up intentional road-blocks, just to make life miserable for those people. So Matty Boy, why not just let Roytam1 continue compiling these applications for XP and Vista compatibility? Forget about "following the agreement to the LETTER"; what about exercising the spirit of the license. Think about it - other than your arrogant and hostile attitude, they ACTUALLY LIKE your work, and want to use it. How much bigger of a compliment can you get?

Well after installing xp on the new HDD, (the difference from the old one is like night and day) the ThinkPad is back in service. All the POSReady updates that were offered to me today were installed with no issues.

So....please tell us why you are wasting time even trying...?! If you are going to continue to post about problems the first thing is...do yourself a favour....you have been used to XP Pro...so install this program "Classic Shell"...no longer being developed but works a treat...you will have a menu like WindowsXP and then you will probably find things.... I want to add here that I am not a diplomat and can be a bit harsh at times.... And I apologise if I have offended anyone...not my intention! I really hope Roffen understands....we are just trying to help.... The more information we have the better.... bookie32