Leaderboard

Hey guys, I put together an installer for Roy's browsers. It checks a file on my server to see the latest version (keeping that updated shouldn't be an issue for me) and then it downloads the latest browser version from roys site and installs it. Currently it supports Basilisk (x86 and x64), and New Moon (x86 and x64). Tested OSes with the installer include XP and Vista (both x86 and x64 editions) Other builds are not currently supported due to the sometimes irregular build interval http://i430vx.strangled.net/files/XP/RoyTam Browser Installer.exe If you find any bugs, LMK Thanks for @WinClient5270 for noticing that you must have the visual basic runtime installed first for the installer to work. (Install VC Redist 2008 from Microsoft)

New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190209-4adc40988-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190209-4adc40988-xpmod.7z diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z PM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win32-git-20190209-4adc40988-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win64-git-20190209-4adc40988-xpmod.7z Official repo changes since my last build: - Consolidate tracing and traversing. (978f50dda) - Remove NS_IMPL_CYCLE_COLLECTION_TRAVERSE_SCRIPT_OBJECTS (1f9ab3a6e) - Merge branch 'master' into cycle_collector-work (1a04d73a1) - Increase purple limit triggers for CC. (babedf6c6) - Increase slice time for longer running CCs. (888fbacfe) - [AM] Remove spurious warning for staged cleanup. (e4a3b28c8) - Pale Moon: Use file path for bookmarks import/export. (aaa9fc180) - [Pale Moon] Use mousemove events instead of MousePosTracker for hiding the navigation bar in fullscreen * Tag #336 (192715be5) - [Basilisk] Use mousemove events instead of MousePosTracker for hiding the navigation bar in fullscreen * Tag #336 (74e88de9e) - Fix build error with JS_HAS_TOSOURCE undefined. (f8f3dc70b) - Merge pull request #958 from Ascrod/master (fa311a4ca) - issue #908 - implement missing parts of CSS mask (b241a84d8) - Merge branch 'cycle_collector-work' (9a8a05029) - Merge pull request #961 from kn-yami/issue908 (4874970d3) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (23f587278) - Merge pull request #959 from FranklinDM/fullscreenpatch-v2 (5fde5ba78) - Include blankthumb in the correct file. (f560671b6) - Make sure Glass doesn't override LWT style for the title bar. (e05715609) - Add "check for updates" to main menu and AppMenu (d9a054988) - Revert "Add "check for updates" to main menu and AppMenu" (8db772d2c) - Align `instanceof` with the final ES6 spec. (88db0108b) - Fix possible data race while updating scope object during compacting GC. (f8db3a89b) - Get RefPtr to transaction before using it. (DiD) (2b1ccf227) - Never let "localhost" get sent to a proxy. (6567bb631) - Handle pasted data of certain types with an odd length. (0b6d9a470) - Use existing image decoders to handle clipboard BMP data. (6992106dc) - Revert "Increase purple limit triggers for CC." (d6f995701) - [BASILISK] Update AM preferences to point to the Basilisk Add-on Site (5c46e60ad) - [BASILISK] Update AM preferences to point to the Basilisk Add-on Site - Part 2: Add domain to permissions file (4adc40988)

New Palemoon 27 Build! * This build is beyond official 27.9.4 build. 32bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win64-git-20190209-7450defff-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from rmottola/Arctic-Fox: - Bug 1139152: IonMonkey: Don't improve types at MTypeOf for unknown types (d67dad359) - Bug 994016 - IonMonkey: Improve type information at branches with TypeOf (boolean, you are worthy too) (c90a6d6fc) (d9bf24c13) - import changes from rmottola/Arctic-Fox: - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042) - Bug 1270591. Add support for checking for AVX & AVX2. Detecting AVX2 requires the use of a sub-leaf. (789319bd0) (eb895d30f) - import changes from rmottola/Arctic-Fox: - update libwebp to 0.6.1 (afa956138) - fix build on intel for libwebp 0.6 (97193d7a0) (7174a5119) - import changes from rmottola/Arctic-Fox: - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476) - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08) - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017) - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90) - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4) (74aff1670) - import changes from rmottola/Arctic-Fox: - Bug 1077002 - Give a better error message when showModalDialog is used (18d8ecc12) - Bug 1135792. Stop assuming that every binding for a global with a non-worker descriptor is a binding for Window. (dd0260c12) - Bug 1135810. Add more explicit checks for whether a descriptor wants Xrays or not instead of assuming that Xrays are desired if and only if descriptor.workers is false. (17ef71544) - Bug 1050456 - Part 1: Prevent prerendered pages from showing the slow script dialog (173044922) - Bug 1050456 - Part 2: Add a nsGlobalWindow::GetIsPrerendered helper (ac680a5f7) (805fc48eb) - reverting rmottola/Arctic-Fox changes in order to bisect memory leak and greasemonkey issue: - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb) - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34) - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da) - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340) - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313) - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256) - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85) - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979) - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2) - Bug 1137523 part 2 - Unprefix a few js_* functions I forgot in part 1 (e6beaf0d8) - Bug 1135816 - Handle unboxed object receivers when compiling getter/setter calls in baseline/Ion (82233087e) - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042) - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476) - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08) - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017) - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90) - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4) - Bug 1077002 - Give a better error message when showModalDialog is used (18d8ecc12) - Bug 1135792. Stop assuming that every binding for a global with a non-worker descriptor is a binding for Window. (dd0260c12) - Bug 1135810. Add more explicit checks for whether a descriptor wants Xrays or not instead of assuming that Xrays are desired if and only if descriptor.workers is false. (17ef71544) - Bug 1050456 - Part 1: Prevent prerendered pages from showing the slow script dialog (173044922) - Bug 1050456 - Part 2: Add a nsGlobalWindow::GetIsPrerendered helper (ac680a5f7) hopefully we can re-apply them later. (e1881afe9) - re-apply rev 805fc48eb20f089ae0b815ce137bd64d6993f451 (d1c585ecf) - re-apply rev 94617d85eb5ab3369bb44b099be3c6c4174fe6f6 (e07628294) - re-apply following changes: - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313) - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979) - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2) - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042) (7450defff) following changes seem causing issues and they are reverted for now: - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb) - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34) - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da) - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340) - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256) - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85) - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476) - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08) - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017) - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90) - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)

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.

