Re: OEMWriteDebugString problem

First, set WINCEREL and rebuild the kernel. In the obj folder will be .COD
files which contain the C code as well as the assembly code that it creates.
Looking at these files will tell you a lot about what is happening.

Next, is it possible that the bootloader and the kernel are using different
ports?

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member



.

Relevant Pages

  • Re: IO-Space
    ... Move this access to the kernel or a driver, ... beitman AT applieddata DOT net ... An ISO 9001:2000 Registered Company ... Microsoft WEP Gold-level Member ...
    (microsoft.public.windowsce.embedded)
  • Re: Linux Assembly
    ... > I know there are short assembly code in the MBR, ... The conventional MBR just contained code to load the boot sector from ... The MBR is not part of the kernel. ...
    (comp.os.linux.development.system)
  • Re: Cross-compilation to i386
    ... > For some reason, as doesn't like big negative numbers. ... > The world and kernel builds then completed succesfully. ... > boots on a diskless machine. ...
    (freebsd-current)
  • Re: Linux* Processor Microcode Data File
    ... instructions are replaced in assembly code? ... The kernel doesn't load microcode automatically but it can provide a ... device to allow userspace to trigger a microcode update (via ...
    (Linux-Kernel)
  • Re: Producing assembly language listing of kernel
    ... want to see the assembly code for the whole kernel. ... imagine anybody actually sitting down and trying to read it at all. ... but I need to see how they are being built, when the kernel is assembled. ...
    (comp.os.linux.development.system)