Description of problem:
The Wdfxxx file located in win8/win8.1/2012/2012r2 folder should named WdfCo*I*nstaller01011.dll instead of WdfCo*i*nstaller01011.dll;
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Wdfxxx file in win8/win8.1/2012/2012r2 are named as "WdfCo*i*nstaller01011.dll"
# ls viorng/w8/x86/Wdf*
# ls viorng/w8/amd64/Wdf*
# ls viorng/w8.1/x86/Wdf*
# ls viorng/w8.1/amd64/Wdf*
# ls viorng/2k12/amd64/Wdf*
# ls viorng/2k12R2/amd64/Wdf*
2.Wdfxxx file in win7/2k8/2k8R2 are named as "WdfCo*I*nstaller01011.dll"
# ls viorng/w7/x86/Wdf*
# ls viorng/w7/amd64/Wdf*
# ls viorng/2k8/amd64/Wdf*
# ls viorng/2k8/x86/Wdf*
# ls viorng/2k8R2/amd64/Wdf*
Wdfxxx file in win8/win8.1/2012/2012r2 are named as "WdfCo*i*nstaller01011.dll"
The file located in win8/win8.1/2012/2012r2 folder should named WdfCo*I*nstaller01011.dll instead of WdfCo*i*nstaller01011.dll
this issue only existed in virtio-win-1.7.2-1.el6.noarch;
build 88 did not hit this issue.
the corresponding version of viorng in virtio-win-1.7.2-1.el6 is build88,and as comment#0 said,build88 does not hit this issue.
(In reply to lijin from comment #7)
> the corresponding version of viorng in virtio-win-1.7.2-1.el6 is build88,and
> as comment#0 said,build88 does not hit this issue.
Right, the driver binaries are the same, but in virtio-win-1.7.2-1.el6 for some reason WdfCoInstaller01011.dll was renamed to WdfCoinstaller01011.dll
cc'ing Mike Bonnet from Release Engineering team to comment on this issue.
still hit this issue with virtio-win-1.7.3-1.el7.noarch,the viorng version is build96
check with virtio-win-1.7.4-1,steps same as comment#0
all the wdf files are named as WdfCo*I*nstaller01011.dll instead of WdfCo*i*nstaller01011.dll.
So this issue has been fixed already.
change status to verified according to comment#18
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.