#1314 WSAStartup failure prevents pd patch from running headless on Windows 10

[Anonymous]

I am attempting to run this simple patch: osc_test.pd on my Windows 10 computer, headless, using pd 0.48-1 vanilla along with the mrpeach external. Using the command prompt, I go to the directory that contains this patch, and then enter the command "pd -nogui osc_test.pd". When I do this, I get

error: udpreceive: socket: Either the application has not called WSAStartup, or WSAStartup failed. (10093)
verbose(4): ... you might be able to track this down from the Find menu.
error: udpsend socket: Either the application has not called WSAStartup, or WSAStartup failed. (10093)
error: udpsend: not connected

However, when I instead enter the command "pd osc_test.pd" (with the GUI) it is able to run properly. By run properly, I mean that

udpsend: connecting to port 9001
print: /test 20 30 40

is printed in the pd terminal window, which is the expected behavior.

[Anonymous]

this should work better in the (upcoming) 0.48-2. (If not, maybe report to github instead
of here to make sure everyone sees it).

[Martin Peach]

When I try that, Pd prints nothing at all. If I do it from a cygwin terminal, I have to kill Pd with ctrl-c, if I try with command prompt, Pd exits straight away with no message, In both cases -verbose has no effect. (With command prompt, but not cygwin, , typing pd.exe -help exiits immediately with no output, so some other stuff is brokem I guess....)

[Miller Puckette]

As of pd-0.48-2test1 I'm automatically calling WASStartup() whenever Pd starts up
(with or without GUI) so if you're using the latest you migth not see the bug (and
perhaps this means I fixed it.

cheers
Miller

On Tue, Aug 07, 2018 at 04:01:18PM -0000, Martin Peach wrote:

When I try that, Pd prints nothing at all. If I do it from a cygwin terminal, I have to kill Pd with ctrl-c, if I try with command prompt, Pd exits straight away with no message, In both cases -verbose has no effect. (With command prompt, but not cygwin, , typing pd.exe -help exiits immediately with no output, so some other stuff is brokem I guess....)

---

** [bugs:#1314] WSAStartup failure prevents pd patch from running headless on Windows 10**

Status: open
Group: v0.48
Created: Sat Aug 04, 2018 06:38 PM UTC by Anonymous
Last Updated: Sat Aug 04, 2018 11:40 PM UTC
Owner: nobody
Attachments:

• osc_test.pd (sourceforge.net) (426 Bytes; application/octet-stream)

I am attempting to run this simple patch: osc_test.pd on my Windows 10 computer, headless, using pd 0.48-1 vanilla along with the mrpeach external. Using the command prompt, I go to the directory that contains this patch, and then enter the command "pd -nogui osc_test.pd". When I do this, I get

error: udpreceive: socket: Either the application has not called WSAStartup, or WSAStartup failed. (10093)
verbose(4): ... you might be able to track this down from the Find menu.
error: udpsend socket: Either the application has not called WSAStartup, or WSAStartup failed. (10093)
error: udpsend: not connected

However, when I instead enter the command "pd osc_test.pd" (with the GUI) it is able to run properly. By run properly, I mean that

udpsend: connecting to port 9001
print: /test 20 30 40

is printed in the pd terminal window, which is the expected behavior.

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/pure-data/bugs/1314/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Anonymous]

Thank you all very much for your time and information! I tested out osc_test.pd with pd-0.48-2test1 and from what I can tell, the test patch runs properly! I have attached an image showing the output that I get when I run osc_test.pd with no GUI.