All Activity

I fail to see the point of this. OPEN SOURCE software is a "team effort". Period. If you want a good reveal on that, feel free to dive into Tobin vs Moonchild, roytam vs basilisk-dev, Chrome vs Chromium, et cetera.

It is not fixed. The left edge of several GUI fonts are not displayed for me in XP. I have this issue in Chromium ESR 92, Chromium ESR 108, CatsXP 115, most recent Supermium, and most-recent Thorium. Both inside a VM and on real hardware. Both on five-monitor PC and single-monitor laptop.

They claim this issue is now fixed, could you confirm? And it's again fixed by @win32, not "Thorium" author. https://github.com/Alex313031/thorium-legacy/releases/tag/M122.0.6261.169 "GDI text rendering alignment is fixed This bug caused text to be askew, either too high or too low, or too much to the left. The reason previous releases didn't have this fixed, is that win32ss fixed it in Skia, which is a third_party submodule of Chromium."

Since WebGPU ("unsafe" GPU, how the devs still call it) now works on Vista+, it'd make sense for @XPerceniol to switch it off, too. (since he disables webgl, I thought it'd be of interest) https://github.com/Alex313031/thorium-legacy/releases/tag/M122.0.6261.169

Interesting,so you use Thorium in a VM. Have you tried checking the Policy below: NetworkServiceSandboxEnabled - true is it OK? Thanks,sorry to bother you,and see you on W.

dean

Mean

lean

leap

Reap

Still doesn't work here under: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Thorium Works under : HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Chromium Sandbox:

@roytam1 I replace the second ntdll.dll with my modded one but get the same reboot just at the end of the Setup process, before you have to hit F8. Please, can you tell me, what simulator you use for the AMD 486 cpu. And is there a possibility, even in this very first Setup of XP to let Windbg watch it, may be via a crash debug log Dietmar

Good tip! I think the filterlist+userscript(s) are actually meant to be used together, even though unfortunately this combination remains somewhat less powerful than their browser extension. It mostly works fine though.

Hi. Policy templates naming is correct now. Did you check if the one Policy you used is OK? chrome://sandbox is available for Windows XP? TH.

he puts some misinformation on this release notes, and I created an issue about this: https://github.com/Alex313031/thorium-legacy/issues/82

Updated XP/Vista Release

I think just cope as best as possible and tomorrows another day. Sorry guys was very bad today. Gonna just go to bed early.

I don't know. Don't know. Sort of struggling to accept my reality, but if I don't, I'm screwed until they cremate me. Have had to limit news (almost noting at all) and what I watch on TV to mundane programing and movies unless I'm easily triggered into severe depression and despair. I don't know.

Oh I think I find my problem: I can't replace resources with resource hacker in patched NTDLL.DLL. so maybe every language of NTDLL.DLL has to be done separately.

@roytam1 With this changes, can you install XP SP3 now on a 486 cpu Dietmar

@roytam1 The ntdll.dll is patched. So I dont know, where this Bsod happens Dietmar EDIT: Ah, I see, there is a second ntdll.dll on the xp.iso, crazy;))..

64-bit OS. Even my XP is 64-bit. I thougth the PAE patch was only for those trying to get XP x86 to see more then 4 GB RAM ???

The startup delay is a separate issue, all browsers, INCLUDING ROYTAM'S, have that delay on my system. I run *ALL* browsers using "portable launchers" but I've done that for TWENTY YEARS. It's only caused startup delays within the last three years - on *ALL* browsers. I have to force the PC off only with Supermium because it PEGS my CPU at 100% and the *ONLY* way out is to force the PC to shutdown. I suppose waiting 10 minutes is another option, but I can reboot in 90 seconds so I'll opt for 90 seconds over 10 minutes.

your setupldr.bin patch doesn't help and I still have to patch 75 to EB in 0x23513, and replacing NTKRNLMP.EX_ with our hacked NTOSKRNL.EXE. because you didn't replace system32\ntdll.dll, it tries to use cmpxchg8b in NTDLL.DLL and BSODs:

For consistency with XAML tooltips.