More questions on the missing hal.dll

  • Thread starter Thread starter Anat
  • Start date Start date
A

Anat

All,
I've been following the discussion with Johannes Stratmann closely,
especially the part where reformatting the HD did help, well, it did not
make a difference with my setting and I still facing the infamous
"missing hal.dll".

Settings are:
SATA HD 80 GB with two partitions C: and D:
On C: Running XP Pro, no problem, running beautifully.
boot.ini -->
[boot loader]
timeout = 30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating system]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional"/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP
Embedded"/noexecute=optin /fastdetect

On D: Running XP Embedded, where the image was created with Target D.

I'm out of ideas, so if anyone has any suggestion, I'll be happy to give
it a try.

Regards, Anat
 
Sean,
Thanks for the prompt response.
Regarding your suggestions - I did set up ARC and drive letters when I
built the image, so those were not the issues.
Since my posting I was trying to rule out Hardware problems and found
out that the SATA HD I was using is faulty. It single boots fine, but
when it comes to dual booting- nope. On a different HD the problem went
away.

Regards, Anat

Dual booting is always troubling.
http://www.seanliming.com/Docs/XPE Stop 0x0000007B Error V1.3.pdf

When you built the image what did you set the ARC path and drive letter
too?


Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
Anat said:
All,
I've been following the discussion with Johannes Stratmann closely,
especially the part where reformatting the HD did help, well, it did
not make a difference with my setting and I still facing the infamous
"missing hal.dll".

Settings are:
SATA HD 80 GB with two partitions C: and D:
On C: Running XP Pro, no problem, running beautifully.
boot.ini -->
[boot loader]
timeout = 30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating system]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional"/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP
Embedded"/noexecute=optin /fastdetect

On D: Running XP Embedded, where the image was created with Target D.

I'm out of ideas, so if anyone has any suggestion, I'll be happy to
give it a try.

Regards, Anat
Click to expand...
Click to expand...
 
The hard drive that is wokring is still a SATA?

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
Anat said:
Sean,
Thanks for the prompt response.
Regarding your suggestions - I did set up ARC and drive letters when I
built the image, so those were not the issues.
Since my posting I was trying to rule out Hardware problems and found out
that the SATA HD I was using is faulty. It single boots fine, but when it
comes to dual booting- nope. On a different HD the problem went away.

Regards, Anat

Dual booting is always troubling.
http://www.seanliming.com/Docs/XPE Stop 0x0000007B Error V1.3.pdf

When you built the image what did you set the ARC path and drive letter
too?


Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
Anat said:
All,
I've been following the discussion with Johannes Stratmann closely,
especially the part where reformatting the HD did help, well, it did not
make a difference with my setting and I still facing the infamous
"missing hal.dll".

Settings are:
SATA HD 80 GB with two partitions C: and D:
On C: Running XP Pro, no problem, running beautifully.
boot.ini -->
[boot loader]
timeout = 30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating system]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional"/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP
Embedded"/noexecute=optin /fastdetect

On D: Running XP Embedded, where the image was created with Target D.

I'm out of ideas, so if anyone has any suggestion, I'll be happy to give
it a try.

Regards, Anat
Click to expand...
Click to expand...
Click to expand...
 
Back
Top