Leaderboard

Solving BSODs 0xA5(..., ..., ..., ...): Windows XP/2003 supports only ACPI 1.0b syntax, last generation bioses uses ACPI 2.0+ To support ACPI 2.0 syntax need replace acpi.sys and apply additional patches to avoid known BSODs : - 0xA5 (0x03, ..., C0140001, ...) missing ACPI 2.0 syntax, 95% solved, solutions: 1) acpi.sys v.5048, sha1:a09c0d9f6b5cb63192e2cebada56db38d3870b29) from Vista Beta/Longhorn v.5048 Pro: - Has most of ACPI 2.0 syntax opcodes - All integers are 64-bit regarding ACPI 2.0 specification Cons: - beta, compiled for next generation of windows - failed implementation of some internal data types, _ValidateArgTypes generates BSOD 0xA5(0x03, xxx, C0140008, yyy) Patches: - Add pointer to _atDataObj struct for QWord Opcode (_OpcodeTable start at .data:00039848, _atDataObj struct at .data:000397A8, missing pointer at .data:00039880, dont forget add additional relocs) 2) acpi.sys v.6666 based on original Windows XP SP3 v.5512 with integrated acpi 2.0 syntax support Pro: - based on original v.5512, match binary/offsets Cons: - All integers are still 32-bit, any operations on 64-bit fields/variables will drop high part of QuadWord 3) acpi.sys compiled from leaked "XP SP1+W2003 RTM" sources Pro: - allow compile x64 build based on W2003 sources Cons: - same as v.6666 - 0xA5 (0x11, 0x08, ..., ...) unknow error in _AMLILoadDDB, probably fail after parsing DSDT/SSDT table, solved Patch (by Diderius): - Ignore status of _AMLILoadDDB in _ACPIInitializeDDB (v5512 jl short .text:00036214 => nop, nop) - 0xA5(0x03, ..., C0140008, ...) DSDT code have operation with unexpected type of arguments, partially solved This BSOD probably means some argument has datatype, allowed only in ACPI 2.0 v6666 & v5048 support only argument datatypes allowed in ACPI 1.0b specification Patch: - _ValidateArgTypes must always return "OK", even on realy wrong types (mov edi, 0xC0140008=>mov edi, 0x00000000 at head of _ValidateArgTypes) - 0xA5 (0x10006, ..., ..., ...), missing _DIS method for "PNP0C0F"s (PCI Interrupt Link Devices) in DSDT/SSDT table Patch (by Daniel_k): - Skip looking for PNP0C0F in _DisableLinkNodesAsyncWorker, (v5512 call strstr, ..., jz .text:0001BBBD => jmp .text:0001BBBD ) Intel Motherboards specific issues: 1) ACPI BSOD 0xA5 (0x02, ..., ..., ...), error in ACPIRangeValidatePciResources, ACPI vs E820 conflict, solved BSOD is generated by DSDT code like this: DWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, NonCacheable, ReadWrite, 0x00000000, // Granularity 0x00000000, // Range Minimum 0xDFFFFFFF, // Range Maximum 0x00000000, // Translation Offset 0xE0000000, // Length ,, _Y0E, AddressRangeMemory, TypeStatic) ... CreateDWordField (BUF0, \_SB.PCI0._Y0E._MIN, M1MN) // _MIN: Minimum Base Address CreateDWordField (BUF0, \_SB.PCI0._Y0E._MAX, M1MX) // _MAX: Maximum Base Address CreateDWordField (BUF0, \_SB.PCI0._Y0E._LEN, M1LN) // _LEN: Length M1LN = M32L /* External reference */ M1MN = M32B /* External reference */ M1MX = ((M1MN + M1LN) - One) Sometimes M1LN, M1MN, M1MX cannot be calculated properly and this code claim most of memory (E0000000 = 3.7Gb) as motherboard resource, this brings to conflict with E820 memory ranges list Patch: - memory check in ACPIRangeValidatePciResources must always return "OK" (v5512 jz short .text:0001E0BB => jmp short .text:0001E0BB) 2) Device Manager show conflict between Video Card and Motherboard resources Device IOTR(PNP0C02) claim 255 I/O adresses in range 0xFF00-0xFFFE, this range conflict with Video Card I/O range because vga has limitation to 10Bit I/O decoding. solved, two solutions: 1) Manual patching DSDT table, remove this lines inside method _CRS of IOTR device, so _CRS will return empty Local0: If ((ITS0 == One)) { ConcatenateResTemplate (Local0, BUF0, Local1) Local0 = Local1 } If ((ITS1 == One)) { ConcatenateResTemplate (Local0, BUF1, Local1) Local0 = Local1 } If ((ITS2 == One)) { ConcatenateResTemplate (Local0, BUF2, Local1) Local0 = Local1 } If ((ITS3 == One)) { ConcatenateResTemplate (Local0, BUF3, Local1) Local0 = Local1 } 2) Patch acpi.sys with injecting special code to override IOTR template buffer: In _Buffer opcode handler replace: mov eax, [ebx+14h] mov ecx, [ebp+arg_0] to call Check_IOTR_Buffer ... Check_IOTR_Buffer: cmp eax, 0Ah ; eax - size of buffer jnz short Skip mov eax, [ebx+30h] mov eax, [eax+10h] ; eax - buffer cmp dword ptr [eax], 00000147h ; need matching all 10 bytes jnz short Skip cmp dword ptr [eax+4], 0FF010000h jnz short Skip cmp word ptr [eax+8], 0079h jnz short Skip mov byte ptr [eax+7], 0 ; MAIN ACTION, set i/o range to 0 instead 255 Skip: mov eax, [ebx+14h] mov ecx, [ebp+arg_0] ret IOTR template defined as: Name (BUF0, ResourceTemplate () { IO (Decode16, 0x0000, // Range Minimum 0x0000, // Range Maximum 0x01, // Alignment 0xFF, // Length _Y21) }) in bytecode: 11 0D 0A 47 01 00 00 00 00 01 FF 79 00 3) No CPU power saving, most time CPU in C0 state even without cpu load Some part of acpi hardware is disabled, so CPU should not use nonexistent ACPI C2/C3 power savings, solved, two solutions (intelppm.sys): 1) C2/C3 States => C1 State : - in _InitializeAcpi2IoSpaceCstates replace offsets AcpiC2Idle and AcpiC3ArbdisIdle to offset AcpiC1Idle 2) C2/C3 States => C7+ States (default Windows 7 power saving mode, DPC Latency Checker shows significal increased latency in this mode): Replace Acpi2C3ArbdisIdle to: push ebx mov ebx, ecx push esi push 0 call _KeQueryPerformanceCounter mov [ebx], eax mov [ebx+4], edx mov eax, offset DummyMon xor ecx, ecx xor edx, edx monitor mov ecx, 1 mov eax, 60h mwait push 0 call _KeQueryPerformanceCounter mov [ebx+8], eax mov [ebx+0Ch], edx xor eax, eax pop esi pop ebx retn DummyMon - any unused 4 byes in .data segment Replace Acpi2C2Idle: push ecx push 0 call _KeQueryPerformanceCounter mov ecx, [esp+4+var_4] mov [ecx], eax mov [ecx+4], edx mov eax, offset DummyMon xor ecx, ecx xor edx, edx monitor mov ecx, 1 mov eax, 33h mwait push 0 call _KeQueryPerformanceCounter pop ecx mov [ecx+8], eax mov [ecx+0Ch], edx xor eax, eax retn 4) Programs show wrong timing results/works only first 3.5 sec Windows XP SP2+ uses disabled acpi timer, solved Skylake+ bioses by default disable ACPI hardware timer (register "ACPI Timer Control (ACPI_TMR_CTL)" in southbridge, see PDF), but WinXP SP2+ still uses disabled acpi timer for getting incremental time counter (acpi spec declare this counter as part of specification). WinXP detect existing this timer by checking special bit USE_PLATFORM_CLOCK in FACP ACPI table, modern bioses still set USE_PLATFORM_CLOCK=1 in acpi (mistake by programmers / inform Win7+ about existing HPET timer (not acpi timer!)) Patch (by Diderius) "HAL_acpitimer_fix" to use CPU TSC counter as performance timer/counter: - in HaliAcpiTimerInit force to ignore USE_PLATFORM_CLOCK and receive it always =0 (v.5512 jns short PAGE:8002934B => jmp short PAGE:8002934B) Compatibility fix ("HAL TSC frequency divider") Some programms do wrong calculation with high values of PerformanceCounter/PerformanceFrequency (HAL_acpitimer_fix set values to cpu freq), to avoid this problem values need to divide to much lesser value, Windows 7 just divide it to 1024, so timer frequency on 3600Mhz cpu is only 3.51Mhz Patch: - divide to 1024 values of PerformanceCounter/PerformanceFrequency, replace _HalpAcpiTimerQueryPerfCount to: 5) No driver for Intel SATA Controller - BSOD 0x7B(..,..,..,..) Windows XP/2003 support SATA controllers only in Legacy IDE mode, modern Intel chipsets has only AHCI mode, solved, many solutions: 1) Intel RST AHCI/RAID 11.2.0.1006 (iaStor.sys) 2) Intel RSTe AHCI/RAID 4.7.0.1098 backport by daniel_k (iaStorA.sys+iaStorF.sys) 3) StorAHCI by skulltera/OneCore (storahci.sys), compiled from Microsoft Windows 8.x DDK Samples, (require storport.sys from Windows 2003) 4) UniATA (opensource) 5) Intel RSTe AHCI/RAID 4.0.2.1019, for Windows 2003 only, enterprise controllers only(??) (iaStorA.sys+iaStorF.sys)) 6) StorAHCI from Windows 8 (require backported storport.sys from Windows 8) 7) StorAhci for Windows 2003, based on Microsoft Windows 8.x DDK Samples source code, https://sourceforge.net/projects/storahci-for-windows-2003/ Tip: Add PCI\VEN_8086&CC_0106 or PCI\VEN_8086&CC_010601 to *.inf as universal DEV_ID for any Intel AHCI Sata Controller AMD Motherboards Issues ACPI BSOD 0xA5 (0x0000000D, ..., ..., ...) duplicated _HID method Patch: - Skip DetectDuplicateHID processing (v5512 .text:00013F6C => jmp .text:00013F6C) BSOD 0x7E (..., ..., C0000005, ...) unknow error in AcpiArbCrackPRT Patch: (v5512 jnz short .text:0001BD6D => jmp short .text:0001BD6D) Intel USB3 Controller Drivers Intel released USB3.x drivers only for Windows 7/8/10, so there were many attempts to use drivers of other usb chip manufacturers. Most of them do not work at Intel hardware, some works, but have problems with PAE or USB3 ports. Following drivers confirmed to work in normal and PAE environment, solved, three solutions: 1) Microsoft Generic v6.2.9200.16384/v6.2.9200.22453 from Windows 8.0, recommended driver 2) AMD v1.1.0.0145 (need amdxhci_adresscalc_fix) 3) Fresco Logic v3.6.9.0 (extended to 32 ports) AMD and Fresco drivers have ssues with recognizing devices after plug<->unplug, sometimes ports go to power saving modes and can't back UAS (Attached SCSI Mass Storage) drivers also available, solved, many solutions: 1) UAS Driver from Windows 8 + storport.sys from Windows 2003, beta 2) UAS Driver from Windows 8 + storport.sys from Windows 7, beta 3) UAS Driver from Windows 8 + storport.sys from Windows 8, beta 4) VIA UAS Driver 5) Etron UAS Driver VIA and Etron UAS Drivers doesn't support Safe Remove, require fixes, solved (via_uas_fix, etron_uas_fix) By default VIA and Etron UAS works only with genuine vendor USB3.0 Driver, but they are generic(?) and can work with any USB3 driver vusbstor.inf: change USB_VIA\Class_08&SubClass_06&Prot_62 to USB\Class_08&SubClass_06&Prot_62 EtronXHCI.inf: change ENUSB\Class_08&SubClass_06&Prot_62 to USB\Class_08&SubClass_06&Prot_62 Patches for Microsoft Generic USB3 driver Windows 8 USB3 driver always report USB2 speed on inserted USB3 devices, MS call it "compatibility", but vendors driver report proper USB3 speed and dont have compatibility issues(?) Fix to report proper USB3 speed, usbhub3.sys (v6.2.9200.21180): .text:19C58: jnz 00019C63 => jmp 00019C63 (75 09 => EB 09) Patch for AMD driver (amdxhci_adresscalc_fix) This driver is known to have issues with PAE environment, need fix: - replace in amdxhc.sys: mov ecx, [esi+458h] ; esi+458h = store of 64bit adress mov eax, [esi+28h] mov [eax], ecx ; low part mov [eax+4], ebx ; dropped high part, ebx=zeroes..... to mov ecx, [esi+458h] mov eax, [esi+28h] mov [eax], ecx mov ecx, [esi+45Ch] ; HIGH part of 64bit mov [eax+4], ecx ; no more zeroes Patch for VIA UASP driver (via_uas_fix) Restore "Safe Remove": - replace in vusbstor.sys (v6.1.7600.4002): page:000209B4: mov [ebp+SurpriseRemovalOK], ebx -> NOPs (89 9D 70 FF FF FF 89 9D 68 FF FF FF => 90 90 90 90 90 90 89 9D 68 FF FF FF) Patch for Etron UASP driver (etron_uas_fix) Restore "Safe Remove": - replace in EtronSTOR.SYS (any version): OR dword ptr [eax+4], 0300h -> OR dword ptr [eax+4], 0000h 4GB+ RAM Support - Windows 2003 supports more than 4Gb RAM without additional actions, limited to some value depending "Edition" - Windows XP ServicePack1 supports more than 4Gb RAM without additional actions, limited to some value (16Gb ?) - Windows XP ServicePack2/3 don't support RAM above 4Gb, need patching, solved, many solutions: 1) PatchPae(v2) by wj32, remove limits only in kernel, lack of HAL_DMA patch 2) fix128/PatchPae(v3) by Evgen_b, contains unfinished HAL_DMA patch, kernel patch is OK 3) WinXPPAE(v2+) by Daniel_k, contains proper HAL_DMA patch, kernel patch is OK UEFI Boot - Bootmgr from some Vista Betas/Longhorns allow boot Windows XP x64 from UEFI x64, alpha, there is issues with Video card, https://www.betaarchive.com/forum/viewtopic.php?f=61&t=20327 - Boot Windows x32 on UEFI 32 UEFI32 on real hardware is rare, confirmed only on emulated environment, alpha, Guide LINK by Gelip - Quibble bootloader (experimental, opensource), alpha, no NTFS support, booting possible only if Windows installed on FAT partition, project page - https://github.com/maharmstone/quibble NVMExpress Drivers Many solutions: - Modified OFA 1.3/1.5 driver + storport.sys from Windows 2003 - MS Windows 7 NVMe Driver by daniel_k + backported storport.sys from Windows 7 - MS Windows 7 NVMe Driver + storport.sys from Windows 7 + Emu_Extender - Samsung NVMe driver + storport.sys GPT partitions Windows 2003 already supports GPT Partitions for non-booting disks, no need additional software Windows XP doesn't support GPT Partitions, solved for non-booting disks, one solutions: - Paragon GPT Loader enable access to 3TB+ Disks/GPT partitions (commercial product, currently not available for sale) Booting from GPT disk partially solved, need convert pure GPT to HybridMBR, Guide LINK by Levvon Saving crash dumps through storport based disk controller drivers To enable saving crash dumps with storport-based disk drivers on Windows XP need patch kernel (scsi support will be disabled) Disk Controller drivers written for Windows 8 mostly will not save crash dumps on disk, they use new API to get information from kernel about dump context List of patches: 1) IopGetDumpStack: Replace unicode string "scsiport.sys" to "storport.sys" This string is 3rd argument of "call _IopLoadDumpDriver@12" 2) IopGetDumpStack: Original XP kernel will disable loading storport emulator(diskdump.sys) if storport/miniport return "Device Object" This is not problem for Windows 2003/7/.., newer OS still load diskdump.sys even if storport/miniport return anything Replace "mov [ebp+ScsiDump], 0" with NOPs Example for ntkrpamp.exe v5512: PAGE:004A0E0F mov byte ptr [ebp-29h],0 -> NOP, NOP, NOP, NOP ]3) IopGetDumpStack: Storport doesnt use SCSI ports names and dont need to search name of driver, need to skip this block Example for ntkrpamp.exe v5512: in range PAGE:004A0F49-004A1018 replace first opcode with "jmp 4A1019" 4) Use diskdump.sys from Windows 2003 or Wondows 7 (Windows 8 version not tested) 5) IoInitializeCrashDump: XP kernel allocate for diskdump.sys buffer of 32Kb (same size in Windows 2000), diskdump.sys from Windows 2003+ expect buffer of 64Kb. To be compatible with new diskdump.sys need to increase buffer Replace "push 8000h" with "push 10000h" as 3rd arg of ExAllocatePoolWithTag call Modded AVX/AVX2 kernel Currently Proof-Of-Concept, only one kernel version supported LINK Projects for Developers/Advanced Users - Remote kernel debug over LAN or USB3 cable, https://github.com/MovAX0xDEAD/KDNET - ACPI DSDT/SSDT Patcher at boot time for any windows, https://github.com/MovAX0xDEAD/ACPI-Patcher - WinXP/W2003 ntoskrnl.exe Emu_Extender, https://github.com/MovAX0xDEAD/NTOSKRNL_Emu, https://msfn.org/board/topic/181615-ntoskrnl-emu_extender-for-windows-xp2003/ Research & Experiments Running Windows XP with "new generation" ACPI.sys taken from many Vista Beta/Longhorn version Running existing USB3 vendor's drivers on Intel USB3.0 controller Implementation of ACPI Timer/HPET on different windows generations Switching between DMA32/DMA64 under PAE Environment, Windows XP Switching between DMA32/DMA64 under PAE Environment, Windows 7 Unresolved Problems/Requested Features: - ACPI.SYS v.6666 lack 64-bit integers - ACPI.SYS v.6666 limits possible datatypes in arguments only to ACPI 1.0b Specification - Boot Windows XP/2003 x32 from UEFI x64 - Generating TRIM command for SSD in filesystem (NTFS/???) - Internal GPT support for x32 Windows XP by replacing disk.sys/partmgr.sys/??? from Windows 2003 - Boot Windows x32 XP/2003 from pure GPT - Restore full Windows XP SP1 implementation of PAE/DMA for Windows XP SP3 - Generic/Universal HDA Audio driver - CSM Emulator for UEFI x64 - DirectX 10/11 kernel support - NDIS 6.x for Windows XP/2003

