Problems with "HAL.DLL" not found

[Hank Schupp]

I'm sure this may be a repeat issue but I have not been able to resolve it.

Hardware: Dell 850 1u rack-mount
Intel Dual-Core
Two 500GB SATA drives (connected via built-in
controller)
CD-ROM

I first loaded the machine with XP Pro and installed the drivers for
everything.
I ran the TAP.EXE and captured the device list.
I imported the device.pmq file and noted the missing drivers.
Spent a couple days figuring out how to import the missing files and create
the repositories.
Finally had a build that "looked" good on paper

Booted the target machine with BartPE and formatted the drive with the OS
already on it.
Used DISKPART to "clean" and repartition both the drives. Disk 1(per
DiskPart) as Primary.
Formatted both as NTFS.
Rebooted machine (again into the BARTPE)

I copied the target image onto a USB drive then copied the files off the USB
onto the primary partition drive (SATA drive "0")
Pulled all the removable media and rebooted.
System halts with the "HAL.DLL not found or corrupted" message.

The original devices.pmw file had detected the processor "driver" as the
ACPI MULTI-processor type and that is what I had used but I tried replacing
it with the UNI and still had the same problem.

I might just be still lost on the ARC path settings but with a single
primary partition of 500GB on the 1st drive I beleive it should be all "0"'s
as far as I understand it: multi(0)disk(0)rdisk(0)partition(0)

Here are my target device settings:
Boot drive = C:
Windows folder = C:\WINDOWS
Program Files folder = C:\Program Files
Documents and Settings folder = C:\Documents and Settings
Boot ARC path = multi(0)disk(0)rdisk(0)partition(0)
Boot partition size (MB) = 5000
Partition cluster size (bytes) = 4096

Any Hints on what to try next?

Sean - Am still waiting on your books to arrive...In the meantime its
"Question Central"!
Thanks to everyone for their support so far... you've been a big help.

Hank Schupp

 

[Adora Belle Dearheart]

I might just be still lost on the ARC path settings but with a single
primary partition of 500GB on the 1st drive I beleive it should be all "0"'s
as far as I understand it: multi(0)disk(0)rdisk(0)partition(0)

No, it should be partition(1)

 

[Sean Liming \(eMVP\)]

Heidi is correct, make sure the partition is 1. How are you transfering the
image over the USB? Are you booting to DOS?

Regards,

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

 

[Hank Schupp]

....And all was well with the world!

Thanks Adora. I had been experimenting and had just tried and succeeded
with that change.
Your reply validates it for me.

Now just to figure out why it doesn't see the mouse...

Hank Schupp

"If at first you don't succeed - try, try again. Then quit. There's no use
being a dang fool about it!" 'as modified by W.C. Fields'

 

[Adora Belle Dearheart]

...And all was well with the world!

Thanks Adora. I had been experimenting and had just tried and succeeded
with that change.
Your reply validates it for me.

Now just to figure out why it doesn't see the mouse...

USB or PS/2?

 

[Hank Schupp]

PS/2 via a KVM.
Mouse is active during the initial startup but when the desktop comes up -
nothing. - including no keyboard.
Am about to go to the lab and try connecting directly - bypassing the kvm.
Just reviewed the component list and it appears all the standard PS/2
drivers for the mouse and keyboard were included in the build.

This is the first pass at using XPe (obvious, I know) so I have not tried
any paring-down of the system. I added every component discovered by the
TAP.EXE utility and then added the missing drivers discovered during the
import.

I have also just found the information about configuring the User Interface
Core so that may have something to do with it. I am going to read up on
that and see what I find.

I appreciate the support!

Hank Schupp

 

[Adora Belle Dearheart]

PS/2 via a KVM.

I've had Issues with KVMs, personally, and have just given mine back to
the IT dept in favour of moving cables about - that seems to work more
often than the KVM.