Printable View
Hi all,
Iam using IcmpParseReplies() Api, but iam getting
error LNK2001: unresolved external symbol _IcmpParseReplies
But i had already included the IcmpAPI.h header file and icmp.lib, Iphlpapi.lib files linked in SETTINGS-> LINK.
Iam also using IcmpSendEcho2() Api in the same code.
Iam not getting unresolved error while using IcmpSendEcho2().
How to solve this problem?
With Regards,
A.Ilamparithi.
This function is only available in Windows 2000 or higher...thus, it might be covered with an '#ifdef...#endif' guard...
Thus, you need to set the WINVER macro accordingly...
Code:#define WINVER 0x0500
Hi Andreas,Quote:
Originally posted by Andreas Masur
This function is only available in Windows 2000 or higher...thus, it might be covered with an '#ifdef...#endif' guard...
Thus, you need to set the WINVER macro accordingly...
Code:#define WINVER 0x0500
Iam working in a Windows 2000 Professional machine only.
Anyway i tried to set WINVER macro, still the error remains the same.
With Thanks,
A.Ilamparithi.
Well...I did not check it, thus, it might be the other macro instead...
Code:#define _WIN32_WINNT 0x0500
Hi Andreas,Quote:
Originally posted by Andreas Masur
Well...I did not check it, thus, it might be the other macro instead...
Code:#define _WIN32_WINNT 0x0500
Still the same linking error occurs.
With Thanks,
A.Ilamparithi.
Well...then I am running out of ideas at the moment...I do not have the header available, thus, cannot look for the function...sorry about that....
No probs!Quote:
Originally posted by Andreas Masur
Well...then I am running out of ideas at the moment...I do not have the header available, thus, cannot look for the function...sorry about that....
Thanks Andreas!
Anyone know the solution?????? :(
A.Ilamparithi.
Well thats a linker error, and #ifdef are resolved at compile time. So defining WIN_VER wont matter. May be u need to upgrade your SDK. Its a failrly recent API supported on Win2K and above.Quote:
Originally posted by Andreas Masur
Well...I did not check it, thus, it might be the other macro instead...
Code:#define _WIN32_WINNT 0x0500
Regards,
Usman.
Ohhh....one more thing that comes to my mind...make sure that you have the latest files...in other words...does the function exists in your header file?
Hi Usman,Quote:
Originally posted by usman999_1
Well thats a linker error, and #ifdef are resolved at compile time. So defining WIN_VER wont matter. May be u need to upgrade your SDK. Its a failrly recent API supported on Win2K and above.
Regards,
Usman.
Iam using Microsoft Platform Software Development Kit (SDK) April 2000 Edition and my system is Windows 2000 Professional 5.00.2195 with service pack 4.
Should i upgrade SDK??
With Thanks,
A.Ilamparithi.
Hi Andreas,Quote:
Originally posted by Andreas Masur
Ohhh....one more thing that comes to my mind...make sure that you have the latest files...in other words...does the function exists in your header file?
I had already checked that.
That function is in the header file. :(
With Thanks,
A.Ilamparithi.
I am not sure about the SDK version problem, But still April 2000 ver is more then 4 yrs old. I would say if possible try upgrading to a newer version first.Quote:
Originally posted by ilamparithi
Hi Usman,
Iam using Microsoft Platform Software Development Kit (SDK) April 2000 Edition and my system is Windows 2000 Professional 5.00.2195 with service pack 4.
Should i upgrade SDK??
With Thanks,
A.Ilamparithi.
Regards,
Usman.
Hi Usman,Quote:
Originally posted by usman999_1
I am not sure about the SDK version problem, But still April 2000 ver is more then 4 yrs old. I would say if possible try upgrading to a newer version first.
Regards,
Usman.
If that is the case, then the header file itself should not have the function definition know??
But, that is not the case here. In the header file, the function definition is there.
With Thanks,
A.Ilamparithi.
Well...you are right about the technical aspect....however, many functions (usually functions not available for all Windows operating systems) are covered by such a guard to prevent using these functions on systems which do not support these...and in this case 'WINVER' etc. does matter pretty much... :cool:Quote:
Originally posted by usman999_1
Well thats a linker error, and #ifdef are resolved at compile time. So defining WIN_VER wont matter.
Then check whether the function is exported through the lib file...using the dependency walker for example...Quote:
Originally posted by ilamparithi
In the header file, the function definition is there.