In a c’t magazine article, the AppLocale tool from Microsoft was
mentioned. I’ll try this and report my findings. ![]()
The funny thing is that Signability runs perfectly fine on my system as
long as the DriverVer line in the INF file is something like this:
DriverVer=11/30/2006,6.0.6000.16386
For all dates after 2006-Nov-30 only an error message is generated.
Very weird.
Using MakeCat is unfortunately not an option as Signability adds some
additional information to the catalog I don’t want to miss.
Comments?
Hagen
Udo Eberhardt schrieb:
Based on your surname, I suppose you are located in Germany…
The Signability tool seems not to work correctly if the system is set to
German data/time format. In Control Panel - Regional and Language
Options set “Standards and formats” to “English (United States)” and try
again. After you are done with Signability you can switch back to German.Udo
Hagen Patzke wrote:
> Today I tried to use Signability to make a CAT file as preparation for
> signing, and encountered this behaviour:
>
> With this line in my INF file:
> DriverVer=12/01/2006,6.0.6000.16386
> Signability reports:
> “Signability Test failed to run, TestDrivers function call failed.”
>
> With “DriverVer=11/30/2006,6.0.6000.16386”, the CAT preparation runs OK.
>
> Dates in the future (2007) produce a clean Signabilty run with an
> error report (post-dating not allowed), which is OK. Same with dates
> far back.
>
> Development OS is WinXP SP2 with WDK 6000 (RTM).
> Comments?
> -H
>