Home/ Questions/Q 1017247
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T10:40:26+00:00

I have an application that needs to operate on Windows 2000. I’d also like

  • 0

I have an application that needs to operate on Windows 2000. I’d also like to use Visual Studio 2010 (mainly because of the change in the definition of the auto keyword). However, I’m in a bit of a bind because I need the app to be able to operate on older OS’s, namely:

  • Windows 2000
  • Windows XP RTM
  • Windows XP SP1

Visual Studio 2010’s runtime library depends on the EncodePointer / DecodePointer API which was introduced in Windows XP SP2.

If using the alternate runtime library is possible, will this break code that relies on C++0x features added in VS2010, like std::regex?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Suma’s solution looked pretty promising, but it doesn’t work: the __imp__*@4 symbols need to be pointers to functions, rather than the functions themselves. Unfortunately, I don’t know how to make Visual C++ spit out a pointer with that kind of name generation… (well, __declspec(naked) combined with __stdcall does the trick, but then I don’t know how to emit a pointer).

    If using an assembler at build-time is OK, the solution is pretty trivial – assemble the following code with FASM and link against the produced object file, and presto – no EncodePointer/DecodePointer references in the exe:

    use32
format ms coff

section ".data" data
public __imp__DecodePointer@4
__imp__DecodePointer@4 dd dummy

public __imp__EncodePointer@4
__imp__EncodePointer@4 dd dummy

section ".text" code
dummy:
mov eax, [esp+4]
retn 4
    • 0