Leaderboard

It installs after fooling the installer into thinking it's running on Windows 10. Installed programs seem to function without issues at first glance without any workarounds. No luck running the installer on Windows 7. It wants SetCoalescableTimer function (Windows 8 and up), which I could redirect to SetTimer, but then the exception is thrown in msxml6.dll and I don't know how to proceed further.

Considering the assumptions in my older posts quoted below remain mostly valid and that most new internet users do so on smartphones... The last time I've estimated the size of the full PC universe, as you can see in the quotation above, I came to 2 billion machines. Let's assume it didn't grow any, just for the sake of simplicity, and that means 5.66% of 2x109 = 113x106 machines or, in other words, there's still a minimum of about 100 million XP users today, not counting the true POSReady and related machines, which purportedly don't browse the web, so that they don't get counted by netmarketshare. So no, not at all, we're still very far from being the last half-a-score of XP users in the world!!! ... we should still have a desktop user universe of not more (probably somewhat less) than 2 billion users. Now: 3.19% x 2 x109 = 6.38 x107 & 2.51% x 2 x109 = 5.02 x107 ... to get to an estimate that minimizes our ignorance, let's take the geometric mean of those two values and we get 5.66 x107, which means there should still be some 50 million XP users today, which is not bad, considering we're 6 months away from POSReady 2009 EoS.

This is a very interesting and needed project for all 10 users, still on development, but so far: See the project on Github: https://github.com/DavidXanatos/wumgr/releases/ Build using .NET Framework 4.6.0 alacran

Except for corporate license holders, but that's only because MAJOR money is involved

Don't hold your breath: they're not even trying to give a damn...

All my 5 PCs at home are running Win7x64 SP-1 updated up to December 2017, Browser is Firefox on all, but two of them also have Google Chrome, AV is Avast Free, and also have Malwarebytes Antimaware Free only to run on demand (just in case), not a single problem so far. Also all of them can dual boot Win10x64 Pro from another partition since I got and ID for them during free update, but nobody here use Win10, all they have an old 10 version. Only one PC has Win10 with a more recent version 1709 updated to December 2017, but updates dissabled, used mainly for running PEBakery to make some new WinPEs. I installed on this PC on a VHD (just to test) the 10x64 Pro 1809 (downlodaded last week with MCT) and I was able to see during second reboot a message saying something like Deleting or maybe Cleaning all old files on user profile, but since it was on a VHD I assume only files on that VHD were affected by this, I didn't loose any file on the HD Documents partition. So since thread title is UpdateWin 7 or Not? = I may say yes but only upto December 2017. Update to 10 = Better don't, it do not have any advantage over 7 and on the contrary it has all disandantages, it is Malware by definition, and ALL updates have a problem, especially the last one that can make you lose all your documents, you can never trust on MS anymore. Best Regards alacran

Lately I tested MSFN again with Opera 12.02. No problems anymore, I can sign in etcetera in normal Author mode. Only limitation I have is that the link to www.msfn.org/board is not visible, but can be reached by clicking in the upper left of a post (apart from some empty symbols). Thanks to the MSFN staff if they made this possible Posted with Opera 12.02 & Windows 98SE with original KernelEx

+1. Let's let Roy concentrate solely on that, which is of paramount importance to both XP and Vista communities.

Actually, this is normal; you should realise that while the UXP platform was forked from a Firefox ESR 52.6.0 platform snapshot, the application Pale Moon 28 itself (built on the UXP platform) does not implement the Australis GUI, much like its previous major version 27. The feature you describe was added on top of the Australis interface (Fx >=29.0) by Mozilla developers and should be there in both Firefox ESR 52.9.0 / Basilisk 52 (Serpent 52.9.0), as long as you do not move the "Zoom Controls" button (- +) to a browser toolbar; this native browser feature was not present in the pre-Australis (Fx <=28.0) Firefox GUI that PM uses... There's nothing to fix here, as explained above; BTW, you should not expect @roytam1 to implement major new features in New Moon 28 (his fork) that are not yet present upstream, i.e. in original Pale Moon 28 source (master branch); the way I see it (and please someone correct me if I am wrong), Roy's main focus is/should be creating and testing patches to Pale Moon that will enable it to run on Windows XP + Vista, both OSs that the official app has dropped support for; main browser code is still the task for Moonchild Productions; if you do find a bug inside Roy's patches (that enable XP+Vista support), by all means report it here, but GUI improvements + implementation of new features should not, IMHO, be a thing for Roy... In any case, if you want the requested functionality in New Moon 28 (currently at version 28.2.0a1), you can install an extension which offers pretty much the same thing, Zoom Page v15.7 (it creates a button that can be placed inside any toolbar, but, sadly, not inside the URLbar): I think it's universally accepted there's no software that is bug-free; however, your bug reporting skills are very flimsy in this case; please read Information to include when asking for support ; providing just a screengrab without further info (e.g. the URL details of the page where this occurs) so other people here can test and try to reproduce results in pure sensationalism, with slim chances of a resolution of your issue... Please understand I have nothing personal against you , my advice above was simply offered so us members here can help each other in a more productive manner... Regards

Out Noscript 5.1.9.

@WinClient5270 That small patch to make Rufus work on Vista is still applicable to version 3.3. I updated the binaries. It says version 3.4 because it's compiled from the source code iteration with this commit and the author bumps the version right away after making changes after publishing the official binaries. So apart from some Italian localization typo fixes, it's identical to 3.3. I'll probably put it on my GitHub account at a later point in time as it's more suitable place for such things. Just have some other things on my mind ATM.

... *and*... 5) Never forget to wear your own Velostat cap while browsing the web!

Do try the latest Basilisk, then. Basilisk/UXP is forked from FF esr 52.x.x and is being compiled for XP by @roytam1, in parallel to New Moon. But, IMO, Basilisk/UXP is the best alternative, in what regards overal compatibility... it's sort of like if FF esr 52.x.x were still being developed, and with XP-specific support in mind, on top of it.

Ublock Origin 1.17.0 for Firefox still support v52.9 ESR https://github.com/gorhill/uBlock/releases/tag/1.17.0

I have, with the help of many other Vista users on here, created just the post for that

There was a fix from MS for this: MicrosoftFixit50688.msi not easily available anymore, But I found it here.

Have you ever wanted to pause a NT Command Script, without using the ping command, vbs or a third party utility? Here's my way of doing it! (see the bottom of this post for the attached file) This is an NT Command Script, (batch file), just place addelay.cmd somewhere in your path and call it from another script, like this: CALL ADDELAY [mins] [secs] Where [mins] is an integer representing the number of minutes you wish to delay for. and [secs] is an integer representing the number of seconds you wish to delay for. If you don't wish to have any minutes, your first parameter, [mins], should be 0 Examples: CALL ADDELAY 0 15 delays the running NT Command Script by 15 seconds CALL ADDELAY 1 7 delays the running NT Command Script by 1 minute and 7 seconds CALL ADDELAY 3 delays the running NT Command Script by 3 minutes CALL ADDELAY 0 72 delays the running NT Command Script by 72 seconds Additionally: CALL ADDELAY displays an error message and delays the running NT Command Script for five seconds CALL ADDELAY 0 displays an error message and delays the running NT Command Script for five seconds CALL ADDELAY 0 0 displays an error message and delays the running NT Command Script for five seconds This is not intended to be a precision timepiece, so please don't start complaining about it being slightly inaccurate. I know it is, but it does the job for which I intended it. I hope it is useful! addelay.cmd