Leaderboard

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.

I agree that someone from MCP coming onto this thread and striking a disagreeable attitude, making threats, and generally being unpleasant, doesn't exactly predispose folks here to try to accommodate their wishes. And it's also true that to the extent there are "branding" issues with unofficial builds, they are the fault of MCP themselves, not @roytam1. So I can sort of understand having a spiteful attitude toward MCP and their demands. But I think we already decided we weren't undertaking a full rebranding of New Moon or Serpent anyhow. At this point, all we're talking about is getting rid of the "you've successfully upgraded" Web page and redirecting a few Web pages that come up when users of @roytam1's browsers use the Help menu. It's just not that big of a deal, and it's worth doing anyhow for the benefit of New Moon / Serpent users (not to mention msfn.org, which stands to gain a few more members). If it eases tensions with MCP a bit too, so much the better. (And if someone's really stubborn about it, they can switch all their prefs back in about:config anyhow.)

thanks for noticing, this rev won't get in my repo.

@Mathwiz -- @VistaLover <-- https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1165197 The above URL from me still summarizes my views accurately. As to doing it, and 'how much' -- I defer to you both on that aspect. To aim the HELP URLs at RT websites seems reasonable to me. However much that happens, I will be good with it. With my last message here, just noting that MSFN.org based URLs could change. As to what to do about that, I defer to say 'Mathwiz' on that. So, if NOTHING changes, I will still be okay with RT Browsers. But currently, I am just looking for the HELP URLs to aim at RT websites. And removing that 'Installed Page' message that refers and aims at PALE MOON, seems a good idea. Which, that seems to be what 'Mathwiz' wants to do it too (per last message). (For amusement) NOT feeling it here, some special need to CRY HAVOC, and Let Slip The DOGS of RE-BRANDING CONTROVERSY (War). Added Later: I think what 'Mathwiz' said in his last message (above), is winning logic. Added Still Later: 'Mathwiz' has FIXED most of the HELP URLs related to RT's Browsers. And 'Mathwiz' has opened a GITHUB website to help with the overall RT Browser situation: https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1167289 Conclusion: There are likely to always be a couple of HELP URLs related to RT's Browsers that might point to a 'wrong' URL somehow. 'Mathwiz' has done what is reasonable to remedy the overall situation. The improvement is significant.

It hurts a bit that some usually very great people here have such extremely onesided black&white views, and don't even consider for a second that things might possibly have other angles too. In this case there's just clearly an elephant in the living room (or rather a duck, it looks like a duck, it walks like it, it has 'duck' written all over it, etc). But it won't go away just by insisting it wouldn't exist. And neither by calling everyone who sees it a moron. And even consider them super morons just because the first person who complained about the elephant-duck was a horrible person, and insist yet harder that there's absolutely NO elephant in the living room. And if people continue to mention it, to accuse them of blind obedience to that horrible guy. But the elephant is there, and as long as problems are denied they will only grow worse.

@TechnoRelic I have already made my position very clear in the matter at hand, in previous posts of this thread: I feel totally indifferent to the whole re-branding issue, in fact I am quite alright with how things were/are now; @roytam1 is NOT compiling builds with the official branding, this is crystal clear; the whole re-branding argument has been always pushed by MCP and/or Matt A. Tobin; I am not confused in any way as to what I am using on my Vista laptop currently ; I might sound harsh, but Roy is NOT to blame whenever some NM/Serpent user knocks on MCP's door; the fault lies, IMHO, solely on those users, who can't tell their right hand from their left one (and, as said already, full rebranding won't relieve MCP of random NM users and/or make them think about us - maintainer+users - in another way; for them, we'll always remain XP+Vista freaks ) ... The recent PRs by @Mathwiz were submitted after you have, apparently, taken sides with MCP/M.A.T in your recent post ; you have yourself appointed only myself and Mathwiz as the users who should be consulted about your "re-branding" expectations, but this leaves out numerous other NM/St users who might not be as vocal in the forums here, but their own opinion should also carry weight... Mathwiz created his PRs as an interim and "easy" solution, with the hopeful aim of deterring additional NM users from seeking support at MCP's HQs; twice you said "is FINE with me", but it now becomes apparent, even after the PRs have been created, that you won't feel satisfied unless a full rebranding takes place: in other words, in your own subtle way, you are coercing @roytam1 to proceed into full re-branding, echoing MCP/M.A.T 's agenda... Roy shouldn't be forced to make any additional efforts, he's working wonders as it is, regularly providing browser builds for a plethora of older OSes/platforms... And this is my final say on this...

Well, I've tested it until today, and finding it works OK for me, too, have just bought the license to have it permanently in premium mode. I've kept MSE, however, because MBAM doesn't require the removal and it remains capable of detecting all that was known to the last definitions file. Moreover, as you all have posted, removing it seems to be a PITA, and I'm not in the mood for such a experience these days. Thanks for the suggestion, @Dave-H! You do rock! And thanks for all who posted here till now, besides Dave. All your posts helped me a lot in deciding what to do. It's wonderful to belong to such a helpful and knowledgeable coummunity!

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!

If you have access to a Win7+ computer, then consider installing KAF19 (Kaspersky AntiVirus Free) on your off-line XP machines ( as suggested by @BTTB ) and then use latest Kaspersky Update Utility on the on-line Win7+ machine to download latest KAF19 definitions: The "def" files can be then transferred to the XP machines via, e.g., a USB flash stick and then installed via a process probably detailed in the Kaspersky Support Site (or just Google/Bing/DDG for it ). EDIT: Support link => https://support.kaspersky.com/11705 Unfortunately, latest KUU v3.2.0.153 is build on Qt 5.8 framework, which requires Win7+ (thus, I can't test it here on Vista... ). EDIT2: Last XP+Vista compatible version of KUU is v3.1.0.25 (built on Qt 4.6); official download link (retrieved via web.archive.org ): updateutility_win_3.1.0.25_release_en.zip Once run for the first time, start an update to populate the "Applications" list with latest KAF entries...

