MSFT HCK
-
What a pain in the but it is for getting a driver signed. Why is it so dependent on hardware? If the hardware hasn't got a serial number, fail. Device descriptor is a bit shoddy at times, fail. Device goes unresponsive. BSOD and fail. Not only that its also dependent on the PC its tested on. One of them has a failure as big as the titanic iceberg right in the ACPI/BIOS subsystem. So the Windows kernel is a highly structured and layered environment, and the driver you are testing sits on at least two others, and is a long way from the hardware, so why does the HCK fail on hardware errors? Why doesn't it implement a virtual piece of hardware via a filter, which it has anyway, and test JUST your driver? It really is a pain in the but at times. Especially if the hardware is a bit flaky.
"The whole idea that carbon dioxide is the main cause of the recent global warming is based on a guess that was proved false by empirical evidence during the 1990s." climate-models-go-cold