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

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)

Added customElements to YouTube and now have live previews (animated thumbnails) in search results on Pale Moon. Also spoofing user agent as Firefox 96. I haven't determined the oldest version they pick to use customElements. Did they remove them on the related / suggested videos on the right side? Never mind, depends on the video. One thing about Babel, you may want to pay attention to source type setting. "Script" is probably correct for most (all?) of the time. For one thing, "Module", where the name implies special kind of JS file, it also always adds "use strict;". The code you're pasting from random scripts may use features of the language that "use strict;" prevents from working. Edit: got stackoverflow.com's full-anon.en.js also transpiled. Again, no account to login, but the site seems to work correctly at the first glance.

@Dietmar thanks for the hacked acpi.sys. It worked as expected.

@maile3241 No further information required anymore! Unfortunately, as usual, problem solved by myself. Now notification shield appears if important updates are available. Without any proxy! ProxHTTPSProxy or HTTPSProxy is not required for connecting via Automatic Updates client. And this is a screenshot with my AU client doing automatically its job even after restarting my system:

@Mov AX, 0xDEAD After again crazy fight with compiler (I use only XP SP3 for everything) here are the new and tested acpi.sys files, "free" and "debug" version. This time without any binary hack ) Dietmar https://ufile.io/wvxclbkz

Not allowing someone who disagrees with you to have the last word or let something slide is what caused this thread to get out of control. MSFN does not have a War Room but we do have a Hurt Locker. Edit: We can try again now

No, you can try DOSBox-X, but my past experience with DOSBox-X is that chances are that it will be very, very unstable. Get 86Box or PCem for that.

StartAllBack 3.3.5

I've been using it for about two weeks now, I don't think it's truly that bad once you install explorer patcher to return some of the graphical interfaces back to the Windows 10 style. But one thing that has irritated me about Windows 8+ is honestly the graphical interface. I know you can choose a color for the titlebar but it's just one, flat color. I wouldn't mind a few aero traits coming back to Windows 11 though. Some of the window animations remind me of Aero to a degree but the flatness drives me insane. Then again, I preferred the original classic theme the best. It felt more colorful and vivid instead of this flat, gray/white garbage that comes out of box.

you'll likely need an AHCI driver for your hardware.

@Birkin_Pl My suggestion - Start from a fresh 2000 install, then install this - http://ximonite.com/kernelxe/Windows2000-KernelXE-v0.2.4.2-x86-ENU.exe then install unmodded XP 368 driver. Kernelxe covers missing dependencies for the driver so I think it should work.

Whats the best way to get in touch with Blackwingcat? I'd like to look at their extended core source code (assuming they'll let me) edit: whats the deviceID on that ? USB controller?

Try the mouse and keyboard out in the USB ports that you connected the Wireless N/Flashdisk to, does Keyboard/mouse work in those ports?

@WinWord2000 OK, done. - It's still in the quote though, can you delete that?

@WinWord2000 Neither. I'll fork from this - link deleted - since I know it works. get it compiling for Win2kDDK and go from there.

Update (January 13, 2022): The update pack and update rollup have been updated to fix a bug with ntoskrnl.exe file (affecting single threaded systems). All files are now available from the Internet Archive: https://archive.org/details/xp-unofficial-sp4-jan2022_20220113

is there any possibility for a source code release?

try here - https://support.hp.com/au-en/drivers/selfservice/hp-laserjet-2400-printer-series/416419

Does anyone know of an Alternative Device Manager for Win98? Preferably one that shows HWIDs? So I can know exactly which device I'm installing

Thanks very much

Can anyone compile this storahci driver sample but target XP? https://github.com/Microsoft/Windows-driver-samples/tree/master/storage/miniports/storahci

I can compile storahci sample with vs2017 for default target platform windows 10 - any tips for compiling for earlier platforms?

I can recall it worked in the past. I remember being able to use storport from server 2003 in the past on XP on an old build using an old version amd_sata driver.

