Hi Ashwin,
Thanks for replying.
I have been able to set some breakpoints and trace some of the OEMDLL code.
their corresponding checked versions are unidrv.dll, unidrvui.dll and
unires.dll. This is apart from oemuni.dll.
If I have to replace unidrv.dll, unidrvui.dll and unires.dll, I will need to
have a partial checked build of Windows right? That means, I'll have to have
the checked builds of Kernel and the HAL!!! I tried this way....but my
windows is not able to boot when I give /kernel=extractedkernel.chk and
/hal=extractedhal.chk. It just keeps on restarting!!!
Now that I have been able to set breakpoints and trace through the code of
OEMDLL, do I still need the partial checked build? What's the use of having
checked versions of Unidrv.dll??
Thanks,
--
Sam.
"Ashwin [MS]" <ashwinn@online.microsoft.com> wrote in message
news:785BB2E7-FE67-40EC-9069-AB33EF980301@microsoft.com...
their corresponding checked versions are unidrv.dll, unidrvui.dll and
unires.dll. This is apart from oemuni.dll.
drivers are in user-mode and for user-mode debugging you do not require two
machines. It doesn't matter which debugger you use.
set breakpoints. I am pasting it below for your reference.
So in the typical case, you would replace the following retail binaries with
their corresponding checked builds:
opposed to installing an entire checked build system is that you don't slow
down the entire system.
attach to the printing application or to the spooler process (spoolsv.exe).
You do not require two separate machines in order to do user-mode debugging.
many commands. The debugger docs also outline the various steps in setting
up user mode debugging.
denotes ERROR or WARNING. You need to set it to 1 which denotes VERBOSE. You
can do this by executing the following command in the debugger:
