Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190608-19c0f5e9f-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190608-19c0f5e9f-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.6.0a1.win32-git-20190608-19c0f5e9f-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190608-19c0f5e9f-xpmod.7z Official repo changes since my last build: - Revert "Improve origin-clean algorithm" (f47d45be4) - Improve `origin-clean` algorithm based on our previous changes. (3f1ef7a67) - Remove e10s force-enable/-disable prefs and a11y considerations for starting in e10s mode. (19c0f5e9f) My changes since my last build: - Change help link for unofficial branding (Serpent) (65bd689bd) - Point release notes to author's Web page (fb327115f) - Update Help link to point to msfn.org (a9836cb56) - Remove palemoon.org from New Moon branding (9e4dfbda3) - Merge pull request #2 from Mathwi/Mathwi-patch-2 (9cee045fd) - Merge pull request #1 from Mathwi/Mathwi-patch-1 (7a5bba6f8) - Redirect support URLs away from palemoon.org (1de2444bc) - Redirect browser.feedback.url from palemoon.org (426aef14c) - Update app.support.baseURL pref again (7254c3400) - Merge pull request #2 from Mathwi/custom (a7ad0dde7) - Revert "Remove e10s force-enable/-disable prefs and a11y considerations for starting in e10s mode."

New build of Firefox 45ESR SSE: test binary: https://o.rths.cf/gpc/files1.rt/firefox-45.9.15-20190608-3e6bd7592-win32-sse.7z repo: https://github.com/roytam1/mozilla45esr Changes since my last build: - revert part of "#446 + #334: trim refresh driver further; restore old Tele removal (4594eee51)" since there is no problem in win32. (3e6bd7592)

this will be fixed in next build

Success finally. All updates installed and Avast 18.8 running OK now. @Vistapocalypse. Thanks for your link to spiceworks. I was following that thread too and the persistence of @spicehead-3vg61 grabbed the attention of @Peter (Avast) mentioning my original post here at MSFN. The first Avast/AVG micro-update (released in April) did indeed change my registry settings for Csrss as @artomberus showed in his screen shot (but in my case using Avast instead of AVG) but my system was still BSOD on reboot. Avast was showing:- Avast program version 18.8.2356 (build 18.8.4084.0) Virus definitions version 190521-4 After confirmation from @Peter (Avast) on 4th June, I ran the Avast Emergency Updater: (just to be sure) (at this stage I had not seen a difference in the ‘About Avast info’) C:\Program Files\AVAST Software\Avast\AvEmUpdate.exe as detailed here. After a reboot: Avast now showing:- Avast program version 18.8.2356 (build 18.8.4084.0) Virus definitions version 190606-4 It appears that Avast Free (For Home) did not update to program version 19.3 (and later to 19.5) as indicated here for (Avast Business Antivirus) but remains at 18.8, BUT now the second micro-update (within the Virus definition update) (released on 4th June) has resolved the BSOD and I am now up to date with MS Updates...Phew! 

It looks like VLC 3.0.7 stable was released today.

Success finally. All updates installed and Avast 18.8 running OK now. @Vistapocalypse. Thanks for your link to spiceworks. I was following that thread too and the persistence of @spicehead-3vg61 grabbed the attention of @Peter (Avast) mentioning my original post here at MSFN. The first Avast/AVG micro-update (released in April) did indeed change my registry settings for Csrss as @artomberus showed in his screen shot (but in my case using Avast instead of AVG) but my system was still BSOD on reboot. Avast was showing:- Avast program version 18.8.2356 (build 18.8.4084.0) Virus definitions version 190521-4 After confirmation from @Peter (Avast) on 4th June, I ran the Avast Emergency Updater: (just to be sure) (at this stage I had not seen a difference in the ‘About Avast info’) C:\Program Files\AVAST Software\Avast\AvEmUpdate.exe as detailed here. After a reboot: Avast now showing:- Avast program version 18.8.2356 (build 18.8.4084.0) Virus definitions version 190606-4 It appears that Avast Free (For Home) did not update to program version 19.3 (and later to 19.5) as indicated here for (Avast Business Antivirus) but remains at 18.8, BUT now the second micro-update (within the Virus definition update) (released on 4th June) has resolved the BSOD and I am now up to date with MS Updates...Phew!

UPDATE [June 7, 2019]: Post-SP4 Update Pack released! This final update pack should be applied to Windows XP installation media immediately after slipstreaming SP4 v3.1b to a Windows XP RTM/SP1/SP2/SP3 source. This will update installation media to May 2019, including every single update released until the POSReady 2009 end-of-life in May 2019. Download available at RyanVM.net.

