Mr. Wowchuk writes:
 
>Again to clip from the ODBC Readme.HP file...
>
>>WLIBSOCK is only supplied by Novell for LAN WorkPlace.  Beginning with
>>  LAN WorkPlace version 4.1, Novell is also supporting WINSOCK.
 
You are quite right.  LWP 5.0 installs WINSOCK.DLL in \WINDOWS\SYSTEM.
 
>So there is winsock support, but I recall having some other problems when I
>was setting up IMAGE/SQL on a site using LWP, but I can't remember the
>specifics.  They may have been something about name resolution, but perhaps
>not.  As LWP clearly supports Winsock, and HP state that IMAGE/SQL supports
>Winsock, can James (or anyone else) give us a clue about the particular
>problem of using IMAGE/SQL through LWP transport?
 
I installed LWP 5.0 per Novell's instructions (using their Windows-based
installation program), and their utilities worked with no apparent errors.
Ditto for Reflection/Win 4.1, Netscape Navigator, Eudora, TCP3270, etc.
 
DNS seems to work OK.  When I attempted to connect to our 3000 using
SCRIPTOR (to verify the connection) over LWP 5.0'w WINSOCK.DLL, I received
this error:
 
        PC Sockets Error #20362: Connection refused.
 
 
This makes me wonder if the wrong Ethernet frame type was sent, and my card
is configured for ETHERNET_802.3, ETHERNET_802.2, ETHERNET_SNAP, and
ETHERNET_II.  This configuration works OK for Wolverine, by the way (which I
am now using).
 
I replied to Jeff Kell privately that all other WinSock applications are
able to run successfully over LWP 5.0, with the *sole* exception of PC API.
 
So I'm at a loss to understand why PC API doesn't get along with LWP 5.0,
and, insofar as LWP 5.0 is the _de facto_ standard here, connecting to
Allbase from our large population of LWP desktops remains a fond fantasy.
 
 
--Jim