C
Chris
Hi all,
We use component designer and target designer to create a XPe kernel running
image that will kick off a shell once winlogon and the shell then runs our
boot loader executable that loads our software image into memory and then
switch the context to start the software (say abc.exe).
Here is the problem:
The XPe OS reboots soon after our software (abc.exe) starts. It repeats
endless. Our software code calls Windows API GlobalMemoryStatusEx at the
beginning. Once I removed the code calling GlobalMemoryStatusEx from abc.exe.
The rebuilt software works and rebooting problem doesn't occur anymore.
It seems to me that there are two possible causes:
1. since our software kicks in soon after winlogon starts. It is possible
that some dependent Windows dlls haven't been fully loaded at the time
GlobalMemoryStatusEx gets called from our software. As a result, a fatal
error occurs and the system reboots.
2. The XPe kernel we built may miss some dlls that GlobalMemoryStatusEx
depends on. As a result, calling on GlobalMemoryStatusEx led to a fatal error
and the system reboots.
Does anyone have the similar problem before? Any solution can be shared?
Thank you
Chris
We use component designer and target designer to create a XPe kernel running
image that will kick off a shell once winlogon and the shell then runs our
boot loader executable that loads our software image into memory and then
switch the context to start the software (say abc.exe).
Here is the problem:
The XPe OS reboots soon after our software (abc.exe) starts. It repeats
endless. Our software code calls Windows API GlobalMemoryStatusEx at the
beginning. Once I removed the code calling GlobalMemoryStatusEx from abc.exe.
The rebuilt software works and rebooting problem doesn't occur anymore.
It seems to me that there are two possible causes:
1. since our software kicks in soon after winlogon starts. It is possible
that some dependent Windows dlls haven't been fully loaded at the time
GlobalMemoryStatusEx gets called from our software. As a result, a fatal
error occurs and the system reboots.
2. The XPe kernel we built may miss some dlls that GlobalMemoryStatusEx
depends on. As a result, calling on GlobalMemoryStatusEx led to a fatal error
and the system reboots.
Does anyone have the similar problem before? Any solution can be shared?
Thank you
Chris