>At 04:45 PM 8/1/96 -0400, Shirley A MacLaughlin wrote:
>>Question:  How can these applications (RNS and TCPMAN) co-exist?
>>
>>I've resorted to alternate boot paths to use both, but this is not
>>satisfactory.
>>
>>Any ideas?
>
>Theoretically, a Winsock application can allow for multiple different
>Winsocks libraries to be present (in different subdirectories) and to access
>the appropriate one.  To quote the spec, "Nothing in the specification
>should be interpreted as restricting multiple Windows Sockets DLLs from
>being present and used concurrently by one or more Windows Sockets
>applications.".
>
>Well it looks good on paper, but I've never seen anyone do it.  RNS and
>TCPMAN, in this case, are not applications but alternative transports.  Your
>actual application, like Reflection 1 needs to be 'smart' enough to search
>for multiple TCP/IPs.
>
 
Jim,
 
Probably because the windows memory manager uses the module name as the
identifying id. This means that you can only have ONE winsock.dll loaded at
the same time. Once winsock.dll is loaded any future references to a
winsock.dll will use the currently loaded copy. So multiple winsock.dll's on
your system are only good for *starting* up a winsock application. This is a
windows limitation, not an implementation limitation.
 
 
Duane Percox  (QSS)
[log in to unmask] (415-306-1608, fax 415-365-2706)
http://www.aimnet.com/~qssnet/
 ftp://ftp.aimnet.com/pub/users/qssnet/
"The best way to have a good idea is to have a lot of ideas." -- Linus Pauling