"missing HAL.dll" fault not in "boot.ini&quot

  • Thread starter Thread starter zapper
  • Start date Start date
Z

zapper

For my graduation project I have to build a Windows XP embedded imag
for an embedded system.
In order to get familiar with WXPe I have made a dual boot system o
my PC. At first this was no problem. I have been able to run WXPe o
my PC. But now after I have made and run a couple of working WXP
versions, I only receive at bootup the "missing HAL.dll" message.
The problem isn't in the "boot.ini" file, nor is it a fault in th
drive letter settings in the target designer.
I had made a back-up of a working version of WXPe, copyied that to th
root but even then I receive the error message.
Can anybody tell me what I can do?

Help me please
Ja
 
Zapper,

This is usually problem related to bad ARC path used in boot.ini. (Other
case would be that file is really missing)
Make sure that you use ntldr from XP and not from W2K. And try different ARC
paths in boot.ini.

Regards,
Slobodan
 
I knew that it wasn't my boot.ini, so I have been searching for th
answer. I have found out why I sundenly could not boot WXPe anymore
I had made my D: drive into a logical drive. From a logical drive
you can not have a bootable operating system. I did not know tha
when I made it a logical drive. Now I have to delete the logica
drive (and all data on it) when I want my system to be a dual boo
system

Thanks everybody for your assistance in finding the answe
 
Zapper,

Well technically it was your boot.ini since it was pointing to wrong
(non-existing) ARC path.
Anyhow thanks for sharing the info.

Regards,
Slobodan
 
Zapper,

It says about EWF partition creation problem during the FBA. You can use Reg
RAM EWF so that this partition is never created or used.

Regards,
Slobodan
PS:
Logical volumes are bad idea anyhow since they can cause you more troubles
that it is worth of thinking about.
 
Back
Top