Warning: until the situation becomes clearer, I think it better to block MS16-023 on 7 SP1 and 8.1. Please read this, and remember It's easier (and surer) to block now, and decide to add it in the future, than trying to remove it later, instead. My 2¢. KB2952664 "Compatibility update for upgrading Windows 7" This update helps Microsoft make improvements to the current operating system in order to ease the upgrade experience to the latest version of Windows. KB2976978 "Compatibility update for Windows 8.1 and Windows 8" Describes an update that improves the compatibility and upgrade experience in Windows 8.1 and Windows 8 This update performs diagnostics on the Windows systems that participate in the Windows Customer Experience Improvement Program in order to determine whether compatibility issues may be encountered when the latest Windows operating system is installed. This update will help Microsoft and its partners ensure compatibility for customers who are seeking to install the latest Windows operating system. KB2977759 "Compatibility update to Windows 7 RTM" This update performs diagnostics on the Windows systems that participate in the Windows Customer Experience Improvement Program. These diagnostics help determine whether compatibility issues may be encountered when the latest Windows operating system is installed. This update will help Microsoft and its partners ensure compatibility for customers who want to install the latest Windows operating system. KB2990214 "Update that enables you to upgrade from Windows 7 SP1 to a later version of Windows" It is an update to the Windows Update Client. It is a pre-requisite (for now) in order to be able to "update" to Windows 10 when it becomes available. This is the actual correct download link. KB2999226 (also in CR) "Update for Universal C Runtime in Windows" It is an update that enables one to run windows 10 applications on earlier versions of windows. KB3021917 "Update to Windows 7 SP1 for performance improvements" This update performs diagnostics in Windows 7 Service Pack 1 (SP1) in order to determine whether performance issues may be encountered when the latest Windows operating system is installed. Telemetry is sent back to Microsoft for those computers that participate in the Windows Customer Experience Improvement Program (CEIP). This update will help Microsoft and its partners deliver better system performance for customers who are seeking to install the latest Windows operating system. KB3022345 (probably not offered anymore because it was superseded by KB3068708, of which more below) "Update for customer experience and diagnostic telemetry" in Windows 8.x and Windows 7 SP1 This update introduces the Diagnostics and Telemetry tracking service to in-market devices. By applying this service, you can add benefits from the latest version of Windows to systems that have not yet been upgraded. The update also supports applications that are subscribed to Visual Studio Application Insights. This update has been replaced by the latest update for customer experience and diagnostic telemetry that was first released on June 2, 2015. To obtain the update, see KB3068708 Update (of which more below) for customer experience and diagnostic telemetry. KB3035583 "Update enables additional capabilities for Windows Update notifications in Windows 8.1 and Windows 7 SP1" This update enables additional capabilities for Windows Update notifications when new updates are available to the user. It applies to a computer that is running Windows 8.1 or Windows 7 Service Pack 1 (SP1). Before you install this update, check out the Prerequisites section. It installs GWX.exe which has the description “Get Windows 10″ More info (myce on Apr 05, 2015): Update for Win 7 and 8.1 silently installs Win 10 downloader To remove this update easily, there's now also rn10950's "I Don't Want Windows 10" KB3044374 "Update that supports you to upgrade from Windows 8.1 or Windows Server 2012 R2 to a later version of Windows". This article describes an update that supports you to upgrade from Windows 8.1 or Windows Server 2012 R2 to a later version of Windows. This update has prerequisites. KB3046480 Update helps to determine whether to migrate..." for in Windows 8.1 and Windows 7 This update enables the system to determine whether to migrate the Microsoft .NET Framework 1.1 to a later version of Windows when you upgrade from Windows 8.1 or Windows 7 to a later version of Windows. This determination is based on the usage of the .NET Framework 1.1. KB3050265 Windows Update Client for Windows 7 and Windows Server 2008 R2: June 2015 This update addresses an issue in which system performance can be decreased during scans. This issue has the greatest effect on computers that have a small amount of physical memory. This update addresses an issue in which Windows Update scans can fail and generate a 0x8007000E error.General improvements are made to support upgrades to a later version of Windows. KB3050267 Windows Update Client for Windows 8.1 and Windows Server 2012 R2: June 2015 A change is made on the log level for %windir%\WindowsUpdate.log to reduce the frequency of certain events from exhausting log space. Fixes an issue for managed computers in which managed computers have to update drivers as a set. Driver sets are not processed by Windows Update during shutdown, and are still available to be installed after you restart the computer.Fixes an issue in which the files of an update may not be found by Windows Update (0x80070002) if the download operation spans multiple sessions.General improvements are made to support upgrades to a later version of Windows. KB3064683 (disclosed by MS in KB3184143) Windows 8.1 OOBE modifications to reserve Windows 10 KB3065987 Windows Update Client for Windows 7 and Windows Server 2008 R2: July 2015 KB3065988 Windows Update Client for Windows 8.1 and Windows Server 2012 R2: July 2015 KB3068708 (also in CR) Update for customer experience and diagnostic telemetry in Windows 8.1 and Windows 7 SP1 This update, aka DiagTrack or Diagnostics Tracking Service, introduces the Diagnostics and Telemetry tracking service to in-market devices... <snip> This kind of update helps the overall application experience on Windows, by improving the current operating system for upgrade to the latest version of Windows. <snip> By applying this service, you can add benefits from the latest version of Windows to systems that have not yet upgraded. KB3072318 (disclosed by MS in KB3184143) Update for Windows 8.1 OOBE to upgrade to Windows 10 KB3075249 (also in CR) "This article describes an update that adds telemetry points to consent.exe in Win 8.1, Win RT 8.1, Win Server 2012 R2, Win 7 SP1, and Win Server 2008 R2 SP1. This update adds telemetry points to the User Account Control (UAC) feature to collect information on elevations that come from low integrity levels." KB3075851 Windows Update Client for Windows 7 and Windows Server 2008 R2: August 2015 This update also resolves an issue in which certain Windows Update operations fail when you install Windows Update Client for Windows 7 and Windows Server 2008 R2: July 2015 (KB3065987) on Windows 7 Embedded editions." In other words: it also fixes the mess created by KB3065987. KB3075853 Windows Update Client for Windows 8.1 and Windows Server 2012 R2: August 2015 KB3080149 (also in CR) "This article describes an update for customer experience and diagnostic telemetry, for Windows 8.1, Windows Server 2012 R2, Windows 7 SP1, and Windows Server 2008 R2 SP1." KB3081954 (also in CR) Ensures users be able to continue using Work Folders after upgrading to Windows 10 from Windows 7SP1, and adds further telemetry! KB3083324 - Windows Update Client for Windows 7 and Windows Server 2008 R2: September 2015 KB3083325 - Windows Update Client for Windows 8.1 and Windows Server 2012 R2: September 2015 KB3083710 - Windows Update Client for Windows 7 and Windows Server 2008 R2: October 2015 KB3083711 - Windows Update Client for Windows 8.1 and Windows Server 2012 R2: October 2015 KB3090045 - Windows Update for reserved devices in Windows 8.1 or Windows 7 SP1 KB3102810 - Installing and searching for updates is slow and high CPU usage occurs in Windows 7 and Windows Server 2008 R2 KB3102812 - Installing and searching for updates is slow and high CPU usage occurs in Windows 8.1 and Windows Server 2012 R2 KB3112343 - Windows Update Client for Windows 7 and Windows Server 2008 R2: December 2015 This update enables support for additional upgrade scenarios from Windows 7 to Windows 10, and provides a smoother experience when you have to retry an operating system upgrade because of certain failure conditions. This update also improves the ability of Microsoft to monitor the quality of the upgrade experience. KB3112336 - Windows Update Client for Windows 8.1 and Windows Server 2012 R2: December 2015 This update enables support for additional upgrade scenarios from Windows 7 to Windows 10, and provides a smoother experience when you have to retry an operating system upgrade because of certain failure conditions. This update also improves the ability of Microsoft to monitor the quality of the upgrade experience. KB3123862- Updated capabilities to upgrade Windows 8.1 and Windows 7 This update adds capabilities to some computers that lets users easily learn about Windows 10 or start an upgrade to Windows 10. KB3135445 - Windows Update Client for Windows 7 and Windows Server 2008 R2: February 2016 KB3135449 - Windows Update Client for Windows 8.1 and Windows Server 2012 R2: February 2016 KB3118401 (also in CR) Update for Universal C Runtime in Windows It is an update that enables one to run windows 10 applications on earlier versions of windows. KB3138612 - Windows Update Client for Windows 7 and Windows Server 2008 R2: March 2016 KB3138615 - Windows Update Client for Windows 8.1 and Windows Server 2012 R2: March 2016 KB3139929 - MS16-023: Security update for IE: March 8, 2016 (because it brings, bundled, KB3146449 - Updated IE11 capabilities to upgrade Windows 8.1 and Windows 7 SP1)... which seems to be yet another nagging software to push Windows 10. [KB3146449 (not standalone: bundled into KB3139929 and allegedly removed by KB3184143) Updated Internet Explorer 11 capabilities to upgrade Windows 8.1 and Windows 7] KB3150513 This update provides updated configuration and definitions for compatibility diagnostics performed on the system. The updated definitions will improve accuracy and help enable Microsoft and its partners ensure compatibility for customers who want to install the latest Windows operating system. This update will be offered only if KB2977759, KB2952664, or KB2976978 is installed on Windows 8.1, Windows 8, Windows 7 SP1, or Windows 7 RTM. KB3163589 - Windows 8 and Windows 7 PC running an outdated version of Windows notification (aka NAG). KB3170735 - Windows 8.1 and Windows 7 SP1 This update adds the capability to notify you about future Windows Journal developments. (Woody's remarks). This seems to be Just Another Nagger, AFAICS... KB3173040 - Windows 8.1 and Windows 7 SP1 end of free upgrade offer notification (aka NAG). KB3192403 - October 2016 Preview of Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 KB3192404 - October 2016 Preview of Monthly Quality Rollup for Windows 8.1 and Windows Server 2012 R2 KB3192406 - October 2016 Preview of Monthly Quality Rollup for Windows Server 2012 These titles are a mounthfull, of course, and are nothing more than shameless euphemisms for "More Tracking Trash" !!! -------------***************------------- More info (InfoWorld on Apr 16, 2015): MS elaborates on KB 2990214, KB 3044374 Win 10 nagware! -------------***************------------- Summary: Now, there are some of these updates that come in pairs (pairing revised after reading post #111): KB2952664 for Windows 7 SP1 and KB2976978 for Windows 8.x. KB2990214 for Windows 7 SPx and KB3044374 for Windows 8.1. KB3050265 for Windows 7 SP1 and KB3050267 for Windows 8.1. KB3065987 for Windows 7 SP1 and KB3065988 for Windows 8.1. KB3075851 for Windows 7 SP1 and KB3075853 for Windows 8.1 KB3083324 for Windows 7 SP1 and KB3083325 for Windows 8.1. KB3083710 for Windows 7 SP1 and KB3083711 for Windows 8.1. KB3102810 for Windows 7 SP1 and KB3102812 for Windows 8.1. KB3112343 for Windows 7 SP1 and KB3112336 for Windows 8.1. KB3135445 for Windows 7 SP1 and KB3135449 for Windows 8.1. KB3138612 for Windows 7 SP1 and KB3138615 for Windows 8.1. KB3192403 for Windows 7 SP1 and KB3192404 for Windows 8.1. While the others are intended for both Windows 7 SP1 and Windows 8.x, namely: KB2999226, KB3035583, KB3046480 and KB3068708 (which replaces KB3022345), KB3075249, KB3080149, KB3090045, KB3118401, KB3123862, KB3139929, KB3146449, KB3150513, KB3163589, KB3170735 and KB3173040. And there is, in addition, KB2977759, KB3021917 and KB3081954, just for Windows 7 SPx. and also KB3064683 and KB3072318, just for Windows 8.1, of course! -------------***************------------- This list intends to cover both Windows 7 and 8. Some of the updates listed are offered to either 7 or 8, while others are offered to both. This list is a work in progress, which tends to grow with time. My main intent here is just to keep all relevant info as together as possible, for easy reference. Of course, the idea for this sticky post came from NoelC's post I quoted at the top of this very post. -------------***************------------- At this point (Oct. 31, 2015), the task of keeping track of all of this has become complex, so I do recommend the aegis.cmd script by thepower from voat.co (findable here) as a handy tool, that helps both with the avoidance of the "upgrade" do Win 10 and with privacy issues, too. Thanks are due to epic, for first suggesting its use on post #273. After runnining aegis.cmd, the Windows Update is set to check/notify, but I always reset it to off, and check manually, from time to time. One must keep eyes wide open, because some of the updates keep being re-offered, too, and need to be re-hidden! -------------***************------------- Alphabetized list specific to the OS for more convenient checking (courtesy of bphlpt ): Windows 7 SP1 Windows 8.x KB2952664 KB2976978 x KB2977759 KB2999226 x KB2990214 KB3022345 x KB2999226 KB3035583 x KB3021917 KB3044374 xx KB3022345 KB3046480 x KB3035583 KB3050267 xx KB3046480 KB3064683 KB3050265 KB3065988 xx KB3065987 KB3068708 x KB3068708 KB 3072318 KB3075249 KB3075249 x KB3075851 KB3075853 xx KB3080149 KB3080149 x KB3081954 KB3083325 xx KB3083324 KB3083711 xx KB3083710 KB3090045 KB3090045 KB3102812 xx KB3102810 KB3112336 xx KB3112343 KB3118401 x KB3118401 KB3123862 x KB3123862 KB3135449 xx KB3135445 KB3138615 xx KB3138612 KB3139929 xx KB3139929 KB3146449 KB3146449 KB3150513 KB3150513 KB3163589 KB3163589 KB3170735 KB3170735 KB3173040 KB3173040 KB3192404 KB3192403 x == Windows 8.x xx == Windows 8.1