I managed to get the USB 2.0 card drivers working, plugged in a USB mouse, now all is good.

tried a zowie usb mouse, similar misbehavior from that too. Oh well, If I make any progress on getting this to work i will update.

is there any way possible to use you own customized CAB files for win9x installation? if so how?

Would anyone want to use Unraid with hardware pass-through to run Windows 98? Or is the objective in this case to have windows 98 running native without any virtualization at all?

For USB - This might be of use - http://www.ebay.com/itm/External-4Port-USB2-0-PCI-Express-X1-Controller-Card-Adapter-Chipset-for-Moschip-/331978294559?hash=item4d4b72c51f - For Sound - there is also a pci-e sound card compatible with windows 98 (maybe also DOS) http://www.ebay.com/itm/PCI-E-5-1-Sound-6-port-sound-card-CMI8738-cinema-stereo-Surround-Sound-Card-ED-/112261025573?hash=item1a23474f25:g:O8EAAOSw5cNYcCwa

I've been trying to use an old version of Kernelex that dibya gave me to patch ntoskrnl and ksecdd with the necessary functions needed for Intel USB 3.0 driver to work. I used visual studio 6.0 to compile this old kernelex It applies a patch, but some of the functions, like EtwRegister, don't get applied correctly and I'm not 100% sure how to fix. https://ufile.io/tna8m Any ideas?

Out of curiosity I was looking at windows 10 ntoskrnl with dependency walker and noticed all these ext-ms-win dll files it depends on. I noticed however that the files do not seem to exist in c:\windows\system32 (or sysWOW64) - So where are these dependencies actually located?

It's more complex than that apparently

Cool, Thanks very much!

grab a windows 10 ISO and install in a VM, you can see they're absent.

Did any of the Vista betas use NTLDR as bootkoader?

anywhere publicly?

which one? is it available online anywhere?

Does anyone know where I can find stpboot.bin as referred to in this thread? Make your own NT OS Loader (NTLDR+SetupLDR)! https://www.betaarchive.com/forum/viewtopic.php?t=5880 - The link used in the thread appears to be dead

what are you trying to achieve by doing that?

i would be happy to test it out if you want me to.

isn't the usbxhci.sys file a generic driver?

I wonder if this works, if it would be possible to use the generic microsoft usb3 driver in xp?

You can get Windows 98 with MIDI through the latest DOSBOX found here http://ykhwong.x-y.net/ It's not a simple task getting windows 98 installed in DOSBOX though. I can help you with it if you have the patience

