Leaderboard

Yes, I would appreciate it too so it will be released when it is ready. Current status is that it does not work correctly yet. On the other side, I doubt that someone needs to upgrade to new builds immediately when it is released, especially when some needed software is not compatible with it.

Well, it is not that you are a newb, it is not like the link explained it much. To try applying the patch you need to have the ACPI.SYS which version ends in v.5512 Then you need a hex editor (any will do) You need to open the file and check that at offset 0x00034214 there are bytes (I believe): 7C xx corresponding to JL: http://faydoc.tripod.com/cpu/jl.htm with the hex editor replace those two bytes with: 90 90 correspondng to nop, nop. jaclaz

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200801-4d76d4e-uxp-091749192-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20200801-4d76d4e-uxp-091749192-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.rths.ml/basilisk/basilisk52-g4.6.win32-git-20200801-4d76d4e-uxp-091749192-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.rths.ml/palemoon/palemoon-28.10.1a1.win32-git-20200801-c485a110c-uxp-091749192-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.1a1.win64-git-20200801-c485a110c-uxp-091749192-xpmod.7z Official UXP changes since my last build: - Issue #1587 Part 11 (followup 1): Implement multithreaded signals for workers. (84cb85484) - Issue #1587 Part 12 (followup 2): Allow clearing of signal by setting to null. (f0ef003f3) - Fix line endings. (62640d775) - Merge branch 'abortcontroller-work' (1977b8de3) - [MailNews] Allow ordering of accounts to respect mail.accountmanager.accounts (39be34c06) - [MailNews] Allow setting "Local Folders" as always the first displayed account (9ac440aa7) - Follow up to 39be34c06 - The check sound be if not ordered (8698bde00) - Revert "Follow up to 39be34c06 - The check sound be if not ordered" (d826eda73) - Follow up to 39be34c06 - The check sound be if not ordered (d7d4567ff) - Revert "Follow up to 39be34c06 - The check sound be if not ordered" (13096ddf1) - Follow up to 39be34c06 - The check sound be if not ordered (15ed0691f) - Issue #1391 - Remove the DOM battery API (08fb2f306) - [network/dom] Improve sanitization of download filenames. (3b0123aa1) - [js] Fix Sink to check for non-recoverable operands. (d84749b0f) - [xpcom] Make Base64 compatible with ReadSegments() with small buffers. (eb845c094) - [js] Don't improve TypeSets containing the magic-args type. (572e7502b) - [dom] Fix a spec compliance issue with the HTML LS regarding script loading. (e655ce397) - [WebRTC] Stop putting addresses in the cookie chunk. (9d155b45c) - Improve dll loading on Windows. (0a8c53ff3) - Issue #1614 - Update en-US Dictionary (947c9d4d5) - Issue #1615 - SunOS LDAP cleanup. (efab8cdf3) - Merge pull request #1616 from athenian200/solaris_ldap_work (0afbef750) - Bug 1318570 - Clean up GetTextNode into TextEditRules. (392aa3987) - Merge pull request #1618 from g4jc/libeditor_patch (091749192) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Update back-end branch pointer (Unstable 2020-07-27) (1718b43a8) - Issue #1772 - Follow-up: properly reference restoreOnDemand (oops!) (cd8e8c19b) - Clear user prefs for AbortController on migration to reset it for users who have disabled it for web compat in the meantime. (c485a110c)

... Considering that the title of that thread on the Windows XP subforum is "On decommissioning of update servers for 2000, XP, (and Vista?) as of July 2019" i.e. our beloved OS is inside parentheses and with a question mark, and given the, admittedly, low respect XP-diehards hold for Vista (), I would suggest a separate dedicated (pinned?) thread/post be posted in the main Vista subforum, wouldn't you agree @greenhillmaniac ? FWIW, a casual search on the Vista subforum has revealed an entry that hasn't (till now...) attracted much attention, Should be helpful for the duration Vista .msus are kept online in the catalog by evil M$... There's also another thread with a very promising title https://msfn.org/board/topic/179120-windows-vista-post-sp2-updates/ but, sadly , NOT the content one would expect going by that title... =========================================== Semi-OT: Vista SP2 reached its EoS without ever getting support for either TLS 1.2 nor SHA-2 code signing ; so I am inclined to believe that all Vista SP2 created MS updates were sha1 code-signed; in https://support.microsoft.com/en-us/help/4569557/windows-update-sha-1-based-endpoints-discontinued so what breaks WU for Vista SP2 is the secure connection negotiation to those WUS SHA-2 endpoints (CDNs); connections which, and this isn't said explicitly, have been probably updated to use TLS 1.2 ... I don't think MS will touch and re-sign with SHA-2 sigs existing WS2008SP2 sha1 update packages (and certainly not the Vista ones...); but we, Vista users, are extremely unlucky : While we can implement postEoS TLS 1.2 support, installing KB4474419 (even v1 with a digital sig of 16/04/2019) + KB4493730 will, as pointed out elsewhere by @Vistapocalypse , change the kernel version to 6.0.6003.205xx; while that is fine with WS2008SP2 and WU, the latter had been probably configured in a way to only serve Vista with a 6.0.6002.xxxxx kernel version... And no-one has found (yet?) a way to (cheat and) make Vista appear in the eyes of WU as WS2008... Another question that comes up is if the Vista MS updates were hosted on special "outdated (SHA-1) Windows Update service endpoints used only for older platforms" that are "now being discontinued", does that mean that the update packages themselves will cease being on line on WU servers? If so, any (theoretical) discussion about re-enabling connections to WU from Vista will be a moot one... ... As The Doors sang many decades ago:

