Reseller Submission - DTM required?

I am trying to create a Driver Update Submission for a driver package that
our company is reselling. The only changes are in the INF file, all binaries
are unchanged.
We have been granted and have accepted the reseller rights through the
WinQual website. According to the WHQL policy documentation, I need to run
ChkInf on my changed INF file and package the resulting log with DTM, then
include this in my INF Update submission.
My question is: Is there a way to package the log file and create the
submission without having to set up a complete DTM environment? As I don't
need to re-test the binaries, I can't see why I would need to set up a test
environment.
I also don't have the original test results from the driver manufacturer. Do
I need these?
The documentation for driver resellers wanting to obtain certification for a
driver package (INF Update) is very sparse, any help would be greatly
appreciated.

Hello,

go to the Wnqual Help site
https://winqual.microsoft.com/help/default.htm

Enter 'DUA' in search field and press GO.
You get 'Driver Update Acceptable' as result and you can found a step by
step instruction to submit a DUA.

Ralf

FPNZ wrote:
> I am trying to create a Driver Update Submission for a driver package that
> our company is reselling. The only changes are in the INF file, all binaries
> are unchanged.
> We have been granted and have accepted the reseller rights through the
> WinQual website. According to the WHQL policy documentation, I need to run
> ChkInf on my changed INF file and package the resulting log with DTM, then
> include this in my INF Update submission.
> My question is: Is there a way to package the log file and create the
> submission without having to set up a complete DTM environment? As I don't
> need to re-test the binaries, I can't see why I would need to set up a test
> environment.
> I also don't have the original test results from the driver manufacturer. Do
> I need these?
> The documentation for driver resellers wanting to obtain certification for a
> driver package (INF Update) is very sparse, any help would be greatly
> appreciated.
>