I'm making some USB 3.0 txtsetup.oem files so that you can add USB 3.0 support to XP textmodem as well as integrate with nlite. (As it is nowm if you install windows XP on a USB stick through a USB 3.0 port, you will get a 0x7b BSOD) ASMEDIA [Disks] disk1="ASMEDIA USB3 Installation Disk",\asmtxhci.inf,\ [Defaults] SCSI=asmtxhci [SCSI] asmtxhci="ASMEDIA USB3 Controller Driver" asmthub3="ASMEDIA USB3 HUB Driver" [Files.SCSI.asmtxhci] driver=disk1,asmtxhci.sys,asmtxhci inf=disk1,asmtxhci.inf catalog=disk1,asmtxhci.cat [Files.SCSI.asmthub3] driver=disk1,asmthub3.sys,asmthub3 inf=disk1,asmthub3.inf catalog=disk1,asmthub3.cat [HardwareIds.SCSI.asmtxhci] id="PCI\VEN_1B21&DEV_1040","asmtxhci" id="PCI\VEN_1B21&DEV_1041","asmtxhci" id="PCI\VEN_1B21&DEV_1042","asmtxhci" id="PCI\VEN_1B21&DEV_1142","asmtxhci" [HardwareIds.SCSI.asmthub3] id="USB\ASMEDIAUSBD_Hub","asmthub3" ETRON [Disks] disk1="ETRON USB3 Installation Disk",\EtronX~1.inf,\ [Defaults] SCSI=EtronXHCI [SCSI] EtronXHCI="ETRON USB3 Controller Driver" EtronHUB3="ETRON USB3 HUB Driver" EtronSTOR="ETRON USB3 STOR Driver" [Files.SCSI.EtronXHCI] driver=disk1,EtronX~1.SYS,EtronXHCI inf=disk1,EtronX~1.INF catalog=disk1,etronx~1.cat [Files.SCSI.EtronHUB3] driver=disk1,EtronH~1.SYS,EtronHUB3 inf=disk1,EtronX~1.INF catalog=disk1,etronx~1.cat [Files.SCSI.EtronSTOR] driver=disk1,EtronS~1.SYS,EtronSTOR inf=disk1,EtronX~1.INF catalog=disk1,etronx~1.cat [HardwareIds.SCSI.EtronXHCI] id="PCI\VEN_1B6F&DEV_7023","EtronXHCI" id="PCI\VEN_1B6F&DEV_7052","EtronXHCI" [HardwareIds.SCSI.EtronSTOR] id="ENUSB\Class_08&SubClass_06","EtronSTOR" [HardwareIds.SCSI.EtronHUB3] id="ENUSB3\ROOT_HUB30","EtronHUB3" id="ENUSB3\EXT_HUB10","EtronHUB3" id="ENUSB3\EXT_HUB20","EtronHUB3" id="ENUSB3\EXT_HUB30","EtronHUB3" NEC (uPD720200 & uPD720200a) [Disks] disk1="RENESAS USB3 Installation Disk",\nusb3xhc.inf,\ [Defaults] SCSI=nusb3xhc [SCSI] nusb3xhc="Renesas USB3 Controller Driver" nusb3hub="Renesas USB3 HUB Driver" [Files.SCSI.nusb3xhc] driver=disk1,nusb3xhc.sys,nusb3xhc inf=disk1,nusb3xhc.inf catalog=disk1,nusb3xhc.cat [Files.SCSI.nusb3hub] driver=disk1,nusb3hub.sys,nusb3hub inf=disk1,nusb3hub.inf catalog=disk1,nusb3hub.cat [HardwareIds.SCSI.nusb3xhc] id="PCI\VEN_1033&DEV_0194","nusb3xhc" [HardwareIds.SCSI.nusb3hub] id="NUSB3\ROOT_HUB30","nusb3hub" id="NUSB3\CLASS_09","nusb3hub" NEC (uPD720201 & uPD720202) [Disks] disk1="RENESAS USB3 Installation Disk",\rusb3xhc.inf,\ [Defaults] SCSI=nusb3xhc [SCSI] nusb3xhc="Renesas USB3 Controller Driver" nusb3hub="Renesas USB3 HUB Driver" [Files.SCSI.rusb3xhc] driver=disk1,rusb3xhc.sys,rusb3xhc inf=disk1,rusb3xhc.inf catalog=disk1,rusb3xhc.cat [Files.SCSI.rusb3hub] driver=disk1,rusb3hub.sys,rusb3hub inf=disk1,rusb3hub.inf catalog=disk1,rusb3hub.cat [HardwareIds.SCSI.rusb3xhc] id="PCI\VEN_1912&DEV_0014&REV_01","rusb3xhc" id="PCI\VEN_1912&DEV_0014&REV_02","rusb3xhc" id="PCI\VEN_1912&DEV_0014&REV_03","rusb3xhc" id="PCI\VEN_1912&DEV_0015&REV_01","rusb3xhc" id="PCI\VEN_1912&DEV_0015&REV_02","rusb3xhc" [HardwareIds.SCSI.rusb3hub] id="RENESAS_USB3\ROOT_HUB30&VID_1912&PID_0014","rusb3hub" id="RENESAS_USB3\ROOT_HUB30&VID_1912&PID_0015","rusb3hub" id="RENESAS_USB3\CLASS_09&SUBCLASS_00&PROT_00","rusb3hub" id="RENESAS_USB3\CLASS_09&SUBCLASS_00&PROT_01","rusb3hub" id="RENESAS_USB3\CLASS_09&SUBCLASS_00&PROT_02","rusb3hub" id="RENESAS_USB3\CLASS_09&SUBCLASS_00&PROT_03","rusb3hub" id="RUSB3HUB,RENESAS_USB3\CLASS_09&SUBCLASS_01","rusb3hub" TEXAS INSTRUMENTS [Disks] disk1="TEXAS USB3 Installation Disk",\tixhci.inf,\ [Defaults] SCSI=tixhci [SCSI] tixhci="TEXAS USB3 Controller Driver" tihub3="TEXAS USB3 HUB Driver" [Files.SCSI.tixhci] driver=disk1,tixhci.sys,tixhci inf=disk1,tixhci.inf catalog=disk1,tixhci.cat [Files.SCSI.tihub3] driver=disk1,tihub3.sys,tihub3 inf=disk1,tihub3.inf catalog=disk1,tihub3.cat [HardwareIds.SCSI.tixhci] id="PCI\VEN_104C&DEV_8241","tixhci" [HardwareIds.SCSI.tihub3] id="USB\TIUSBD_Hub","tihub3" The VIA and Fresco-Logic controllers are dependent on the Kernel Mode Driver Framework, and thus-far have proven very difficult to get working, so they won't be included for now. Unless someone is willing to help me with the VIS/Fresco problem.