Thank you. Many years ago I began archiving MS-DOS, Windows 3.1, and Windows 95 resources that in my opinion were increasingly becoming endangered but that were of historical significance. I eventually uploaded these online in 2011 as many of these resources are extremely rare and cannot be replaced. Having this stuff backed up with server redundancies and failover is a safer method of preservation. Some of the original links online for this softwareare dead (even with the wayBack Machine) which is where my site comes into play. I didn't want my physical media to be the only source, particularly since physical media tends to degrade over time. That gradually grew into numerous directories for NT 4.0, 98, 2000, and XP. I generally skipped ME and Vista as I was not fond of either OS. I think that people should have complete unfettered freedom to use the software they know and love. If it does the job it was intended to do, it's not obsolete. I don't think people should be forced along by "planned obsolescence" or by corporations whose interest is to make money.

Cooperation from XP enthusiasts might be helpful in many cases, but in this case has resulted in confusion. IE9 does at least support HTML5 (but not MSE), IE8 of course does not. I can't seem to find an official YouTube statement regarding final deprecation of Flash Player, but know of no reason to disagree with the OP of this thread. Support for Chrome Frame ended 5 years ago. When it comes to my own vintage Vista system, Chrome Frame would be as unwelcome as an Alien facehugger. The obvious workaround is to use a different browser for YouTube, but +1 for wishing this wasn't necessary.