Kaspersky Free working on XP No off-line updates as far as I know.

After several testing conducted in pm with looking4awayout it is noted that problematic site causing RT1_F45ESR (45.9.15-2019025) crash doesn't dipend on the UOC Patch (which in truth is a solver, removing plugin-container), but on the Roytam1 version itself. Unlike what was done previously all tests were conducted on clean browser installations. Summing up: Firefox 45.0.1 (if you install original FF 45 ESR, it's soon automatic upgraded to 45.0.1) - OK RT1_FF45ESR - CRASH RT1_FF45ESR + UOC Patch - OK The only way to get patch working (for me as it's proven) is doing both of the following action: 1) put UOC_Patch45.js in C:\Program Files\Mozilla Firefox\Defauls\Pref\" folder 2) rename another instance of UOC_Patch45.js as prefs.js and putting it in C:\Documents and Settings\(Your Username)\Application Data\Mozilla\Firefox\Profiles\(Your Profile folder)"

Yes; M$ sort of added insult to injury. They weren't satisfied with just disabling future updates, thus rendering MSE useless; they also gave us a non-working uninstaller so we couldn't even get rid of the $#@$^ thing! Oh; forgot to mention that even after disabling the anti-malware service and killing the msseces.exe process, I still had to use Unlocker to completely delete the directories. I guess you wouldn't want it to be too easy for malware to do a rogue uninstall, so maybe this makes sense - but that's all the more reason the official uninstaller should work! Oh, well; at first blush I'm quite impressed with Avast. It did falsely trigger on ProxHTTPSProxyMII, but that's understandable; that is a MITM after all! I'm glad I'm one of the lucky ones Avast seems to run OK on. Probably should've ditched MSE for it years ago.

It is easier to use the Autoruns program (https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns). In the "filter" window, enter: microsoft security client and then deselect all displayed items. This is effective if the MSE has been installed in the folder with the default name: Microsoft Security Client. And: 1. Disabling the Microsoft Antimalware Service At the end you need to restart the computer.

That's a good point. It would therefore be best not to have the browser point directly to specific pages at msfn.org, since the URLs could change. They could point to msfn.org indirectly, though, via a redirect. Yes, for New Moon that will work fine. Edit: In fact I see it's already up (although the page is blank for now). I'll make that change tonight. For Serpent, you would need two related pages: https://<something>/ and https://<something>/keyboard-shortcuts. Each of those two pages can bring up either a static page or a redirect. The first page will come up if the user goes to Help / <browser> Help. The second page will come up if they go to Help / Keyboard Shortcuts. Mozilla's pages are already arranged that way, so I just left the app.support.baseURL pref in Serpent pointing to Mozilla's site for now.

I too use Symantec Endpoint Protection (Client) version 12.1.6 on one of my WinXP machines. It is very heavy on the hardware, but is also very reliable and relatively easy to configure. Updates will be coming for at least one more year from now.

Ironically, the problems you noted with the "unofficial.shtml" page are MCP's own doing. They own the www.palemoon.com Web site, and they programmed "unofficial" browser builds (i.e., New Moon) to open that page. They do have a disclaimer about support, but given how sensitive they seem to be about not calling unofficial builds "Pale Moon," it's amusing that their own Web page for unofficial builds commits that very same error. If Matt or anyone else hassles @roytam1 about "misrepresenting" his browser again, it might be worth pointing out that it's MCP's own "unofficial.shtml" page that's doing a good bit of the "misrepresenting." Since all "unofficial" builds are called New Moon, surely their Web page for those builds should call it New Moon as well, or at least use wording like "unofficial build of Pale Moon" vs. just plain "Pale Moon." FWIW, I do think @roytam1 should develop his own branding, but that has proven to be more easily said than done; we can't even come up with a browser name that everyone's OK with! ("New Moon" is just MCP's default name for unofficial Pale Moon builds.) Maybe @roytam1 should be a "dictator" on this question and just pick a name he likes. (Or maybe it's been New Moon for so long, he's grown to like the name "New Moon.")

For those of you that don't know. There is a new 2019 update for XP / XP x64 & Server 2003 / Server 2003 x64 ! https://www.catalog.update.microsoft.com/search.aspx?q=4500331.

I believe I just found some new stable drivers and am also currently testing some others to make sure they work properly. So, hopefully if all goes well there will be new stable drivers uploaded by me.

So, if this update is so crucial, why exactly aren't they pushing these updates automatically? Last I checked, Windows update service still works on Windows XP.

The community is stronger with members like heinoganda that do good work, thank-you. For users willing to put in a few hours of labour while the official updates are readily available, just perform a fresh install on a spare partition, download and apply all applicable updates, save and archive them from the download directory for future re-use. Activate the new installation while you're at it, in case MS stops the service, and you have a fresh new install ready to go as a backup. Is there a chance MS would stop online or phone activation? I noticed the online Microsoft update library still even had Windows 2000 updates available for manual download. Will the download library be shut down later this year too or just the ability to automagically apply system updates?

@maxtherabbit At your request, a list for nonSSE2 processors.

that is outstanding! is it or could it be possible to have a way to exclude updates that require SSE2?

Ok, but does it mean Windows Update Service, or wiping out patches from the catalogue as well?