Leaderboard

New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190202-a31b9e067-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190202-a31b9e067-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-20190202-a31b9e067-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win64-git-20190202-a31b9e067-xpmod.7z Official repo changes since my last build: - Only use white audio indicator when using a lightweight theme (46958a2aa) - Only use white audio indicator when using a lightweight theme [pinned tabs] (b39e0b131) - Merge pull request #945 from FranklinDM/audioindicator-lwtheme-fix (2d43b6eee) - Add nullcheck for addons (pre-installed webextensions return null) (d6a2deb0c) - Remove remote add-on debugging control. (2e581f48e) - Always treat composition time offsets as signed (bed24fdb7) - [BASILISK] Align browser glue with TychoAM for enableable add-ons. (2cbbc5de4) - [PALEMOON] Remove some dead code from browser glue (plugin update service) (e82fdef9c) - Reduce number of allocations in AutoStopwatch (3476c1d60) - Revert "Reduce number of allocations in AutoStopwatch" (abcaa560f) - Reduce number of allocations in AutoStopwatch (b55d41c24) - Merge pull request #948 from trav90/media-work (7f992d50e) - [TychoAM] Fix GMP* so that EME works in Basilisk (a606410ba) - [AM] Remove spurious warning for staged cleanup. (efac6cc1c) - Remove telemetry leftovers from JS engine. (493c956d8) - Revert "Fix bookmarks backup logic." (dcc5d6a78) - Only state the stop notification for JSDownloads in nsWebBrowserPersist::EndDownload (aa28523a5) - Merge pull request #952 from adeshkp/remove-telemetry-js (fecab2c54) - Merge pull request #954 from MoonchildProductions/TychoEME-work (6edfc0a20) - Set incremental GC slice to 20 ms duration (278eda6a0) - Update HSTS preload list (a31b9e067) My changes since my last build: - update nss to git rev 4aea92b574d2d674ee75838d46ea95b113e8fecb with nss339-vc2013.diff applied - update Twemoji font to v11.3 based build. - update libaom to rev 0ec86ac7ae1e32a7e70410fa4972a655ec3670a4 (without moz.build and aom_ports/aom_once.h)

already discussed: https://forum.palemoon.org/viewtopic.php?f=3&t=19262&p=142312&hilit=howtogeek#p142312

WebGL work only with DirectX9 cards. The last DireceX9.0с and the driver is necessary for Windows XP Fx5*** and Radeon 95**- x1200 - only CPU WebGL (layers.prefer-d3d9, webgl.force-enabled and webgl.disable-angle - true) GF6100+ and Radeon x1300 + - GPU WebGL ( layers.prefer-d3d9, layers.acceleration.force-enabled, webgl.force-enabled - true) Test https://get.webgl.org/

No.

The same problem in the beta version, too. We need more stable version. Especially for 1809 (RS5).

I used the great program Startup Delayer https://www.r2.com.au/page/products/show/startup-delayer/ and added 30 seconds delay. Then during the whole day I have restarted my computer up to 10 times to test if the delay would help. And it did! The taskbar haven't disappeared anymore after I added the startup delay.