StartAllBack 3.3.5

@Dietmar you may as well try my earlier suggestion -

Note regarding versions: The regular version will have a file name ending in _rebuild_#. Versions with a file name ending in _ungoogled disables embedded Google APIs in much the same way that "ungoogled-chromium" ( https://chromium.woolyss.com/ ) disables embedded Google APIs. The "ungoogled" version is recommended for those that prefer tighter control over a Google-based browser basically giving special treatment to Google cookies and violating user preference settings. A side effect to this approach (which also exists in "ungoogled-chromium") is that the Chrome Web Store is intentionally broken only in as far as the "Add to Chrome" button is concerned. This is great for those that prefer to manually install extensions as opposed to obtaining from the Chrome Web Store. A workaround to restore the "Add to" button (special thanks to @VistaLover for this solution) can be obtained from here -- https://github.com/NeverDecaf/chromium-web-store Mileage may vary, for me this only added the "Add to" button but clicking it only downloaded the extensions .crx (which I personally prefer anyway) as opposed to 'adding to' 360Chrome. I had similar results with official "ungoogled-chromium" on the official Chrome Web Store (restores "Add to" button but does not actually 'add to'). Special thanks to @Humming Owl for translated .png files. Special thanks to @Dixel for discussions leading towards the "ungoogled" versions. XP x86 SP2: v12, v13, and v13.5 work as-is in XP x86 SP2 but v11 requires special modifications - see this post by @we3fan Download links for starting from scratch with a NEW PROFILE: Regular: https://www.dropbox.com/s/mes4wez1v34w9k4/360ChromePortable_11.0.2031_rebuild_8.zip?dl=1 (last updated: Jan 9, 2022) https://www.dropbox.com/s/wol8va166au2p7j/360ChromePortable_12.0.1247_rebuild_12.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/6lnst7yp0dt34s5/360ChromePortable_13.0.2206_rebuild_9.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/8h4z346251wg7r8/360ChromePortable_13.5.1030_rebuild_6.zip?dl=1 (last updated: Jan 11, 2022) Ungoogled: https://www.dropbox.com/s/6z65t5yo08fr0ym/360ChromePortable_11.0.2031_rebuild_8_ungoogled.zip?dl=1 (last updated: Jan 9, 2022) https://www.dropbox.com/s/j5zxk7aqv9ljjjc/360ChromePortable_12.0.1247_rebuild_12_ungoogled.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/ld5dz2uwdowf1cz/360ChromePortable_13.0.2206_rebuild_9_ungoogled.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/glulv6r8sce6xpy/360ChromePortable_13.5.1030_rebuild_6_ungoogled.zip?dl=1 (last updated: Jan 11, 2022)

