Export (0) Print
Expand All

EConvert Messages (Windows Embedded Standard 2009)

4/23/2012

When you convert text files to an .sld format, make sure to monitor warning and error messages that are generated during the import process.

The INF importer displays warnings about unrecognizable .inf file directives, for example, a directive you created. In this case, you must inspect the .inf file directives, and then make the appropriate adjustment to the resulting component definition.

Bb499379.note(en-US,WinEmbedded.51).gifNote:
These same messages display when you use EConvert or import a file into Component Designer.

The following table shows the messages that may appear.

Message Description

Warning: <section name> is empty.

A section of the specified name is empty.

Warning: <section name> is missing

A section of the specified name is missing.

Warning: <section name> needs to be processed by the user

The specified section cannot be processed automatically by INFMGR. You must revise the resulting .sld file to make the necessary adjustments to the sections referenced by RenFiles, DelFiles, and DelServices.

Warning: <section name>: cannot process directive: <directive name>

A directive in the specified section cannot be processed using INFMGR. You must handle the directive manually.

Warning: <section name>: cannot append to non-multisz value: regroot, registry key, value name, flag, value

Warning occurs if FLG_ADDREG_APPEND is set but FLG_ADDREG_TYPE_MULTISZ is off in the registry.

Warning: <section name>: cannot handle key "key name"

A key inside a section is not understood and cannot be handled by INFMGR. You must view these keys and handle them manually.

Warning: <section name>: contains RunOnce AddReg item

The section contains the RunOnce key that may result in more file resources. INF import add-in does not parse a RunOnce key and add the appropriate file resource to the resulting component. You must do this manually.

Warning: <section name1>: cannot find <section name2> specified in Needs directive in the current and included INFs.

<section name1> contains a Needs directive that points to another section named <section name2> which is not found anywhere. This is a potential flaw in the .inf file.

Warning: ClassGUID GUID cannot be recognized

The ClassGUID specified for a Plug and Play device .inf file is not known to the tool. This usually means that the .inf file defines a new device installation class with a new GUID. This can become an issue because the tool assigns the category for each device component based on its ClassGUID. To resolve, make a new entry in the GUID mapping table in the registry.

Error: Invalid argument format: "argument"

The specified argument is not in a valid format. You must correct the argument, and rerun the tool. However, any argument that is not understood entirely, such as /HELLO, is silently ignored. This warning is given for the known argument types that are not valid.

Error: <section name> has invalid line " line"

This error occurs when the INF importer detects a format under a section which is not valid. This usually indicates a flaw in the .inf file. This includes missing registry flags. Fix the flaw in .inf and rerun the application.

Error: <section name>: cannot handle HKR

HKR is used by a non-Plug and Play device .inf file. In this case, you may need to implement run-time code or script to accommodate these registry entries. If the HKR is in a Plug and Play device .inf file, they are ignored.

Error: <section name>: no destination directory defined

No default destination directory is defined for a section referenced by CopyFiles. To resolve this issue, correct the error and then rerun INFMGR.

Error: <section name>: cannot find included INF file: "xxx.inf".

An .inf file specified in the Include directive cannot be found in the current working directory.

Community Additions

ADD
Show:
© 2014 Microsoft