"load needed DLLs for kernel" error

[Guest]

I know that this error has been discussed before. KM suggested I search the archive to find this topic. Unfortunately, I have not been successfully with the Search feature. I'm not sure what I'm doing wrong but every time I searched for a topic or keyword the result comes up blank. So I'm asking for the information on this again

I've been having problem building an image for CompactFlash with EWF on my target system so I decided to create an image to run on hard disk just to get it going on the target system. Now I run into couple of problems

1) I get the following error when I try to boot the system
"Windows could not start because of an error in the software. Please report this problem as: load needed DLLs for kernel. Please contact your support person to report this problem."
I know KM said there was a discussion on this earlier. But I'm unable to search for this topic. I found some information on this in the MSDN website. It said that the HAL.DLL and NTOSKRNL.EXE are mismatched. Could it be the QFEs that I installed? I did not get this error prior to installing the QFEs when I build an image for a standard PC system. I'm very frustrated about this error

2) Another problem I have is NTDETECT.COM and NTLDR.EXE are not in the root directory after I built the image. KM suggested I check to see if I have NT Hardware Detect component in my configuration. I checked and it is included. So I had to manually copy these two file from my previous successful build into the root directory. I think I'm missing a component somewhere but I don't which one it is

This message is quite long but I want to describe clearly my problem

Regards
Trung.

 

[Brad Combs]

Trung...

1) I get the following error when I try to boot the system.

"Windows could not start because of an error in the software. Please report
this problem as: load needed DLLs for kernel. Please contact your support
person to report this problem."

I know KM said there was a discussion on this earlier. But I'm unable to

search for this topic. I found some information on this in the MSDN
website. It said that the HAL.DLL and NTOSKRNL.EXE are mismatched. Could
it be the QFEs that I installed? I did not get this error prior to
installing the QFEs when I build an image for a standard PC system. I'm
very frustrated about this error.

See Below...

2) Another problem I have is NTDETECT.COM and NTLDR.EXE are not in the

root directory after I built the image. KM suggested I check to see if I
have NT Hardware Detect component in my configuration. I checked and it is
included. So I had to manually copy these two file from my previous
successful build into the root directory. I think I'm missing a component
somewhere but I don't which one it is.

See Below...

Are you building a debug build? The debug build functionality of TD doesn't
work as expected so build all your images as release builds.

Also for searching....

http://groups.google.com/groups?hl=...F-8&group=microsoft.public.windowsxp.embedded

Add it to your favorites!

HTH,
--
Brad Combs
Imago Technologies, LLC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[KM]

Good catch, Brad!

I almost forgot about the Debug build option

 

[KM]

Trung,

Sorry for the too common answer but have you been able to run TAP on your target device (either from XP PRo install, or WinPE)?

Also, you may use /SOS boot.ini switch to find out more info about the breaking or missing driver.
Also, there is always KD as an option for debugging BSODs.

--
Regards,
KM

Hi Brad,
I tried what you suggested (build Release version) and it works. Thanks!

Now I have a new problem. The system displays a blue screen with
"STOP: c0000221 Unknow Hard Error \SystemRoot\System32\ntdll.dll"

I searched in the on-line and it said I maybe missing a device driver or some a dll that it did not catch during Dependency Check.

I remember seeing this in the newsgroup. I'm going to search for it. If you have any idea about this let me know.

 

[Trung]

Hi KM,
I have found a solution (don't why it works though). I disconnected the IDE
CD-ROM drive and it booted up fine. I did use TAP with this drive installed
and a generic CD-ROM component was included in my configuration. I have
tried to replace the CD-ROM component with NEC CD-ROM component (which I
have) and it still will not boot up with the CD-ROM connected. So everytime
I boot up I have to remove the CD-ROM drive. Maybe I have an old CD-ROM
drive. It was manufactured back in July 1998. Would this be the case? I'm
going to try to get a more current CD-ROM drive to see if it solves the
problem. I have been successfully booting to WinPE from this CD-ROM drive
that's how I executed TAP to obtain information on the target system
hardware.

I will try your suggestiong with /SOS in the boot.ini. Thanks.

Regards,
Trung

Trung,

Sorry for the too common answer but have you been able to run TAP on your

target device (either from XP PRo install, or WinPE)?