Xpe, warning 1006: Corrected invalid registration data

Xpe, warning 1006: Corrected invalid registration data

Bill Zhong (cudng@msn.com)

Date: 2007-08-27

The translation is used for academic exchange and belongs to the original version.

 

Symptom: one feature of xpe can be imported from the Registry Editor. reg file. unfortunately, the import process does not parse the correctness of each key. when you compile the image, the answer is: "Warning 1006: Corrected invalid registration data :". this problem is that during the import process, no data is added for those registered resources without numerical names. in the following description, the imported registered resource does not have a numerical value name. you will find that the key value next to the folder icon is the path of the typical pre-save key value.

Use Notepad and open the SLD. The numeric name cannot be found.
<Property name = "valuename" format = "string" context = "1"
Platformguid = "{00000000-0000-0000-0000-000000000000 }"
> </Property>

Solution: key values are valid, but the value name feature must be added to XML and imported. reg file, you will find the key value. no value name or folder icon. currently, there are two options for correcting registered resources:

1. Open notepad and add the following registry resource tags:
<Property name = "valuename" format = "string" context = "1"
Platformguid = "{00000000-0000-0000-0000-000000000000 }"
> </Property>

2. Component designer:

A. in component desinger, double-click to edit the registry key value.
B. Click the "binary" radio button.
C. Click "default ".
D. Click "OK" to add the value name to the Registry resource in XML.
You can see that the icon has been changed back to the correct type

 

Original article:

Problem: one of the nice features of xpe is the ability to import. reg file that was exported from Regedit. unfortunately, the import doesn't parse every key correctly. when you go to build the image, you get a "Warning 1006: Invalid registry data fixup:" followed by the key in question. the problem lies with the import process not adding all the data for registry resources that don't have a value name. in the figure below, there is no value name for the imported Registry
Resource. You can spot that a folder icon is next to the key which is typically reserved for key paths only.

Using notepad to look in side the SLD, you will see the property for the value name is missing.

<Property name = "valuename" format = "string" context = "1"
Platformguid = "{00000000-0000-0000-0000-000000000000 }"
> </Property>

Solution: The keys are valid, but the Value Name property needs to be added to the XML. after importing. reg file, look for keys that have values, no value name and a folder icon. there are two options to correct the Registry Resource:

1. Open notepad and add the following between the Registry resource tag:

<Property name = "valuename" format = "string" context = "1"
Platformguid = "{00000000-0000-0000-0000-000000000000 }"
> </Property>

2. Component designer:

A. in component designer, double click to edit the registry key
B. Click on the "binary" radio button
C. Then click on the "default" radio button
D. Finally, click OK. This will add the registry value name to the Registry resource in XML.
You will see that the icon has changed to the proper type

Windows is a registered tradem ark of Microsoft Corporation.

Copyright 2006 sjj embedded micro Solutions, LLC., All rights reserved. www.sjjmicro.com
03/04/06