chia-plot-sink doesn't work with mmx-cpu-plotter

[aramod]

The parameter does not accept '-d @localhost' for WIN10. Will there be support in new versions?
It was also great to add GPU plotter supports multiple -d

[madMAx43v3r]

Windows doesn't like you using localhost to refer to the local host, you have to use the actual host name like @PC-345345345.

[aramod]

-d @PC-345345345 not work for mmx-cpu-plotter. There is no new version 2.4 for WIN10
It only works for mmx-cuda-plotter

[aramod]

Farmer Public Key (48 bytes) needs to be specified via -f, see chia keys show.
This is the error it shows

[madMAx43v3r]

ah yeah it only works with GPU plotter yes

[aramod]

Will copy-sink be supported in the future by mmx-cpu-plotter?

[madMAx43v3r]

yes

[aramod]

Thanks for what you do! You are a great person and will remain in history forever.

[madMAx43v3r]

Now available here: https://github.com/madMAx43v3r/chia-gigahorse

[aramod]

Dear friend, -d @hostname does not work again in the new version.
The readme also does not specify the additional parameter -d, as for cuda-plotter
cpu-plotter - (-d, --finaldir arg Final directory to copy plot in parallel (default =tmpdir))
cuda-plotter - ( -d, --finaldir arg Final destinations (default = tmpdir, remote = @host))

[madMAx43v3r]

yes need to update readme, -d @HOSTNAME is need to make it work

[aramod]

The problem was in powershell for windows. Need extra quotes " " "@hostname". Everything works fine for CMD

[aramod]

After the task is ready, I get error 10093
Copy to *.plot failed with: socket() failed with: 10093
What could be the problem? Tried on different machines
My task
./chia_plot -n -1 -k 32 -C 6 -x 11337 -r 31 -K 1 -u 256 -v 256 -t A:\ -d @hostname -f ... -p ...

[aramod]

Internet search turned up that this is related to WSAStartup

WSANOTINITIALISED10093	Successful WSAStartup not yet performed.Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.

WSANOTINITIALISED 10093 Successful WSAStartup not yet performed. Either the application has not called [WSAStartup](https://learn.microsoft.com/en-us/windows/desktop/api/winsock/nf-winsock-wsastartup) or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or [WSACleanup](https://learn.microsoft.com/en-us/windows/desktop/api/winsock/nf-winsock-wsacleanup) has been called too many times.

https://learn.microsoft.com/en-US/windows/win32/winsock/windows-sockets-error-codes-2

[madMAx43v3r]

oh yes, I forgot something...