windows sockets????

[alondra]

my neighbor has a problem with freei.net. they said they were going to a new Emai lformat and to re load the proggy, now he cant get on and gets the following banner
talk
windows sockets version 1.1 or greater required.
What is "sockets" Help.

[Richard_Cranium72]

If they are running Win98, they need DCOM98 download from MS. Win95 is dun 1.3. These are the dial up networking protocols. I have a couple of links here. =>>
ReleaseID (http://www.microsoft.com/downloads/release.asp?ReleaseID=12646)

W95WinsockUpgrade (http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95winsockupgrade/default.asp?site=95)

and =>> W95Sockets2 (http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/)

and DCOM98 for Windows 98, version 1.3

FReleaseID (http://www.microsoft.com/com/dcom/dcom98/download.asp?FinishURL=%2Fdownloads%2Frelease%2Eas p%3FReleaseID%3D10338%26redirect%3Dno) DrVette


Edited the links, Doc, they were blowing out the frames http://sysopt.earthweb.com/forum/wink.gif -socalgal


Thanks Girl, btw, how did ya do that, R click and "rename" or what. Really nice now, BOY it WAS ugly.. DoktorVette

[This message has been edited by Richard_Cranium72 (edited 08-01-2000).]

[Richard_Cranium72]

I think they are related to "Winsock" the dial up networking feature, =>> " A socket contains three pieces of information: an internetwork address, a protocol, and a port number. The address information must contain a network ID and a node ID. Because both TCP/IP and IPX/SPX have network and node information incorporated in their addressing schemes, either protocol can use the sockets interface. The port number combined with the protocol determines whether the socket uses TCP, UDP, or IPX, and which service will be used.

The component files that make up the sockets interface for Windows 95 are Winsock.dll and Wsock32.dll. The files that are included with Windows 95 support the sockets interface for both TCP/IP and IPX/SPX. The Cheyenne ArcServe Agent makes calls directly to Wsock32.dll to obtain an IPX socket for communication with a NetWare server to perform backup operations over the network.

Because some third-party vendors may require functionality from the sockets interface for their proprietary protocol stacks, they may replace the component files that make up the sockets interface with their own proprietary versions of these files. If the third-party vendor's sockets interface does not support sockets using IPX/SPX, any program that uses the sockets interface to communicate using IPX/SPX may generate an error message." hope this helps, somehow. DrVette

[alondra]

Thanks, don't know why the customer should have to add files, but downloaded the Frelease to a floppy. will try to get hold of the ISP on my machine tomorrow. its a toll phone call... one reason why I don't mind paying 17.50 a month to my LOCAL isp. 5 min from my house. http://sysopt.earthweb.com/forum/smile.gif
Al

[Richard_Cranium72]

I had to do the DCOM98 thing on mine when I got the usless isp Americasomethingortheother. HEY, didn't I post for ya to get AltaVista for these folks? www.microav.com (http://www.microav.com) ? It don't hurt to say it again I guess. Here's MS's thought as to why you have to grab some more ptp software AGAIN.=>> "Because some third-party vendors may require functionality from the sockets interface for their proprietary protocol stacks, they may replace the component files that make up the sockets interface with their own proprietary versions of these files." SO, freeinet may have diddled with the sockets or some other isp, perhaps a botched install by the user? Gluck, DrVette