User forums > Help

Problems with ntdll.dll and cl.exe

<< < (2/3) > >>

mandrav:

--- Quote from: stefangachter ---I am using Windows XP Professional, SP1
--- End quote ---


--- Quote from: 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!

--- End quote ---


--- Quote from: stefangachter ---Would be nice to know the reason. If somebody has an idea, then please let me know.
--- End quote ---
(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...

Navigation

[0] Message Index

[#] Next page

[*] Previous page