ntoskrnl extender for windows 2000

[infuscomus]

So I've attempted to make an ntoskrnl extender for windows 2000.

I tried to get storahci to run with it.
It currently does not work, so if anyone is willing to help, it'd be much appreciated.
It's based off of the XP SP1 ntoskrnl/hal with a new entrypoint and new functions with code merged in from the ntoskrnl extender for XP.

I'll upload some files shortly.

This is the BSOD I get after trying to run it.

NTOSKRNL_ENTENDER_2000_BSOD.PNG (13.09 KiB) Viewed 13807 times

NTOSKRNL_ENTENDER_2000_BSOD.PNG (13.09 KiB) Viewed 13807 times

here are the files -
[Download Link Removed]

Note from the staff team:
The archive you linked to contains internal Microsoft source code that is not allowed to be distributed publicly. We have removed the link as we do not allow this on EclecBoard.

[win32]

As far as I could tell, you hit the exception handler for syscalls (so definitely a call made by the driver to the extender). Some more information is needed.

[infuscomus]

I'm not skilled with using a debugger, so I'm not sure how to trace the cause of this.

is there anyone here skilled with debugging?

[WIN2000WARRIOR]

I'm not skilled with using a debugger, so I'm not sure how to trace the cause of this.

is there anyone here skilled with debugging?

You should get the Memory.dmp file
https://support.microsoft.com/en-us/topic/b863c80e-fb51-7bd5-c9b0-6116c3ca920f
Try to install Windows 2000 twice in C: and in D: for example, before testing so that you can recover old files after the appearance of BSoD

[infuscomus]

I wouldn't know what to look for inside a memory dump.

The extent of my debugging knowledge is that I know I need a serial COM port card in both my debuging and target PC, as well as Windbg and my extender's PDB symbols to put names to things.
But even then I still lack knowledge of assembly language and still wouldn't know what to look for.

[WIN2000WARRIOR]

I wouldn't know what to look for inside a memory dump.

The extent of my debugging knowledge is that I know I need a serial COM port card in both my debuging and target PC, as well as Windbg and my extender's PDB symbols to put names to things.
But even then I still lack knowledge of assembly language and still wouldn't know what to look for.

In this case, I advise you my friend to ask help from Mov AX, 0xDEAD's as he most likely encountered these problems during his task with Windows XP and 2003, extract the error using serial COM port card and tell him the all results, and send him the files in a private message on MSFN . And then tell us.
You're doing a great job and really deserve someone to help you .

[win32]

You could try using a VM and hooking up windbg to a virtual serial port.

[WIN2000WARRIOR]

I think the reason for the error is the need for Windows 2000 the extended "nt kernel table" ْand It seems to require too many code changings , It might be easier with XP SP1 ntoskrnl/hal , Do not despair, continue and you will succeed