Thank you for the information, both of you. I think I may have made an error in reading the logs. I think it may have actually worked, but I realized that the problem was in another DPRINT1 statement I added further down the code. Sorry about that. There is one piece of information I'm not entirely ...

So for a while, I wasn't entirely sure how to construct the try-except statement so that it would compile. Yesterday I figured it out, but I haven't constructed it correctly, because it's still crashing. I tried this: _SEH2_TRY { DPRINT1("Irp->IoStatus.Status: %p\n", Irp->IoStatus.Status);...

Well, I had. I just that doing that would mean that it wouldn't have WinDBG, but then I thought about it again and realized I hadn't even checked if that were really true. In any case, building it with MSVC makes it stop even sooner with a BSoD that says this at the bottom. *** STOP: 0x0000007F (0x0...

Do you have a recommendation on what versions to use? I tried installing MSVC 2013 with WDK 7.10, but I don't think I have them configured right. Would the next versions up work too? I mean, I tried 2019 first, but generating sln didn't work out too well. It might be too new. I tried adding prints t...

This is related to the last topic I posted: https://www.reactos.org/forum/viewtopic.php?f=2&t=19396 In it ThFabba talked about how IRPs are asynchronous. ... IRPs are asynchronous in nature and sometimes they're processed in less-than-obvious ways. For example it's possible for the owner of an I...

So I've been looking around at where the OS goes when calling a function or returning a value. Except that sometimes when I try to figure out where it is going to go next, I get stumped, and this time it's really confusing me. It is because I look at the logs with extra DPRINT1 statements sprinkled ...

Thanks for the explanations, and the resources too! Now, let's see if I've got the boot process that leads up to KERNEL_ENTRY_POINT correct. I'll also include the code lines that lead to the next file in the boot process isoboot.S: ljmp16 0, FREELDR_BASE i386.S: .byte HEX(0ff), HEX(25) entry.S: call...

So the process looks something like this: isoboot.S --> i386.S + freeldr.spec? --> ? --> freeldr.c --> winldr.c The first 512 bytes of setupldr.sys is in fathelp.inc, which is mostly skipped over at the entrypoint 0000:FA00 with a .byte directive coded to go to 0000:FA00. I can't really tell what's ...

So I've looked over the isoboot.S file a lot, and I think I've learned a bit about it. That file tells the computer how to load the contents of a cd into system memory, is that right? It's pretty low level, because it's makes a few BIOS interrupt calls here and there, mainly text video services and ...

So, on one of my machines I try to install Reactos (I posted to Jira CORE-16362 ) it stalls out. I'd like to know how I can determine what part of the process it has stalled out at. For instance, the normal debug logs from Qemu look a little like this (This isn't where the problem is, it's just a hy...