... You "sound" surprised ; if you please read more carefully previous posts in this thread and/or inspect related commits in Roytam1's GitHub repository (as the result of Mathwiz's PRs), you'd realise ONLY NM28/UXP and (some of) Serpent52/UXP "Help" entries were altered... If, OTOH, you are truly asking for Mail News's "Help" entries to be modified, that's a different matter; AFAICT, @roytam1 hasn't published a forked Binary Outcast GitHub repository (unlike his UXP one!) one can then re-fork and submit the necessary PR... He, of course, can do this in his local BO repo, if he agrees to your requests... NB: I am NOT a user of any of the BO forks (nor will I choose to be )...

The "Windows XP SP4 MUI October 2018 Update" is the best way to use SP4 in languages other than English (ISO was flagged and no longer available, will re-upload sometime). However, several OS components will not be translated to another language.

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190608-6cd09e714-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190608-6cd09e714-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190608-6cd09e714-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190608-6cd09e714-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - Reverted following changes in order to make KM happy: - Bug 868814 - Fold mozalloc library into mozglue. (324250a8c) - Bug 1141660 - Fix bustage from bug 868814 with --disable-replace-malloc (7f74490b2) - Followup for bug 868814 - replace non-obvious #if with simpler alternative. (2a1520452) - Bug 1134920 - Remove nsMemory::Alloc/Realloc/Free. (514d8e8eb) (e96afb6ea) - import change from rmottola/Arctic-Fox: - Bug 1138527 part 1 - Make ruby annotations have the same font inflation as its containing ruby frame. (088bbf5bc) - Bug 1138527 part 2 - Reftest for application of font inflation to ruby. (41ae8c811) - Bug 1097468 - Part1: expose |homescreen-webapps-manage| in Apps.webidl (b182f49b7) - Bug 1097468 - Part 2: test for permission |homescreen-webapps-manage|. (1b097c139) - Bug 943537 - In the GeckoContentController interface, take the modifiers for tap events in 'widget modifier' format rather than 'DOM modifier' format (4b7de6b31) - Bug 943537 - Handle modifiers on tap events in RemoteContentController and ChromeProcessController. (2bbe91961) - Bug 1130455 - Remove the ScrollingBehavior code to propagate APZ and use gfxPrefs instead. (09a0c8e61) - Bug 1139258 - Use ScreenIntSize in PBrowser::Show/UpdateDimensions (2189f8921) - Bug 1139575 - Don't set the fast motion flag on multitouch blocks. (5155bfd13) - Bug 1137267 - Enable event-regions automatically when APZ is enabled, and allow the APZ code to assume event-regions are enabled always. (29d7e7d1c) - Bug 1137267 - Remove unneeded flags to track touch listeners and touch caret. (cb6cc1139) - Bug 1036967 - Use ScaleFactors2D instead of ScaleFactor where appropriate in APZ and surrounding code. (09ce986a9) - Bug 1036967 - Remove ScaleFactor::ScaleFactor(float, float). (87d13024c) - Bug 1036967 - Followup to fix debug logging. (d01fca6e4) - Bug 1036967 - Follow-up to fix debug logging. (776b4b65e) - Bug 1149060. Fix dev pixels per CSS pixel and presshell resolution layer dumping after bug 1036967. (6d26e4d3c) - Bug 1130982 - Reftest for this bug. (00bff9489) - Bug 1130982 - Ensure the clip rect is appropriately adjusted for multi-framemetrics layers. (211d15a4d) - Bug 1130982 - Fix a reftest so an element that's supposed to be scrollable actually is. (71dc992e2) - Bug 1130982 - With multi-FrameMetrics on APZ platforms, do not apply clips to scroll ports of frames other than the bottom-most one on the layout side. (4d9342324) - Fix APZ using incorrect scroll wheel deltas. (bug 1141728) (cad854639) - Bug 1139675 - Update JS callers of nsIDOMWindowUtils.setResolution and getResolution in accessibility code. (28dffc78d) - Bug 1136914 - Don't lose scale from parent document when descending into subdocument. (0d3cef358) - Bug 1139283 - Move some properties from nsStyleDisplay to nsStylePosition. (ff61201ae) - Bug 1125767. Centralize code into nsStylePosition::IsFixedPosContainingBlock. (f256191f4) - temporary override -> MOZ_OVERRIDE again (ed8caa82d) - Bug 1139675 - Add a couple of operator overloads to BaseSize. (a214c0eab) - Bug 927995 - Handle antialias+preserveDrawingBuffer properly. (9ceaf6d0a) - Bug 1142926 - Only notify the docshell of state changes when moving in and out of a transforming state across all APZCs. (153054d1e) - Bug 1116806: Enable dom.ipc.plugins.asyncInit by default; (bf0e3464d) - Bug 1143789. Remove unnecessary cast to BasicLayerManager. (fd30ade6c) (1cf10c95c) - import change from rmottola/Arctic-Fox: - Bug 1143518 - Remove the TryCapture path which is now obsolete. (5b1b50333) - Bug 1112040 - Report invalid regular expressions to the console. (909f196ee) - Bug 1143010 - Stopping a mochitest-browser run is rocket science. (c7c482690) - Bug 1110487 P1 Fix some non-unified bustage before adding new code. (e8c3346a4) - Bug 1140051 Avoid Cache shutdown assert when Manager alive, but not active (1fd5d21d2) (6cd09e714)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190608-f12228c-uxp-19c0f5e9f-xpmod.7z Browser-only Suite Win32 https://o.rths.cf/boc-uxp/bnavigator.win32-20190608-f12228c-uxp-19c0f5e9f-xpmod.7z source patch (excluding UXP): https://o.rths.cf/boc-uxp/boc-uxp-src-xpmod-20190223.7z Official repo changes since my last build: - [PLATFORM] Update commit pointer (e2374c9) - [Mail] Use gre value for layout.css.devPixelsPerPx (f12228c) For UXP changes please see above.

