Problems with ntdll.dll and cl.exe

[stefangachter]

Hi,

I have installed Microsoft Visual C++ Toolkit 2003 (Compiler Version 13.10.3077 for 80x86). When I try to compile with cl.exe, I get an entry point not found error for ntdll.dll (Version 5.1.2600.1106, I am using Windows XP Professional, SP1).
If ignoring the error message, the compilation terminates correctly and the exe file works as expected. The problem is not related to Code Blocks since I get the same error when starting cl.exe from the command prompt. However, somebody might have had the same problem when installing the toolkit.

Therefore, my questions:

Why do I get this error message?
How can I get rid of it?
Does this error affect the compilation result?

Thanks in advance for any hint.

Regards,

Stefan

[Michael]

Hello,

Just some suggestions:

- Did you search for the error using google?
- Did you search in the M$ website?
- Did you download Microsoft and .NET SDK?
- Update to SP2?

Best wishes,
Michael

[stefangachter]

Thanks for the reply.

Just some suggestions:

- Did you search for the error using google?
 Yes, but I couldn't find any information related with this problem.
- Did you search in the M$ website?
 The same here.
- Did you download Microsoft and .NET SDK?
 I downloaded the Windows Server 2003 SP1 Platform SDK, but not the .NET SDK.
- Update to SP2?
 I want to avoid that.

Maybe the strange thing is that I installed at the begin Code Blocks and Microsoft Toolkit without any problems. It compiled well without any entry point errors. Then I added additional components of the SDK, i.e. I added the debugger provided with the package. After doing that, the entry point error appeared. So, I don't know yet what exactly corrupted the ntdll.dll. Maybe it helps, if I deinstall the debugger.

[stefangachter]

Yes, if I deinstall the debugger provided with the Windows Server 2003
SP1 Platform SDK, then the entry point error does not appear and everything works fine!

Would be nice to know the reason. If somebody has an idea, then please let me know.

[Michael]

Which version of C::B are you using? It is always the same version that you are using or you the problem come out with another version?

Could you may be post the full error?

[EDIT]: Too slow in my reply . May be it is a dll conflict or incompatibility.

Michael

PS.: I hope that in Lausanne the weather is warmer than here in Austria .

[mandrav]

I am using Windows XP Professional, SP1

Yes, if I deinstall the debugger provided with the Windows Server 2003
SP1 Platform SDK, then the entry point error does not appear and everything works fine!

Would be nice to know the reason. If somebody has an idea, then please let me know.

(emphasis added)

Do you still want to know why?

[stefangachter]

Of course, I am curious...

I am using C::B Version 1.0. But I think, the problem is not related to C::B, because the same error appears when compiling and linking within the command prompt.

After installing the debugging tools for Windows and typing cl.exe in the command prompt the following error msg appears:

cl.exe - Entry Point Not Found
The procedure entry point RtlIpv6StringToAddressExW could not be located in the dynamic link library ntdll.dll.

The same message appears for link.exe.

It's a drizzly day in Lausanne...

[takeshimiya]

Hint: Windows Server 2003 and Windows XP are NOT the same Operating System.

[stefangachter]

なるほど！ I see...

[stefangachter]

I checked the Microsoft web page. Concerning the Windows Server 2003 SP1 Platform SDK, they write the following:

The applications you develop with this edition of the SDK can run on the x86, x64 and Itanium-based versions of Windows Server 2003 SP1, Windows XP SP2, Windows XP x64 Pro Edition, and Windows 2000.

However, I am running Windows XP SP1, and there is a version difference between the ntdll.dll for SP1 and SP2.

SP1: ntdll.dll Version 5.1.2600.1106
SP2: ntdll.dll Version 5.1.2600.2180 (I am not sure.)

This may cause the problem. Anyway, I don't use the debugger at the moment...

[Michael]

I am using C::B Version 1.0. But I think, the problem is not related to C::B, because the same error appears when compiling and linking within the command prompt.

I was thinking the same. Anyway, RC2 is old and the installation of the latest nightly build is worth.

It's a drizzly day in Lausanne...

When I was in Lausanne, I think that the weather in winter was cold (especially for someone coming from the south of Switzerland). But when I moved Carinthia, I discovered what cold is....

I checked the Microsoft web page. Concerning the Windows Server 2003 SP1 Platform SDK, they write the following:

The applications you develop with this edition of the SDK can run on the x86, x64 and Itanium-based versions of Windows Server 2003 SP1, Windows XP SP2, Windows XP x64 Pro Edition, and Windows 2000.

However, I am running Windows XP SP1, and there is a version difference between the ntdll.dll for SP1 and SP2.

SP1: ntdll.dll Version 5.1.2600.1106
SP2: ntdll.dll Version 5.1.2600.2180 (I am not sure.)

Yes, it is possible. May be you can try with a computer where SP2 is installed. If it works there, then it is a version issue.

Michael