A (long awaited) SSE App for Windows can be found on the Power User's Apps page.
It will badly crash on non-SSE machines.
With the larger variety of Apps it had gotten harder to write an app_info.xml that satisfies everyone's needs. The one in this package should allow smooth migration for tasks assigned to App versions 4.15, 4.25 and 4.26. You may want to take a look into the file before installing the App (i.e. restarting the client).
This App was built using VS2003 to avoid the serious performance-hitting bug of VS2005 ("store forwarding stall"). Unfortunately the Windows runtime debugger doesn't work there, so in case of computation errors there are fewer chances to find out what went wrong.
Only run this if you're sure of what you're doing
The App will probably have some CPU vendor detection linked into it (as the 4.26 has), but my guess is that the linear sin/cos code that we're using now isn't affected by this noticeably, so there should be no "penalty" for AMD users. Please try to prove me wrong!
Happy crunching!
BM
BM

Windows S5R3 "power users" App 4.32 available
)
Hey, not that fast - I was still typing...
BM
BM
RE: RE: Hey, not that
)
Well, actually you were right. However, an indication that I'm still working on publishing a new app is that the "thread" link on the page still points to the "dummy thread".
That's good news, thank you!
BM
BM
I should point out that I had
)
I should point out that I had a lot of help from Bikeman on this App. I wouldn't say that it were impossible without him, but it had taken me much, much longer.
BM
BM
RE: RE: Strange, 4.32 is
)
Nope. The client might try to find App version 4.32 because it finds tasks it had already assigned that version. Are you sure you never had installed a 4.32 App previously?
BM
BM
RE: I noticed the
)
This looks like the graphics program doesn't get any progress information from the main program.
In stderr of your results there are lines like:
This means that from the side of the main application all is working well.
Could you try to use the graphics App from 4.26? Either rename the version number to 4.32 or replace the entry in the app_info.xml.
BM
BM
RE: Got an other one that
)
If it's really related to network problems, a client with "asynchonous DNS" could fix it. I think it's currently only in development versions, though.
BM
BM
RE: ... and I am very happy
)
Well, then you probably don't want to try 4.36.
BM
BM