Problem: Winsock dependency?

[Brendan Reville <br...@tenzing.com>]

hi all,

two issues covered here:

I thought somebody should know about this -- I've been using the 1.2 win32
Xerces DLL on an original Windows 95 machine and it worked fine, with only
an occasional error about the NetAccessor not being initialized/available
(can't quite remember the exact error). Anybody know why this would go
wrong?

I suspect it's a winsock error.  Since I'm only parsing a local file, I
don't think the NetAccessor even needs to be initialized.

Anyway, I just d/led the latest stable release (1.3), and it no longer
works on an original Windows 95 box, because it depends on WS2_32.DLL,
Winsock 2.  Is there any easy way to remove this dependency?  Or do I need
to recompile the source without the NetAccessor component?

thanks

Re: Problem: Winsock dependency?

[Andy Heninger <an...@jtcsv.com>]

From: "Brendan Reville" <br...@tenzing.com>
Subject: Problem: Winsock dependency?


> two issues covered here:
>
> I thought somebody should know about this -- I've been using the 1.2
win32
> Xerces DLL on an original Windows 95 machine and it worked fine, with
only
> an occasional error about the NetAccessor not being
initialized/available
> (can't quite remember the exact error). Anybody know why this would go
> wrong?
>
> I suspect it's a winsock error.  Since I'm only parsing a local file, I
> don't think the NetAccessor even needs to be initialized.
>
> Anyway, I just d/led the latest stable release (1.3), and it no longer
> works on an original Windows 95 box, because it depends on WS2_32.DLL,
> Winsock 2.  Is there any easy way to remove this dependency?  Or do I
need
> to recompile the source without the NetAccessor component?
>

To change xerces back to the old WinSock you don't need to
change any source, just have it link with wsock32.lib instead of
ws2_32.lib

I'm inclined to leave the prebuilt binaries as they are.  Either way,
they won't be right for some people - some apps need ws2.

Back in July, Eliot Muir suggested a solution...

> It's possible to dynamically link at runtime to the Winsock
> DLL which is a good idea if you don't have too much control
> over the destination machines.
>
> i.e. one has to use GetProcAddress etc. to get winsock function
> addresses.
>
> (haven't actually done it ourselves yet - it's on the TODO list)
>
> Cheers,
> Eliot
>
> --
> Eliot Muir, Technical Director                 iNTERFACEWARE
> mailto:eliot.muir@interfaceware.com
> ICQ# 73674543
> Voice 1-416-8207050      http://www.interfaceware.com
>
> Makers of iNTERFACEWARE Chameleon
>    "Program to the iNTERFACE not the implementation"
>
> -----Original Message-----
> From: Jon Smirl [SMTP:jonsmirl@mediaone.net]
> Sent: Thursday, July 06, 2000 11:50 PM
> To: xerces
> Subject: Windows and Winsock
>
> I just noticed that Xerces is linking to the old winsock while Apache is
> linking to the new Winsock2. Shouldn't Xerces be using Winsock2?
>
> Apache: ws2_32.lib
> Xerces: wsock32.lib
>
> I vaguely recall read some messages about problems caused by mixing
these
> two in the same app.
>
> Jon Smirl
> jonsmirl@mediaone.net