hal.dll is corrupt or missing

[Fab]

After having succefully tested an XPE configuration on a PC (an ACER
travelmate laptop) with a Windows XP running Virtual PC 2004, I decide to
erase the disk and to install the final XPe version. Here my steps:

1) Started Windows PE
2) Launched TAP.EXE
3) Moved the PMQ file on the development machine
4) Created a new component importing the a.m. PMQ file
5) Generate the new XPe configuration
6) On the target (ACER) I mapped the host HD and I copied (XCOPY and
ROBOCOPY) the "Windows Embedded Images" folder content to the C: disk of the
target computer.

At the boot I have the message "HAL.DLL is corrupt or missing".

The file is there (c:\windows\system32), and the BOOT.INI file content is ok
(rdisk(0),partition(1)).

Any idea ? Thanks in advance for any support....

BTW: I also boot at DOS and executed TA.EXE, with no success.

Fabrizio

 

[DPM]

Did you use "/H" with xcopy? If not, then hidden/system files will not be
copied.

Dean

 

[Sean Liming \(eMVP\)]

Step 6: What do you mean by map the host HD - where you under DOS? If so
XCOPY will not work. You loose long file names.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit

 

[Fab]

No, I didn't...I will try!

Thanks!

Fab

Did you use "/H" with xcopy? If not, then hidden/system files will not be
copied.

Dean

 

[Fab]

Step 6: What do you mean by map the host HD - where you under DOS? If so
XCOPY will not work. You loose long file names.

When running Windows PE you have access to a command window (DOS like, CMD).
At the command prompt I can map the HD of the development machine with the
command

MAP Z: \\192.168.100.100\D$ /USER:username

Then I used the XCOPY command to copy the target designer's product to the
target machine

XCOPY "Z:\Windows Embedded Images" C: /S/E

Dean just suggested to add the /H qualifier for the hidden files (maybe an
hidden module called by the HAL.DLL referred by the error message). I was
not aware that XCOPY was not able to deal with long filenames. I will try
with other utility, but I wonder how if it could have worked when I did the
same ops under the Virtual PC!

Thanks for the suggestion!

Fab

 

[Sean Liming \(eMVP\)]

I didn't understand how you map the drive. Under DOS, long file names will
be lost. Under WinPE, you should be okay.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit

 

[Fab]

I didn't understand how you map the drive. Under DOS, long file names will
be lost. Under WinPE, you should be okay.

As WinPE boot, it open a command window,and there it starts several network
services (See also
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxpesp1/html/winpepe.asp).
They allow you to MAP network resources as disk unit.

Fab

 

[Sean Liming \(eMVP\)]

Thanks. Someday I will have to actually read my book that discusses this....

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit

 

[Caf]

Did you use "/H" with xcopy? If not, then hidden/system files will not be
copied.

Done...same error. One information more: The target CPU is a "Celeron M".
Anybody see an incompatibility ?

Thanks
Fab

 

[Caf]

Solved! I just overlooked at the disk partitioning that was coming from
ACER...
The first partition where I intended to install XPe (Partition(1)) was
marked as OEM (???) and not "Primary". DISKPART assigned the C: to the first
primary partition (i.e. partition(2)). So, the BOOT.INI created by the XPe
was incorrect.
Once updated that system booted.

Thanks to everybody for the support!

Ciao
Fab