Jump to content

George King

Members
  • Posts

    459
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by George King

  1. @skulltrail

    Any news for mising functions for SD / MMCE in One-Core-API v2.5?

     

    I have also prepared https://github.com/MovAX0xDEAD/NTOSKRNL_Emu code with new blank functions, that "only" needs C code to be added into blank functions.

    So these functions needs C code to get extender work with Generic MMC / SD v8056

    PoFxIdleComponent
    IoSynchronousCallDriver (probably done)
    PoFxSetDeviceIdleTimeout
    PoFxUnregisterDevice
    PoFxStartDevicePowerManagement
    PoUnregisterPowerSettingCallback
    PoFxActivateComponent
    KeLeaveGuardedRegion
    KeEnterGuardedRegion
    PoFxCompleteIdleCondition
    PoFxCompleteIdleState
    PoFxReportDevicePoweredOn
    PoFxCompleteDevicePowerNotRequired
    PoFxRegisterDevice
    IoGetActivityIdIrp
    RtlQueryRegistryValuesEx
  2. Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)

     Here are compiled ACPI2.0 v4 from latest sources
     
    1) x86 Windows XP x86 SP3 (5.1.2600.7777.4) + Windows Server 2003 SP2 (5.2.3790.7777.4) debug and free
     
    2) x64 Windows Server 2003 / XP SP2 (5.2.3790.7777.4) debug and free
     
    https://www.mediafire.com/file/wsqgptapdrxhidf/ACPI2.0_v4_x86+x64_5.1+5.2.7z/file

    acpi-Ver.png

     

    Extras included:

    a) _OSI extra OS list to unlock hidden devices

    b) modded acpiosnt.rc to overwrite PruductVersion attribute in file info, replaced "," with "." so it's now in same logic as other standard files, added .4 to easily detect which patch was used as build base

  3. @skulltrailAny chance to get these kernel functions? I would like to see working sdbus.sys and sdstor.sys from Windows 8.0 to get Generic SD / MMC driver

    PoFxIdleComponent
    IoSynchronousCallDriver
    PoFxSetDeviceIdleTimeout
    PoFxUnregisterDevice
    PoFxStartDevicePowerManagement
    PoUnregisterPowerSettingCallback
    PoFxActivateComponent
    KeLeaveGuardedRegion
    KeEnterGuardedRegion
    PoFxCompleteIdleCondition
    PoFxCompleteIdleState
    PoFxReportDevicePoweredOn
    PoFxCompleteDevicePowerNotRequired
    PoFxRegisterDevice
    IoGetActivityIdIrp
    RtlQueryRegistryValuesEx
    

  4. Hi, 

    is there an chance to compile current version 1.7.0.16 to support XP host with .NET 4.0?

    Or where I can get older version 1.7.0.13 as new .NET requirement was from 1.7.0.14 according to changelog. I would like to have latest working one under XP Hosts

     

    https://www.win-unattended.de/viewtopic.php?f=17&t=73

     

    Many thanks

     

    EDIT: I found 14 and 15 online on various places. But nothing for 13. Anybody downloaded it and have archived 13?

     

    EDIT2: 13 doesn't work under XP, no error, icon appear near clock, then disappear

  5. @Andalu

    How I prepared environment and how I compiled it on Windows 10 21H2 x64. Note I added some aditional steps to be able compile XPSP1 files as x64 target

    1) Extracted NT5 SRC and followed compile guide for 2003 to set up latest environment (Yes for 2003 see below why)

    2) Download TXT ACPI v2.0 XPSP1toXPSP2 patch + patch.exe 

    https://nav.dl.sourceforge.net/project/gnuwin32/patch/2.5.9-7/patch-2.5.9-7-bin.zip

    3) Open CMD in Base\busdrv\acpi\ and update source tree with patch.exe -Np1 -u -l -i sp1_to_sp3(ACP2).patch

    4) Grab tools folder from 2003 source tree, backup XP one and copy it here

    5) Copy build.exe and mofcomp.exe from x86 to amd64 in tools folder

    6) Run razzle.cmd as CMD /k  tools\razzle.cmd Win32 offline No_urt no_binaries no_certcheck No_prefast (you can add Free parameter if you would like compile smaller non debug file). If someone add needed ASM code converted to C in devpower.c , internal.c , type2op.c , osnotify.c., then we can compile x64 acpi.sys too, just replace Win32 with Win64 amd64

    7) Go to Base\busdrv\acpi\driver\ and then build /Degbw

    😎 Compiled ACPI.sys is in Base\busdrv\acpi\driver\nt\obj\i386\

  6. 11 hours ago, Andalu said:

    @George King

    I tried your last acpi.sys from the "i386_free" folder on the following boards:

    - Gigabyte H470 HD3 -> A5 BSOD (0x011, 0x08, 0xB998B000, 0x20160527);

    - Asus Prime Q370M -> A5 BSOD (0x03, 0xA755B9BC, 0xC014008, 0x494E495F);

    - Asrock H310M-HDV -> A5 BSOD (0x03, 0x97EE06D0, 0xC0140008, 0x494E495F);

    - Asrock B250M Pro4 -> A5 BSOD (0x03, 0x8A8A64C4, 0xC0140008, 0x494E495F);

    - Asus Prime B250M -> it works as well as the previous version.

    @Mov AX, 0xDEAD Can you have a look into code for possible solution please? Seems like similar BSOD as encountered 

    @Dietmar on Z690 Asrock extreme board -> A5 BSOD (0x03, 0x98E1DBA4, 0xC0140008, 0x494E495F)

  7. Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)

     Here are compiled ACPI2.0 v4 from latest sources
     
    1) x86 Windows XP x86 SP3 (5.1.2600.7777.4) + Windows Server 2003 SP2 (5.2.3790.7777.4) debug and free
     
    2) x64 Windows Server 2003 / XP SP2 (5.2.3790.7777.4) debug and free
     
    https://www.mediafire.com/file/wsqgptapdrxhidf/ACPI2.0_v4_x86+x64_5.1+5.2.7z/file

    acpi-Ver.png

     

    Extras included:

    a) _OSI extra OS list to unlock hidden devices

    b) modded acpiosnt.rc to overwrite PruductVersion attribute in file info, replaced "," with "." so it's now in same logic as other standard files, added .4 to easily detect which patch was used as build base

  8. @DietmarNice tests. Of course vendors are lying about performance. Machines about 2010+ have only differences in GPUs which I need only for 4K video. CPUs are mostly same but another nm technology was used to assemble it. Yes, more changes can be found, like removing IDE, PCI etc..

    First big boom will be with quantum computers (powered by small fuse reactors) :D

  9. 14 hours ago, Dietmar said:

    I just build an XP SP3 with the Sata driver from Kai and the storport.sys with SMART support, with all updates for XP and my last acpi.sys from last August.

    For USB I use the from Win8.1 ported driver.

    It boots XP SP3 on all(!) my Intel boards from x58 to z690, always all USB works,

    niccccee😍

    Dietmar

    Ported USB drivers from 8.1? Any links? :)

  10. On 1/6/2022 at 4:48 PM, Mov AX, 0xDEAD said:

    No, PDB not published for early vista betas, PDB exist since v5342, maybe earlier, but i not tested

    Thats sad. I would like to see patched ACPI for x64 too. Can you please create some kind of 6666 for x64 in same way as you did for x86?ACPI_LatestXP+5048_x64.7z

    According to this info I can only apply fix for 0xA5 (0x11, 0x08, ..., ...) _AMLILoadDDB. I cannot find now same places. A good start would be 6666 for x64. Can you please have a look on it? Or do you have some precreated file? I have attached latest 4099 ACPI for XP and 5048 from Longhorn.

    Windows XP/2003 support 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, 99% solved, two 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 generate 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 from Windows XP SP3 (v.5512->v.6666) 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
    
    - 0xA5 (0x11, 0x08, ..., ...) unknow error in _AMLILoadDDB, probably fail after parsing DSDT/SSDT table, solved
    
    Patch (by diderius6):
    - 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
    v5512 & 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 )
×
×
  • Create New...