Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. First I tried this FF38/TLS1.,3 on my main machine Win ME - KernelEx 25/26 - Kext. Yes, indeed it starts and runs (compat. mode XP). Besides Icecat 38 I have one more FF38 fork working on ME, but of course basically with the same issues as with version 35 I documented. I am curious, because I had tried to start versions 36 - 41 myself for a long time without success. Other tests could follow on a bit different systems. The plugin container can run in the background after close. So I switched it off. It makes sense to disable Javascript (I installed QuickJava), due to its age-related infirmities. It will freeze on many sites, also on this msfn board. FF38 OT.
  3. Well, how about that? I guess it's a recent change on these sites that just started triggering the old bug. But at least now, we have someplace to start looking. So Mozilla must have fixed it somewhere between FFs 53 and 68, and (assuming MyPal 29.3 was based on PM 29.3) it appears MCP incorporated the fix long ago as well; yet somehow the fix still hasn't make it into any of @roytam1's browsers (well, to be fair, no one has tried NM 27 yet). Does that seem reasonable, and does it help us find the issue?
  4. @nicolaasjan consider setting `version.UPDATE_HINT` in your builds to disable `-U` with a custom message.
  5. Today
  6. I completed almost all the steps but I get a "verification file setup" error when trying to run setup.exe
  7. I completed almost all the steps but I get a "verification file setup" error when trying to run setup.exe
  8. XP SP3 on Alderlake N100 cpu, 6 Watt Dietmar Now, this board is full XP SP3 compatible: Sound, Lan, Graphik, COM1, PS/2 combi, Harddisks, USB3, USB2, all works. And it is fast.
  9. There is a build of KMGoanna from 2020 that runs HexGL smoothly on Windows XP when you set both WebGL and webpage compositing to use OpenGL. I've not seen another build like it since. Admittedly, I haven't checked any of 2024 builds yet. Maybe it's old Mozilla bug, but I haven't checked any old Firefox versions. The issue seems to crop up in recent SeaMonkey builds as well, but they've fallen quite behind the Moonchild's crew.
  10. Yesssaaa I succeed to enable CSM mode, even it is not shown in Bios^^ Dietmar PS: Just now I am installing XP SP3 on the ASRock N100DC-ITX. EDIT: After flash of Bios Modd, you always have to clear CMOS with jumper! Here is the Bios for working CSM of the ASRock N100DC-ITX and all the needed EFI tools. No EEPromer is needed! Intel lost this time https://ufile.io/l3w3s78e EDIT2: I install with Firadisk . When you want to see F8, you have to disconnect this USB stick for a second and reconnect. The same is needed for GUI Setup, when you see the running bar, crazy^^..
  11. Is there an explanation on how to install Office 2016 on Windows Vista with Extended Kernel?
  12. That‘s just crazyy. I mean a few years ago I thought 52.9 was our last way to go on Vista and now 125 (73 versions above) works
  13. AVSforum and Wrestlingforum looks OK with MP68, 360Redux and Mypal 29.3 Same problems as Mathwiz and kuja killer with Serpent 52/55, NM28 and Seamonkey 2.49.5 For some reason I've a minor font issue with Supermium/Thorium and MiniBrowser on both sites. BTW, both sites use the same forum software as a lot of other interesting forums. https://fora.com/communities/
  14. Official build of PM 33.0.0 from January 2023 renders this correctly, roytam1's builds from that time do not. So rather than new Googlism it looks more like an old roytam1's bug. One of those that go on for years! Same for wrestlingforum.com.
  15. This problem did not occur in earlier versions of MyPal68. When trying to open the website https://allegro.pl/ there is a request: Confirm you are a human. After accepting this request, a picture is displayed, where you need to move the puzzle to the right place (you can do it) - only after this operation the desired website opens. Can a change of settings in about: config can help here?
  16. Did you specifically try Driver signing bypass dseo13b.exe?
  17. Oh crazy, I still get Write Protected message during AmiSetupWriter 0xCB3 0x0 Hm, this looks, as if the UEFI nvram Write Protect BIT is not only located in Bios Dietmar EDIT: AmiSetupWriter 0xCB3 0x0 gives now answer: Current Setup[0xCB3] is 0x0 Ru.efi tells the same now for the very first time. That means, the variable has indeed changed from 01 ==> 00 via Bios modd. But still the crazy message after this: SetVariable call returned Write Protected. This means: I can change nvram Variables via Bios Modd, but I cant change this Write Protect until now.
  18. This branch is 1256 commits ahead of, 36159 commits behind chromium/chromium:main. What does an average Joe get out of those commits?
  19. Might be hidden beneath the plastic. I'll take a better look when it runs out. I didn't even bother replacing the one in desktop, only removed it when it ran out, every once in a while when I unplug PC during the bad weather, I just put the clock and rest of the BIOS settings back in order afterwards.
  20. I understand. I see that only the installable software is up to date,not the extensions whose development is stopped at 2023. I have a mindset geared toward IT security. I never add third-party softwares for functionality that can be done natively by browsers because the increase of especially third-party code in the system statistically implies an increase that is directly proportional to the vulnerabilities. I also follow the same reasoning for extensions. I use as few extensions as possible.
  21. @reboot12 Here is the original Bios 1.06 file and the modded 1.06 one without Write Protect for the UEFI NVRAM variables for ASRock N100DC-ITX board, Bios Version 1.06 Dietmar https://ufile.io/b28vzhl0 EDIT: Cool, I can flash this Bios without EEPromer. Instant flash tells: Secure fail, but FTP.efi for 128 Bios works from USB stick.
  22. @reboot12 Next search with UEFI Tool. I found those Hex Values in 3(!) different raw files. In each of those raw files exact 1 times: Needs to be checked VERY careful, I search for a sequence of about 300 Bytes each. CEF5B9A3-476D-497F-9FDC-E98143E0422C EE4E5898-3914-4259-9D6E-DC7BD79403CF 77D3DC50-D42B-4916-AC80-8F469035D150 Dietmar
  23. Win10 21H2 was not entirely EOL (only the home & pro editions went EOL in mid-2023 but the enterprise & education editions of 21H2 will go EOL in mid-2024) guess that's why I like using LTSB/C releases (I run ltsc 2019 & ltsc 2021 which have much longer support)
  24. 24H2 got released in the release preview channel for windows insiders in late May https://blogs.windows.com/windows-insider/2024/05/22/releasing-windows-11-version-24h2-to-the-release-preview-channel/ also, OP has yet to tell us what kind of CPU/processor that person is using. SSE4.2 support was first added on the Nehalem series (1st gen Intel core) of Intel CPUs and also started with the AMD Bulldozer & Piledriver series of AMD CPUs (the FX series). any old Intel & AMD processors before these series do not have SSE4.2
  25. are you running Win11 24H2 on a modern UEFI system or non-UEFI (legacy bios) system? modern UEFIs block unsigned drivers, especially on modern Intel based UEFI PCs with Intel PTT (platform trust technology) enabled
  26. After crazy search in original Bios I found the place, where the UEFI variables are set to Write Protected Dietmar 010101010101010101000001000001556E02011E414646641E466464000000000000000000000000000000000002011E414646641E4664640000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000FF0000000000010100000000020202010000020000000000000104FF0000000000000000000000 EDIT: It can be found at 2(!) places in Bios. I replace both 01 ==> 00. Überprüfung auf Unterschiede 1. F:\n100Biosmodd\06modd.ROM: 16.777.216 Bytes 2. F:\n100Biosmodd\06.ROM: 16.777.216 Bytes Offsets: hexadez. 500D6B: 00 01 FAD8A3: 00 01 2 Abweichung(en) gefunden.
  1. Load more activity
×
×
  • Create New...