New regular/weekly KM-Goanna release: https://o.rths.cf/kmeleon/KM76.1-Goanna-20190202.7z Changelog: Out-of-tree changes: * update Goanna3 to git 21b0da255..92d2d7f76: - disable nsAutoOwningThread, which cause crash in KM (9e8200e7a) - snappy: update snappy to r114 from UXP (c2d58c15a) - update NSS to git rev e76a339d424a5fad9bc42a7e91154a4dd89b83f3 with nss339-vc2013.diff applied (e37e83161) - import changes from rmottola/Arctic-Fox: - change some pointer style, or patches do not apply (0de8fac13) - Bug 1137523 - Unprefix most js_* functions. (16507a434) (65938cdd9) - import changes from rmottola/Arctic-Fox: - Bug 1130166 - Use SizePrintfMacros.h when printing line numbers. (9fd08a254) - Bug 1133369 - Use consistent allocation kinds for new objects after converting an unboxed group (51e5f25bc) - Bug 1129510 - Trace references to JS heap from Profiler buffers. (90dfbed12) (743d64fb7) - import changes from rmottola/Arctic-Fox: - Bug 994016: TI: add removeSet (slightly reworked) (4cccc36c4) - Bug 994016: IonMonkey: Add MTypeOf folding to MCompare (9eb64c54a) - Bug 994016: IonMonkey: Use high level TI API for improving types at branches (what was left unapplied) (959c796ab) - Bug 994016: IonMonkey: Improve types at compares with MTypeOf (c8e580d34) - Bug 994016: IonMonkey: More agressively improve types at branches (5d4be5bfd) (129bd4b32) - import changes from rmottola/Arctic-Fox: - 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) (0838d9d1a) - import changes from rmottola/Arctic-Fox: - 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) (94617d85e) - update Twemoji font to v11.3 based build. (92d2d7f76) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses.

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-20190202-92d2d7f76-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190202-92d2d7f76-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190202-92d2d7f76-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win64-git-20190202-92d2d7f76-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - disable nsAutoOwningThread, which cause crash in KM (9e8200e7a) - snappy: update snappy to r114 from UXP (c2d58c15a) - update NSS to git rev e76a339d424a5fad9bc42a7e91154a4dd89b83f3 with nss339-vc2013.diff applied (e37e83161) - import changes from rmottola/Arctic-Fox: - change some pointer style, or patches do not apply (0de8fac13) - Bug 1137523 - Unprefix most js_* functions. (16507a434) (65938cdd9) - import changes from rmottola/Arctic-Fox: - Bug 1130166 - Use SizePrintfMacros.h when printing line numbers. (9fd08a254) - Bug 1133369 - Use consistent allocation kinds for new objects after converting an unboxed group (51e5f25bc) - Bug 1129510 - Trace references to JS heap from Profiler buffers. (90dfbed12) (743d64fb7) - import changes from rmottola/Arctic-Fox: - Bug 994016: TI: add removeSet (slightly reworked) (4cccc36c4) - Bug 994016: IonMonkey: Add MTypeOf folding to MCompare (9eb64c54a) - Bug 994016: IonMonkey: Use high level TI API for improving types at branches (what was left unapplied) (959c796ab) - Bug 994016: IonMonkey: Improve types at compares with MTypeOf (c8e580d34) - Bug 994016: IonMonkey: More agressively improve types at branches (5d4be5bfd) (129bd4b32) - import changes from rmottola/Arctic-Fox: - 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) (0838d9d1a) - import changes from rmottola/Arctic-Fox: - 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) (94617d85e) - update Twemoji font to v11.3 based build. (92d2d7f76)

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.

So I updated my laptop to the new build. It crashed because of SteamUI.dll. I replaced steamui.dll from my backup of jan 4th build. Steam worked, after disabling updates. But then somehow in my stupidity I messed the whole thing up, gonna have to completely restore steam from my old backup

Windows Server 2k8 x64 is running stable on Ryzen thus far; with third party pci-e devices for storage, usb & of course video. Drivers for sata is the default ahci drivers that come with windows; it's been working stable so far. Also, I have many devices and such disabled in BIOS; for instance SMT is disabled just in case. I'm currently logging everything i do or change to better understand the cause of a system failure if it arises. I'll update you all on further progress later on. "lol I'm currently using this system as I write this". PS: The reason I'm using Server 2008 Enterprise x64 is because windows vista enterprise x64 gave me blue screens before I could even log in; it was very random and would give me blue screens often and than sometimes not for a little awhile. I'm not 100% sure as to why Server 2008 is more stable on Ryzen since both Vista and Server 2008 are almost identical; for now all I can do is speculate.

Hi Dclem and ojt_1998.... Having a hard time believing that Roffen is really interested in any help he gets.... He is on two threads this one that I started way back when and this one... @Roffen If you are going to post then respond with comments that let us know that we are being acknowledged for giving advice.... Just want some clarity... *Roffen I am sorry if I have been a little harsh... Learning computers is a pain at the best of times and as I run a business helping lots of pensioners....should be a bit kinder to you....I would like you to write a post and then sort of answer if anything we suggests helps you so we know how to proceed.... Please don't be put off by a grumpy old git like me....lol bookie32

So....please tell us why you are wasting time even trying...?! If you are going to continue to post about problems the first thing is...do yourself a favour....you have been used to XP Pro...so install this program "Classic Shell"...no longer being developed but works a treat...you will have a menu like WindowsXP and then you will probably find things.... I want to add here that I am not a diplomat and can be a bit harsh at times.... And I apologise if I have offended anyone...not my intention! I really hope Roffen understands....we are just trying to help.... The more information we have the better.... bookie32

Wow, this is excellent news for Windows 8.0 users! The last Internet Explorer upgrade Microsoft will ever release for a Windows platform. Feels like a historic moment.

I don't think that anyone today is using Windows Vista for streaming or gaming but i'm pleased to say that the Elgato HD 60 S works fine on Windows Vista! It's a USB 3 1080p 60 FPS capture card which is widely known by Twitch streamers and is only meant to work on Windows 10. So @WinClient5270 you can add it to the list, if you like https://gc-updates.elgato.com/windows/drivers/hd60-s/download.php download the drivers from here, extract the exe with 7-ZIP and manually install the drivers in device-manager. The Elgato Streaming Software doesn't work because the installer blocks it but it's useless anyway because it doesn't have that much options and OBS is better for recording stuff. I'm also using the USB 3.1 TYPE-A PCIe CARD (works just fine on Vista) which allows you to play the games directly in the preview window with no delay! DRIVERS