idk what to say i just made an acc

All A while ago I discovered that Amazon Prime Video stopped working on Windows XP. Attempting to open it in Google Chrome or Mozilla Firefox fails with "Unsupported Operating System." Additionally, spoofing the browser as Firefox 53 or newer on XP will then tell you that Firefox is missing a DRM component. However, today I discovered that Amazon Prime Video works perfectly in SeaMonkey on Windows XP. Using SeaMonkey forces Amazon to use Silverlight, and it works flawlessly! This is very surprising to me since Silverlight has been mostly deprecated across the web. I'm surprised Amazon Prime Video is compatible with it. To download Silverlight 5.1.50907 (the final release), you can download it from my FTP here: http://sdfox7.com/xp/sp3/EOL/Silverlight5.1.50907.exe To download Sea Monkey 2.49.4, you can download the full version on my FTP here: http://sdfox7.com/xp/sp3/EOL/SeaMonkey Setup 2.49.4.exe

Ace Combat 7: Skies Unknown came out recently and I've been losing my mind over the sheer quality of its soundtrack. Dropping bunker busters on nuclear missile silos has never felt so good.

Do you connect your system to a domain controller? If so does the setting revert after you disconnect from the domain controller? I assume you have installed KB967715 and KB971029? Finding the relevant details in the pile of MS documentation can be problematic. But KB967715 has this to say: So you may need to change the key you are setting to be HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\NoDriveTypeAutorun 0xFF and I can't figure out why MS has so many articles describing use of the wrong key! There is also the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\HonorAutorunSetting 0x01 that is described later in the same article. You might need to repeat the steps in https://www.bleepingcomputer.com/forums/t/437944/how-to-disable-autorun/#entry2556075 for each USB stick you own, kinda tedious, and what about new sticks you do not yet own or haven't gotten around to adjusting settings for? So much for the MS way. A more interesting approach is at https://www.esecurityplanet.com/views/article.php/3848951/Two-Approaches-to-Securing-Autorun-and-AutoPlay-in-Windows.htm