Polyfilling is just plugging in new JavaScript functionality at runtime not supported by the browser's engine, so your usage of "polyfill" in that sentence is kinda off. But I know what you meant. Specifics are tricky, an example is @InterLinked's chromefill extension for Chromium browsers (https://github.com/InterLinked1/chromefill). You basically write new functions and make them available in a way JS interperter encounters them before site's code that tries to call them. Due to the nature of this particular extension, it can be easily implemented as the user script. They're more universal and advanced users tend to already have an user script manager extension such as GreaseMonkey or TamperMonkey. You take the content of polyfills.js and add the metadata block like the one below at the top. There are additional options that are supported by user script managers, their docs are your friend, but these should be sufficient for now. // ==UserScript== // @name chromefill // @namespace http://yourwebsiteorjustuniquestringyouwilluseforyourscripts.net/ // @version 0.1 // @description Automatically injects polyfills for older browsers into webpages // @author Your name // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== Use the option to create a new user script in your user script manager and paste everything into the editor window and save. Set it ro run before other scripts you may have do. InterLinked's polyfills script was tested on Pale Moon 28.9.3 with GreaseMonkey for Pale Moon 3.31.4 and SRWare Iron 70 with TamperMonkey 4.15 on stackoverflow.com - not the best example since the site has other issues with old browsers, but the script seems to execute correctly, message about missing globalThis is gone. I don't know any other site to test. For usage with TamperMonkey, in its settings, Advanced mode should be set under Config mode and then Inject Mode set to Instant. Regarding limitations, you can't eg. make Firefox support Web Serial API with Polyfills since this requires new low-level code interacting with COM ports. Polyfills also don't cover new JavaScript language syntax, eg. the famous nullish coalescing operator or optional chaining operator.

If it helps anyone, I discovered a very simple trick that allows me to directly download Dropbox files without going directly to the website. You copy the link address of the Dropbox file you want to download, then put ?dl=1 at the end. So, for example, if you want to download the latest update of @NotHereToPlayGames's ungoogled 360EE 13.5, this is how the link should look: https://www.dropbox.com/s/glulv6r8sce6xpy/360ChromePortable_13.5.1030_rebuild_6_ungoogled.zip?dl=1 This trick should make it possible to download Dropbox files in most browsers, even very old ones that can't render the site correctly (such as RetroZilla). Typing this reply from Mypal 68, but I also have Serpent 52 open and have verified the trick there to make sure it works.

I am writing this reply from Mypal 68 too! Haven't posted here in months, but I just wanted to write in to say that on my old Pentium D, it's running extremely well. A little bit less stable than trusty Serpent 52 (which I am still keeping around, along with 'ungoogled' 360EE 13.5), but everything I've tried works fine! Of course, I am sure that later updates will have vastly improved stability. I'm definitely excited and hopeful for future breakthroughs in getting modern browsers working in XP. Between Serpent 52/Mypal 68/360EE 13.x, the modern web still seems to be quite manageable, but things change frequently these days. Also, many thanks to @feodor2 and @roytam1 for all of their hard work in helping to keep XP useful after all these years!

ACPIBusIrpQueryResourceRequirements(): ACPIBusIrpQueryResourceRequirements doesn't have trace output, we can rely only on ACPIDevPrint() text output

@Dietmar Creating fields was OK NBAS = NHLA shows as OK, but NHLA was evaluated as Buffer, must be Integer NHLL - One is OK, NHLL evaluated as 0x0 Integer, result = 0 - 1 = -1 = 0xffffffff NMAS = (NHLA + (NHLL - One)) is Failed Add() expect two integers, but first argument (Arg0=NHLA) evaluated as Buffer/Field How it was declared (on my bios): NHLL is OK, 32bit field, at Subtract() evaluated as 0x0 Integer NHLA is BAD, seems XP ACPI don't handle 64bit field declaration as Integer and alias it as Buffer type This declaration is not CreateQWordField opcode, it handled in other place(OperationRegion/Buffer opcode i guess ) On my Skylake H110 board this code has OS check, so DSDT authors know about ACPI compatibility

Hello @AstroSkipper I found something interesting in the www. This is a similar software as ProxhttpsProxy or HTTPSProxy that supports Tls 1.3 and it should even run under IE6. I tried to install it but failed. Here is the link: https://bitbucket.org/ValdikSS/oldssl-proxy/src/master/ Best regards

Feodor2 is back https://github.com/Feodor2/Mypal/blob/master/README.md

You can try to replace Windows 2000 acpi.sys with one that is linked on first page to WinCert. Or try explore that file on running Windows with Depency Walker to see if there are missing import. If no missing import, then you can try to replace it on running system

No, that was on 30.0.0, which I got before it was pulled (I don't dare to "downgrade"). However now I tried again and indeed see the issue is still there (didn't encounter it this morning)...

I didn't really read any condescension, per se. Disliked the pro-Mac rhetoric and the banking reference. Bingo! And that INCLUDES banking web sites. I once contacted Customer Service for one of the three largest credit card companies and requested to speak with the supervisor of the customer service representative. Then pulled teeth to get that supervisor to properly direct my call. All on account of me attempting to pay my credit card in a SECURE manner but their web site pulling over 60+ javascript files and I saw 8 (if I recall correctly) in the list that were coming from FACEBOOK and I don't even have a Facebook account. Quite a bit off-topic, apologies for the "rant". But it is kinda related, all these polyfills, from the way I understand it, all come into play NOT because the site you are visiting is employing them, but because they have OUTSOURCED large portions of their "web design". The "chaining" aspect of polyfill disturbs me, sounds similar to what "script kiddies" used to do when they "obfuscated" their code.

You have mentioned just "modern" Web 2.0 websites, like LinkedIn. They don't care about your old browser and they're not wrong on their side about that. They have to move forward with the path that is the Web 2.0. Don't get me wrong - this is just business for them. The world moved forward with that. Why should they care about someone using ancient browsers? Not good for their business. Meanwhile, these old browsers are Web 1.0, which is the path I strongly believe they should have followed - browsers should just display pages, not heavy web apps or any flashy stuff, like a js based dosbox emulator... not stuff like ReactJS... best we, as classic web developers, can do is what I told before, graceful degradation. Businesses like LikedIn won't care about that for the reasons I mentioned before. It's the progress of technology and business. I work for an organization that sells customized Moodle LMS with a theme that I built with the most modern HTML5/CSS3 stuff. And in spite of that, I did a test for Windows 98 & XP with some old browsers and while my Moodle instance was nearly functional, some parts of my design were blanked out, as expected. I do think that I did a good job considering the huge gap between old and new technology, and that the look of it was still pretty good, since I can log in, navigate, and do some activities in a course. This was only possible because of my "old school" style of programming HTML/CSS and attention to detail which subconsciously led me to do some graceful degradation even when I didn't want nor thought about it - I always try to rely more on CSS than JS for design solutions, this is only possible because of CSS3. I never liked JS, really. However, I did drop the Internet Explorer compatibility, years ago (circa 2019) because I totally despise how the Trident engine render the things in a page. I always needed a polyfill to fix that, server-side. I was always angered at how it was different to Gecko and Webkit based browsers. Now we support newer Edge and all other browsers. This helped to move forward the development of our product instead of losing time with *censored* old browsers. This is why I do understand why the business work that way with Web 2.0. We can't be bothered about ancient browsers and with using polyfills to support them anymore. This was the case when IE was still around and gave me a huge headache for nearly a decade. If you want to access modern websites with your old machine, just do the MITM technique. You'll need a modern machine between you and the web to do that effort. It will at least let you access TLS 1.3 websites by downgrading that protocol to your machine, but won't fix the issue with modern HTML5/CSS3 code not being understood by your browser. And please don't do some internet banking with that technique, as it is very unsecure for you. I do that for my old Win 9x and MacOS 9.2 emulators just to access a secondary email I set up for that purpose only, and some fun pages like this one and VOGONS where I don't have to disclose some sensitive data. Some techniques for example is Browservice (look for it on github) and Crypto Ancienne (also on github, a technique to overcome TLS 1.3 limitation for the Classilla browser on MacOS 9.2, but I think it could work for RetroZilla, since the codebase is similar to Classilla. This is the best you can do "client side". However, your problem is completely unfixable unless someone does a new browser for these old machines with a modern rendering engine - and this will never happen. Browsers like Pale Moon won't do that, because the premise of Pale Moon is to follow the path Mozilla should've followed instead of being a "Chrome wannabe" and with a different rendering engine. Best you can do is live with some concessions. If you want to make something really useful with your Web 1.0 browser, take a look at this niche effort on MacRumors forums: https://forums.macrumors.com/threads/web-1-1-building-the-new-old-web.2290616/ It's a small community effort to create a Web 1.1 (evolution of Web 1.0) network of pages to enjoy our old macs, pcs and ancient browsers. Cheers

I just saw the new Mypal beta release, based on Firefox 68 and I can say I am impressed on how smooth it is on my machine. Certainly there is a huge potential in this project. @feodor2 is a genius. I am writing those lines from Mypal 68.

I don't understand what do you mean. Your statement was makes me confusing.

Hi @kampaster , I think you dont know the blackwingcat extended kernel for windows 2000, for me PickMeApp work correctly on windows 2000 : at first you should to install the bwc update Windows2000-KB935839-v31aM-x86-ENU , link of update : http://blog.livedoor.jp/blackwingcat/archives/1299806.html and before you should to install wlu decompressor from bwc site : http://win2k.org/wlu/wluen.htm

@roytam1 : I just, accidentally, stumbled upon yet another UXP (longstanding) bug, that manifests itself on GitHub issues; the bug is there regardless of whether the relevant github-wc-polyfill extension is installed or not... I used recent Serpent 52.9.0/UXP builds to test. STR: 1. Load a new, fresh, Serpent 52.9.0 profile (default prefs, no add-ons) 2. New Tab => Paste & Go: https://github.com/JustOff/github-wc-polyfill/issues/45#issuecomment-1066105393 NB: It is imperative the body of the issue comment contain at least one active link (not only in the form of a plain "https://*" string, but any type of "linkified" string) 3. Place the cursor on top of the active link, then right click to access the browser's context menu; so far, so good: 4. Move the cursor away from the context menu, left-click to make the menu go away... 5. Repeat step 3; right-clicking this second time results in the whole content of the issue comment to get selected: I have successfully reproduced this bug with many GitHub issue-comments, with/without the gh-wc-pf add-on... Trying to find a regression range for this bug, I've spent considerable time and effort which, in the end, got me all the way back to mid-2020: Last Good build (without the bug): basilisk52-g4.6.win32-git-20200530-d6ba7ac-uxp-1cecef624-xpmod First Bad build (with the bug as described above): basilisk52-g4.6.win32-git-20200606-547d236-uxp-fdb918dea-xpmod Hopefully, the cause could be narrowed down... Obviously, this isn't a deal breaker, however little annoyances like this one make me use more often either 360EEv11/v12 for GitHub (with extra polyfills applied there via @InterLinked 's extension), while I'd be happy to cling on to Serpent 52 for most of my on-line tasks... Many thanks

Hi Winword2000, Club This is possible only if someone leak win2000 acpi sources from MS. Second option is binary patching without sources, but you need to find some Bro who interested with this job

Hello everyone. I'm sorry for the very long period of inactivity lately. I've had a lot going on outside of MSFN in my personal life that has kept me busy. I also walked away from an unhealthy relationship and have been taking steps to rebuild my life since then, which has kept me from being able to update the list for the past several months. In light of the recent announcement that MSFN is going offline, I will be moving my list over to a forum hosted by my friend Ryan: http://forum.eclectic4un.me/ This will take a while as I need to manually re-add all of the links and formatting, but I will post the link here when it is finished. Feel free to join our forum if you're looking for a new home once MSFN is no longer available! We're still grassroots at the moment, but we will be building a new legacy software community over there and we'd love to have you join us (@Ximonite& @win32 are already there and have pertinent posts related to Vista Extended Kernel & Win2000's KernelXE!). Thank you so much everyone here for your contributions to the list over the past 6 years. It has been my pleasure to help provide this information to Vista users for the past several years, and I like to believe our efforts have helped many Vista (and even XP) users over the years. I'm sad to see MSFN go, but all good things do come to an end. Best regards

PrivacyTests.org No. 6 Open-source tests of web browser privacy. Updated 2021-11-24: https://privacytests.org/

Well, after several weeks of reading, I finally reached the (current) end of "My Browser Builds (Part 3)!" No thanks to the forum software, which reset my "last visited" page to back to page 1 when the thread was moved this week (need an emoji for "mildly irritated" here - "angry" doesn't quite fit). Still rocking Serpent 55 as my main browser, even though it's showing its age. Using New Moon 28 + JustOff's add-ons for GitHub/GitLab (I'd use Serpent 52, but I can't run 52 and 55 at once). Of course very disappointed with some of what I read: MCP bullying @feodor2 into axing MyPal/Centuary and taking the UXP source repo private (now releasing source only with release builds; probably the bare minimum they can get away with under MPL). It does show that all MAT's bluster about "proper branding" was nothing more than an excuse to harass @roytam1, since MyPal followed all his branding rules and still got targeted! (Although if I were to suggest a new name for New Moon at this point, I'd probably go with Uranus, for reasons that should be obvious ) Even though I don't expect to use it much, I grabbed and installed the last MyPal build (thanks, Wayback Machine) out of spite. Also disappointed, but not surprised, with Google playing "Monopoly" and forcing their "Web Components," or whatever their nonsense is called, down all our throats. Why use simple HTML when you can make the Web so complicated it'll bring a quad-core CPU to its knees instead? Main reason Serpent is looking so old these days. Reminds me of Micro$oft's reindeer games from a quarter century or so ago! Haven't started reading the 360EE threads yet, but that'll probably have to be my next task. (Now angry fits ) OTOH, very pleased that @mixit spent so much time finally tracking down and fixing that nettlesome 23-minute (or thereabouts, depending on audio sampling rate, of all things) video playback bug! Even got the fix into the Mozilla code base, even though it's a moot point nowadays. I like that idea - sort of an XP version of Waterfox (yes, I know Waterfox was forked from FF 56) - but I rather doubt it'd help much with the modern Web. I also vaguely recall this being discussed once before, and I think it was said that FF 53 is pretty much the end of the line for XP, which basically gives you Serpent 55. If it could be done, though, it would be compatible with more WebEx add-ons, which is something, at least.

My hunch is that the Google monopoly plays HEAVILY into that !!! There is a very large amount of .css code dedicated to the "dark theme" that has nothing to do with the 360Chrome user interface - so it seems evident that there was a "concensus" by complying websites that wanted to be "included". Or I supposed more than likely something of the form of "publicly disclosed .css code" -- "If you want to follow in our footsteps and be 'dark' at night, use these .css selectors and users will flock to your site like a dung beetle to a turd." Google fully owns and controls YouTube, DoubleClick, and Fitbit (among others - YouTube our primary concern here). There were industry rumors circa 2015/2017 that Twitter was going to be acquired by Google or Microsoft - that didn't happen but Google did acquire "portions" of Twitter. But in all honesty, I just don't get it! I hear (over and over and over, actually) that my XP theme is "blindingly bright". My monitors are only 1920x1080 - they have higher resolutions but I only use them for certain map-based programs where I want to see more of a city/town at one time. I do not "hide" the taskbar so that's 1920x1050 usable by 360Chrome. If you use default tabs in the middle, my theme uses 76 rows of pixels at the top and another 25 at the bottom for the status bar. 76 + 25 = 101. Consumed from a total of 1050 horizontal lines of resolution. That is 9.62% of total horizontal lines, not undermining that - but my point is that it is the remaining 90.38% of your screen that is "blinding" you (ie, the web site that you are visiting). Auto-hide the XP taskbar and it only drops from 9.62% to 9.35%. Display tabs on top instead of bottom and we are down to 7.50% to 7.71% depending on taskbar presence - and 92.29% to 92.50% of the screen being the website that you are visiting. It "seems to me" that if you don't want basically 91% to 93% of your screen "blinding you", then we are talking about Stylus .css sheets customizing those pages and not the brower user interface only consuming 7% to 9% of your screen. Okay, we do have the settings menus - black text on white background -- but just how often are you "in" the settings menus ??? Is it the MENUS that you dark-theme users are so "against" ???

That's the great thing about the internet. You could be a dog and we wouldn't even notice! If you have spelling problems, well then, you have to accept, that some typos lead to funny jokes (plenty of great jokes work that way, exchanging one letter with another, mixing two words...). You'll also have the burden to be judged by that, and even insulted. "Grammar Nazis", so to speak, will try to stomp on you, regardless of the contents of what you've written. But that has one advantage: Your bad spelling will work as some kind of filter, as it freaks out the Grammar Nazis and the spelling-tolerant people will remain calm and engage in a discussion with you staying on topic.

That's not really a typo, it's a neologism, something cross-breed between an alarm and an alert is an alart jaclaz