Windows XP had about 26% market share at the end of support in April 2014. (source https://www.businessinsider.com/microsoft-windows-xp-market-share-2014-2 and https://arstechnica.com/information-technology/2014/03/weeks-before-expiration-date-windows-xp-still-has-29-os-market-share/ and https://cdn.arstechnica.net/wp-content/uploads/2014/05/os-2014-04-640x480.png) Other sources are available but I won't post them all here. Image below courtesy ArsTechnica With Windows 7 currently near 35% (http://gs.statcounter.com/os-version-market-share/windows/desktop/worldwide), this means it would have to lose 10% in the next year JUST TO REACH THAT SAME LOW POINT OF THE RANGE. While it's possible, I don't see such a dramatic drop, particularly when you consider macroeconomic factors. The global economy is slowing. It has been cited that the global financial crisis in 2008 contributed to keeping people and businesses on XP for so long. As of today, here in the United States we are dealing with a (currently) 15-day-old government shutdown with no end in sight; 800,000 federal workers aren't being paid and there is a highly polarized political climate. Wild swings in the stock market; with Windows 10 no longer being free, upgrading may be the last thing on people's minds right now. Finally, my opinion is that people who were going to upgrade to Windows 10 already have. Even XP's market share has remained stable since 2014, and has more market share than most versions of Mac OS X (source NetApplications Desktop OS share for December 2018: https://netmarketshare.com/operating-system-market-share.aspx?options={"filter"%3A{"%24and"%3A[{"deviceType"%3A{"%24in"%3A["Desktop%2Flaptop"]}}]}%2C"dateLabel"%3A"Custom"%2C"attributes"%3A"share"%2C"group"%3A"platformVersion"%2C"sort"%3A{"share"%3A-1}%2C"id"%3A"platformsDesktopVersions"%2C"dateInterval"%3A"Monthly"%2C"dateStart"%3A"2018-12"%2C"dateEnd"%3A"2018-12"%2C"segments"%3A"-1000"}).

I don't think so.... XP' market share was big enough when they dropped the support for XP. I'm not afraid for the lack of Windows updates. without support a web browser becomes totally unusable like IE6

Correct. So we can reasonably expect that Windows 7 will probably continue receiving Chrome updates until at least January 2022 three years from now. This ComputerWorld article addresses just that in addition to other milestones during Windows 7 end of life (EOL): https://www.computerworld.com/article/3322618/microsoft-windows/the-definitive-windows-7-retirement-timeline-countdown.html However, I believe that Windows 7 will persist with high market share for years due to the fact that Windows 10 has much higher system requirements (XD or NX bit execute disable bit processor, etc). In contrast, it was relatively easy to install Windows 7 on a Windows XP computer dating back to the original Pentium 233. Windows 7's market share in January 2022 probably will strongly influence Google's decision either way on whether or not to continue or discontinue support. Infected machines could wreak havoc on the rest of the Internet. Also, don't forget that Chrome 49 (49.0.2623.112 m) is still highly serviceable on Windows XP. I'm still using it nearly three years later! Adobe Flash Player updates for Chrome (PepperFlash) still work if you follow my instructions here: http://sdfox7.com/chromexp3.htm

Windows 7 will be the next Windows XP. Only a year of Windows 7 support left and it still has nearly 40% market share. The fact that Windows 7 turns 10 years old this year and still commands such high market share is a testament against the spyware and flawed updates that make up Windows 10. You'll never change my mind Even with Microsoft offering Windows 10 for free and using "unethical" methods to get people to unwittingly install, it couldn't kill Windows 7 quickly enough.

Here's my experience with AMD Ryzen CPUs on Vista: they work great! There are no random BSOD or services not starting like Haswell or above. USB 3.x drivers for Windows 7 work just fine on Vista, but you can't slipstream them into the installation, because they are not signed for NT 6.0. You'll need to have a PS/2 keyboard at hand (you only really need the keyboard). A few drivers you should not install, because they do not work: AMD PCI AMD GPIO (this one will make your system unbootable!) Everything else works just fine. I've used a MSI B350 PC Mate motherboard with 16GB of DDR4 RAM. Had to enable legacy USB, enable CSM and disable Secure Boot. After that, I was able to boot Vista in UEFI. Hope this (really late) post helps, since you've asked ages ago @WinClient5270

Phew... after a lot of research and work, this post is mostly complete. Now I just need you, @greenhillmaniac, to repost your experience with using Vista on Ryzen, plus the RX 300 series drivers that you discovered recently, whenever you get a chance. If you're busy, I understand, there's no rush