Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/06/2018 in all areas

  1. +1. Let's let Roy concentrate solely on that, which is of paramount importance to both XP and Vista communities.
    4 points
  2. New build of basilisk/UXP for XP! Test binary: Win32 https://o.rthost.cf/basilisk/basilisk52-g4.1.win32-git-20181006-8860eddce-xpmod.7z Win64 https://o.rthost.cf/basilisk/basilisk52-g4.1.win64-git-20181006-8860eddce-xpmod.7z diff: https://o.rthost.cf/basilisk/UXP-xp-gitdiff-20180606.7z PM28XP build: Win32 https://o.rthost.cf/palemoon/palemoon-28.2.0a1.win32-git-20181006-8860eddce-xpmod.7z Win64 https://o.rthost.cf/palemoon/palemoon-28.2.0a1.win64-git-20181006-8860eddce-xpmod.7z Official repo changes since my last build: - Update upstream URL and update script for libnestegg (d8434bf15) - Update libnestegg from upstream (dad1c31db) - Get rid of the incorrect mechanism to remove insecure fallback hosts. (347aea437) - Update HSTS preload list (778b3c4d7) - Update test files for libnestegg update (704c93539) - Merge pull request #800 from trav90/update-from-upstream (c7e12ca39) - Remove telemetry to find optimal cache entry hash size (0b1600742) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (6d9103276) - Update telemetry whitelists. (ddf29811b) - Clean up a number of unused variables. (81b341a9b) - Remove telemetry probes for cache file system. (3343a4b47) - Remove telemetry probes to get detailed disk cache hit rate. (ab9edfb54) - Remove cache I/O telemetry. (8ba6dd1bd) - [ffvpx] Update ffvp9/ffvp8 to release 4.0.2 (edc124b92) - Clobber for ffvpx update (7d1ee0e5e) - Remove unused telemetry functions/variables. (7b0f3f2f9) - Remove telemetry from cache v1 service locking (part1). (d718e32b5) - Remove telemetry from cache v1 service locking (part2). (ec4c6dd42) - Remove telemetry reporting functions from CubebUtils (38e8ee1e6) - [PALEMOON] Use message manager to detect full-screen HTML5 video in S4E module (35a1adb07) - Merge pull request #804 from JustOff/PR_s4e_FullScreenVideo (ab881a3bf) - Merge pull request #801 from trav90/update-from-upstream (79b00fc33) - Revert "Update ffvpx code to 4.0.2" (45c24f05d) - Merge pull request #805 from MoonchildProductions/revert-801-update-from-upstream (8e8fcee4a) - [ffvpx] Update ffvp9/ffvp8 to release 4.0.2 (ebc8d7e3c) - [ffvpx] Remove unneeded libavcodec symbols and dummy functions (82238ada2) - Clobber for ffvpx update (41ccd52bf) - Merge pull request #806 from trav90/ffvpx-resync (69d83c8fb) - [ffmpeg] Always allocate memory to pass extradata (c0d9931cf) - Merge pull request #808 from trav90/media-work (26975ccf5) - Make all arguments to init*Event() optional except the first (e42166a5b) - Bug 1493900. (ca7ecd37c) - Ensure we got an nsISSLStatus when deserializing in TransportSecurityInfo. (95379e337) - Fix in-tab close button behavior (#775) (d74519372) - Merge pull request #811 from MaxKoll/MaxKoll-patch-1 (8860eddce) My changes besides above changes: - reverted rev ebc8d7e3c...82238ada2 (i.e. 69d83c8fb) in favoring ffmpeg-3.4 branch, since ffmpeg-4.x needs SRWLock and bcrypt changes to be undone which is not yet tested
    3 points
  3. 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
    2 points
  4. A new definition for "Just in time" (pausing an update) ... Just sayin': https://www.theverge.com/2018/10/6/17944966/microsoft-windows-10-october-2018-update-documents-deleted-issues-windows-update-paused jaclaz
    1 point
  5. KernelEx core update 4.5.2016.18 (beta) - KexBeta.18.7z 206.93 KB VKrnlEx.vxd - System driver KernelEx.dll - Core logic Kexbases.dll - API extensions (Shared) Kexbasen.dll - API extensions (Non-shared) KexCOM.dll - COM extensions Sheet.dll - Property Sheet Handler ApiLog.exe - Debugging console ApiHook.dll - Debugging support Verify.exe - Verify installation is working. Core.ini - Settings for KernelEx.dll LZDLL.reg - Registry support for six missing (98/SE) DLL's LZDLL_ME.reg - Registry support for four missing (ME) DLL's API-MS-Win.reg - Registry support for Win7 API sets 1) Exit Windows or reboot to DOS. 2) Copy all files except KernelEx.dll to existing KernelEx folder. (Kexstubs users: edit Core.ini [BASE] contents= line here.) 3) Reboot to Windows. 4) Run Verify.exe 5) (Optional) Add registry entries as needed. More updates are already nearing completion: Ktree, Kexports; SList, SRW, PowerRequest. Specific API requests welcome.
    1 point
  6. It's funny, many of the reasons stated in that article for saying no to the LTSC are precisely the reasons why I'm saying yes! That helped. Thanks! I must say, MS has really ruined the whole experience for me! I remember saying that about the "new" Windows Vista control panel, but it still had some logic to it, and thus I was able to adjust to it over time (plus, it did genuinely get better in Windows 7, and even 8.1, for what it's worth, had some very good improvements, not only for the CP, but for the OS as a whole; too bad it got mostly cancelled out by all that Metro stuff), but this Settings app... everything's so obtuse and difficult to find it's driving me nuts! MS has become a master of obfuscation, and I can't stand it!! c
    1 point
  7. "The overall execution of dark theme across Windows is poor; an opinion re-enforced by the recent introduction of a dark theme in MacOS Mojave. On its first move, Mojave appears to have magically gotten the concept pristinely materialized systemwide. Windows 10, on the other hand, has had a dark theme for 3 years and exceptions are still the norm. This seems to be the case with just about every aspect of Windows 10’s design." https://www.onmsft.com/news/its-here-our-hands-on-review-of-the-windows-10-october-2018-update-video
    1 point
  8. XP is still good today - except for the internet stuff. In relation to Windows 10 with its user unfriendliness, endless complexity and sly telemetry it is a day to the night comparison.
    1 point
  9. nope, the SRWLock changes are needed to be undone as well.
    1 point
×
×
  • Create New...