InfVerif error 1235 ('%') in (legacy) LogConfig sections

  • Thread starter Thread starter luisc_
  • Start date Start date
L

luisc_

Guest
Hello,

this is a post similar to Package rejected with error 1235 because of "%" in MemConfig directive - what is wrong? in the hopes that this forum is more active.

I've annotated the Warnings and Errors of infverif using ';' (infverif referenced from Hardware Dev Portal Dashboard):

[testdrv_ISA_Inst.NTx86]
CopyFiles=testdrv.CopyDriverFiles,testdrv.CopyProgramFiles,testdrv.NTx86.CopySystem32Files
;WARNING 2009 for target OS e: Legacy directive 'LogConfig' will be ignored.
;WARNING 1300 for target OS e: Found legacy LogConfig operation.
LogConfig=ISA_CNF_16K_OPT,ISA_CNF_16K,ISA_CNF_16K_IRQ
AddReg=testdrv_Security

;WARNING 2083: Section [isa_cnf_16k] not referenced or used.
[ISA_CNF_16K]
ConfigPriority=HARDRECONFIG
;ERROR 1235: String token '4000@C0000-FC000%FFFFC000' not defined in [Strings] section - if intending to use a literal '%' in a string, use '%%' instead.
MemConfig=4000@C0000-FC000%FFFFC000 ; MemoryRange0;

Is it in this case valid to replace the '%' with '%%'? It seems that all warning before indicate that LogConfig is not processed and checks for error 1235 processes the whole inf regardless.

Is such a modified inf supported on previous Windows versions (e.g. 7)?

I've checked the output of a modified ('%%') and unmodified ('%') inf using the previously available chkinf scripts (WDK 10.0.26624 and 7600.16385.1) and both seem to be fine.

Additional note:

  • This driver is not intended as a unified driver package, so LogConfig should be possible to use.
  • The hardware referenced in the inf are PCI/PCIe and ISA devices.

Thanks in advanced for clarifications,

Luis

Continue reading...
 
Back
Top