Jump to content

Damnation

Member
  • Posts

    797
  • Joined

  • Last visited

  • Days Won

    3
  • Donations

    0.00 USD 
  • Country

    Australia

Posts posted by Damnation

  1. @blackwingcat

    Would you maybe have any interest in porting the ntoskrnl_emu extender of XP over to 2000?

    I've made some attempts, nothing working as of yet though.

    XP acpi.sys - BSOD 0x1E KMODE_EXCEPTION_NOT_HANDLED in hal.dll

    2k3 storport / storahci - BSOD D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL

    ---

    I'm not skilled at all with kernel level debugging and am not sure how to solve this.

    ---

    Any interest in this?

  2. @Mov AX, 0xDEAD

    I know Windows 98 works a bit differently to 2000/XP, but 98 does have some WDM driver support in the form of it's NTKERN.VXD file that gets used to load WDM drivers on 98.

    Since 98 does have some WDM driver support I was wondering if it might be possible to write a WDM extender for 98 to improve hardware support like you did with XP?

    Maybe figure out how NTKERN.VXD works?

    Some stuff from the 98 DDK that might help:   https://ufile.io/5pokmhe8

  3. 6 hours ago, cyberluke said:

    Can this be used to implement ACPI driver that will in fact ignore ACPI for BIOS that does not support ACPI and does not have ACPI table? Something like silently ignore ACPI, provide SMP support (multiprocessor support via MPS multiprocessor) and don't throw BSOD?

    @cyberluke

    Not quite, to disable ACPI you'll also need a type of HAL that specifically ignores ACPI.

    Multiprocessor ACPI HAL is the best HAL for modern hardware, the other HALs might not even work.

  4. @Dietmar

    Thanks,

    So this message means

    Quote

    'This Device Manager error message indicates that the function driver for the device returned an error from its AddDevice routine.

    But I'm unsure which AddDevice routine failed in USBXHCI there seems to be more than one - can you see if loading PDB symbols gives more info?

×
×
  • Create New...