Damnation

I am also interested in finding out if this is possible.

@Dietmar Alright, no worries.

@Dietmar I know this is targeting windows 2000 but would you be interested in helping debug these BSODs? or you're not interested?

@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?

@jumper Ah, So you don't know where the source code is for WDMEX is either, fine. --- Anyone else interested in extending WDM driver support for 98?

@Cixert The drive is showing up in device manager so XP sees it at least. Try making a 1.9TB MBR partition and see if that mounts.

@jumper No I can't find the source code, do you know where I can find it?

@ward201185 It might be a HAL timer issue - @Dietmar knows more about this problem and can help you determine if that's what you issue is.

@jumper I found it, but There's No source code for it though, I want to help improve it.

@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

@cyberluke Sorry, I don't fully understand what it is that you're trying to accomplish here, could you please elaborate?

@R1600 This is an XP ntoskrnl extender - https://github.com/MovAX0xDEAD/NTOSKRNL_Emu Take a look at how it works and then try to apply that to NT3.51

@geeb21 from zone62.com download XP-IE patch integrator script included in the XP download,

@geeb21 In the optional patch integrator script folder Patches\ACPI drivers change the acpi.sys 7777 -> acpi.sys 6666 version from the other folder. then run the script again to build a new xp.iso with the alternate acpi driver.

@cyberluke Yeah I read it, they select the MPS HAL in this case which means this threads ACPI driver irrelevant as it's not used by that HAL.

@Dietmar @geeb21 IIRC This acpi.sys 7E BSOD happened because an ISA GPIO device was being treated as PCI by mistake, unless I'm mistaken.

@Brickedandroid Try windows 7 instead of Vista.

@Brickedandroid Unfortunately I don't think ntoskrnl extender will help for something like this - ntoskrnl extender just resolves missing exports. Maybe try the XP driver on Vista, see if that works.

@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.

@geeb21 I think you lost USB Input in this case, so you'll need to use the optional patch integrator to integrate USB 3.0 drivers before you can continue with setup.

@Brickedandroid What bug are you referring to?

@MrMateczko you could try this - https://github.com/JHRobotics/patcher9x

@Dietmar Thanks, So this message means 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?

@Dietmar Whoops! OK new version. https://ufile.io/mkr85nmw

@Dietmar Thanks, Can you do a debug with these files too? No BSOD with these but it will fail in device manager. https://ufile.io/lqmpvf6h