A new Windows App is available from our Beta Test Page.
This App combines the Apps previously known as 4.26 and 4.36 (SSE) (see Power User's Apps page) with the App-switching mechanism we already use on Linux and MacOS PPC, and this Beta test is mainly to test this switcher. In contrast to the Linux and MacOS implementation on Windows the switcher will keep running as a separate process, i.e. you should see two einstein_4.46_* processes running in the Task Manager per running Einstein@home Task.
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 contains the following tags and should allow smooth migration for tasks assigned to these versions:
415
425
426
432
436
You should take a look into the file before installing the App (i.e. restarting the client) if your version is not listed here.
The graphics_app link in the slot directory is not updated, i.e. after installing this App the "Show Graphics" button doesn't work for tasks that were already run with an older App version. This is a known issue for switching App versions in the middle of a task which is actually not supported by BOINC.
Happy testing!
BM
BM

Windows S5R3 App 4.46 available for Beta Test
)
Thanks for spotting & reporting this!
Yes, that's a serious problem; I already fixed this in the code and will build a new App soon. Following a suggestion from Rom Walton the next App will also have latest BOINC code to work better with the latest Core Clients.
We (actually Oliver) is currently working on refurbishing the graphics code, this will hopefully fix the graphics display problems, too (and use way less CPU for the graphics process than the current App does).
BM
BM
For some reason I still need
)
For some reason I still need to find out the switcher does work with the Apps in the 4.46 package, but not with Apps compiled from latest code (might be a BOINC issue).
For the time being I updated the 4.46 package (and the Beta page) with a new switcher that should properly hand down the priority class.
Please download the 4.46 (again if you already did) and try it.
BM
BM
RE: APP DEBUG: Application
)
This is a floating point exception (FPE).
I don't see this on Windows very often, it's much more common on Linux due to the "lazy FPU restore" on certain kernels.
As for Windows I've read some reports where some badly programmed hardware drivers (typically printer drivers) leave the FPU stack in a bad state, which would cause such an exception.
What version of Windows are you running?
BM
BM