Leaderboard

Hello I occasionally look here, but foremost i look on the github. Today i occupied with wasm error https://github.com/Feodor2/Mypal68/issues/57 this is bunch of sites and new ublock Also i want to fix bsod, however i still don't know what about. https://github.com/Feodor2/Mypal68/issues/3 Too little data, though if you do not want to bother with github please post your bsod data here as described.

Mypal 68 has its own TLS (1.2 and 1.3) protocol and the associated ciphers. A TLS 1.2 proxy isn't needed for Mypal 68. Please, provide information about your hardware! Furthermore, open the setting page of Mypal 68, disable hardware acceleration, clear cache, delete all cookies, and restart the browser. Do you use Mypal 68 in single-process or multiprocess mode?

@George King Can you read this document as it is a rare document? Some pages seem to tell you the limitations used to check how the system works. Firstbootcheck I've provided along with the original symbols provided by Microsoft. https://drive.google.com/drive/folders/124kJQ5c9Ddngbjf3mvlP_H6VsxVMy1TD

Thanks, @feodor2. I haven't had any bsod, but I disable things (webgl, wasm and such) by default, using mostly the standard user.js for ff68 from https://github.com/ghacksuserjs/ghacks-user.js. This may help singling out the source of trouble. Be well. Thanks for this.

Without a doubt. I recently tried 360v9.5 again and was quite impressed with the speed myself. Its Chromium engine is only 6 releases older than the version used in 360v11, and seems to offer comparable if not slightly better performance on my Pentium D machine. A meaningful advantage that 360v11 does have is a better TLS 1.3 implementation (I believe TLS 1.3 is supported up to "Experiment 3" in 360v9.5, but in 360v11 it goes all the way up to "Final"), but most sites shouldn't give you trouble on that front. Chromium-based browsers seem to fare better with sites like Twitter, and 360v9.5 loads the desktop site and runs it with good speed, despite the Chromium 63 engine beginning to show its age now. It definitely handles it better than old Chrome 49, which once ran it like a champ but now struggles with it (probably because aspects of the JS backend had 'modern' JS features added that didn't exist or weren't fully implemented when Chrome 49 was first released). For people who really like Chromium and don't want to touch anything Mozilla-based, my recommendation is to keep two browsers around: Chrome 49 for basic web surfing, and 360 for sites that won't load in 49 + more serious tasks (with 9.5 or 11 advised as a starting point if you want to keep CPU usage down; you can experiment from there if you absolutely need something more modern).

There are ESU-bypass tools but they‘re obviously not legal, since people pay for these updates. It‘s your own choice

Good news on that front: I got 360EE v13 working again. Turns out I need to "Run as Administrator" on Win 7 - no idea why. I've never needed to run a browser as "Administrator" before.... Edit: Now that I think about it, I think I know why. I foolishly put the 360EE folder under the "Program Files (x86)" directory, and 360EE modifies some files there. That works fine in XP but requires administrator privileges on Win 7. Oops! Anyhow, the troublesome site https://cw33.com/morning-in-america/ doesn't load correctly there either! I'm starting to think the Web page itself is broken, not a problem with older browsers. Sorry for the false alarm, everyone....

Is is possible we can come up a setting that I saw in browser like Slimjet called "Optimization period" which allows memory release in timed interval? Thanks.

Hear, hear!!! Long live Windows XP--and thank you for your own contributions! All of you have played a very big part in keeping XP alive!

And one thing is totally clear. Without the efforts and support of @roytam1, @feodor2, @NotHereToPlayGames, @Humming Owl and so on, Windows XP would have been died years ago. Therefore, thanks to you all for your great work , and keep Windows XP alive as long as possible! Kind regards, AstroSkipper +

driver is too complex, need reverse how it works, i dont know how it inject own code to kernel context switching, probably PsSetCreateThreadNotifyRoutine(), PsSetLegoNotifyRoutine(), KeSetSwapContextNotifyRoutine() do this job for x64 need rewrite it fully, so much easy to hack existing x 64 kernel code instead write new "x32 avx enabler" has small asm source (FASM syntax), anyone can improve my inject code or rewrite for x64 (after finding where to store/load 256 additional bytes) inject.asm

Hi, Dave, I just last night finished up comparing my prefs to the latest Serpent and put on my thinking cap (I found one at a local flea market used ... hehe) and made changes that MC made to theirs and left some of FF 52.9.1 and spoofed to FF62 everything works very well still for me, as well. You're welcome. To go even a bit further backward, @Humming Owl's... Version: 9.5.0.138 Based on Chromium: 63.0.3239.132 Is super fast without the telemetry as well if you're looking for a light browser, but the internet is getting cruel towards us; sadly.

1) struct _CONTEXT has unused 1a0 bytes, it is enough to store high part of ymm0-ymm15 (low part of ymm* is xmm* and stored by kernel itself) struct _M128A VectorRegister[26];// Offset=0x300 Size=0x1a0 2) struct _KERNEL_STACK_CONTROL has embeded _XMM_SAVE_AREA32 union, no enough space to store high part of ymm0-ymm15 regs I dont sure what struct used on x64 to store FPU context, if _XMM_SAVE_AREA32 - need to expand struct (200h->300h) and change all related size/offsets in kernel, finding these places may be very hard, see KxContextToKframes(), KiInitializeKernel(), KiInitializeContextThread(), PspGetSetContextInternal(), RtlInitializeContext(), KeSaveLegacyFloatingPointState(), ...