Leaderboard

I installed portable 112.3.4.3. (Release date 12/04) this morning. Everything including Secure DNS works as expected. I never got any errors or crashes from any of the Catxp versions ( 110, 111, 112 ) what so ever. Furthermore clear browsing data has been addressed. https://www.catsxp.com/forum/viewtopic.php?t=168 Cheers

This project make possible to compile ACPI 2.0 driver from leaked XP SP1 & W2003 RTM sources, has same functionality as existing acpi.sys v6666 (still missed integer/fields/memory 64 bit support/) Grab leaked XP SP1/W2003 RTM sources (google it) Use "XPSP1/NT" directory as basedir if you want to compile acpi.sys for Windows XP x32 Use "Win2K3/NT" directory as basedir for Windows 2003 x32 / Windows 2003 x64 / Windows XP x64 Download any GNU patch package for windows (gnuwin32.sourceforge.net, cygwin, mingw, msys2, ...) Open command console, change current dir to base\busdrv\acpi\ (Windows XP x32) Save text diff patch https://pastebin.com/C5NXwHbS (v7 update) to file base\busdrv\acpi\sp1_to_sp3(ACP2).patch (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Save text diff patch https://pastebin.com/8QURrM49 (v7 update) to file base\busdrv\acpi\rtm_to_sp2(ACP2).patch (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Rename Win2K3/NT/public to Win2K3/NT/public2 (Windows 2003 x32 / Windows 2003 x64 / Windows XP x64) Update compiler and headers to mix of W2003 DDK+WRK, unpack https://anonfiles.com/J1W9H1a8y1/W2003_tools_update_7z to basedir with overriding existing files Remove "read only" flag from base\busdrv\acpi directory including sub-dirs and files Apply patch to convert original SP1/RTM sources to SP3/SP2 with extended ACPi 2.0 syntax: patching file driver/amlinew/amlipriv.h patching file driver/amlinew/amlitest.c patching file driver/amlinew/data.c patching file driver/amlinew/misc.c patching file driver/amlinew/object.c patching file driver/amlinew/parser.c patching file driver/amlinew/proto.h patching file driver/amlinew/type1op.c patching file driver/amlinew/type2op.c patching file driver/inc/aml.h patching file driver/nt/debug.c patching file driver/nt/debug.h patching file driver/nt/devpower.c patching file driver/nt/internal.c patching file driver/nt/interupt.c patching file driver/nt/irqarb.c patching file driver/nt/osnotify.c patching file driver/nt/pciopregion.c patching file driver/nt/rangesup.c patching file driver/nt/root.c patching file driver/nt/wake.c Change current dir to basedir (Windows XP x32 / Windows 2003 x32) Run razzle environment setup: (Windows 2003 x64 / Windows XP x64) Run razzle environment setup Change current dir to base\busdrv\acpi\driver\ Complie ACPI driver: build /Dcegbw Compiled acpi.sys.sys will be in (x32) base\busdrv\acpi\driver\nt\obj\i386\ or (x64) base\busdrv\acpi\driver\nt\obj\amd64\ Project contains implementation of new ACPi 2.0 syntax: ToInteger ToString ToHexString Continue ConcatenateResTemplate ToDecimalString Mod ToBuffer CopyObject MidString QwordConst (inside ParseIntObj) Timer CreateQWordField(fake it as CreateDWordField) Know issues workarounds: BSOD 0xA5 (0x10006, ...) missing _DIS method for "PNP0C0F" (PCI Interrupt Link Devices) BSOD 0xA5 (0x02,xxx, 0x0, ...) ACPI vs E820 mem ranges conflict IOTRAPS I/O range 0xFF00-0xFFFF vs VGA (10-bit decode!) conflict BSOD 0xA5(0x03, ..., C0140008, ...) error in ValidateArgTypes() when reading 64-bit fields BSOD 0x7E(c0000005, ...) error in AcpiArbCrackPRT() when referencing null pointer BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (zero lenght buffer) BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (doubled device definition) BSOD 0xA5 (0x0000000D, ..., 0x4449555F, 0) absence _UID method BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (Connection() opcode) CPU definition as Device with _HID=ACPI0007 BSOD 0xA5(0x03, ..., C0000034, ...) postponed SSDT loading on x64 platform (v8 update) Assertion Fail on loaddsdt.c, line 488 for x64 builds (v8 update) Unresolved issues: BSOD 0xA5 (0x0000000D, ..., ..., ...) duplicated/absence _HID/_UID method (AMD boards) BSOD 0xA5 (0x2001, 0x01, 0xC0000034, ...) failure to evaluate the _PIC method in NotifyHalWithMachineStates() Conflicted device names in Windows device manager (Code 42)

Risk is relative, there are much more risky things. Only as an example I use as a browser Opera, Kasperski as antivirus, and Softmaker as office suite (without having checked the german ancestry of the programmers of the latter company). jaclaz

Perhaps @NotHereToPlayGames will do something about it in the future, because he already has experience in this

Now try and switch it on in your 360 explorer and it will not work ! From what I gather, all chinese browsers intentionally broke it ! How to check ? You need to trace the browser UDP connections to 1.1.1.1 (or another safe DNS) with DNSQuerySniffer. Try it.

Yes, it says disabled for me, also. BUT it says I'm running a low res moniror 1920×1080 16:9! It's not true because it's NOT my Screen Resolution !

Too here: https://browserleaks.com/javascript Scroll to: navigator.userAgentData (Client Hints) API Status × Disabled / Not Supported

Very important to check if your user agent spoofing works ! New "feature" to check your real UA is called client hints, https://browserleaks.com/client-hints

Well, you asked me to suggest more for you to try, So I suggested the ones that are important. Fonts in your system are unique. You can disable remote fonts, but can't the system ones. Random fingerprint is the only solution.

I'm sorry , but you're mixing up two different matters. Font Fingerprint Defender has nothing to do with remote fonts, it protects against websites that scan your system fonts. It makes a random font fingerprint, which is very good ! For remote fonts I just use the flag --disable-remote-fonts (so no extension neded at all). The flag is old, but it still works, try it.

Tracking Token Stripper 2.6.2.6.0.0 Font Fingerprint 0.1.0.1

I'm sorry to disappoint you, your readings of my mood are wrong, it's on the contrary, I was not satisified with one of the chinese browsers not deleting cookies. Spent a couple of hours and found no solution.

Hello, I have many problems with your new version of the extended kernel. I used the one from October 2022 and no worries and I tried the one from March 2023 and a lot of problems appeared. I made a video to make it easier to see. https://youtu.be/BmPZTJX18sE

Yesssssssaaaaaaaaa Ты действительно самый лучший! @Mov AX, 0xDEAD What a crazy hard work. Here it is, XP SP2 bit64 on Gigabyte z690 UD DDR4 with free acpi.sys without any Debugger Dietmar

We'll have to convert those functions implemented with _asm into C code if we ever want to produce an x64 version of this.