First time using

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

I am a OEM, and a programmer, I am always intrested in expanding in to new
areas and learning new things, I downloaded the windows xp embedded kit and I
am basically experimenting. I understand the basics, but whenever i fully
build anything and put it on a target, I get a error saying hal.dll was not
found

I need advise on how to get around this.

thanks
 
Hi Willhil,

1. Please make sure that ARC patch in boot.ini point to valid parititon.
2. Make sure that hal.dll is in windows\system32 folder that is located in root of your volume.

Regards,
Slobodan
 
Just to add to that a couple of common mistaken scenarios.

If you build an image for non C: system partition, TD will produce the build under DriveX folder (where X is your boot partition
drive letter set up through Configuration Settings).
Assuming you set up the boot.ini ARC path properly, please copy the content of the DriveX folder (not the folder itself) to the
target partition.

Also, make sure your "Windows" directory in mentioned properly in the boot.ini's ARC path.

KM
 
Hi Wilhil. What process are you using to put together your runtimes? It
sounds like you may be composing your runtime manually, and you may either
have the incorrect HAL component or your configuration may be missing it
entirely when you build.

Does your target machine have a "safe build" installed on it? The easiest
way to do this is to install an OS such as WinXP Pro on a partition other
than C: (for example, D:), and create a boot.ini file that you can use to
select between C: and D: when you boot. Then when you're booted to the safe
build, you can run TAP.exe (copy it from your development machine) to get a
snapshot of the hardware in the machine. This will include a reference to
the correct HAL component for that computer. Copy the resulting devices.pmq
file to your dev machine, then import that file into Target Designer. It's
recommended that you do this as your first step before including other
components.

Also, to assist you with putting together a runtime, there are a number of
pre-defined scenario templates you might find useful. Take a look at the
macro components under "Design Templates" in the tree view in Target
Designer. These scenarios will bring in all the necessary components to
fulfill common roles such as gaming kiosks, network storage units, etc. You
can, of course, add and remove components as you wish, but these templates
are great for helping you get started.

You can also find more generic design templates such as a "Minlogon" and
"Winlogon" scenario, which do not require that you import a PMQ file. They
will provide the necessary components to get a very generic runtime
running - you might want to try those out as well.

I hope this helps. Please let us know if you have any more questions. =)

--
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
 
Back
Top