HI Soeren,
Thanks for catching the closesocket() name clash... I would have hit that one pretty soon myself!
I don't see anything wrong with what you did (but "foo;" will do nothing ... instead of the command line write "foo hi there;" to the program's input (on the command prompt window) once it's running.
Maybe, just maybe, it needs "localhost" or <machine name> instead of 127.0.0.1, but that's just a desperate guess. If Pd ruins at all, then "10093" can't just mean "sorry, no network"... because Pd uses exactly the same mechanism to talk to its own GUI.
baffled...
Miller
On Fri, Aug 16, 2002 at 09:38:33PM +0200, Søren Bovbjerg wrote:
Apparently there's no"pdsend" in teh windows version. My windows machine is on the road at the moment so I can't look into it right now. But the source code (u_pdsend.c) ought to be there, and to compile to a standalone "command prompt" program...
I alsoneed this program so I tried to compile it tonight in MSVC 6 (it needs to be linked to wsock32.lib, I assume). Compiling was not without a fight. It breaks at:
void closesocket(int fd); with error C2373: 'closesocket' : redefinition; different type modifiers
Changing the name 'closesocket'solves the problem (erm.. is it the right solution?) but when I try to send to PD netreceive patch (the one in the reference folder) with pdsend 3000 127.0.0.1 tcp "foo;" I get Socket(): Unknown error 10093
According to www.sockets.com this may mean that "the network subsystem is misconfigured or inactive" - which it isn't (AFAIK). Can it be a Windows XP thing?
I am still quite a novice in this programming/compiling field - so be gentle if I am missing the obvious.
Take care
Soeren