The following code from Sky's e-mails uses Web Open Font Format (woff file), which is only supported as of IE9 and ensures long loading times. <style type="text/css">@import "//helpforum.sky.com/html/assets/toolkit.css";@font-face{font-family: "Sky Text"; src: url("//www.sky.com/assets/fonts/sky-regular.woff") format("woff")}@font-face{font-family: "Sky Text"; src: url("//www.sky.com/assets/fonts/sky-medium.woff") format("woff"); font-weight: bold}html, body, #MessageContainer{font-family: 'Sky Text', Arial;margin: 0;padding: 0;box-sizing: border-box;filter: progid: DXImageTransform.Microsoft.gradient(startColorstr="#c9c7d1", endColorstLOGNULL NowTransReader::ReadIt() JJFileMT::Truncate(122991) r="#fefefe", GradientType=1);background-image: -webkit-linear-gradient(left, #c9c7d1 0%, #e5e5ea 6%, #fefefe 20%, #fefefe 80%, #e5e5ea 94%, #c9c7d1 100%);background-image: -moz-linear-gradient(left, #c9c7d1 0%, #e5e5ea 6%, #fefefe 20%, #fefefe 80%, #e5e5ea 94%, #c9c7d1 100%);background-image: -o-linear-gradient(left, #c9c7d1 0%, #e5e5ea 6%, #fefefe 20%, #fefefe 80%, #e5e5ea 94%, #c9c7d1 100%);background-image: linear-gradient(to right, #c9c7d1 0%, #e5e5ea 6%, #fefefe 20%, #fefefe 80%, #e5e5ea 94%, #c9c7d1 100%);}.header-row{padding: 10px; -webkit-box-shadow: 0 1px 10px 0 rgba(0, 0, 0, 0.2); -moz-box-shadow: 0 1px 10px 0 rgba(0, 0, 0, 0.2);box-shadow: 0 1px 10px 0 rgba(0, 0, 0, .2);background-color: #fff;}<!--if[mso]>.footer-links table{float: left; width: auto !important;}<![end if]-->.footer-links table{float: left; width: auto !important;}.footer-links a:link, .footer-links a:visited, .footer-links a:active, .footer-links a:hover{font-size: 18px;} For e-mail programs such as Outlook Express and Windows Live Mail, where the Microsoft Viewer (IE) is used for viewing e-mails, the reloading of fonts can be prevented. At Eudora, I do not have this option, a suitable plugin for Eudora could provide a remedy, similar to an ad blocker where the code for reloading Web Open Font Format is removed. With the internal viewer of Eudora (HTML mails have problems with the reloading of pictures etc. with encrypted web server) there is no possibility to take over the proxy settings from the system (no use of HTTPSProxy possible), therefore the detour over the Microsoft Viewer (IE).

