can msvc application depended on sdk 7.1A run on windows XP sp3?

Question

can msvc application depended on sdk 7.1A run on windows XP sp3?

gy l 1

compiled env: vs 2013 + sdk 7.1A + platform toolset v120_xp.
run on windows xp sp3 , got errors as follows:

Xiaopo Yang - MSFT 12,731 Reputation points Microsoft External Staff

2021-08-09T06:48:04.367+00:00

I recommend testing with a minimal sample.
RLWA32 49,636 Reputation points

2021-08-09T09:04:53.717+00:00

I did test a minimal sample created with VS2013 (without QT) and targeted for Windows XPSP3.

1 answer

Your answer

Xiaopo Yang - MSFT 12,731 Reputation points Microsoft External Staff

2021-08-09T06:48:04.367+00:00

I recommend testing with a minimal sample.
RLWA32 49,636 Reputation points

2021-08-09T09:04:53.717+00:00

I did test a minimal sample created with VS2013 (without QT) and targeted for Windows XPSP3.

Answer 1

RLWA32 49,636

I only understand English but I'm guessing that your code fails on Windows XP sp3 because it is attempting to use functions that were introduced in Windows Vista. When you build to Target windows XP sp3 you must properly define _WIN32_WINNT before including any sdk headers. Refer to using-the-windows-headers

For example,

#define NTDDI_VERSION NTDDI_WINXPSP3  
#define _WIN32_WINNT _WIN32_WINNT_WINXP  
#include <Windows.h>

After properly targeting for Windows XPSP3 any code attempting to use functions that were not available until later versions of Windows will now cause compilation errors. So it will be necessary to find alternate solutions that are available in the version of Windows that is targeted.

gy l 1 Reputation point

2021-08-08T05:20:38.21+00:00

Thanks.
The failure means "Unable to locate program input point if_nametoindex on dynamic link iphlpapi.dll" and "Unable to locate program input point RtlIdnToAscii on dynamic link ntdll.dll". they are as same as you guessing.
I add those macros in preprocessor definitions of project.

Then, compile the project, no compilation errors. But the failures of running on xp sp3 aren't removed.
Unable to locate program input point if_nametoindex on dynamic link iphlpapi.dll

what am I doing wrong?

the failuration dll of location imported in source code.
RLWA32 49,636 Reputation points

2021-08-08T08:26:58.86+00:00

The preprocessor definitions look correct to me to target Win XPSP3. In a sample VS2013 project (without QT) that correctly produced compilation errors for functions introduced in Vista the preprocessor definitions looked like this

The windows.h header file from the 7.1A SDK has a #include statement for sdkddkver.h at the very top which is essential when using the symbolic values for NTDDI_VERSION and _WIN32_WINNT. It looks like this

The include path for headers looks like this

If your use of QT is causing a version of windows.h that does not #include sdkddkver.h to be used that could be a problem.

Try using the hexadecimal values in the preprocessor definitions instead of the symbolic values, like this

RLWA32 49,636

To help diagnose you can set your project options to show the headers being included in the build. Set this

When building the project the Output pane will show the headers like this-

1>------ Build started: Project: Win32Project1, Configuration: Release Win32 ------  
1>  stdafx.cpp  
1>  Note: including file: c:\users\rlwa32\documents\visual studio 2013\projects\win32project1\win32project1\stdafx.h  
1>  Note: including file:  C:\Program Files\Microsoft SDKs\Windows\v7.1A\include\windows.h  
1>  Note: including file:   C:\Program Files\Microsoft SDKs\Windows\v7.1A\include\sdkddkver.h  
  
    Rest of headers follow

gy l 1 Reputation point

2021-08-08T09:36:05.82+00:00

project configuration:

preprocess defination:

This configuration has a contradiction, platform toolset is v120_xp, but in preprocess defination use _USING_V110_SDK71_. May this is a problem?

This application is one based on qt5.4. But i think it has #include sdkddkver.h, because when I define those two macro in a .h headfile, I got a warning of macro redefine.

And I can jump to the sdkddkver.h through compiling output hints.
when I define them in preprocess definations, warning is disappeared.
I have modify two macros with hexadecimal values. But failure still occurr on xp sp2.
I find that dll occurring failure locate in source code.

thanks!
RLWA32 49,636 Reputation points

2021-08-08T10:15:22.98+00:00

This configuration has a contradiction, platform toolset is v120_xp, but in preprocess defination use USING_V110_SDK71. May this is a problem?

No.

I have modify two macros with hexadecimal values. But failure still occurr on xp sp2.

I believe that the version of XP targeted by the v120_xp toolset is XPSP3. I don't know if an application built by this toolset will run properly on XPSP2.

This application is one based on qt5.4. But i think it has #include sdkddkver.h, because when I define those two macro in a .h headfile, I got a warning of macro redefine.

As I previously noted, the macros must be defined BEFORE including any SDK header files. If you are not receiving compilation errors when the macros are defined in the preprocessor definitions and the application fails to start on XPSP2 then perhaps QT is improperly redefining them for your purposes.

Did you use the project options to show includes to verify proper inclusion of sdkddkver.h?

But the ultimate solution is to remove the use of the unavailable functions from the code!

gy l 1

2>Note: including file:    e:\qt\qt5.4.0\5.4\msvc2013_opengl\include\qtcore\qqueue.h
**2>Note: including file:   E:\Qt\Qt5.4.0\5.4\msvc2013_opengl\include\QtCore\qt_windows.h
2>Note: including file:    C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\include\windows.h
2>Note: including file:     C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\include\sdkddkver.h**
2>Note: including file:     D:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\excpt.h
2>Note: including file:      D:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\crtdefs.h
2>Note: including file:     C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\include\windef.h
2>Note: including file:      C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\include\winnt.h
2>Note: including file:       C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\include\specstrings.h

Are these include files correct? Many places include windows.h and sdkddkver.h.
Are there are other possibilities to led to that failure?

In my source code I find the .lib file lead to failure, as follows:

#include "Wlanapi.h"
#pragma comment(lib, "Wlanapi.lib")
#include "Setupapi.h"
#pragma comment(lib, "setupapi.lib")
#include"iphlpapi.h"
#pragma comment(lib,"Iphlpapi.lib")
#include "Shlwapi.h"
#pragma comment(lib,"Shlwapi.lib")

But i didn't found this file included in building output pane. Why?

RLWA32 49,636 Reputation points

2021-08-09T00:53:52.627+00:00

The guidance I have given you is what is needed to target Windows XPSP3 when building with VS2013.

However, if after implementing this guidance your development environment with QT continues to produce binaries (.exe, .dll) that cannot function on Windows XPSP3 due to their use of unavailable functions then it is probably due to QT. Maybe your development environment is using QT libraries that reference these unavailable functions or perhaps there is some additional configuration of QT that is required. I suggest you pursue this problem in the QT forums since it does not appear to me to be a VS2013 problem.
gy l 1 Reputation point

2021-08-21T08:06:15.987+00:00

Thanks a lot for your guild. I will make more try, and I had learned many, And I got some thoughts and ways from you.

Share via

can msvc application depended on sdk 7.1A run on windows XP sp3?

1 answer

Your answer