I suspect that there might be more interest very soon. See my post here, and BTW posting there might be better than of flurry of OT posts in this Server 2008 thread such as we saw last summer. Edit: See new Windows Vista Update Repository thread!

It was from the latest Intel Chipset Drivers I could find. Intel doesn't provide .sys files in their drivers. They use .sys files that are included in Windows.

Hello, Crusader Kings 2 and Europa Universalis 4 work very well. https://imgur.com/a/S4Y9KvB

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.ml/boc-uxp/mailnews.win32-20200801-2260e89d-uxp-091749192-xpmod.7z Browser-only Suite Win32 https://o.rths.ml/boc-uxp/bnavigator.win32-20200801-2260e89d-uxp-091749192-xpmod.7z source patch (excluding UXP): https://o.rths.ml/boc-uxp/boc-uxp-src-xpmod-20200801.7z Official repo changes since my last build. - Update platform commit pointer (56e38213) - Update platform commit pointer (53936a63) - Remove MOZ_MAIL_LEGACY flag except from ClassicTB2. (748db910) - Merge pull request #104 from athenian200/moz_mail_legacy_removal (fa583858) - Issue #95 - Remove OS Search Integration (51b1178f) - Merge branch 'TRUNK' into removeSearch-work (1ac2f93e) - Merge branch 'removeSearch-work' into TRUNK (50260d73) - Sort out app vs branding prefs and move some urls to branding (f6142f73) - Update platform commit pointer (3736560e) - [Mail] Remove un-needed js code from aboutDialog.js (1e5b59ad) - [Mail] Update about:logo to include the brand wordmark (6f300932) - module.ver ISN'T processed by the preprocessor (ac6bb340) - Add branded 7z sfx (4c7eb9c8) - [Mail] Disable plugins completely by default (b3cf3192) - [Mail] Remove un-used mail.tabs.drawInTitlebar pref (46b4bb48) - [Mail] Remove un-used chat core prefs (2260e89d) -- New build of IceApe-UXP for XP! Test binary: https://o.rths.ml/gpc/files1.rt/iceape.win32-20200801-id-eed056673-ia-41157bf-uxp-091749192-xpmod.7z for UXP changes please see above.

Some readers may not know what a broken record sounded like. In the days when music and other audio was sold on vinyl records, a crack or scratch often prevented the stylus (needle) from following the groove containing analog audio. In some cases the stylus skipped forward, but in a good many cases it skipped backward, causing the same passage to repeat over and over until someone intervened to break the cycle. I have seen many of your posts far and wide. Your preferred topic is always old Vista patches, but you seem to have an aversion to post-EOL patches (such as the one that was required to solve this thread), and you seem to believe that Firefox 52.9.0 is the only browser worthy of discussion. Your “broken record” analogy seems appropriate.

Confirmed. Those Windows 6.0 updates were released in 2019, so this thread’s title is somewhat perplexing (nothing has changed). You should definitely install the April 2019 SSU first. I would recommend that you then install the September 2019 SSU KB4517134, but I haven’t experimented enough to say that it is “required” for your purposes. Finally, install the latest version of KB4474419. (The first version had issues.) But if your objective is to salvage Windows Update for Vista, I’m afraid you are barking up the wrong tree. Any update for Windows 6.0 released in April 2019 or later will change the build number to 6003 (updates for IE9 being the only exception I know of), and it has been found that Windows Update gives “Vista 6003” the cold shoulder - but by all means try it yourself sometime.

Can anybody confirm that YouTube with the Classic interface no longer works with the "Mozilla/5.0 (compatible; Googlebot/2.1) User Agent override? R.I.P YouTube Classic, July 10th 2020.

My guess would be Update your browser for the best viewing experience. Actual link is (no surprises there) : https://www.youtube.com/supported_browsers Except for Firefox Browser (which is simply a Chrome wannabe ), all three other alternatives are Chromium based...

The most important advantage of the Classic Layout, especially for old browsers, is that it gets displayed without JS too, for at least seeing what the video is about, description, date, number of downloads, likes etc. And then it's possible to get direct video links with sophisticated userscripts. But with old system, old browsers, short on RAM etc, and blocked JS (which would only freeze anyway) it's a disaster now: neither Mobile nor "Modern" Layout shows anything ecxept gray fields or black box, zero text, and the direct embed-link only opens an error page. Which doesn't contain even descriptions in the source. At the moment my only one -lousy- workaround for any non-Classic view is to load the full (300kb) page source with Ctrl+U in Notepad++, then run Plugins > JS Tool > JS Format, and scroll down to almost bottom to finally see some readable text at least. How to get the video download links the future will tell. Perhaps using 3rd-party websites again, or someone can update the userscripts?

I'd like to know the difference between 52.9.1 and 52.9.0, so I checked from https://hg.mozilla.org/releases/mozilla-esr52/pushloghtml/1 to https://hg.mozilla.org/releases/mozilla-esr52/pushloghtml/8 Firefox related changes are all like ffxbld — No bug, Automated blocklist update | No bug, Automated HPKP preload list update | No bug, Automated HSTS preload list update from host bld-linux64... Except one: Mihai Tabara — Bug 1471223 - have automation update firefox-sha1-ssl bouncer entry too. r=rail a=release And that Bug 1471223 seems trivial: as I understand it's for firefox-sha1-ssl version (don't know exactly what that version is for) not auto-update to latest 52.9 version correctly. Maybe that's why Mozilla did not release it. No need to update at all. Yet I have downloaded and run it, I'll keep using it.