Setting default registry entries for enumerated hardware

[Gereon]

I'm making a component out of a Microtouch touchscreen. I imported the .INF
file, then I went to a machine that already had all the settings set the way
I wanted and imported a bunch of the registry entries. Of course, the
values for the registry entries I wanted to set up were all inside of
enumerated keys, such as like
HKEY_CURRENT_USER\ControlPanel\MtsTch\USB00332896.

I changed HKEY_CURRENT_USER to HKEY_USERS\.Default, and I "guessed"
(apparently incorrectly) that I should change the "USB00332896" part of the
key to something like "USB00000000", or "0000" or something like that. But
nothing I tried made the registry entries become defaults for the new
hardware when it was detected during deployment. I ended up with new
enumerations like USB00134867 that did not inherit the default values I
wanted.

Is there a way to specify that certain registry keys are supposed to be
defaults (or overwrite the defaults) for new instances of the hardware that
appear in the registry?

 

[Slobodan Brcin \(eMVP\)]

Gereon,

Unfortunately there are only two ways but they are ok.

First way you can set values in PnP enum branch trough inf file itself, so
what ever that new name is values will be stored on correct path.
Other way is trough application by using SetupApi functions.

Regards,
Slobodan

 

[Mike Warren]

Hi Gereon,

I'm making a component out of a Microtouch touchscreen.

A word of caution: Make sure you try more than one touch screen
on your target.

I have included the standard XP Microtouch driver into my image
and found that it will cause problems when a different (same model)
touch controller is connected. This may only be relevant with dual
video cards and EWF as the screen mapping is reset.

3M tell me that I need to use their XPE component to solve this
problem but we have to sign an agreement with them and this will
take about 3 top 4 weeks to organise.

-Mike