Thread: Windows XP compatibility with 10.2 update 2
Posts:
21
Registered:
6/12/04
|
|
|
We are experiencing issues since 10.2 update 2 (2004) on Windows XP platform :
"The procedure entry point inet_pton could not be located in the dynamic link library ws2_32.dll".
Seems the inet_pton procedure does not exists on Windows XP....
Anyone experiencing this ?
|
|
|
Posts:
801
Registered:
3/14/14
|
|
Pascal Bellebouche wrote:
We are experiencing issues since 10.2 update 2 (2004) on Windows XP
platform : "The procedure entry point inet_pton could not be located
in the dynamic link library ws2_32.dll". Seems the inet_pton
procedure does not exists on Windows XP....
Anyone experiencing this ?
That's correct, according to the MSDN
( https://msdn.microsoft.com/en-us/library/windows/desktop/cc805844(v=vs.85).aspx):
Minimum supported client Windows 8.1, Windows Vista [desktop apps | UWP
apps]
Minimum supported server Windows Server 2008 [desktop apps | UWP apps]
Windows XP is not supported anymore by Embarcadero or Microsoft. |
|
|
|
|
Posts:
3
Registered:
12/29/04
|
|
We are experiencing issues since 10.2 update 2 (2004) on Windows XP platform :
"The procedure entry point inet_pton could not be located in the dynamic link library ws2_32.dll".
Seems the inet_pton procedure does not exists on Windows XP....
Anyone experiencing this ?
Yes.
Try to set "Link with runtime packages" to false (at least for the XP version).
Edited by: Rickard Johansson on Dec 19, 2017 7:39 AM |
|
|
|
|
Posts:
21
Registered:
6/12/04
|
|
We are experiencing issues since 10.2 update 2 (2004) on Windows XP platform :
"The procedure entry point inet_pton could not be located in the dynamic link library ws2_32.dll".
Seems the inet_pton procedure does not exists on Windows XP....
Anyone experiencing this ?
Yes.
Try to set "Link with runtime packages" to false (at least for the XP version).
Edited by: Rickard Johansson on Dec 19, 2017 7:39 AM
That's correct, without RunTimePackages, it does work. But... Our applications uses runtime packages ! Therefore this is not a possible fix for us.
By the way it was working fine in 10.2 update 1, so I am really curious to know why did Embarcadero changed this behaviour in a minor update.... |
|
|
|
|
Posts:
801
Registered:
3/14/14
|
|
Pascal Bellebouche wrote:
We are experiencing issues since 10.2 update 2 (2004) on Windows
XP platform : "The procedure entry point inet_pton could not be
located in the dynamic link library ws2_32.dll". Seems the
inet_pton procedure does not exists on Windows XP....
Anyone experiencing this ?
Yes.
Try to set "Link with runtime packages" to false (at least for the
XP version).
Edited by: Rickard Johansson on Dec 19, 2017 7:39 AM
That's correct, without RunTimePackages, it does work. But... Our
applications uses runtime packages ! Therefore this is not a possible
fix for us.
By the way it was working fine in 10.2 update 1, so I am really
curious to know why did Embarcadero changed this behaviour in a minor
update....
There must be a reason. However according to
http://docwiki.embarcadero.com/PlatformStatus/en/Main_Page the last
version that was built to support Windows XP SP 2 was XE5 so you should
expect in newer versions that Embarcadero will use newer Windows API
without a warning. |
|
|
|
|
Posts:
9,447
Registered:
12/23/01
|
|
Pascal Bellebouche wrote:
By the way it was working fine in 10.2 update 1, so I am really
curious to know why did Embarcadero changed this behaviour in a minor
update....
10.2.2 is more than just a minor update, it does have some new features
in it, too. So it is not unreasonable to expect that newer APIs might
get called.
--
Remy Lebeau (TeamB) |
|
|
|
|
Posts:
21
Registered:
6/12/04
|
|
Pascal Bellebouche wrote:
By the way it was working fine in 10.2 update 1, so I am really
curious to know why did Embarcadero changed this behaviour in a minor
update....
10.2.2 is more than just a minor update, it does have some new features
in it, too. So it is not unreasonable to expect that newer APIs might
get called.
--
Remy Lebeau (TeamB)
I thought Embarcadero update roadmap was clear but it seems I've been wrong... As you state, 10.2.2 is NOT 10.2 Update 2 as I expected .
I'm still surprise they "broke" WindowsXP compatibility so quickly.
As software editor, we are really aware of this kind of issues so we try to keep our products compatible with older versions od operating systems (because our clients are often lazy on running microsoft updates) |
|
|
|
|
Posts:
9,447
Registered:
12/23/01
|
|
Pascal Bellebouche wrote:
I thought Embarcadero update roadmap was clear but it seems I've
been wrong...
In what way?
As you state, 10.2.2 is NOT 10.2 Update 2 as I expected.
It is. It just has more than just an update in it.
I'm still surprise they "broke" WindowsXP compatibility so quickly.
They didn't just now break it. They started breaking it a long time
ago.
--
Remy Lebeau (TeamB) |
|
|
|
|
Posts:
424
Registered:
6/28/02
|
|
They didn't just now break it. They started breaking it a long time
ago.
--
Remy Lebeau (TeamB)
Breaking everywhere but seldom valuable new features. Most new features is just plagiarizing other languages , and there is seldom valuable case for those new features.
It's hard to see the new libraries, components or products developed by third parties using those "new features".
However, "embarcadero" is still stubbornly thought those "breaking " is valuable. |
|
|
|
|
Posts:
314
Registered:
5/16/97
|
|
it was working fine in 10.2 update 1
our clients are often lazy on running microsoft updates
So keep using 10.2.1, It's still on your customer downloads. That's what it's there for. |
|
|
|
|
Posts:
10
Registered:
3/16/00
|
|
I have a new project proxy functions to all exported functions of original Windows XP's WS2_32.dll including inet_pton that was missing in Windows XP's WS2_32.dll.
It tricks the Windows XP application process to think that inet_pton is available and not prompting any errors.
Repository: https://github.com/ccy/WS2_32_XP
--
Best regards,
Chau Chee Yang |
|
|
|
Legend
|
|
Helpful Answer
(5 pts)
|
|
Correct Answer
(10 pts)
|
|
Connect with Us