palpal,
I don't think you can manage HKLM\Hardware key from TD.
Unlike many of the other subkeys in the Registry, the HKLM\Hardware subkey
is not considered a hive. The HKLM\Hardware sub-key is populated when
NT/2000/XP/XPe boots during kernel initialization. This means that the
values for entries in the subkey, as well as entries themselves, are created
when OS boots and detects what hardware is installed and how it is
configured.
As there is no hive for the subkey, TD won't be able to set up your registry
values/keys under HKLM\Hardware subkey.
You may want to look at FBA PnP Device ID request as an option for setting
up your device.
--
KM,
BSquare Corporation
I built a component for a non plug and play device driver. In registry
data I added hklm\hardware\resourcemap\pnp
manager\pnpmanager\device\xxxx.raw and hklm\hardware\resourcemap\pnp
manager\pnpmanager\device\xxxx.translated which are identified by InCtrl5.
There is no problem in import the component to the database. However when
the target designer starts to build the image, it gives "invalid key path"
on those regstry keys
