Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/09/2020 in all areas

  1. I'm not 100% sure, but I'm not worried about the inability to produce unofficial 32-bit Basilisk builds. There was a topic about the current/future state of Pale Moon for Linux... https://forum.palemoon.org/viewtopic.php?f=37&t=23031 Matt A. Tobin stated that Pale Moon 32-bit Linux support will be officially dropped in/after November 2020, but it will not affect UXP at the codebase level. I believe the same principle will apply to 32-bit Basilisk builds. Officially there will be no 32-bit builds, but it will still be possible to build/compile your own 32-bit unofficial Basilisk browser. I'm sure 32-bit Serpent/Centaury will survive the year.
    2 points
  2. @roytam1 Just FYI, 32-bit Basilisk will be discontinued... https://forum.palemoon.org/viewtopic.php?f=61&t=25397 Will it then still be possible to build 32bit binaries from the source code?
    2 points
  3. I brought BWC's PE Maker to its knees. It appears that the gigantic export table of my 32 bit ntext with about 1850 functions and about 109 000 (decimal) bytes in size is too much for the application. It only seems to write the first 100 000 bytes of it. And having the export table below rsrc/reloc is a no-go with PE32 of course (need to redirect to a kernel32 pointing to ntdll or OG ntext for x86 software to work at all on my system right now ). So I looked at the problematic x86 K32* functions again. It appears that any upgrading of Nt/Zw* functions will need to be done in ntoskrnl, and some of those are very complex. But there are other ways to look at the situation, like comparing the changes between the original psapi functions and the K32 equivalents (simply forwarding a K32* to psapi doesn't work in many cases). And guess what, the only differences I saw between psapi's GetProcessMemoryInfo and K32GetProcessMemoryInfo were quite minor. All of them were like this: NT 6.0 psapi!GetProcessMemoryInfo jz routine1 if not zero, go to routine2 NT 6.1 kernel32!K32GetProcessMemoryInfo jnz routine2 if zero, go to routine1 Every routine was the exact same!! A change in strategy is needed.
    2 points
  4. @roytam1 Maybe now is a good time to start thinking seriously about branching off completely and establishing your own fork, independent of the Pale Moon developers, and thus largely immune from their meddling? Of course, such would possibly be nontrivial, and someone would still need to maintain it. DISCLAIMER: I'm not a developer! c
    1 point
  5. Let us hope the official UXP/Basilisk repositories remain public, so that any future purging of 32-bit-only codeblocks could be reverted... Nonetheless, successfully compiling the source for x86 targets will turn, over time, into an increasing challenge, since upstream won't test anymore whether their codebase compiles into 32-bit binaries, nor would they offer any kind of help to mitigate eventual future 32-bit compilation errors...
    1 point
  6. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.6.win32-git-20201010-a61cc61-uxp-bda6f1a93-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.6.win64-git-20201010-a61cc61-uxp-bda6f1a93-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-20201010-a61cc61-uxp-bda6f1a93-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.2a1.win32-git-20201010-aa3ff776a-uxp-bda6f1a93-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.10.2a1.win64-git-20201010-aa3ff776a-uxp-bda6f1a93-xpmod.7z Official UXP changes since my last build: - Issue #1665 - Take overflow-wrap into account when calculating min-content intrinsic size. (8e18743ab) - Issue #1666 - Implement overflow-wrap: anywhere (dadef50bd) - [devtools] Teach devtools about overflow-wrap: anywhere (521f2b476) - Issue #1606 - Add support for multi-monitor DPI awareness v2 (W10 1706+) (bda6f1a93) Official Basilisk changes since my last build: - Update back-end branch pointer. (0839087) - Issue #23 - Enable per-monitor DPI v2 in Basilisk (a61cc61) Official Pale-Moon changes since my last build: - Back-end branch pointer update (Unstable 2020-10-04) (f6ae5e03d) - [app update] Move update cert entries to branding (b48aee553) - Issue #1812 - Enable per-monitor DPI v2 in Pale Moon (762408f9b) - [SSUAO] Update Yahoo override, since they now throw a fit when seeing anything "Pale Moon" in the UA. (aa3ff776a) My changes since last build: - partly import changes from tenfourfox: - #627: M1631583 M1631597 M1636771 M1637222 M1649316 M1651520 (2373458b5) - #627: M1631573 (0abd0fc5d) (75e16e512) - import tzdata and DNS from tenfourfox (as of rev 16c85bb3) (c0eddaf73)
    1 point
  7. since they put their repo in private, it is hard to tell if they have this fixed or not. if I need to fix it by myself, it will be in very low priority below $dayjob, $movement, and $build.
    1 point
  8. Definitely working on my end too , latest LGHUB , absolutely amazing.
    1 point
  9. In this case, it would only be needed for the licensing component of one application. At the very least it would satisfy the version check. And less risky than say, putting IE7 on win2k since they started to decouple IE from the shell in Vista. Web applications that rely on IE probably don't use its most cutting edge features. Since it's a licensing service issue, maybe there are other ways to fix it, but I will not talk about them.
    1 point
  10. Yes it is. It turns out that Qt does not discriminate against Vista, and I just updated user32 so that Qt 5.10+ will work. The Qt 5.15 application that @dencorso mentioned is working. It seems more interesting than I thought it would be, but I shouldn't need a 1200 USD licence to use multithreading, when 12 thread CPUs are dirt cheap. Bugfixes for kernel32 have been made that allow browsers such as Brave 83 to load, but it appears that something else has broken page rendering in all Chromium browsers on my end. 3ds max 2021 starts, but now it complains about there being no IE10. If you run it through dependency walker then it doesn't, but then the licensing service whines and brings everything to a halt. (it relies on IE). Perhaps the IE10 platform preview could work.
    1 point
  11. Car manufacturers phasing out spare tires, because they are used for less than 1% of the car mileage... LOL... sigh
    1 point
  12. Have you ever heard about binary ninja ? I've never had the opportunity to test it myself, but maybe it can be of help in your project...
    1 point
  13. Look like to this video: https://youtu.be/7h1UsiBuQVg This is a Windows Update v4 Clone, alternative to Windows Update Mini Tool on Windows 2000 (because is not compatible). Works good, but require ActiveX enabled as Trusted Site on IE6 and the offline file.
    1 point
×
×
  • Create New...