Many sites download their own fonts. I suspect Gmail is among them. Panda may be blocking the font download; I don't know anything about it but you might look for a setting related to downloading fonts.

It's strange that on your computer you need to put the patch in your profile folder too, in other computers, the patch just works by putting it in the \Defaults\Pref\ folder, of course, being a defaults replacement, you won't see any custom entry in your about:config, because the entries that are modified by the patch are now considered as default ones, and so they won't appear highlighted, nor they will appear in the prefs.js, that contains only the parameters edited by the user*. That's how me and the others install it. But hey, I'm glad you got that site working now, even though you had to install the patch twice. *: However, I discovered that there are two parameters that for some reasons, the patch ignores, but they can be edited manually in the about:config. Here they are: image.mem.max_decoded_image_kb 512000 browser.urlbar.maxRichResults 1 While it's not strictly compulsory to reduce the "awesome bar" to just one entry, I do it to save RAM. It's important to set the max decoded image memory to 512000 though, as that further speeds up images rendering. For some reasons, the browser ignores just these two parameters. But it's just a quick fix, just open about:config and edit the two parameters above. Remember, the UOC Patch is not set in stone, you can edit it to suit your needs and add or remove some features you like/dislike. But I'm glad you sorted your issue out. I've updated the main post with the two settings for the awesome bar and the maximum decoded memory for images.

@Mathwiz's PRs have been now merged into @roytam1's custom UXP branch, expect to see the changes landing in tomorrow's NM28/St52 builds... On another note, the few (?) of you running Serpent 52.9.0 in forced multiprocess (e10s) mode ( @Mathwiz, still doing this? ), will soon be unable to continue this practice, considering the upstream dev has patched that loophole: https://github.com/MoonchildProductions/UXP/issues/1130 https://github.com/MoonchildProductions/UXP/commit/19c0f5e

Ads are gone since 25. June and nobody knows what's going on. I'm concerned too. https://support.google.com/adsense/thread/6825406?hl=en

Quoting what I said on OP's similar thread about the problem. This has fixed OP's problem, so it should fix yours.

I had been meaning to respond to this topic for a week, but I'd been so preoccupied with work and other commitments that I hadn't had the chance to ... until now! I wanted to leave a huge thank-you, @XP-x64-Lover, for all you've done in finding these drivers and allowing those of us sticking with XP64 a chance to upgrade to hardware a bit more recent. Between your drivers and the trick explained by Matt's Repository for getting XP/XP64 drivers for the nVidia 9XX series, on Memorial Day Weekend I was able to finally give my desktop the badly needed overhaul I'd been wanting to do since my first posts at MSFN back in 2014! That's 64 GB of DDR4 RAM, SABERTOOTH X99 motherboard, Intel i7-6950X CPU, and a GeForce GTX TITAN X. I wasn't able to get the SSD thing sorted out, so I wound up using the IDE method, which has worked amazingly well with my existing install. Since @bluebolt figured out a way to get an install of XP64 working on a NVMe 2.0 drive, I may skip the SSD and attempt a fresh install off of that instead, since the X99 has a bay for NVMe drives. For now, though, I'm just excited to have not only put my hardware troubles behind me for now, but that I've now got the RAM upgrade I've wanted for years!

Same here

Take a look at these topics for driver slipstreaming information: https://msfn.org/board/topic/149231-trying-to-use-infinst-to-add-drivers-to-win-98-install/ https://msfn.org/board/topic/162717-how-do-you-slipstream-drivers-into-a-custom-win98se-install-disc/