Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/10/2021 in all areas

  1. On sister's Win7 SP1 64-bit laptop, I updated official Pale Moon unstable to the latest 32-bit build: Version: 29.0.3a1 (32-bit) (2021-05-07) [buildID=20210507130743] and that build was compiled from following sources Platform module: uxp-master-git-20210506-ge7e6356 Pale Moon source: pm-master-git-20210507-g2ad022d The platform (official UXP) source does include 6f707bd which is equivalent to a4b0f33 in the custom branch of your UXP fork... The thing is, the AOM (about:addons) in the above official PM unstable build works as intended, i.e. no additional patching of 6f707bd is required, whereas to get AOM working in latest NM28 you had to patch a4b0f33 according to 8eb3a27 ; @roytam1 : Why was NM28 (and several other UXP forks) affected by "upstream" changes, while their own app was "not messed up" ? Just wanting to get a clearer understanding of things in a somewhat deeper level, nothing more... As always, thanks for your on-going efforts into supplying browsers that still keep XP and Vista kicking for a tad longer ...
    3 points
  2. Honestly, since I was able to find that Technet article describing the KBs which give the various XP versions SHA-2 functionality, I wasn't worried. Far as I'm concerned, we had our answer: XP may not have initially come with SHA-2 support, but Microsoft provided some functionality in later updates. Especially once people tracked down the relevant updates and put them up for download. If something happens, I've got the installation on hand. And we've got @legacyfan and @erpdude8 to thank for that.
    2 points
  3. And why is this certificate expiry the death of Windows XP? (hint - it's not - almost nothing will change)
    2 points
  4. I tried Panda Free six years ago and had to reinstall Vista due to the damage it caused. True, it still supports XP/Vista and is listed as ONG in this thread’s original post. (Bullguard is also ONG, has anyone tried that?) Your opinion “it works better than Avast” is not persuasive in the least to me. Edit: Of course I don’t have your famous slow Vista laptop to worry about.
    1 point
  5. Ok I just edited my previous post to mention a Latitude E6400 & E6410, which DO have XP x64 support E6420 & higher do not have it
    1 point
  6. no. the ms catalog site should still work - ms catalog is the modern day "ms download center" yea, so much for the SHA1pocalypse (hah!) my friend's old HP a1600n desktop PC with XP media center edition 2005 (patched with SP3 and a lot of the post-EOL XP updates) is still working recently
    1 point
  7. VLC 3.0.13 has been released. (It’s been available since late April, but has just now replaced 3.0.12 as the main download.) There is a security bulletin. Platform Update is required. This may be the final update before VLC 4.0, which will not support Windows XP or vanilla Vista.
    1 point
  8. Merged. Do not create any more threads in this section.
    1 point
  9. Samsung 860 EVO appears to be a SATA SSD. As for whether there is something particular with the disk that will make it so that it will not function properly in the notebook, it is difficult to tell. I can't really find anyone trying to use the two things together. On the surface I would say there would be no issue, but know that saying this isn't an endorement that it will work. The one thing that I can tell you about this is that your notebook's drive bay was specifically designed for whatever size HDD it was sold with. Be aware that some SSDs are actually thinner than HDDs. The difference may be that if there are any pads on the drive chassis (if it uses one) they may not be sufficient to keep the SSD from moving. You may need to use additional padding. You won't know this until you get the drive in hand and try to install it.
    1 point
  10. I actually read one of Microsoft's articles, and they're going to block everything sha-1 blocked. I tried a beta insider and I had to start windows in mode without signature verification, since in Windows 10 20H2 it lets me use my Wireless but not in 21H2. This will affect those of us who use older hardware if we need to update to the upcoming versions of Windows 10. But I still use Windows 10 1511 since it is very stable on my computer with 4GB of RAM, SandyBridge and an HDD since I can dual-boot with XP or 2000. Regarding the updates, nothing was affected despite the fact that they mentioned the services and processes. For me they already gave the final grim reaper to XP when they eliminated TLS 1.0 support and the need for the elliptic curve.
    1 point
  11. Nothing has changed, no signatures have disappeared, neither for the drivers, nor for updates. It looks like the panic was in vain.
    1 point
  12. You seem to think that Windows Update stopped working for Vista and earlier last year only because users did not install certain updates. What gave you that idea? Windows Update no longer works for Vista and earlier because Microsoft does not want it to work for them anymore. Dave-H and others in this thread have fully-updated XP systems, but Windows Update only gives them an error. If anyone reading this wants to update Vista, greenhillmaniac has a complete repository. As for Windows 7, the only update that has thus far been needed to get Windows Update working is SP1. Perhaps that will change today, but there is no immediate danger of Win7 updates being removed from the Catalog.
    1 point
  13. Posts relating to the expiration of SHA-1 certificates moved here.
    1 point
  14. Whether odd or not, it depends on the point of view (beauty is always in the eyes of the beholder) While I can well understand how a "special/custom" case (which is in open view) may be sometimes *needed* and while I can well understand the "modders" (yeah, those that have windowed cases that actually show the inside) I find more difficult to understand how the colours that you can see only when opening the case (which for cleaning/maintenance may happen when? once every six months or so) can actually affect your aesthetic taste to the point to prefer a brand of Ram over another only because of a matching or contrasting colour. But of course to each his own . jaclaz
    1 point
  15. FTR, it's in: https://github.com/roytam1/UXP/commit/8eb3a27
    1 point
  16. thank you! all good now on NM28XP.
    1 point
  17. Hi General Problem "Iceape-upx ,Newmoon 28 and bnavigator" About:Performance "does not work" About:Support "does not work" Add-ons Manager "does not work" Serpent 52.9 and Newmoon 27.10 is OK
    1 point
  18. New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20210508-355db4de-uxp-e7e63565e-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20210508-355db4de-uxp-e7e63565e-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom-older * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20210508-id-f0915f3-uxp-e7e63565e-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20210508-id-f0915f3-ia-c642e3c-uxp-e7e63565e-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.
    1 point
  19. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210508-e29e57e-uxp-e7e63565e-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210508-e29e57e-uxp-e7e63565e-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.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210508-e29e57e-uxp-e7e63565e-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.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210508-1eb6e649b-uxp-e7e63565e-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210508-1eb6e649b-uxp-e7e63565e-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win64-git-20210508-1eb6e649b-uxp-e7e63565e-xpmod.7z Official UXP changes since my last build: - Issue #1767 - Prevent incorrect calling of network change detection function. (4e31a42b2) - Issue #1751 -- Remove XP_MACOSX conditionals from /dom (0dd3424f7) - Issue #1751 -- Remove XP_IOS (56da7e274) - Issue #1751 -- Remove XP_DARWIN (3d671e427) - Issue #1751 -- Remove files unused without XP_DARWIN (cd1f72413) - Issue #1751 -- Remove XP_MACOSX conditionals and support files from /gfx (616b39413) - Merge branch '1767' (b1eb04d3f) - Issue #1751 -- Remove XP_MACOSX conditionals and support files from /xpcom (1bf0734a7) - Issue #1751 -- Remove XP_MACOSX conditionals from /layout (aa0fd3d68) - Issue #1751 -- Remove XP_MACOSX conditionals from the rest of the tree. (6f707bde9) - Issue #1751 -- fix up a few stray #ifs (e7e63565e) Official Basilisk changes since my last build: - Issue #39 - Warn before opening many URI nodes in tabs (bdb17e6) - Merge pull request 'Warn before opening many URI nodes in tabs' (#40) from FranklinDM/Basilisk:issue-39-work into master (173ff3a) - Back-end branch pointer update. (e29e57e) Official Pale-Moon changes since my last build: - [SSUAO] Update Citi bank override. (4eb014170) - New cycle. (1eb6e649b)
    1 point
  20. i dont know i just found this topic today but i have a link to my sha2 updates for all windows versions archive in a topic above yours
    1 point
  21. Took me long enough, but I've noticed that updating an installation of official RetroZilla 2.2 with Roytam1's build merely by extracting his package over it actually doesn't work properly. The problem is that while Roy's build, unlike the official 2.2 release, has many components statically linked into the EXE instead of in separate DLLs, it will still load and use unnecessary DLLs left over from the old version. Symptoms include the wrong Gecko build date in the user agent as seen on the "About" page ("Gecko/20190223" instead of "Gecko/20200201") and the additional TLS ciphers supported by Roy's build not actually being presented to web servers (as reported by, e.g., https://www.howsmyssl.com/). The fix is to delete all of the 2019-dated DLL and XPT files in the root installation folder and the "components" subfolder, except for gkgfx.dll in the root folder and gkwidget.dll in "components", and also delete the compreg.dat and xpti.dat files in the "components" folder to ensure that RetroZilla regenerates them to reflect the changes. The reason I advise keeping those two DLLs is due to a bug in Roy's build where it does not display a "hand" cursor when the cursor is over a link; Windows 95 and NT 4.0 do not support a "link select" cursor at the system level, so applications such as browsers must use their own, and Roy's build on its own fails to do this. Retaining those two DLLs from the official 2.2 release fixes this.
    1 point
  22. Would any of these help? If not for the laptop in question, maybe it's still of use on another piece of hardware. New registry setting to disable modern standby: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Power] "PlatformAoAcOverride"=dword:00000000 EFI program that patches ACPI tables to disable modern standby: https://github.com/ElectronicElephant/Modern-Standby-Byby
    1 point
×
×
  • Create New...