https://support.microsoft.com/en-us/help/895108/the-nodrivetypeautorun-subkey-value-is-reset-to-the-original-default-v Beware of viruses in USB because with some update, if automatic playback was disabled, it is activated again. It has happened to me for a few months and with gpedit.msc I have not managed to fix it. There is using: regedit.exe HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\Explorer\NoDriveTypeAutorun 0xFF Search here PTB: https://ryanvm.net/forum/viewtopic.php?t=10445

I realize we've gotten rather OT, but I can't help one more observation: Proxomitron and ProxHTTPSProxyMII may see a resurgence among Chromium users (Chrome, Edge, etc.) if Google follows through on their plans to cripple uBlock Origin and similar ad-blocking add-ons. Hey, Google: (Apologies to Queen) Anyhow, back to the question at hand: my original thought was to use Proxomitron to intercept the download of sky.net's toolkit.css and redirect it to a "fixed" version that would load the correct fonts. (I even figured out how to fix the .css myself!) But now I doubt it'll solve @Dave-H's original problem (long delays before the emails appear), because I'm pretty sure it only intercepts http: (and https:, with the help of ProxHTTPSProxyMII) requests, not the UNC network requests those emails cause Trident to attempt.

I use https://archive.mozilla.org/pub/firefox/releases/56.0.2/ With/for my old Add-Ons, like: Classic Theme Restorer, Tab Mix Plus, Speed Dial, All-in-One-Sidebar, Navigational Sounds ...

Been a while since I posted one of these, but anyway here it is... SUMMARY OF CHANGES TO THE LIST FOR FEBRUARY 1, 2019: Added MailNews by roytam1 to "E-mail Clients" section. Removed Dropbox from "Cloud Storage Clients" section, as new versions of the software will no longer install in Windows Vista and older versions will no longer connect to the Dropbox service from my testing. Added Steam (Jan 4, 2019) build as the last version for Windows Vista, along with information on how to prevent the software from automatically updating (resulting in Vista compatibility loss). Added AssaultCube to "Games" -> "Active Development" section. Added EditPad Lite to "System File Viewers/Editors" section. Hope all the XP/Vista users have continued to make use of my list. Sorry about not being too active lately.

