madConfigDrv.exe bug on Windows 10
Posted: Mon Aug 24, 2015 8:40 am
Hi,
I've found some weird bug in madConfigDrv.exe.
To reproduct the bug:
* Development environment: Windows 10, x64 machine, Visual Studio 2015(SP5)
1) Set up a Win32 empty project on Windows 10 and Visual Studio 2015(SP5).
2) In Post Build Event, set madConfigDrv.exe script(e.g. madConfigDrv.exe Xxx.sys DrvName Xxx1.dll Xxx2.dll -stopDisallowed)
3) Set Configuration Properties -> General -> Platform Toolset to "Visual Studio 2013 - Windows XP (v120_xp)"
4) Build the project, and you get the generated sys file.
5) Now this .sys file cannot be loaded Windows 7(x64) machine. But this .sys file is loaded successfully on Windows 8.1/10.
If you set Platform Toolset to "Visual Studio 2013", this bug doesn't occur.
On Windows 8.1 this bug does not occur.
Also if you run madConfigDrv.exe outside Visual Studio, everything's fine.
Why is that?
I've found some weird bug in madConfigDrv.exe.
To reproduct the bug:
* Development environment: Windows 10, x64 machine, Visual Studio 2015(SP5)
1) Set up a Win32 empty project on Windows 10 and Visual Studio 2015(SP5).
2) In Post Build Event, set madConfigDrv.exe script(e.g. madConfigDrv.exe Xxx.sys DrvName Xxx1.dll Xxx2.dll -stopDisallowed)
3) Set Configuration Properties -> General -> Platform Toolset to "Visual Studio 2013 - Windows XP (v120_xp)"
4) Build the project, and you get the generated sys file.
5) Now this .sys file cannot be loaded Windows 7(x64) machine. But this .sys file is loaded successfully on Windows 8.1/10.
If you set Platform Toolset to "Visual Studio 2013", this bug doesn't occur.
On Windows 8.1 this bug does not occur.
Also if you run madConfigDrv.exe outside Visual Studio, everything's fine.
Why is that?