Hello all, I'm from the driverpacks.net forum, Caleb37 posted there about this problem he was having there too. - http://forum.driverpacks.net/viewtopic.php?id=6403 I'm asking, is the megasr.sys driver that intel provide for X79 RAID - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20963〈=eng&OSVersion=%0A&DownloadType=Drivers) HWID: PCI\VEN_8086&DEV_2826&CC_0104 Is this driver in fact incompatible for XP Textmode with RAID?

OK sorry for the confusion, I should clarify I would like a command prompt script (or batch file, if the term is still used) to loop through all the drive letters, FOR %%i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %%i:\foundme.txt and then if it's finds foundme.txt, to set that drive, based on the drive letter to read only, using diskpart did I describe it well enough?

Hi everyone! new here, looking for some help So I've already got XP working on USB stick in USB2 I'm attempting to inject a textmode driver into my install for USB3 support I've attempted to create a txtsetup.oem files for my USB3 controller (A Renesas USB3 Controller) I've injected successfully but have not had much luck installing as it BSODs right after the part where you can select your RAID Driver here is my attempt at a txtsetup.oem (not really sure how to do this, so it's sure to have mistakes) TXTSETUP.OEM [Disks] disk1="RENESAS USB3 Installation Disk",\nusb3xhc.inf,\ disk2="RENESAS USB3 HUB Installation Disk",\nusb3hub.inf,\ [Defaults] SCSI=nusb3xhcx86 [sCSI] nusb3xhcx86="nusb3xhc Driver x86" nusb3xhcx64="nusb3xhc Driver x64" nusb3hubx86="nusb3hub Driver x86" nusb3hubx64="nusb3hub Driver x64" [Files.scsi.nusb3xhcx86] driver=disk1,nusb3xhc.sys,nusb3xhc inf=disk1,nusb3xhc.inf catalog=disk1,nusb3xhc.cat [Files.scsi.nusb3xhcx64] driver=disk1,nusb3xhc.sys,nusb3xhc inf=disk1,nusb3xhc.inf catalog=disk1,nusb3xhc.cat [Files.scsi.nusb3hubx86] driver=disk1,nusb3hub.sys,nusb3hub3 inf=disk1,nusb3hub.inf catalog=disk1,nusb3hub.cat [Files.scsi.nusb3hubx64] driver=disk1,nusb3hub.sys,nusb3hub3 inf=disk1,nusb3hub.inf catalog=disk1,nusb3hub.cat [HardwareIds.scsi.nusb3xhcx86] id="detected\nusb3xhc","nusb3xhc" [HardwareIds.scsi.nusb3xhcx64] id="detected\nusb3xhc","nusb3xhc" [HardwareIds.scsi.nusb3hubx86] id="detected\nusb3hub","nusb3hub" [HardwareIds.scsi.nusb3hubx64] id="detected\nusb3hub","nusb3hub" [Config.nusb3xhc] [Config.nusb3hub] Any help would be appreciated!

OK, I used nlite to inject the USB3 Drivers, and then I edited TXTSETUP.SIF adding these manually [BootBusExtenders.Load] nusb3hub = nusb3hub.sys nusb3xhc = nusb3xhc.sys [BootBusExtenders] nusb3xhc = "Renesas Electronics USB 3.0 Host Controller",files.none,nusb3xhc nusb3hub = "Renesas Electronics USB 3.0 Root Hub",files.none,nusb3hub Seems to be working now, it's seeing my USB So one last question, does anyone know what to add to a TXTSETUP.OEM file so that it will add those lines to BootbusExtenders automatically? heres my revised TXTSETUP.OEM [Disks] disk1="RENESAS USB3 Installation Disk",\nusb3xhc.inf,\ disk2="RENESAS USB3 HUB Installation Disk",\nusb3hub.inf,\ [Defaults] SCSI=nusb3xhcx86 [SCSI] nusb3xhcx86="Renesas USB3 Driver x86" nusb3hubx86="Renesas USB3 HUB Driver x86" [Files.SCSI.nusb3xhcx86] driver=disk1,nusb3xhc.sys,nusb3xhc inf=disk1,nusb3xhc.inf catalog=disk1,nusb3xhc.cat [Files.SCSI.nusb3hubx86] driver=disk1,nusb3hub.sys,nusb3hub inf=disk1,nusb3hub.inf catalog=disk1,nusb3hub.cat [HardwareIds.SCSI.nusb3xhcx86] id="PCI\VEN_1033&DEV_0194&REV_03","nusb3xhc" id="PCI\VEN_1033&DEV_0194&REV_04","nusb3xhc" [HardwareIds.SCSI.nusb3hubx86] id="NUSB3\ROOT_HUB30","nusb3hub" id="NUSB3\CLASS_09&SUBCLASS_00&PROT_00","nusb3hub" id="NUSB3\CLASS_09&SUBCLASS_00&PROT_01","nusb3hub" id="NUSB3\CLASS_09&SUBCLASS_00&PROT_02","nusb3hub" id="NUSB3\CLASS_09&SUBCLASS_00&PROT_03","nusb3hub" [Config.nusb3xhc] value = Interrupt Management\MessageSignaledInterruptProperties,MSISupported,1,0x00010001,1 value = "", ErrorControl, REG_DWORD, 1 value = "", Group, REG_SZ, "Boot Bus Extender" value = "", Start, REG_DWORD, 0 value = "", Type, REG_DWORD, 1 [Config.nusb3hub] value = "EventMessageFile",0x00020000,"%11%\iologmsg.dll;%12%\nusb3hub.sys" value = "TypesSupported",0x00010001,7 value = "", ErrorControl, REG_DWORD, 1 value = "", Group, REG_SZ, "Boot Bus Extender" value = "", Start, REG_DWORD, 0 value = "", Type, REG_DWORD, 1 just wondering what to add to it so it will add the lines to BootbusExtenders Automatically Thanks for the help

So I attemped to follow your instructions and edited TXTSETUP.SIF as well as hivesft.inf I created USB3\Renesas Directories but it says it cannot find nusb3hub.sys

OK, hers my new TXTSETUP.OEM Any problems with it? It's made these changes to TXTSETUP.SIF