>> What means error 10050? Does anybody know what to do? <<
According to the Winsock documentation, 10050 means "Network is down". This is why I include that text in the error message. All WideClient is doing is attempting to start the service, yet when it tries, Windows replies with that error. In case it is useful, here is some expanded text from MS sources:
----------------------------------------------
WSAENETDOWN
(10050)
Network is down.
A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.
----------------------------------------------
I must admit I don't like WinME and regard it as the biggest mistake Microsoft ever made. I tolerated it for a full two days when it came on a new Notebook of mine a while back -- then I reformatted the HD and went back to Win98SE.
Howwever, that said, there must be some way of resolving your problem. Maybe the ServerNode you are specifying is wrong? Maybe you are not specifying a ServerNode and Windows ME wants one?
A friend of mine who had Win98SE on one PC and WinME on his notebook NEVER ever managed to get the ME machine to see the other -- he eventualy upgraded to XP instead.
You could also try changing everything over to TCP/IP instead. If you ever intend to move on to XP in the future that would probably be needed in any case. Version 5.41 performas quite well on TCP/IP, much more smoothly than it used to. That's where I've been doing most of the recent work on it.
Regards,
Pete