Hi. Okay, my reasons for needing to get a crash dump may seem kind of funny... but, anyway here's what's going on. I'm trying to patch Windows 7 to work on a Pentium 1 MMX. Now that you're laughing, no my main computer is an 8 core FX-8150.
I just want to see this happen, because it would be interesting to see how it runs. Anyway, I have an old socket 7 motherboard that is late-model so it has ACPI support. Windows 7 runs fine on it when I have an AMD K6 installed. The K6's instruction set is identical to the Pentium 1 MMX, being 5x86 + MMX support.
However, when swapping the CPU out with a P1 MMX Windows 7.. it crashes during the boot phase shortly after showing the Windows logo on the "Starting Windows" screen. There is a STOP 0x5C blue screen. 0x5C code means HAL init failed.
Considering that the CPU instruction sets are totally identical, I am led to believe that this is an artificially generated error because MS just doesn't want it to run on a CPU as old as the Pentium 1 MMX.
Anyway, I have it all set up to create dump files on a blue screen and I'm using the "bootdebug" option when it starts. It just doesn't create any dumpfiles though. It also doesn't create ntbtlog.txt if I tell it to, or when trying safe mode.
I need the dump files so I can figure out what part of the HAL init fails with WinDbg, so that I can analyze the HAL library in IDA pro and patch the code to skip the (what I think is) artificial error generation.
Does anybody know why it may possibly not be creating a dump? Maybe I could figure it out without these dumps, but man that would make this take so much less time. Or if anybody knows for sure that it's not an artificial error, please let me know so I am not completely wasting my time.