I still have my old PWS running, or limping along. I just got a new station and thought I'd jump right in with MX. I've not yet tinkered with a Pi but would love to take a crack at it as time allows, but for now I'm under Win7. From what I've read, any customization should port (as long as one deals with DOS ASCII vs Unix I imagine...)

As far as I can tell, anyone who is a registered forum user should be able to see the attachment in the announcement, without actually needing to post a message. Some people are posting their first message having already installed MX, so that would seem to confirm that.

steve wrote:As far as I can tell, anyone who is a registered forum user should be able to see the attachment in the announcement, without actually needing to post a message. Some people are posting their first message having already installed MX, so that would seem to confirm that.

I think the most likely reason that people can't find the file is that fail to see the link at the end of the first post in the announcement topic. They get excited to download the file, but fail tofirst read the entire message as you suggest. (I know from experience because I did the same thing. )

Beta 3028 seems to be running well on my installation and I am away from the machine on the other side of the country right now.

Running on Windows Server 2012 R2 Essentials for the first time. The web page loads on port 8998, but no data values are displayed. This is the error on the command line. MXDiags text file is attached. BTW, I love your work. Thank you for years of enjoyment.

System.InvalidOperationException: Once the socket has been disconnected, you can only reconnect again asynchronously, and only to a different EndPoint. BeginConnect must be called on a thread that won't exit until the operation has been completed.

You do not have the required permissions to view the files attached to this post.

NorthSharon wrote:System.InvalidOperationException: Once the socket has been disconnected, you can only reconnect again asynchronously, and only to a different EndPoint. BeginConnect must be called on a thread that won't exit until the operation has been completed.

This is a known issue with using the 'periodic disconnect' facility on Windows, to be fixed in the next build.