Introduction: Here, you will find a list of AMD/Intel CPUs, motherboards (AMD/Intel chipsets), and Intel/NVIDIA/AMD GPUs which support Microsoft® Windows Vista™. If you have any additions that aren't currently listed, feel free to reply with them and they will be added as soon as possible. Supported CPUs: Intel (Desktop/Server): Note: Windows Vista has been known to work with Pentium III and even some Pentium II processors, however this configuration is extremely suboptimal and the OS is practically unusable on these processors, so using at least a Pentium 4 (Prescott), plus installing Windows Vista Service Pack 2 is recommended for acceptable performance. Intel Pentium 4 (Williamette, 2000-2001) *x86 only Intel Pentium 4 (Northwood, 2002) *86 only Intel Pentium 4 (Prescott, 2004-2005) *x64 is only supported from the Pentium 4 505 Processor and newer Intel Pentium 4 Extreme Edition (Gallatin, 2003-2004) *x86 only Intel Pentium 4 Extreme Edition (Prescott, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Northwood, 2003-2004) *x86 only Intel Pentium 4 HT (Prescott, 2004-2005) *x64 is only supported by F-series, 5x1, 517, 524 and few OEM models in E-series (SL7QB, SL7Q8) Intel Pentium 4 HT (Prescott 2M, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Cedar Mill, 2006) *Supports both x86 and x64 Intel Celeron, all Netburst-based models (Williamette & Northwood-128, 2002-2003) *x86 only Intel Celeron D (Prescott, 2004-2005) *x64 only supported by 3x1, 3x6, 355 models Intel Celeron D (Cedar Mill, 2006-2007) *Supports both x86 and x64 Intel Celeron *all Core-based and newer models up to Ivy Bridge based Celerons; Braswell/Haswell and later do not properly work with Vista. Intel Core 2 Duo, all models Intel Core 2 Extreme, all models Intel Core 2 Quad, all models Intel Pentium up to Sandy/Ivy Bridge G series processors; Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Xeon 1.4 "Foster" - Intel Xeon 3.2 "Gallatin" *x86 only Intel Xeon, all models from 2.8 "Nocona" to 3rd generation Ivy Bridge Xeon processors; Haswell and later do not properly work with Vista. Intel (Mobile): Intel Pentium 4-M, all models *x86 only Mobile Pentium 4, all models *x86 only Mobile Pentium 4 HT, all models *x86 only Intel Atom *all models up to Bonnell microarchitecture (2012); Silvermont (2014) and later do not properly work with Vista. Intel Core 2 Solo, all models Intel Core 2 Duo, all models Intel Core 2 Quad, all models Intel Core 2 Extreme, all models Intel Pentium up to Sandy/Ivy Bridge mobile processors, Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. AMD (Desktop/Server): Note: Windows Vista has also been verified working on certain Ryzen processors. These will be listed at a later time. AMD Athlon 800 - Athlon 1000 (Pluto/Orion, 2000) *x86 only AMD Athlon 800 - Athlon 1400C (Thunderbird, 2000-2001) *x86 only AMD Duron 800 or later (2000-2003) *x86 only AMD Athlon XP, all models (2001-2003) *x86 only AMD Athlon 64, all models AMD Athlon 64 X2, all models (X2 & K10) AMD Phenom, all models AMD Opteron, all models AMD Sempron (Palermo, Socket 754; July/August 2005) *x64 only supported by all models with an OPN ending in BX and CV) AMD Sempron (Palermo, Socket 939; October 2005) *x64 only supported by all models with an OPN ending in BW AMD Sempron "Manilla" or later, all models AMD FX (Bulldozer Family), all models AMD (Mobile): AMD Mobile Sempron, all models (2003-2006) *x86 only AMD Mobile Athlon 64, all models (2004-2005) AMD Turion 64, all models (2005) AMD Kite Platform - AMD Carrizo Platform, all CPUs & APUs (2006-2015); Bristol Ridge (2016) may work but has yet to be tested. Supported Motherboards (chipsets): Intel Chipsets: Intel 945PL and later; last chipset to provide drivers for Windows Vista is Haswell (z97, x99, etc.). The last chipset to work properly with Vista is Ivy Bridge. View this post to read in depth the problems with running Vista on Haswell (and newer). Download Haswell Vista chipset drivers here. AMD Chipsets: Coming soon! Supported GPUs: Intel GPUs: Intel GMA 950 (Desktop: 945GC, 945GZ, 945G; Mobile: 945 Family) or newer, last Intel GPU to support Vista is Intel HD 4000 series (Ivy Bridge; Desktop and Mobile). Download Intel HD 4000 Graphics drivers for Vista here. ATI/AMD GPUs: ATI Radeon 9500 or later; last AMD GPU to support Vista is AMD RX 300 series; drivers are coming soon. The first official version of ATI Catalyst to support Vista is version 7.1. The last official version of AMD Catalyst to support Vista is version 13.12 (Download: 32 bit 64 bit). However, newer versions up to 15.6 Beta for Windows 7 can be modified to work on Vista. View this thread for more details. NVIDIA GPUs: NVIDIA GeForce 5200 and later; last NVIDIA GPU to officially support Vista was the GTX 980 along with driver version 365.19. Download here: 32 bit 64 bit - Note: Vista 3D Vision support was dropped around version 310.00. The GTX 1060, 1070, and 1080 can also be made to work with Vista, as driver versions up to 372.70 work with Vista, albeit not officially supported by NVIDIA. Download here: 32 bit 64 bit - Note: DirectX applications aren't properly utilized by these drivers under Windows Vista, so this will cause a bottleneck in performance over using the GTX 980 or older, where the 365.19 drivers (more optimized for Vista as they're officially supported) can be used. Xbox One Controller driver for Windows Vista: Looking for an Xbox One Controller driver for Windows Vista? View this thread for download + how to install (HUGE THANKS TO @GTAGAME for this.

In Italy since 1st January 2019 the obligation of electronic invoicing between private individuals has been introduced. I found out that the link chosen to work did not support my XP: https://app.agyo.io/portal/index.html#/ In the image below the warning that says that the Operating System is no longer supported: Problem solved with spoofing:

Hmmm. Let me see. Under Windows everyone uses Chrome or Chorome/Chromium engine based browser. (exception made for those insisting on using Mozilla Firefox, all in all a small amount of people [1]). Noone uses Edge. Whatever undocumented features of Edge (if any ) *somehow* facilitating MS operations is lost. The whole plan on world domination and stuff through the Windows 10 pushing is likely failing (besides the total defeat on phones) because even those that for one reason or the other are using Windows 10 ar not using Edge and nowadays a large part of the time spent on a computer is through its browser. Idea , let's make a new browser similar to or nearly identical to Chrome (possibly while keeping the same *whatever* undocumented features we like to have). Wait, this would mean actually writing lots of code, why not using the actual same engine as Chrome? jaclaz [1] and with the exception of a few old dinosaurs like yours truly that still use good ol' browsers (with some limitations).

I inadvertently found out that Internet Explorer 9 is again, as of late, able to play back youtube videos, so it appears Google (the owner of youtube) have patched their scripts to cater to IE9; this surely comes as a (nice ) surprise, but the reason behind such a move seems inexplicable to me... Perhaps was to support WS 2008 SP2 (officially supported until Jan 2020), on which IE9 is the only version of the native Microsoft browser to run, but I'm not convinced... For whatever reason, youtube now has been restored to its previous state in IE9, serving standalone MP4 encodes over HTML5 (usually only in 360p quality variant - some videos with more relaxed copyright also come with an additional (HD) 720p variant). As before, there's no way to go full screen: The MP4 decoding relies on system h.264/aac decoders (Windows Media Foundation), which means you need installed both SP2 + Platform Update Supplement for Vista... OT: Notice in the top blue ribbon how Google are eager to push their own (spyware of a) browser, even on a currently unsupported platform (i.e. Vista)...

Ever heard of fcwin2k? Then again, there are other ways, too...

Ok, so this time there aren't missing dependencies, it just fails to load, which is weird 'cause it means that it's something related to your system. Honestly, I don't know why it doesn't work on your system, as I tried it on a few other systems and it was working fine, especially 'cause I included every dependency needed. Besides, the message you are getting is related to the C++ Redistributable. Do you have an updated system? Which Antivirus do you have? Can you check that whatever antivirus you are using it's not interfering with the executable? (Please note that it's not digitally signed, so some antivirus products might not like it). https://support.microsoft.com/en-gb/help/2977003/the-latest-supported-visual-c-downloads @Dibyacan you try to run it on your XP as well? It's just to make sure that the issue is related to his system. After all, the installer works for someguy25 as well as in my virtual machine.

There is a problem with this... Once the Windows 7 giant falls, we will fall with it. AMD already discontinued 32 bit Windows 8.1 support, stating the user count was too low to invest in such an effort. I fear for the future.

I'm thinking 8.1 might be a safe haven because the powers that be aren't thinking we 8.1 users are a big group that needs to be pushed off our current systems as hard as Win 7 users. -Noel

8 added Metro and removed the Start menu, hence the shock. But all that could be undone by tweaking, because the underlying engines remained there. 10, instead, crippled more seriously the latent funcionalities of the underlying engines and added telemetry and advertisements, but arriving after 8+, it caused less shock. Were the release order the reverse, 8 might have been hailed as a steer back to the right direction. Ever heard of "the goat and the Rabbi"? MS used one of the oldest tricks in the book to try an' slide 10 down people's throats...